Cisco Cisco Web Security Appliance S680 Guía Del Usuario
2-25
Cisco AsyncOS 8.0.6 for Web User Guide
Chapter 2 Connect, Install, and Configure
Using the P2 Data Interface for Web Proxy Data
Figure 2-1
Using VLANs to Increase the Number of Networks Available on the Appliance
VLANs appear as dynamic “Data Ports” labeled in the format of: “VLAN DDDD” where the “DDDD”
is the ID and is an integer up to 4 digits long (VLAN 2, or VLAN 4094 for example). AsyncOS supports
up to 30 VLANs.
is the ID and is an integer up to 4 digits long (VLAN 2, or VLAN 4094 for example). AsyncOS supports
up to 30 VLANs.
A physical port does not need an IP address configured in order to be in a VLAN. The physical port on
which a VLAN is created can have an IP that will receive non-VLAN traffic, so you can have both VLAN
and non-VLAN traffic on the same interface.
which a VLAN is created can have an IP that will receive non-VLAN traffic, so you can have both VLAN
and non-VLAN traffic on the same interface.
VLANs can only be created on the Management and P1 data ports.
Configuring and Managing VLANs
You can create, edit and delete VLANs via the
etherconfig
command. Once created, a VLAN can be
configured via the
interfaceconfig
command in the CLI.
Example 1: Creating a New VLAN
In this example, two VLANs are created (named VLAN 31 and VLAN 34) on the P1 port:
Step 1
Do not create VLANs on the T1 or T2 interfaces.Access the CLI.
NOC
DMZ
VLAN
“Router”
VLAN1
VLAN3
VLAN2
Cisco appliance configured for VLAN1,
VLAN2, and VLAN3
VLAN2, and VLAN3