[f-nsp] Port-region on MLX and CER/CES

[Greg]

Thank you both for your replies. For the sake of clarity what do you mean
by "The only limitation that I see at a quick glance on the manual is when
doing Provider (Backbone) Bridging you cannot specify different tag-types
for BVLAN, CVLAN & SVLAN on MLX"?

My understanding...

C-VLAN -> Customer VLAN's 802.1q (aka regular VLAN tagged/untagged)
S-VLAN -> Provider VLAN's 802.1ad (aka VLAN to carry a regular VLAN as
above)
B-VLAN -> Backbone VLAN's 802.1ah (aka carry a Q-in-Q in yet another VLAN?)

Thanks!

Greg

2012/8/20 Niels Bakker <niels=foundry-nsp at bakker.net>

> * greg at dotkom.ch (Greg) [Mon 20 Aug 2012, 19:27 CEST]:
>
>> I am trying to figure out the hardware port-regions on both Brocade MLX4
>> and Brocade NetIron CER/CES. The purpose is to set multiple Q-in-Q
>> point-to-point Layer-2 connectivity toward different locations, but also
>> use BGP capabilities.
>>
>> On NI-MLX-1Gx20-SFP will tag-type affect all ports from 1 to 24? On
>> CER2024F and CES2024F, will the tag-type also affect all these ports? I
>> have not checked if its tag-type statement or another one.
>>
>
> "The Brocade device supports per port tag-type configuration." from the
> CES/CER/MLX/XMR/MLXe 5.2.0b configuration guide.  I know this holds true
> for 4x10G and 8x10G modules in MLX.
>
> The only limitation that I see at a quick glance on the manual is when
> doing Provider (Backbone) Bridging you cannot specify different tag-types
> for BVLAN, CVLAN & SVLAN on MLX while you can on CER
>
>
>         -- Niels.
>
> --
> ______________________________**_________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/**mailman/listinfo/foundry-nsp<http://puck.nether.net/mailman/listinfo/foundry-nsp>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20120821/6af4eb2c/attachment.html>