Cisco Systems 3130 User Manual
16-6
Cisco Catalyst Blade Switch 3130 for Dell Software Configuration Guide
OL-13270-01
Chapter 16 Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
Configuring IEEE 802.1Q Tunneling
IEEE 802.1Q Tunneling and Other Features
Although IEEE 802.1Q tunneling works well for Layer 2 packet switching, there are incompatibilities
between some Layer 2 features and Layer 3 switching.
between some Layer 2 features and Layer 3 switching.
•
A tunnel port cannot be a routed port.
•
IP routing is not supported on a VLAN that includes IEEE 802.1Q ports. Packets received from a
tunnel port are forwarded based only on Layer 2 information. If routing is enabled on a switch
virtual interface (SVI) that includes tunnel ports, untagged IP packets received from the tunnel port
are recognized and routed by the switch. Customer can access the internet through its native VLAN.
If this access is not needed, you should not configure SVIs on VLANs that include tunnel ports.
tunnel port are forwarded based only on Layer 2 information. If routing is enabled on a switch
virtual interface (SVI) that includes tunnel ports, untagged IP packets received from the tunnel port
are recognized and routed by the switch. Customer can access the internet through its native VLAN.
If this access is not needed, you should not configure SVIs on VLANs that include tunnel ports.
•
Fallback bridging is not supported on tunnel ports. Because all IEEE 802.1Q-tagged packets
received from a tunnel port are treated as non-IP packets, if fallback bridging is enabled on VLANs
that have tunnel ports configured, IP packets would be improperly bridged across VLANs.
Therefore, you must not enable fallback bridging on VLANs with tunnel ports.
received from a tunnel port are treated as non-IP packets, if fallback bridging is enabled on VLANs
that have tunnel ports configured, IP packets would be improperly bridged across VLANs.
Therefore, you must not enable fallback bridging on VLANs with tunnel ports.
•
Tunnel ports do not support IP access control lists (ACLs).
•
Layer 3 quality of service (QoS) ACLs and other QoS features related to Layer 3 information are
not supported on tunnel ports. MAC-based QoS is supported on tunnel ports.
not supported on tunnel ports. MAC-based QoS is supported on tunnel ports.
•
EtherChannel port groups are compatible with tunnel ports as long as the IEEE 802.1Q
configuration is consistent within an EtherChannel port group.
configuration is consistent within an EtherChannel port group.
•
Port Aggregation Protocol (PAgP), Link Aggregation Control Protocol (LACP), and UniDirectional
Link Detection (UDLD) are supported on IEEE 802.1Q tunnel ports.
Link Detection (UDLD) are supported on IEEE 802.1Q tunnel ports.
•
Dynamic Trunking Protocol (DTP) is not compatible with IEEE 802.1Q tunneling because you must
manually configure asymmetric links with tunnel ports and trunk ports.
manually configure asymmetric links with tunnel ports and trunk ports.
•
VLAN Trunking Protocol (VTP) does not work between devices that are connected by an
asymmetrical link or devices that communicate through a tunnel.
asymmetrical link or devices that communicate through a tunnel.
•
Loopback detection is supported on IEEE 802.1Q tunnel ports.
•
When a port is configured as an IEEE 802.1Q tunnel port, spanning-tree bridge protocol data unit
(BPDU) filtering is automatically enabled on the interface. Cisco Discovery Protocol (CDP) and the
Layer Link Discovery Protocol (LLDP) are automatically disabled on the interface.
(BPDU) filtering is automatically enabled on the interface. Cisco Discovery Protocol (CDP) and the
Layer Link Discovery Protocol (LLDP) are automatically disabled on the interface.
Configuring an IEEE 802.1Q Tunneling Port
Beginning in privileged EXEC mode, follow these steps to configure a port as an IEEE 802.1Q tunnel
port:
port:
Command
Purpose
Step 1
configure terminal
Enter global configuration mode.
Step 2
interface interface-id
Enter interface configuration mode for the interface to be configured as a
tunnel port. This should be the edge port in the service-provider network
that connects to the customer switch. Valid interfaces include physical
interfaces and port-channel logical interfaces (port channels 1 to 48).
tunnel port. This should be the edge port in the service-provider network
that connects to the customer switch. Valid interfaces include physical
interfaces and port-channel logical interfaces (port channels 1 to 48).
Step 3
switchport access vlan vlan-id
Specify the default VLAN, which is used if the interface stops trunking.
This VLAN ID is specific to the particular customer.
This VLAN ID is specific to the particular customer.
Step 4
switchport mode dot1q-tunnel
Set the interface as an IEEE 802.1Q tunnel port.