[j-nsp] Cross Platform VPLS Multihoming

[Rodny Molina Maldonado]

Sebastien, this is a known issue that we're currently working on to have
it fixed asap. And no, you can't ignore the site-preference values being
exchanged, that would go against the l2vpn/vpls path-selection rules. What
you can do though, is to set your designated-forwarder (DF) with the
maximum site-preference value '65535' (0xFFFF), so that this endianness
encoding issue doesn't impact the DF election process.

/Rodny

On 4/6/12 7:57 AM, "Sebastien MALHEIRO" <Sebastien.MALHEIRO at bullpi.com>
wrote:

>Hi,
>
>Does anyone has ever configured a VPLS multihoming instance between a M
>and a MX (same JunOS or not) ?
>We tried to do this in a Lab and we encountered some weird results, the
>site-preference configured locally on each router is not normally
>announced / received in L2VPN routes.
>
>For Example :
>For site-preference 200 configured on the MX the M will see the L2VPN
>route with site-preference 51200
>Fir site-preference 400 configured on the M the MX will see the L2VPN
>route with site-preference 36865
>
>It's like that the 2Bytes VPLS-PREFERENCE attribute is not handle the
>same way between each routers :
>SP 100 is in binary equal to 1100100 ==> but routers see the 2 Bytes
>value of 01100100 00000000 = 25600
>SP 200 is in binary equal to 110010000 --> but routers see the 2 Bytes
>value of 1001000000000001 = 36865
>
>Between two M or two MX routers the site-preference received is the same
>as the one configured.
>
>Another question, is it possible to rewrite or to ignore the
>VPLS-PREFERENCE attribute in L2VPN announcements ?
>
>
>Thanks.
>
>Sébastien
>
>_______________________________________________
>juniper-nsp mailing list juniper-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp