[j-nsp] Juniper MPLS VPN using PE-P and P-PE LSPs !
vaibhava varma
svaibhava at gmail.com
Mon Dec 26 09:37:12 EST 2011
HI Mark
Oh Yes what I mentioned for using LDP was without RSVP-TE at all..I
was trying to run RSVP-TE without using LDP at all..
With Ivan's suggestion I was enabled to get lables for the remote PE's
Loopback,,,
Thanks much to You and Ivan for your support on getting hold of this issue..
I finally summarize the network setup requirement to establish MPLS
VPN Traffic flow across Broken LSP as
1. Enable PE-P and P-PE RSVP TEs
2. Announce the RSVP-TEs into the IGP on PE and P routers
5. Import inet.0 routes to inet.3 using rib-group import at PE-Routers/RRs
3.Enable LDP Tunneling on the RSVP-TE at PE and P routers
4.Enable LDP on the Loopback interface at PE and P routers.
Thanks much again for all your help..
lab at edge1.pop1# run traceroute 10.0.6.1
traceroute to 10.0.6.1 (10.0.6.1), 30 hops max, 40 byte packets
1 10.0.10.10 (10.0.10.10) 3.943 ms 1.811 ms 2.832 ms
MPLS Label=300688 CoS=0 TTL=1 S=1
2 10.0.6.1 (10.0.6.1) 11.451 ms 3.897 ms 8.285 ms
[edit]
lab at edge1.pop1#
lab at edge1.pop1# run show route 10.0.6.1 extensive
inet.0: 17 destinations, 22 routes (17 active, 0 holddown, 0 hidden)
10.0.6.1/32 (2 entries, 2 announced)
State: <FlashAll>
TSI:
KRT in-kernel 10.0.6.1/32 -> {Push 300688}
*LDP Preference: 9
Next hop type: Router
Next-hop reference count: 3
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label-switched-path to_core1.pop1
Label operation: Push 300608
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label-switched-path to_core1.pop1
Label operation: Push 300608
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1, selected
Label-switched-path to_core1.pop2
Label operation: Push 300688
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label-switched-path to_core1.pop2
Label operation: Push 300688
State: <Active Int>
Local AS: 64513
Age: 53 Metric: 1
Task: LDP
Announcge-0/0/ent bits (1): 0-KRT
AS path: I
Secondary Tables: inet.3
OSPF Preference: 10
Next hop type: Router
Next-hop reference count: 5
Next hop: 10.0.10.2 via ge-0/0/0.0
Next hop: 10.0.10.10 via ge-0/0/1.0, selected
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label-switched-path to_core1.pop1
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label-switched-path to_core1.pop2
State: <Int>
Inactive reason: Route Preference
Local AS: 64513
Age: 22:46 Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcge-0/0/ent bits (1): 3-LDP
AS path: I
Secondary Tables: inet.3
inet.3: 10 destinations, 15 routes (10 active, 0 holddown, 0 hidden)
10.0.6.1/32 (2 entries, 2 announced)
State: <FlashAll>
*LDP Preference: 9
Next hop type: Router
Next-hop reference count: 3
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label-switched-path to_core1.pop1
Label operation: Push 300608
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label-switched-path to_core1.pop1
Label operation: Push 300608
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1, selected
Label-switched-path to_core1.pop2
Label operation: Push 300688
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label-switched-path to_core1.pop2
Label operation: Push 300688
State: <Secondary Active Int>
Local AS: 64513
Age: 53 Metric: 1
Task: LDP
Announcge-0/0/ent bits (1): 2-Resolve tree 1
AS path: I
Primary Routing Table inet.0
OSPF Preference: 10
Next hop type: Router
Next-hop reference count: 5
Next hop: 10.0.10.2 via ge-0/0/0.0
Next hop: 10.0.10.10 via ge-0/0/1.0, selected
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label-switched-path to_core1.pop1
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label-switched-path to_core1.pop2
State: <Secondary Int>
Inactive reason: Route Preference
Local AS: 64513
Age: 22:46 Metric: 2
Area: 0.0.0.0
Task: OSPF
Announcge-0/0/ent bits (1): 1-LDP
AS path: I
Primary Routing Table inet.0
[edit]
lab at edge1.pop1#
lab at edge1.pop1# run show route table CE1A.inet.0 172.16.251.1 extensive
CE1A.inet.0: 6 destinations, 8 routes (6 active, 0 holddown, 0 hidden)
172.16.251.1/32 (2 entries, 1 announced)
TSI:
KRT in-kernel 172.16.251.1/32 -> {indirect(131071)}
Page 0 idx 1 Type 1 val 8f0d8a4
Nexthop: Self
AS path: [64513] 64513 I
Communities: target:64513:100
Path 172.16.251.1 from 10.0.2.1 Vector len 4. Val: 1
*BGP Preference: 170/-101
Route Distinguisher: 64513:1
Next hop type: Indirect
Next-hop reference count: 10
Source: 10.0.2.1
Next hop type: Router, Next hop index: 131075
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label operation: Push 16, Push 300608(top)
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1, selected
Label operation: Push 16, Push 300608(top)
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label operation: Push 16, Push 300688(top)
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label operation: Push 16, Push 300688(top)
Protocol next hop: 10.0.6.1
Push 16
Indirect next hop: 8ffc000 131071
State: <Secondary Active Int Ext>
Local AS: 64513 Peer AS: 64513
Age: 28 Metric: 0 Metric2: 1
Task: BGP_64513.10.0.2.1+63485
Announcge-0/0/ent bits (2): 0-KRT 1-BGP RT Background
AS path: 64514 I (Originator) Cluster list: 10.0.2.1
AS path: Originator ID: 10.0.6.1
Communities: target:64513:100
Import Accepted
VPN Label: 16
Localpref: 100
Router ID: 10.0.2.1
Primary Routing Table bgp.l3vpn.0
Indirect next hops: 1
Protocol next hop: 10.0.6.1 Metric: 1
Push 16
Indirect next hop: 8ffc000 131071
Indirect path forwarding next hops: 4
Next hop type: Router
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
10.0.6.1/32 Originating RIB: inet.3
Metric: 1 Node path count: 1
Forwarding nexthops: 4
Nexthop: 10.0.10.2 via ge-0/0/0.0
Nexthop: 10.0.10.2 via ge-0/0/0.0
Nexthop: 10.0.10.10 via ge-0/0/1.0
Nexthop: 10.0.10.10 via ge-0/0/1.0
BGP Preference: 170/-101
Route Distinguisher: 64513:1
Next hop type: Indirect
Next-hop reference count: 10
Source: 10.0.5.1
Next hop type: Router, Next hop index: 131075
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Label operation: Push 16, Push 300608(top)
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1, selected
Label operation: Push 16, Push 300608(top)
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label operation: Push 16, Push 300688(top)
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Label operation: Push 16, Push 300688(top)
Protocol next hop: 10.0.6.1
Push 16
Indirect next hop: 8ffc000 131071
State: <Secondary NotBest Int Ext>
Inactive reason: Not Best in its group - Update source
Local AS: 64513 Peer AS: 64513
Age: 28 Metric: 0 Metric2: 1
Task: BGP_64513.10.0.5.1+56350
AS path: 64514 I (Originator) Cluster list: 10.0.5.1
AS path: Originator ID: 10.0.6.1
Communities: target:64513:100
Import Accepted
VPN Label: 16
Localpref: 100
Router ID: 10.0.5.1
Primary Routing Table bgp.l3vpn.0
Indirect next hops: 1
Protocol next hop: 10.0.6.1 Metric: 1
Push 16
Indirect next hop: 8ffc000 131071
Indirect path forwarding next hops: 4
Next hop type: Router
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Next hop: 10.0.10.2 via ge-0/0/0.0 weight 0x1
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
Next hop: 10.0.10.10 via ge-0/0/1.0 weight 0x1
10.0.6.1/32 Originating RIB: inet.3
Metric: 1 Node path count: 1
Forwarding nexthops: 4
Nexthop: 10.0.10.2 via ge-0/0/0.0
Nexthop: 10.0.10.2 via ge-0/0/0.0
Nexthop: 10.0.10.10 via ge-0/0/1.0
Nexthop: 10.0.10.10 via ge-0/0/1.0
[edit]
lab at edge1.pop1#
On Mon, Dec 26, 2011 at 5:49 PM, Mark Tinka <mtinka at globaltransit.net> wrote:
> On Monday, December 26, 2011 03:24:21 PM vaibhava varma
> wrote:
>
>> Thanks for the help so far..I tried to use
>> "ldp-tunneling" under RSVP TEs from PE-P to P-PE but it
>> does not works as I do not have LDP enabled anywhere to
>> tunnel it via RSVP..
>
> That's interesting, because I recall you mentioned that you
> have LDP enabled everywhere and that is already working;
> that you only needed RSVP for MPLS-FRR and MPLS-TE.
>
> Mark.
--
Regards
Vaibhava Varma
More information about the juniper-nsp
mailing list