[f-nsp] Support for tag-type on FESX?

[Peter Olsen]

You cannot set this on individual ports on fesx. It is set per 'port
region' 12 ports at the time.
At least older sw even have a bug on this and either the entire box runs
8100 or 9100 or xxxx.

Haven't been playing with it for some time so I'am not sure if it have
been fixed in newer releases.
I guess that this also explains why the sh tag-type do not work :-)



Med venlig hilsen/Best regards

Peter Olsen
CTO
D: +45 7730 3122
M: +45 2726 3122

-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net
[mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of Stephen Wilcox
Sent: 17. marts 2010 21:59
To: foundry-nsp at puck.nether.net
Subject: [f-nsp] Support for tag-type on FESX?

Hi,
 setting up something like below:

<customer tagged port with VLANs>----tagged 0x8100----[FESX]----tagged
0x9100----[FESX] ----tagged 0x8100----<customer tagged port with
VLANs>

note there is no untagged/tagged mismatching so we are not trying to
do qinq with the customer vlans.

The above works for other Foundry platforms just fine, for FESX tho it
seems to put 0x8100 onto the wire in the middle, which, doesn't work.

Does the FESX not support having different ports with different
tag-types?

(Of course, the tag-type is per dma, so the ports are allocated to
ensure they are using the different tag-types)

Has anyone tried this or have it working?

I'm also a little concerned that the 'sh tag-type' command doesn't
work. These are all documented as being features.

Cheers
Steve
_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp