[j-nsp] Interprovider MPLS VPN

[Jonathan Tse]

Hi Andrew,

I was trying option b and didn't notice 5.0 is not supporting. It can take
all the option b configuration just that it is not working perfectly. Thanks
for your reply. This really solves my puzzle.

Jonathan.

----- Original Message -----
From: "Andrew Ramsey" <akramsey@juniper.net>
To: "Jonathan Tse" <jonathantse@pacific.net.sg>;
<juniper-nsp@puck.nether.net>
Sent: Thursday, December 12, 2002 10:47 AM
Subject: RE: [j-nsp] Interprovider MPLS VPN


> Hi Jonathan,
>
> 5.1 added support for the PE-ASBR function for Interprovider VPN option b
and option c, as described in section 10 of IETF draft,
draft-ietf-ppvpn-rfc2547bis-03.txt.  Before that option b and c were not
supported.
>
> What are you trying to do?
>
> Andy
>
> >-----Original Message-----
> >From: Jonathan Tse [mailto:jonathantse@pacific.net.sg]
> >Sent: Wednesday, December 11, 2002 8:10 PM
> >To: juniper-nsp@puck.nether.net
> >Subject: [j-nsp] Interprovider MPLS VPN
> >
> >
> >Hi,
> >
> >Below lines are copied from the Release 5.1 Features of JUNOS
> >5.1 Internet
> >Router Release Notes.
> >
> >"Interprovider VPNs with multihop EBGP--Allows exchange of VPN
> >NLRI carrying
> >labels across autonomous system (AS) boundaries using EBGP. The feature
> >enables a Layer 3 VPN network to span multiple ASs."
> >
> >Does it mean 5.0 is not able to do so? We have a production
> >box running on
> >5.0R1.4 and seems it can't install the inet-vpn routes to mpls.0
> >
> >Thanks!
> >
> >Jonathan Tse,
> >Senior Network Engineer, Pacific Internet Singapore,
> >NOC: 65-8721010, DID: 65-7710843, FAX: 65-8726674
> >
> >_______________________________________________
> >juniper-nsp mailing list juniper-nsp@puck.nether.net
> >http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>