[f-nsp] running vpls with multiple vlans on CES2000

[Dunc]

Hiya Igor,

I've had exactly this problem, it was on MLXes, but I believe they work
similarly. The code I was using at the time didn't support vc-mode
tagged, but we've since upgraded, and when I tried it, it didn't seem to
make any difference.

I haven't had time to lab it any more since, but would be interested to
hear if anyone else has had success from tagged-mode, because the docs
indicate it should work, but like I say seemed to have no effect for me.

I too have solved it by using 2 VPLSes for now.


Cheers,

Dunc


On 02/08/11 19:10, Igor Ybema wrote:
> Hi there,
>
> Today I was trying create a VPLS between some CES2000's holding more
> than one vlan so that I could transport two vlan's from the same
> customer over one vpls:
>
> router mpls
>    vpls test 10
>    vpls-peer some-ip-address
>      vlan 100
>        tag e 1/1
>      vlan 200
>       tag e 1/1
>
>
>
> The config would let me do this (instead of with a VLL, which blocks
> when you enter more than one vlan).
> However, when I connected a normal vlan switch on the e1/1, I noticed
> that the mac-addresses from vlan 100 where flooded over vlan 200 and
> vice versa.
>
> Is this indeed not possible? Was I just creating a vlan-translation
> thing? The document is very unclear about this.
> What if I had a MLX/XMR and would do the same with 'vc-mode tagged'
> enabled within the vpls? Would that work?
>
> I fixed my problem by creating two VPLS instances each with one vlan.
>
> regards, Igor Ybema
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
________________________________
 This email and any attachments it may contain is confidential and solely intended for the use of the named addressee(s) only. Any views or opinions presented are solely those of the author and do not necessarily represent those of The Bunker. If you are not the intended recipient, be advised that you have received this email in error and that you should not rely on it or take any action based on it. You should not publish, use, disseminate, print, forward or copy this email as it is strictly prohibited. Please contact the sender if you have received this email in error and destroy it.