C
ONFIGURING
IEEE 802.1Q T
UNNELING
12-21
4. After successful source and destination lookup, the packet is double
tagged. The switch uses the TPID of 0x8100 to indicate that an
incoming packet is double-tagged. If the outer tag of an incoming
double-tagged packet is equal to the port TPID and the inner tag is
0x8100, it is treated as a double-tagged packet. If a single-tagged packet
has 0x8100 as its TPID, and port TPID is not 0x8100, a new VLAN
tag is added and it is also treated as double-tagged packet.
5. If the destination address lookup fails, the packet is sent to all member
ports of the outer tag's VLAN.
6. After packet classification, the packet is written to memory for
processing as a single-tagged or double-tagged packet.
7. The switch sends the packet to the proper egress port.
8. If the egress port is an untagged member of the SPVLAN, the outer
tag will be stripped. If it is a tagged member, the outgoing packet will
have two tags.
Configuration Limitations for QinQ
• The native VLAN of uplink ports should not be used as the SPVLAN.
If the SPVLAN is the uplink port's native VLAN, the uplink port must
be an untagged member of the SPVLAN. Then the outer SPVLAN tag
will be stripped when the packets are sent out. Another reason is that it
causes none-customer packets will be forwarded to SPVLAN.
• Static trunk port groups are compatible with QinQ tunnel ports as long
as the QinQ configuration is consistent within a trunk port group.
• QinQ and L2MPLS mode cannot be supported at the same time.
• The native VLAN (VLAN 1) is not normally added to transmitted
frames. Avoiding using VLAN 1 as an SPVLAN tag for customer traffic
to reduce the risk of misconfiguration. Instead, use VLAN 1 as a
management VLAN instead of a data VLAN in the service provider
network.
• There are some inherent incompatibilities between Layer 2 and Layer 3
switching:
- A tunnel port cannot be a routed port.
Summary of Contents for 7824M/FSW - annexe 1
Page 2: ......
Page 24: ...TABLE OF CONTENTS xxiv ...
Page 28: ...TABLES xxviii ...
Page 32: ...FIGURES xxxii Figure 16 3 DNS Cache 16 7 ...
Page 34: ...GETTING STARTED ...
Page 46: ...SYSTEM DEFAULTS 1 12 ...
Page 62: ...SWITCH MANAGEMENT ...
Page 74: ...CONFIGURING THE SWITCH 3 12 ...
Page 112: ...BASIC MANAGEMENT TASKS 4 38 ...
Page 168: ...USER AUTHENTICATION 6 30 ...
Page 223: ...SHOWING PORT STATISTICS 9 33 Figure 9 12 Port Statistics ...
Page 230: ...ADDRESS TABLE SETTINGS 10 6 ...
Page 304: ...CLASS OF SERVICE 13 16 ...
Page 316: ...QUALITY OF SERVICE 14 12 ...
Page 338: ...MULTICAST FILTERING 15 22 ...
Page 346: ...DOMAIN NAME SERVICE 16 8 ...
Page 348: ...COMMAND LINE INTERFACE IP Interface Commands 35 1 ...
Page 362: ...OVERVIEW OF COMMAND LINE INTERFACE 17 14 ...
Page 494: ...USER AUTHENTICATION COMMANDS 21 48 ...
Page 514: ...CLIENT SECURITY COMMANDS 22 20 ...
Page 540: ...ACCESS CONTROL LIST COMMANDS 23 26 ...
Page 558: ...INTERFACE COMMANDS 24 18 ...
Page 576: ...MIRROR PORT COMMANDS 26 4 ...
Page 582: ...RATE LIMIT COMMANDS 27 6 ...
Page 616: ...SPANNING TREE COMMANDS 29 28 ...
Page 644: ...VLAN COMMANDS 30 28 ...
Page 664: ...CLASS OF SERVICE COMMANDS 31 20 ...
Page 678: ...QUALITY OF SERVICE COMMANDS 32 14 ...
Page 720: ...APPENDICES ...
Page 726: ...SOFTWARE SPECIFICATIONS A 6 ...
Page 730: ...TROUBLESHOOTING B 4 ...
Page 746: ...INDEX Index 6 ...
Page 747: ......