VLAN Management
Regular VLANs
Cisco 350, 350X and 550X Series Managed Switches, Firmware Release 2.4, ver 0.4 235
12
IPv4/IPv6 forwarding and VLAN tunneling are mutually exclusive. Meaning that if either
IPv4 or IPv6 forwarding are enabled, an interface cannot be set to VLAN tunneling mode.
And if any interface is set to VLAN tunneling mode, IPv4 and IPv6 forwarding cannot be
enabled on that device.
The following features are also mutually exclusive with the VLAN tunneling feature:
• Auto Voice VLAN
• Auto Smartport
• Voice VLAN
IPv4 and IPv6 interfaces cannot be defined on VLANs containing edge interfaces.
The following Layer 2 features are not supported on VLANs containing edge interfaces:
• IGMP/MLD snooping
• DHCP Snooping
• IPv6 First Hop Security
The following protocols cannot be enabled on edge interfaces (UNI - user network interfaces):
• STP
• GVRP
The following features are not supported on edge interfaces (UNI - user network interfaces):
• RADIUS VLAN assignment
• 802.1x VLAN
• SPAN/RSPAN – As a destination port with the network keyword or as a reflector port
destination port with the network keyword or reflector port.
Applying VLAN tunneling on an interface requires the use of router TCAM rules. If there is
not a sufficient number of router TCAM resources, the command will fail. Users can add/
remove router TCAM resources allocation for VLAN tunneling (and mapping) purposes via
the Administration---> Routing Resources (this requires a system reboot).
The original QinQ implementation (customer mode-related commands) continues to exist
alongside the new implementation of VLAN tunneling. The customer port mode is a particular
case of VLAN-mapping tunnel port mode, and does not require allocation of TCAM
resources.
To Next Page
Loading...
Need help?
General
