@puck.nether.net
Asunto: RE: [j-nsp] Problem of Forwarding on VPN using vrf-table-label.
This is as all as per design.
http://www.juniper.net/techpubs/software/junos/junos95/swconfig-vpns/id-10978770.html
By default the route lookup action for l3vpn is performed on the vrf label.
This prevents IP L3
; Cristian Frizziero
CC: juniper-nsp@puck.nether.net
Asunto: RE: [j-nsp] Problem of Forwarding on VPN using vrf-table-label.
This is as all as per design.
http://www.juniper.net/techpubs/software/junos/junos95/swconfig-vpns/id-10978770.html
By default the route lookup action for l3vpn is performed
p.m.
Para: Ger, Javier; David Lockuan; Cristian Frizziero
CC: juniper-nsp@puck.nether.net
Asunto: RE: [j-nsp] Problem of Forwarding on VPN using vrf-table-label.
If I follow, by learning a route from the ce whether by static, ospf, bgp, etc,
the PE is able to bind that route to the CE next-hop
of Forwarding on VPN using vrf-table-label.
Hi Cristian,
It is correct, I had 2 PE with 2 VPN. Sorry I don't send the
configuration of both PE's. Just now I send you the both
configurations.
I noted that when I used the command vrf-table-label the next-hop
after the label lookup is to next-table
; Cristian Frizziero
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] Problem of Forwarding on VPN using vrf-table-label.
Dear community,
just to add some additional comments/questions about this topic.
We have 2 PE (logical systems) with 2 VRF belonging to same VPN (working with
AFI IPv4 and SAFI
Hi Cristian,
It is correct, I had 2 PE with 2 VPN. Sorry I don't send the
configuration of both PE's. Just now I send you the both
configurations.
I noted that when I used the command vrf-table-label the next-hop
after the label lookup is to next-table of the VPN and when I don't
used it the
Hy David!!!
I understand that the statement vpn-table-label allow PE to announce a
different label for every VPN route of a VRF. In this way, in the
forwarding plane we can avoid a lookup, which is very useful in the case
of multipoint interfaces, such as ETH. The point is that multipoint
Hi Cristian,
JUNOS does not send label per prefix. It is always one label per vrf.
vrf-table-label enables special handling for the packets destined to the vrf
w/ vrf-table-label enabled in the egress PE on its core facing PFEs (PE-P
link). It avoids the double lookups needed for multi-access
Ok Nilesh,
Thank you very much, I had a wrong concept in my head.
I think that David is working with a lab where he has 2 VPNs in PE1, and
there will be a second PE with VPN-A and VPN-B too.
The issue he is seeing is between the CEs of VPN-A connected to PE1 and PE2.
David, can you confirm
Hi guys,
I have been doing a lab with a MX960 with release 10.0R3.10, I set a
topology with logical-systems, in theory all it is working because I can see
the routes of VRF into table bgp.l3vpn.0 but the forwarding between the CE
is not working. This is the configuration of the routing-instance
10 matches
Mail list logo
