VLANs
Supported VLANs
Supported VLANs: 1-4094
Optional parameters:
To verify:
Normal Range vs Extended Range
Normal Range VLANs: 1-1005* – Supported by VTP v1,v2,v3 in all modes.
Extended Range VLANs: 1006-4094 – Only supported in Transparent mode by VTPv1 and v2, and in all modes by VTP v3.
* Reserved VLANs: 1002-1005 (Token Ring and FDDI)
Port Modes
Static Access
2.1.1Access with static VLAN assignment
Default VLAN for all ports is VLAN 1.To change it, use:
Access with dynamic VLAN assignment
This configuration requires a VMPS Server (VLAN Management Policy Server).
Static Trunk
First, Define the encapsulation type:
To configure the port as a static Trunk port, use:
Native VLANs
On 802.1q trunks, frames in the native vlan are sent untagged. To set the native vlan, use:
Allowed VLANs
By default, all VLANs are allowed on a trunk. To limit the VLANs that can travel over a trunk link, use:
Dynamic
A port configure in dynamic mode, will become either an access or a trunk port, depending on the negotiation with the other pot it is connected to. DTP is used to negotiate Dynamic Trunks. To configure a port as dynamic, use the following command:
Here’s how the ports will end up in a dynamic configuration:
This side\The other side | Access | Trunk | Dynamic Auto | Dynamic Desirable |
---|---|---|---|---|
Access | access\access | access\trunk | acces\access | access\access |
Trunk | trunk\access | trunk\trunk | trunk\trunk | trunk\trunk |
Dynamic Auto | access\access | trunk\trunk | access\access | trunk\trunk |
Dynamic Desirable | access\access | trunk\trunk | trunk\trunk | trunk\trunk |
DTP works by default, even if the port is configured as a static trunk. This is needed so that the other end of the connection could negotiate to become a trunk. DTP is disabled if the port is set in the acccess mode or if the following command is used:
This is usually used when a static trunk is created with a neighbor that does not support DTP (like a router or a firewall). DTP negociation will fail if the devices are in different VTP domains.
Private VLAN
See Private VLANs
Dot1Q Tunnels (Q-in-Q Tunnels)
Q-in-Q tunnels are used to carry frames tagged with 802.1q by a customer over a provider’s network. Customer traffic is encapsulated within another 802.1q tag (metro tag) which is used inside the provider network. An asymmetric link must be configured, where the port on the customer switch will be set as Trunk port, and the port on the Provider switch will be set as Tunnel Port.
Configure the Customer Switch
To configure the customer switch, use:
Configure the Provider Switch
Since Q-in-Q tunnels add an additional dot1Q header, the MTU of the frames can reach 1504 Bytes. The switch will warn when a port is configured for dot1q tunneling that the default MTU of the switch (1500) should be changed. This change should be done on all provider switches:
To test that the provider network can accomodate such frames, you can try:
Native VLAN on Dot1q Tunnels
Since trunk belonging to the native VLAN is normally sent untagged, this could end up in problems inside the provider network. To prevent this use one of the following:
Use ISL encapsulation inside the provider network
Make sure the native VLAN on the customer/provider edge is not within the customer VLAN range.
Tag the native VLAN:
Tunneling L2 Protocols
Normally traffic for VTP, CDP, STP, PAgP, LACP, UDLD is not switched. It is interpreted by each device on a per-link basis. To enable L2 Protocl Tunneling, use the following config on the provider switch:
To tunnel protocols used over point-to-point connections, use the following command to emmulate such a connection:
The number of L2 packets that can be tunneled can be limited, using:
You can also configure the interface to shutdown if a threshold is violated:
To auto-recover from such an error, use:
To monitor,use:
Last updated