[j-nsp] IOS JUNOS MPLS-TE interoperability

alaerte vidali alaertevidali at gmail.com
Fri Jun 6 16:03:12 EDT 2008


Hello Rubens,

I have used Cisco 7600, XR 12410 and Juniper 9.x TE. Works fine.
Remember that what Cisco call fast reroute is not the same Juniper calls
fastreroute.

Good Luck,
Alaerte

>
>
>
> Today's Topics:
>
>   1. IOS JUNOS MPLS-TE interoperability (Rubens Kuhl Jr.)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 4 Jun 2008 21:40:40 -0300
> From: "Rubens Kuhl Jr." <rubensk at gmail.com>
> Subject: [j-nsp] IOS JUNOS MPLS-TE interoperability
> To: "cisco-nsp at puck.nether.net" <cisco-nsp at puck.nether.net>,
>        "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net>
> Message-ID:
>        <6bb5f5b10806041740h75fdef4alea50ebd7c9b51a2d at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> Does anyone has experience with MPLS-TE interoperability between IOS
> (specifically ME6500, but it's probably like any other 12.2SX IOS) and
> JUNOS (recent/stable/good-for-service-providers version) ?
>
> I was wondering about 2 cenarios in particular:
> 1) JUNOS as head-end or tail-end, but not middle-point
> 2) JUNOS as head-end, tail-end and middel-point
>
> All routers would be in the same OSPF area 0, within the same AS #; TE
> is done by explicit naming of both primary, secondary paths, and a
> dynamic backup path. AUTOBW is desired. On IOS, traffic is injected on
> the tunnel using static route to the loopback address; OSPF contains
> only link states and loopbacks, directly-connected, customer static
> routes or customer dynamic routes are propagated via IBGP.
>
>
> Tks,
> Rubens
>
>
> ------------------------------
>


More information about the juniper-nsp mailing list