Changes between Version 6 and Version 7 of QinqResults


Ignore:
Timestamp:
12/20/10 15:25:14 (11 years ago)
Author:
jwilliams@bbn.com
Comment:

replaced 8a88 with 88a8

Legend:

Unmodified
Added
Removed
Modified
  • QinqResults

    v6 v7  
    2020|| none  || per protocol   || untagged frame || access port ||   IP = 0x800, ARP = 0x0806, etc  ||
    2121|| customer  || 0x8100 || tagged frame || 802.1q VLAN trunk port|| 802.1q VLAN tagging  ||
    22 || service || 0x8a88  || QinQ tagged frame || 802.1ad (QinQ) VLAN trunk port|| 8021.ad provider tunnel  ||
     22|| service || 0x88a8  || QinQ tagged frame || 802.1ad (QinQ) VLAN trunk port|| 8021.ad provider tunnel  ||
    2323
    2424For 802.1q VLANs and 802.ad QinQ VLANs the !EtherType is actually a "Tag Protocol Identifier (TPID)" that, along with other tagging information, is inserted after the frame's source MAC address field. As this TPID is at the same byte offset as the original !EtherType field, it is common to refer to this field as the !EtherType field when discussing VLANs. The image below illustrates this distinction. Each tag adds 4 Bytes of data to the Ethernet frame.
     
    127127=== QinQ Tagging ===
    128128'''Purpose'''[[BR]]
    129 Verify that a given DUT's QinQ port sends double-tagged QinQ frames in the expected format. For switches to understand that the trunking mechanism is a QinQ VLAN trunk the Ethernet's Header must contain the appropriate QinQ header field  type indication (0x8a88).
     129Verify that a given DUT's QinQ port sends double-tagged QinQ frames in the expected format. For switches to understand that the trunking mechanism is a QinQ VLAN trunk the Ethernet's Header must contain the appropriate QinQ header field  type indication (0x88a8).
    130130
    131131[[Image(source:/trunk/wikifiles/QinqResults/QinQTaggingTestOverview.jpg)]]
     
    135135
    136136 * HP: cvlans and svlans are used to distinguish port type. svlan trunk (QinQ) ports use the 0x88a8 value.
    137  * NEC: configures a QinQ trunk-port explicitly with the setting "switch dot1q ethertype 8a88" for a given port.
     137 * NEC: configures a QinQ trunk-port explicitly with the setting "switch dot1q ethertype 88a8" for a given port.
    138138 * CISCO: The access port for the QinQ portion needs configured for QinQ, the QinQ trunk (ES) port is configured with 0x88a8.
    139139
     
    385385[[Image(source:/trunk/wikifiles/QinqResults/NEC_VLAN128NoQinQ.jpg)]]
    386386
    387 VLAN 128 is capable of being sent out port 1, however it's tagged type is "0x8a88" (service VLAN), "not 0x8100" (customer VLAN). This implies that the Switch on the other side  of the trunk must be a service VLAN; sending the VLAN as a "normal" VLAN isn't possible in this configuration. This implies that A port is either dedicated for normal dot1q or qinq - but can't do both.
     387VLAN 128 is capable of being sent out port 1, however it's tagged type is "0x88a8" (service VLAN), "not 0x8100" (customer VLAN). This implies that the Switch on the other side  of the trunk must be a service VLAN; sending the VLAN as a "normal" VLAN isn't possible in this configuration. This implies that A port is either dedicated for normal dot1q or qinq - but can't do both.
    388388
    389389
     
    634634
    635635=== Customer VLAN Out QinQ Port ===
    636 VLAN 128 is capable of being sent out ES port 1, however it's tagged type is "0x8a88" (service VLAN), "not 0x8100" (customer VLAN). This implies that the Switch on the other side of the trunk must be a service VLAN; sending the VLAN as a "normal" VLAN isn't possible in this configuration. This is the same behavior as the NEC switch.
     636VLAN 128 is capable of being sent out ES port 1, however it's tagged type is "0x88a8" (service VLAN), "not 0x8100" (customer VLAN). This implies that the Switch on the other side of the trunk must be a service VLAN; sending the VLAN as a "normal" VLAN isn't possible in this configuration. This is the same behavior as the NEC switch.
    637637
    638638=== Same Inner and Outer VLAN Tags ===
     
    990990interface vlan [vlan id]        Select the vlan to configure.  The only (useful) thing I've found is the ability to associate a VLAN with an IP address and THAT was only useful to define the HOME interface of the device...
    991991media [rj45/sfp]        While configuring an interface.  Ports 1-4 are dual-option, RJ-45 is ethernet, SFP is the fiber port.  One or the other is enabled...
    992 switch dot1q ethertype 8a88     Switches the ethertype announced between 802/1ad (“tunnel”) and 802.1q mode on this interface.
     992switch dot1q ethertype 88a8     Switches the ethertype announced between 802/1ad (“tunnel”) and 802.1q mode on this interface.
    993993}}}
    994994