2eW4ZRB
2eW4ZRB
2eW4ZRB
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
to 10.36.0.2 via xe-0/0/0.0, Push 300672, Push 299872(top)<br />
> to 10.36.2.2 via xe-0/0/2.0, Push 300672, Push 299904(top)<br />
It is easy to pick out two routes, one for each PE router. Also note the presence of two push<br />
operations: one for the P2MP LSP, common to all the destinations, and one for the “sub-LSP.”<br />
Additional information is available when using the detail keyword:<br />
user@mx80-23> show route table NG-MVPN-1.mvpn.0 detail<br />
1:192.168.138.1:33:192.168.38.1/240 (1 entry, 1 announced)<br />
*BGP Preference: 170/-101<br />
PMSI: Flags 0x0: Label 0: RSVP-TE:<br />
Session_13[192.168.38.1:0:7209:192.168.38.1]<br />
…<br />
Source: 192.168.38.1<br />
Protocol next hop: 192.168.38.1<br />
…<br />
Local AS: 65538 Peer AS: 65538<br />
…<br />
Router ID: 192.168.38.1<br />
Primary Routing Table bgp.mvpn.0<br />
Once messages are exchanged, membership information is spread across the network. As a<br />
result, the PEs build a list of neighbors:<br />
user@mx80-23> show mvpn neighbor instance-name NG-MVPN-1<br />
MVPN instance:<br />
Legend for provider tunnel<br />
S- Selective provider tunnel<br />
Legend for c-multicast routes properties (Pr)<br />
DS -- derived from (*, c-g)<br />
RM -- remote VPN route<br />
Family : INET<br />
Instance : NG-MVPN-1<br />
MVPN Mode : RPT-SPT<br />
Neighbor<br />
Inclusive Provider Tunnel<br />
192.168.38.1 RSVP-TE P2MP:192.168.38.1, 7209,192.168.38.1<br />
192.168.38.24 RSVP-TE P2MP:192.168.38.24, 35847,192.168.38.24<br />
The list contains two neighbors. They are the two egress routers of our P2MP LSP.<br />
Finally, we can look at the state of the LSP that will carry the traffic over the core:<br />
user@mx80-23> show mpls lsp p2mp ingress detail<br />
Ingress LSP: 1 sessions<br />
P2MP name: 192.168.136.23:36:mvpn:NG-MVPN-1, P2MP branch count: 2<br />
192.168.38.24<br />
From: 192.168.36.23, State: Up, ActiveRoute: 0, LSPname:<br />
192.168.38.24:192.168.136.23:36:mvpn:NG-MVPN-1<br />
ActivePath: (primary)<br />
P2MP name: 192.168.136.23:36:mvpn:NG-MVPN-1<br />
…<br />
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 5)<br />
10.36.2.2 S 10.36.37.1 S 10.37.1.1 S 10.37.38.1 S 10.38.2.1 S<br />
192.168.38.1<br />
From: 192.168.36.23, State: Up, ActiveRoute: 0, LSPname:<br />
192.168.38.1:192.168.136.23:36:mvpn:NG-MVPN-1<br />
ActivePath: (primary)<br />
P2MP name: 192.168.136.23:36:mvpn:NG-MVPN-1<br />
…<br />
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 5)<br />
10.36.2.2 S 10.36.37.1 S 10.37.1.1 S 10.37.38.1.1 S 10.38.0.1<br />
…<br />
Let’s try to understand how to read this output:<br />
• There is one, and only one, ingress LSP session, which is a P2MP one. Then<br />
different “sub-LSPs” are listed.<br />
Copyright (©) 2016 Juniper Networks. All Rights Reserved.<br />
Page 46 of 53
Change language