can you share the configuration?
Thx
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Hi,
The RR needs routes to all its clients in the inet.3 table, otherwise the RR
will not advertise inet-vpn routes to its clients.
If you do not want receive those routes via LDP/RSVP, then you can always do a
static route on the RR. This will never be used for forwarding, just route
reflecti
Hi Diogo/Doug
Thanks for all the pointers. I will get back to you with the outputs
and further investigations.
By the way if you have time I have posted another stange issue for
OSPF in MPLS VPN as PE-CE for my another customer.
If you can see through it and suggest any pointers.Title is "Strang
Hi,
I don't think this is the problem because your issue is in the
control-plane between PE4 and PE2. First of all, you need identify why
the routes sent by PE2 are not arriving at PE4.
If your config is correct, you need enable some traceoptions in the
bgp session between pe2 and pe4 to investi
Traceoptions enabled under BGP will tell you exactly what's happening to
the prefix when being received.
On 7/11/12 9:19 AM, "vaibhava varma" wrote:
>Hi Diogo
>
>Yes the RR Config is fine and the BGP neighbours are negotiated for
>inet-vpn. RT I did verify earlier and was correct.
>
>Unfortuan
Hi Diogo
Yes the RR Config is fine and the BGP neighbours are negotiated for
inet-vpn. RT I did verify earlier and was correct.
Unfortuantely I do not have the access right now but I will surely get
you the configs and outputs tomorrow morning.
COming back to the LSP between the PE and the RR, a
Hi,
Based on this, I would check the bgp configuration between pe2 and
pe4, and the RR configuration as well on PE2. Check if the inet-vpn
family is negotiated between both neighbors. If the BGP config looks
fine, then it points to rtarget.
The LSP (LDP or RSVP) between PE and RR is required to a
Hi Diogo
> - verify the status of the routes in PE4. Are they being received by
> the BGP neighbor ? Check the protocol NH status.
Routes are not received by BGP neighbour and I verified this "show
route receive-protcol bgp x.x.x.x(PE2/RR)
>
> - you need to have an LSP between the PE1 and your R
Hi,
I suggest some steps below:
- verify the status of the routes in PE4. Are they being received by
the BGP neighbor ? Check the protocol NH status.
- you need to have an LSP between the PE1 and your RR. Same for PE4
and RR. But I am assuming this is fine because you see the routes
being advert
Hi Diogo
They are not hidden and have already verified the route-target.Its
correctly configured. Any other pointer ?
Also while using RR do we reallly need the Loopback IP of RR used for
BGP peering to be present in the inet.3 table of PE coz the RR just
reflects the route and does not modifies
You need check the status of the routes in PE4. If they are hidden it
may be a LDP issue. If there is no hidden route then your problem may
be wrong route-target selection.
Thanks
On 7/11/12, vaibhava varma wrote:
> Hi Diogo
>
> I have not checked that yet but what I did check was that PE2/RR is
Hi Diogo
I have not checked that yet but what I did check was that PE2/RR is
advertising the route via BGP to PE4 and PE4 is not accepting it.
Right now I do not have access to the setup.
Please suggest where can be the issue and what more to check apart
from the one you mentioned and I will chec
Dear All
I was testing a setup whereby I am using mix of LDP and RSVP in the
backbone for transporting MPLS VPN Traffic. The setup is something as
below:
CE1--PE1--PE2/RR---PE3PE4--CE2
Now we have a limitation that we can only run LDP between PE4 and PE3.
>From PE3 to PE2/RR we h
13 matches
Mail list logo
