Thanks to the person who contacted me offlist -- I've been pointed to defect 377562, which I'm told is fixed on the FLS but not the ICX.
"Q-in-Q removes the original customer's tag for broadcast" Frank -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Frank Bulk - iName.com Sent: Friday, April 20, 2012 2:51 PM To: [email protected] Subject: [f-nsp] Preserving double-tagged traffic on ICX6100 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 _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
