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

[Rolf Hanßen]

Hi,

if I understand correctly you want your customer to have tagged vlans on
the port to you and use only one vlan-id on your equipment for
transporting the data.

That works if you switch 8100 and 9100 in your example.
The port directed to the customer must have set the "wrong" type, the
internal link between your devices keeps set to 8100.

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

best regards
Rolf

> 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
>