2eW4ZRB

Recommendations

Info

} peer-as 65538; neighbor 192.168.38.24; neighbor 192.168.38.1; Copyright (©) 2016 Juniper Networks. All Rights Reserved. Page 44 of 53
9 NG MVPN: Monitoring and Verification 9.1 Autodiscovery As soon as the configuration is committed, PE routers discover their neighbors in order to determine the other members of the MVPN. This process is called autodiscovery, as shown in Figure 22, and makes use of the Type 1 MVPN messages described before. Figure 22. PE Autodiscovery The MVPN messages are sent and received by BGP: user@mx80-23# run show route receive-protocol bgp 192.168.38.1 table NG-MVPN- 1.mvpn.0 detail NG-MVPN-1.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) * 1:192.168.138.1:33:192.168.38.1/240 (1 entry, 1 announced) Import Accepted Nexthop: 192.168.38.1 AS path: 65538 I Communities: target:360:380 PMSI: Flags 0x0: Label 0: RSVP-TE: Session_13[192.168.38.1:0:7209:192.168.38.1] Note the format of the NLRI: • NLRI-type: in this case 1 • Route distinguisher: 192.168.138.1:33 • Remote PE loopback: 192.168.38.1 We also see information about some common BGP attributes like next-hop or AS-path. The Community attribute is not standard but extended; it contains the route-target. Another important value to keep in mind is the RSVP-TE session number, 7209. Identical output is obtained by examining routes received from other EBGP neighbors. These routes are installed in the main routing table of the routing instance: user@mx80-23> show route table NG-MVPN-1.mvpn.0 NG-MVPN-1.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 1:192.168.136.23:36:192.168.36.23/240 *[MVPN/70] 03:43:12, metric2 1 Indirect 1:192.168.138.1:38:192.168.38.1/240 *[BGP/170] 01:28:28, localpref 100, from 192.168.38.1 AS path: 65538 I, validation-state: unverified to 10.36.0.2 via xe-0/0/0.0, Push 300688, Push 299872(top) > to 10.36.2.2 via xe-0/0/2.0, Push 300688, Push 299904(top) 1:192.168.138.24:38:192.168.38.24/240 *[BGP/170] 01:28:47, localpref 100, from 192.168.38.24 AS path: 65538 I, validation-state: unverified Copyright (©) 2016 Juniper Networks. All Rights Reserved. Page 45 of 53
Page 1 and 2: Establishing MPLS LSPs Across Multi
Page 3 and 4: Table of Contents 1 What’s Inside
Page 5 and 6: 1 What’s Inside This Document? Fi
Page 7 and 8: 2 Test Setup 2.1 Test Topology Figu
Page 9 and 10: 3.2 MPLS Inter-Domain Figure 3: Int
Page 11 and 12: 3.4 Inter-AS Link Figure 5: Tunnel
Page 13 and 14: prefix-list PRL-LOCAL-LOOPBACKS { 1
Page 15 and 16: } While EBGP for PE-PE connectivity
Page 17 and 18: 4 Inter-AS LSPs with expand-loose-h
Page 19 and 20: Figure 9. The ASBR and Expanding Lo
Page 21 and 22: When we reach MX80-22, we’re fina
Page 23 and 24: 1 LinkID (2), length 4: 172.16.37.1
Page 25 and 26: 5.3 BGP-LS BGP is the protocol resp
Page 27 and 28: 5.6 Inter-AS Link This configuratio
Page 29 and 30: interface xe-2/0/0.0; The IBGP conf
Page 31 and 32: • Router 192.168.36.5 is in AS 65
Page 33 and 34: 7 Node-Link Protection In this sect
Page 35 and 36: Figure 16: RSVP and Primary and Byp
Page 37 and 38: Figure 19: Transit and Egress LSP R
Page 39 and 40: Our example uses the second option,
Page 41 and 42: At this point we still need to conf
Page 43: oute-distinguisher 192.168.36.23:36
Page 47 and 48: • For each “sub-LSP,” we have
Page 49 and 50: PE routers are responsible for tran
Page 51 and 52: This route is advertised to both EB
Page 53: Cache lifetime/timeout: forever Wro

2eW4ZRB

Create successful ePaper yourself

Delete template?

Save as template?