2eW4ZRB

Recommendations

Info

Mar 16 11:43:39.854570 Hop Len 12 172.16.37.2/0x80000025
1 LinkID (2), length 4: 172.16.37.1 LocIfAdr (3), length 4: 172.16.37.2 RemIfAdr (4), length 4: 172.16.37.1 The ASBR is actually advertising the two addresses for the inter-AS link. user@mx240-7-re1# run show ted database 192.168.36.7 TED database: 0 ISIS nodes 12 INET nodes ID Type Age(s) LnkIn LnkOut Protocol 192.168.36.7 Rtr 5539 3 4 OSPF(0.0.0.0) … To: 172.16.37.1, Local: 172.16.37.2, Remote: 0.0.0.0 Local interface index: 0, Remote interface index: 0 But what if we remove the traffic-engineering option from the configuration? user@mx240-7-re1# show protocols ospf area 0.0.0.0 interface xe-2/2/0.0 passive { inactive: traffic-engineering { remote-node-id 172.16.37.1; } } Remember that in order to reach the egress router, we need a BGP route toward it. Once we have that, we also require that the BGP route next-hop can be found in the TED. user@mx240-7-re1# run show route 192.168.38.24/32 table inet.0 inet.0: 34 destinations, 49 routes (34 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both 192.177.33.24/32 *[BGP/170] 03:54:21, localpref 100 AS path: 65537 65538 I, validation-state: unverified > to 172.16.37.1 via xe-2/2/0.0 [BGP/170] 03:54:21, localpref 100, from 192.168.36.5 AS path: 65537 65538 I, validation-state: unverified > to 10.36.4.1 via xe-2/0/1.0 user@mx240-7-re1# run show ted database 192.168.36.7 TED database: 0 ISIS nodes 11 INET nodes ID Type Age(s) LnkIn LnkOut Protocol 192.168.36.7 Rtr 35 3 3 OSPF(0.0.0.0) … # NOTE: no information about 172.16.37.1 !!! And, as a result, the LSP is down: user@mx80-23# run show mpls lsp extensive Ingress LSP: 1 sessions 192.168.38.24 From: 192.168.36.23, State: Dn, ActiveRoute: 0, LSPname: Inter-AS-38 ActivePath: (none) PathDomain: Inter-domain … 1140 Mar 16 15:40:01.514 10.36.2.2: No Route toward dest We have an analogous scenario if we use the loopback address when configuring the remote side of the inter-AS link. In any case, we won’t have the BGP next-hop in the TED, making the establishment of the LSP impossible. Copyright (©) 2016 Juniper Networks. All Rights Reserved. Page 23 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: When we reach MX80-22, we’re fina
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 and 44: oute-distinguisher 192.168.36.23:36
Page 45 and 46: 9 NG MVPN: Monitoring and Verificat
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?