802.1Q Configuration Considerations; Default Layer 2 Ethernet Interface Vlan Configuration - Cisco Catalyst 3750 Software Configuration Manual

Metro switch
Hide thumbs Also See for Catalyst 3750:
Table of Contents

Advertisement

Chapter 10
Configuring VLANs

802.1Q Configuration Considerations

802.1Q trunks impose these limitations on the trunking strategy for a network:

Default Layer 2 Ethernet Interface VLAN Configuration

Table 10-6
Table 10-6 Default Layer 2 Ethernet Interface VLAN Configuration
Feature
Interface mode
Trunk encapsulation
802.1Q encapsulation ethertype value
Allowed VLAN range
VLAN range eligible for pruning
Default VLAN (for access ports)
Native VLAN (for 802.1Q trunks)
78-15870-01
In a network of Cisco switches connected through 802.1Q trunks, the switches maintain one instance
of spanning tree for each VLAN allowed on the trunks. Non-Cisco devices might support one
spanning-tree instance for all VLANs.
When you connect a Cisco switch to a non-Cisco device through an 802.1Q trunk, the Cisco switch
combines the spanning-tree instance of the VLAN of the trunk with the spanning-tree instance of
the non-Cisco 802.1Q switch. However, spanning-tree information for each VLAN is maintained by
Cisco switches separated by a cloud of non-Cisco 802.1Q switches. The non-Cisco 802.1Q cloud
separating the Cisco switches is treated as a single trunk link between the switches.
Make sure the native VLAN for an 802.1Q trunk is the same on both ends of the trunk link. If the
native VLAN on one end of the trunk is different from the native VLAN on the other end,
spanning-tree loops might result.
Disabling spanning tree on the native VLAN of an 802.1Q trunk without disabling spanning tree on
every VLAN in the network can potentially cause spanning-tree loops. We recommend that you
leave spanning tree enabled on the native VLAN of an 802.1Q trunk or disable spanning tree on
every VLAN in the network. Make sure your network is loop-free before disabling spanning tree.
On an ES port, you can use the switchport trunk dot1q ethertype value interface configuration
command to program a custom ethertype value for the interface. This feature allows the switch to
interoperate with third-party vendor switches that do not use the standard 0x8100 ethertype to
identify 802.1Q-tagged frames. For example, if you set 0x1234 as the custom 802.1Q ethertype on
a trunk port, incoming frames containing that ethertype are assigned to the VLAN contained in the
tag following the ethertype as they would be with a standard 802.1Q trunk. Frames arriving on a
trunk port with either the standard ethertype (0x8100) or the custom ethertype value are treated as
valid 802.1Q traffic; frames containing any other ethertype are assigned to the native VLAN of that
trunk.
shows the default Layer 2 Ethernet interface VLAN configuration.
Default Setting
switchport mode dynamic auto
switchport trunk encapsulation negotiate
0x8100
VLANs 1 to 4094
VLANs 2 to 1001
VLAN 1
VLAN 1
Catalyst 3750 Metro Switch Software Configuration Guide
Configuring VLAN Trunks
10-19

Advertisement

Table of Contents
loading

Table of Contents