Difference between revisions of "QinQ Cisco IOS"
From Teknologisk videncenter
m (→Hardware understøttelse) |
m (→Hardware understøttelse) |
||
Line 21: | Line 21: | ||
==Hardware understøttelse== | ==Hardware understøttelse== | ||
− | + | Hardware det virker på. | |
*ME-3400G-2CS-A(12.2(58)SE2 ME340x-METROIPACCESSK9-M) | *ME-3400G-2CS-A(12.2(58)SE2 ME340x-METROIPACCESSK9-M) | ||
*3550 | *3550 | ||
+ | *6500 | ||
+ | *7600 | ||
+ | *Nexus 7000 | ||
+ | *Nexus 5000 |
Revision as of 16:00, 11 January 2012
QinQ
For at aktivere VLAN tagging skriver man i global configuration[1]
vlan dot1q tag native
På interfacet definerer vi at alt trafik skal i vlan 130, men at den indre tag skal bibeholdes, og der skal klistres en ny på.
interface FastEthernet 0/0 switchport access vlan 103 switchport mode dot1q-tunnel
Begrænsninger
Configuring a port as an IEEE 802.1Q tunnel port has these limitations:
- IP routing and fallback bridging are not supported on tunnel ports.
- Tunnel ports do not support IP ACLs.
- If an IP ACL is applied to a trunk port in a VLAN that includes tunnel ports, or if a VLAN map is applied to a VLAN that includes tunnel ports, packets received from the tunnel port are treated as non-IP packets and are filtered with MAC access lists.
- Layer 3 quality of service (QoS) ACLs and other QoS features related to Layer 3 information are not supported on tunnel ports.
For more information about configuring IEEE 802.1Q tunnel ports, see the software configuration guide for this release.
Hardware understøttelse
Hardware det virker på.
- ME-3400G-2CS-A(12.2(58)SE2 ME340x-METROIPACCESSK9-M)
- 3550
- 6500
- 7600
- Nexus 7000
- Nexus 5000