[j-nsp] Juniper Foundry MPLS interoperability

David Ball davidtball at gmail.com
Wed May 1 12:30:48 EDT 2013

  I can't comment on your specific requirement, but I've done L2VPN
(Martini l2ckt, actually) and L3VPN between a Brocade MLX4 and Juniper MX
and T-series in the past.  Required a small amount of fiddling (if I recall
correctly, MLX couldn't support the consolidated RSVP message dump that
Junipers did, so I just disabled it on the Juniper side).  There were some
other issues with respect to the way the MLX handled QinQ (outer tag
required different ethertype) for some transparent services, but it
eventually worked.  This was all in a lab, though....where EVERYthing
works.  :)


On 20 June 2011 16:11, Armin Kask <Armin.Kask at energia.ee> wrote:

> Hi All,
> we have a network consisting of FESX/SuperX and CES/CER switches in a ring
> formation
> FESX/SuperX are used for L2 forwarding and CES/CER are also connected to
> the ring doing L2 and L2VPN on top.
> We have an idea to break up the large L2 domain kept together by MSTP with
> some MPLS routers so that the MSTP domains will be between any two routers.
> The routers will need to do something like MSTAG or mac flush on VPLS
> topology change.
> I was wondering if we could/should use MX-80 or 240 for this. I am pretty
> sure that simple L2 with MSTP will be interoperable between the vendors but
> I am not so sure about L2VPN and VPLS and L3VPN in the future.
> Can anybody comment on this
> *
> ------------------------------
> Käesolev kiri võib sisaldada konfidentsiaalset informatsiooni ja on
> mõeldud kasutamiseks ainult selle adressaadile. Kui antud sõnum ei ole
> suunatud Teile, siis selle avaldamine, kopeerimine, levitamine või muul
> viisil kasutamine on rangelt keelatud ning võib olla ebaseaduslik. Kui
> saite selle kirja ekslikult, palun teavitage sellest koheselt
> informatsiooni saatjat ning kustutage kiri oma süsteemidest.
> The information in this communication may be confidential and is intended
> solely for the use of the addressee. If you are not the intended recipient
> you are hereby notified that any use, disclosure, copying, distribution or
> taking any other action in reliance on the contents of this information is
> strictly prohibited and may be unlawful. If you received this e-mail in
> error, please contact the sender and delete the material from your systems.
> *
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

More information about the juniper-nsp mailing list