【CCNP 8-2】Introducing TRUNK.ppt

Customer traffic tagged in the normal way with appropriate VLAN IDs comes from an 802.1Q trunk port on the customer device and into a tunnel port on the service-provider edge switch. The link between the customer device and the edge switch is asymmetric because one end is configured as an 802.1Q trunk port, and the other end is configured as a tunnel port. You assign the tunnel port interface to an access VLAN ID that is unique to each customer. See Figure 16-1. Understanding 802.1Q Tunneling（QinQ） Understanding 802.1Q Tunneling（QinQ） Understanding 802.1Q Tunneling（QinQ） Packets coming from the customer trunk port into the tunnel port on the service-provider edge switch are normally 802.1Q-tagged with the appropriate VLAN ID. The the tagged packets remain intact inside the switch and when they exit the trunk port into the service-provider network, they are encapsulated with another layer of an 802.1Q tag (called the metro tag) that contains the VLAN ID that is unique to the customer. The original customer 802.1Q tag is preserved in the encapsulated packet. Therefore, packets entering the service-provider network are double-tagged, with the outer (metro) tag Understanding 802.1Q Tunneling（QinQ） containing the customer’s access VLAN ID, and the inner VLAN ID being that of the incoming traffic. When the double-tagged packet enters another trunk port in a service-provider core switch, the outer tag is stripped as the switch processes the packet. When the packet exits another trunk port on the same core switch, the same metro tag is again added to the packet. Figure 16-2 shows the tag structures of the double-tagged packets. Understanding 802.1Q Tunneling（QinQ） Configuring 802.1Q Tunneling（QinQ） Default 802.1Q Tunneling Configuration： By default, 802.1Q tunneling is disabled because the default switchport mode is dynamic auto. Tagging of 802.1Q native VLAN packets on all 802.1Q trunk ports is also disabled. 802.1Q Tunneling Configuration Guideli