[f-nsp] Preserving double-tagged traffic on ICX6100

Frank Bulk - iName.com frnkblk at iname.com
Fri Apr 20 15:50:57 EDT 2012


We're having difficulty moving double-tagged traffic through the ICX6100.
The inner tag (235) is being removed somewhere inside the Brocade because
packet captures from the Brocade's ingress port (tagged 1048) show two tags
while the Brocade's egress port (tagged 1048) shows one tag (captures
attached).  What's left is the outer tag (1048) with the contents of the
payload.

Both have tags have TPIDs of 0x8100.

Any reason why is this happening?  Why is the switch doing anything with the
inner tag?

Frank


begin 666 double-tagged.pcap
MU,.RH0(`! ```````````/__```!````MIB13ZIY`@!$````1 ```/______
M_P`5K0HZ7X$`!!B!``#K" 8``0@`!@0``0`5K0HZ7PH`B!8````````*`(@>
2````````````````````````
`
end

begin 666 single-tagged.pcap
MU,.RH0(`! ```````````/__```!````59:13PX%``! ````0 ```/______
M_P`5K0HZ7X$`!!@(!@`!" `&! `!`!6M"CI?"@"(%@````````H`B!X`````
.````````````````````
`
end



More information about the foundry-nsp mailing list