Downloaded 96 times
Uploaded byAlp isik
Mpls TE
The document discusses MPLS Traffic Engineering (TE) concepts including: 1. MPLS TE can be used with IS-IS to signal tunnels and establish paths between routers. 2. Explicit paths can be used to avoid issues if a link fails and dynamic paths cannot be established. 3. Bandwidth reservations can be made for tunnels using RSVP to ensure sufficient resources. 4. The TE metric can be manipulated separately from the IGP metric to influence path selection. 5. Static routing can be used over TE tunnels to establish connectivity between routers.
Mpls TE
- 1. INE MPLS TEDRAFT Alp ISIK
- 2. 5.2 MPLS TEwith IS-IS G0/0/0/0 E0/0 MPLS TE G0/0/0/0 E1/0 ISISMPLS TE Level 2 lo0 ISIS Level 2 RSVP, Dynamic Tunnel option G0/0/0/3 lo0 lo0 RSVP, Dynamic Tunnel option Autoroute Announce PE PE Autoroute Announce lo0 E1/2.36 G0/0/0/2 E0/0 E0/2.34 E0/2.56 E0/1 E1/2.45
- 3. 5.3 MPLS TEExplicit Paths G0/0/0/0 E0/0 MPLS TE ISIS Level 2 G0/0/0/0 E1/0 RSVP, Dynamic Tunnel option lo0 Autoroute Announce G0/0/0/3 PE PE lo0 E1/2.36 G0/0/0/2 E0/0 E0/2.34 E0/2.56 E0/1 E1/2.45
- 4. 5.3 MPLS TEExplicit Paths • Once R5’s link is disabled R2’s tunnel interface goes down. From the above output we can see that there is a path calculation error, as R2 cannot reach the link between R5 and XR1. Even though R2 can still reach the Loopback of XR1, which is the tunnel destination, traffic cannot be routed over the tunnel since there is no valid path option. The result is that R2 and XR1 can still reach each other, but the end customers cannot. • To avoid this problem either Fast Reroute (FRR) Link or Node Protection can be configured to automatically heal around the broken link or router, or a lower priority dynamic path option can be configured. R2(config)#int tunnel0 R2(config-if)#tunnel mpls traffic-eng path-option 2 dynamic RP/0/0/CPU0:XR1(config)#interface tunnel-te0 RP/0/0/CPU0:XR1(config-if)#path-option 2 dynamic
- 5. 5.4 MPLS TEBandwidth Reservations 50 Mbps G0/0/0/0 E0/0 G0/0/0/0 E1/0 lo0 lo0 G0/0/0/3 PE 35 Mbps PE 75Mbps 30Mbps 30Mbps 75Mbps via RSVP G0/0/0/2 via RSVP E1/2.36 via RSVP via RSVP E0/0 MPLS TE E0/2.34 ISIS Level 2 E0/2.56 RSVP, Dynamic Tunnel option Autoroute Announce E0/1 75Mbps E1/2.45 75Mbps via RSVP via RSVP
- 6. 5.5 MPLS TEMetric Manipulation G0/0/0/0 E0/0 G0/0/0/0 E1/0 lo0 lo0 G0/0/0/3 PE PE E1/2.36 G0/0/0/2 E0/0 MPLS TE E0/2.34 ISIS Level 2 E0/2.56 RSVP, Dynamic Tunnel option Autoroute Announce E0/1 E1/2.45
- 7. 5.5 MPLS TEMetric Manipulation When OSPF or IS-IS is used in the SP core for the purpose of MPLS Traffic Engineering, two different metrics are advertised for each link, the IGP metric and the TE metric. By default the TE metric is inherited from the IGP metric. If the IGP metric is changed, i.e. the OSPF cost or the IS-IS metric, the TE metric will likewise change. However, the TE metric can be manually changed separately from the IGP metric. Additionally by default all MPLS TE tunnels will prefer to use the TE metric value for their dynamic path selection. This can be controlled globally or on a per-tunnel basis with the command tunnel mpls trafficeng path-selection metric igp in regular IOS or path- selection metric igp in IOS XR at the tunnel interface level. The TE metrics can be verified by viewing the MPLS TE topology, as follows.
- 8. R2#show mpls traffic-engtopology | include (TE Id|Intf Address|TE metric) IGP Id: 0000.0000.0002.00, MPLS TE Id:2.2.2.2 Router Node (isis level-2) frag_id: 0, Intf Address: 20.2.3.2 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.2.4.2 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 IGP Id: 0000.0000.0003.00, MPLS TE Id:3.3.3.3 Router Node (isis level-2) frag_id: 0, Intf Address: 20.2.3.3 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.3.4.3 TE metric: 10, IGP metric: 10, attribute flags: 0x0 IGP Id: 0000.0000.0005.00, MPLS TE Id:5.5.5.5 Router Node (isis level-2) frag_id: 0, Intf Address: 20.3.6.3 frag_id: 0, Intf Address: 20.5.19.5 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.4.5.5 IGP Id: 0000.0000.0004.00, MPLS TE Id:4.4.4.4 Router Node (isis TE metric: 1000, IGP metric: 10, attribute flags: 0x0 level-2) frag_id: 0, Intf Address: 20.5.6.5 frag_id: 0, Intf Address: 20.3.4.4 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 TE metric: 10, IGP metric: 10, attribute flags: 0x0 IGP Id: 0000.0000.0006.00, MPLS TE Id:6.6.6.6 Router Node (isis level-2) frag_id: 0, Intf Address: 20.2.4.4 frag_id: 0, Intf Address: 20.6.19.6 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.5.6.6 frag_id: 0, Intf Address: 20.4.5.4 TE metric: 10, IGP metric: 10, attribute flags: 0x0 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.4.6.6 frag_id: 0, Intf Address: 20.4.6.4 TE metric: 10, IGP metric: 10, attribute flags: 0x0 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.3.6.6 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 IGP Id: 0000.0000.0019.00, MPLS TE Id:19.19.19.19 Router Node (isis level- 2) frag_id: 0, Intf Address: 20.6.19.19, Nbr Intf Address: 20.6.19.6 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.5.19.19, Nbr Intf Address: 20.5.19.5 TE metric: 1000, IGP metric: 10, attribute flags: 0x0
- 9. 5.6 MPLS TEwith Static Routing G0/0/0/0 E0/0 Static route to XR1 Static route to R2 over TE tunnel over TE tunnel G0/0/0/0 E1/0 lo0 lo0 G0/0/0/3 PE PE E1/2.36 G0/0/0/2 E0/0 MPLS TE E0/2.34 ISIS Level 2 E0/2.56 RSVP, Dynamic Tunnel option Autoroute Announce E0/1 E1/2.45
- 10. 5.6 MPLS TEwith Static Routing R2#show ip route 19.19.19.19 Routing entry for 19.19.19.19/32 Known via "static", distance 1, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via Tunnel0 Route metric is 0, traffic share count is 1 RP/0/0/CPU0:XR1#show route 2.2.2.2 Thu Jan 3 16:10:43.516 EET Routing entry for 2.2.2.2/32 Known via "static", distance 1, metric 0 (connected) Installed Jan 3 15:49:07.335 for 00:21:37 Routing Descriptor Blocks directly connected, via tunnel-te0 Route metric is 0 No advertising protos.
- 11. 5.7 MPLS TEwith Targeted LDP Adjacencies G0/0/0/0 E0/0 RSVP G0/0/0/0 E1/0 Static route via tunnel to XR1 MPLS TE Static route via tunnel to R2 G0/0/0/3 PE PE ldp ldp ldp E1/2.36 Target ldp G0/0/0/2 E0/0 Target ldp E0/2.34 E0/2.56 E0/1 E1/2.45 ldp
- 12. 5.8 MPLS TEFast Reroute G0/0/0/0 E0/0 E1/0 MPLS TE G0/0/0/0 L3VPN lo0 RSVP G0/0/0/3 PE lo0 PE Autoroute announce FRR lo0 G0/0/0/2 E1/2.36 BFD >1sec E0/0 E0/2.34 E0/2.56 FRR lo0 E0/1 BFD >1sec E1/2.45 Autoroute announce
- 14. 5.10 Inter-Area MPLSTE with IS-IS IS-IS NET IS-IS NET G0/0/0/0 01.0000.0000.000Y.00 E0/000.0000.0000.000Y.00 Level-1 MPLS TE Level-1 G0/0/0/0 E1/0 RSVP Autoroute G0/0/0/3 L1/L2 Level-2 E1/2.36 L1/L2 G0/0/0/2 E0/0 Level-2 E0/2.34 Level-2 E0/2.56 E0/1 E1/2.45 L1/L2 Level-2 L1/L2
- 15. 5.11 Inter-AS MPLSTE IS-IS NET OSPF Static to R1 00.0000.0000.000Y.00 AREA 0 lo0 via tunnel G0/0/0/0 E0/0 E1/0 Level-2 G0/0/0/0 Passive interface G0/0/0/3 MPLS TE PE autoroute E1/2.36 G0/0/0/2 E0/0 E0/2.34 E0/2.56 Level-2 E0/1 E1/2.45 MPLS TE, RSVP on transit int
Editor's Notes
- #2 Last modified 12.01.2013
- #3 R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.• Configure an MPLSTE tunnel from R2 to XR1 as follows:o Unnumber the tunnel to R2’sLoopback0 interfaceo Set the tunnel destination as XR1’sLoopback0 interfaceo Set the tunnel’s path option to dynamic.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure an MPLSTE tunnel from XR1 to R2 as follows:o Unnumber the tunnel to XR1’sLoopback0 interfaceo Set the tunnel destination as R2’sLoopback0 interfaceo Set the tunnel’s path option to dynamic.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Once complete the following reachability should be achieved:o R1 and XR2 should have full IP reachability to each other, and a tracerouteshould indicate that their L3VPN tunnel is transiting over the MPLSTE tunnels inthe core of the SP network.
- #4 • R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.• Configure an MPLSTE tunnel from R2 to XR1 as follows:o Unnumber the tunnel to R2’sLoopback0 interfaceo Set the tunnel destination as XR1’sLoopback0 interfaceo Set the tunnel’s path option to explicitly follow the path from R2 to R3 to R4 to R6to R5 to XR1.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure an MPLSTE tunnel from XR1 to R2 as follows:o Unnumber the tunnel to XR1’sLoopback0 interfaceo Set the tunnel destination as R2’sLoopback0 interfaceo Set the tunnel’s path option to explicitly follow the path from XR1 to R6 to R5 toR4 to R3 to R2.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Once complete the following reachability should be achieved:o R1 and XR2 should have full IP reachability to each other, and a tracerouteshould indicate that their L3VPN tunnel is transiting over the MPLSTE tunnels inthe core of the SP network.
- #6 Note that in regular IOS when you issue the ip rsvp bandwidth command at the interfacelevel, the default amount of reservable bandwidth is 75% of the configured bandwidthcommand. In IOSXR there is no default and the amount of bandwidth available forreservations must be manually specified.• R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.o Configure R3 and R6 so that 30 Mbps can be reserved via RSVP on any of theirinterfaces.o Configure all other routers in the core so that 75 Mbps can be reserved via RSVPon any of their interfaces.• Configure an MPLSTE tunnel from R2 to XR1 as follows:o Unnumber the tunnel to R2’sLoopback0 interfaceo Set the tunnel destination as XR1’sLoopback0 interfaceo Set the tunnel to request a bandwidth reservation of 50 Mbpso Set the tunnel’s path option to dynamic.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure an MPLSTE tunnel from XR1 to R2 as follows:o Unnumber the tunnel to XR1’sLoopback0 interfaceo Set the tunnel destination as R2’sLoopback0 interfaceo Set the tunnel to request a bandwidth reservation of 35 Mbpso Set the tunnel’s path option to dynamic.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Once complete the following reachability should be achieved:o R1 and XR2 should have full IP reachability to each other, and a tracerouteshould indicate that their L3VPN tunnel is transiting over the MPLSTE tunnels inthe core of the SP network.
- #7 Not : Smaller weight is better.• R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.• Configure an MPLSTE tunnel from R2 to XR1 as follows:o Unnumber the tunnel to R2’sLoopback0 interfaceo Set the tunnel destination as XR1’sLoopback0 interfaceo Set the tunnel’s path option to dynamic.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure an MPLSTE tunnel from XR1 to R2 as follows:o Unnumber the tunnel to XR1’sLoopback0 interfaceo Set the tunnel destination as R2’sLoopback0 interfaceo Set the tunnel’s path option to dynamic.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure MPLSTE metrics as follows:o The preferred path from R2 to XR1 should be R2 to R3 to R4 to R6 to XR1.o The preferred path from XR1 to R2 should be XR1 to R6 to R4 to R3 to R2.• Once complete the following reachability should be achieved:o R1 and XR2 should have full IP reachability to each other, and a tracerouteshould indicate that their L3VPN tunnel is transiting over the MPLSTE tunnels inthe core of the SP network.
- #8 Smaller weight is better.
- #10 • R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.• Configure an MPLSTE tunnel from R2 to XR1 as follows:o Unnumber the tunnel to R2’sLoopback0 interfaceo Set the tunnel destination as XR1’sLoopback0 interfaceo Set the tunnel’s path option to dynamic.o Configure a static route for XR1’sLoopback0 interface via the tunnel.• Configure an MPLSTE tunnel from XR1 to R2 as follows:o Unnumber the tunnel to XR1’sLoopback0 interfaceo Set the tunnel destination as R2’sLoopback0 interfaceo Set the tunnel’s path option to dynamic.o Configure a static route for R2’sLoopback0 interface via the tunnel.• Once complete the following reachability should be achieved:o R1 and XR2 should have full IP reachability to each other, and a tracerouteshould indicate that their L3VPN tunnel is transiting over the MPLSTE tunnels inthe core of the SP network.RP/0/0/CPU0:XR1#sh bgp vpnv4 unicast Thu Jan 3 15:18:23.392 EETBGP router identifier 19.19.19.19, local AS number 100BGP generic scan interval 60 secsBGP table state: ActiveTable ID: 0x0 RD version: 4BGP main routing table version 8BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > best i - internal, r RIB-failure, S staleOrigin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight PathRoute Distinguisher: 100:1 (default for vrf VPN_A)*>i1.1.1.1/32 2.2.2.2 0 100 0 i*>i10.1.2.0/24 2.2.2.2 0 100 0 i*> 10.19.20.0/24 0.0.0.0 0 32768 i*> 20.20.20.20/32 10.19.20.20 0 32768 iProcessed 4 prefixes, 4 pathsR2#sh ip bgp vpnv4 vrf VPN_ABGP table version is 7, local router ID is 2.2.2.2Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter, x best-external, a additional-path, c RIB-compressed, Origin codes: i - IGP, e - EGP, ? - incompleteRPKI validation codes: V valid, I invalid, N Not found Network Next Hop Metric LocPrf Weight PathRoute Distinguisher: 100:1 (default for vrf VPN_A)*> 1.1.1.1/32 10.1.2.1 0 32768 i*> 10.1.2.0/24 0.0.0.0 0 32768 i*>i10.19.20.0/24 19.19.19.19 0 100 0 i*>i20.20.20.20/32 19.19.19.19 0 100 0 i
- #12 • R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.• Configure an MPLSTE tunnel from R2 to R6 as follows:o Unnumber the tunnel to R2’sLoopback0 interface.o Set the tunnel destination as R6’sLoopback0 interface.o Set the tunnel’s path option to explicitly follow the path from R2 to R3 to R4 to R5to R6.o Configure a static route on R2 for XR1’sLoopback0 interface via the TE tunnel toR6.• Configure an MPLSTE tunnel from XR1 to R3 as follows:o Unnumber the tunnel to XR1’sLoopback0 interface.o Set the tunnel destination as R2’sLoopback0 interface.o Set the tunnel’s path option to explicitly follow the path from XR1 to R6 to R5 toR4 to R3.o Configure a static route on XR1 for R2’sLoopback0 interface via the TE tunnel toR3.• Configure LDP in the core of the network as follows:o Enable LDP on the link between R2 and R3.o Enable LDP on the link between R6 and XR1.o Enable LDP on the MPLSTE tunnel from R2 to R6.o Enable LDP on the MPLSTE tunnel from XR1 to R3.o Configure R3 and R6 to accept target LDP sessions.• Once complete the following reachability should be achieved:o R1 and XR2 should have full IP reachability to each other, and a tracerouteshould indicate that their L3VPN tunnel is transiting over the MPLSTE tunnels inthe core of the SP network.
- #13 • R2 and XR1 are preconfigured as PE routers for the MPLSL3VPN customer routers R1and XR2 respectively, however the core of the Service Provider network is not runningLDP.• Configure the core of the Service Provider network to support MPLSTE tunnels asfollows:o Enable MPLSTE support for the IS-IS Level 2 core.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces running IS-IS inthe core.• Configure an MPLSTE tunnel from R2 to XR1 as follows:o Unnumber the tunnel to R2’sLoopback0 interfaceo Set the tunnel destination as XR1’sLoopback0 interfaceo Set the tunnel’s path option to explicitly follow the path from R2 to R3 to R4 to R5to XR1.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure an MPLSTE tunnel from XR1 to R2 as follows:o Unnumber the tunnel to XR1’sLoopback0 interfaceo Set the tunnel destination as R2’sLoopback0 interfaceo Set the tunnel’s path option to explicitly follow the path from XR1 to R5 to R6 toR3 to R2.o Configure Autoroute Announce on the tunnel so that the IS-IS core can use it fordynamic routing.• Configure an MPLSTE tunnel from R4 to R5 for FRR as follows:o Unnumber the tunnel to R4’sLoopback0 interface.o Set the tunnel destination as R5’sLoopback0 interface.o Set the tunnel’s path option to explicitly avoid the link between R4 and R5.o Configure BFD signaling between R4 and R5 to detect a link failure betweenthem in less than one second.o R2’sTE tunnel to XR1 should be Fast Rerouted if the link between R4 and R5 isdown.• Configure an MPLSTE tunnel from R6 to R3 for FRR as follows:o Unnumber the tunnel to R6’sLoopback0 interface.o Set the tunnel destination as R3’sLoopback0 interface.o Set the tunnel’s path option to explicitly avoid the link between R3 and R6.o Configure BFD signaling between R3 and R6 to detect a link failure betweenthem in less than one second.o XR1’sTE tunnel to R2 should be Fast Rerouted if the link between R3 and R6 isdown.• Once complete you should be able to perform the following verifications:o Traceroutes from R1 to XR2 should follow the R2 to R3 to R4 to R5 to XR1 path.o Remove VLAN 45 from SW1 to simulate a failure of the link between R4 and R5;immediately following this the traceroutes from R1 to XR2 should be FastRerouted via R6.o Traceroutes from XR2 to R1 should follow the XR1 to R5 to R6 to R3 to R1 path.o Remove VLAN 36 from SW1 to simulate a failure of the link between R3 and R6;immediately following this the traceroutes from XR2 to R1 should be FastRerouted via R4.
- #14 • Configure OSPFv2 routing in the network as follows:o Area 0 consists of links interconnecting R3 & R4, R3 & R6, R4 & R6, R4 & R5,and R5 & R6.o Area 1 consists of links interconnecting R1 & R1, R2 & R3, and R2 & R4.o Area 2 consists of links interconnecting XR1 & R5, XR1 & R6, and XR1 & XR2.o Advertise the Loopback interfaces of R3, R4, R5, and R6 into Area 0.o Advertise the Loopback interfaces of R1 and R2 into Area 1.o Advertise the Loopback interfaces of XR1 and XR2 into Area 2.• Configure the network to support MPLSTE tunnels as follows:o Enable MPLSTE support for OSPF Area 0, Area 1, and Area 2.o Set the OSPFMPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces.• Configure an MPLSTE tunnel from R1 to XR2 as follows:o Unnumber the tunnel to R1’sLoopback0 interface.o Set the tunnel destination as XR2’sLoopback0 interface.o Configure the tunnel’s explicit path option to use loose next-hops as follows: Traffic from Area 1 to Area 0 should use R3 as the ABR. Traffic from Area 0 to Area 2 should use R5 as the ABR.o Configure Autoroute Destination so that R1 uses the tunnel to route towardsXR2’s Loopback0.• Configure an MPLSTE tunnel from XR2 to R1 as follows:o Unnumber the tunnel to XR2’sLoopback0 interface.o Set the tunnel destination as R1’sLoopback0 interface.o Configure the tunnel’s explicit path option to use loose next-hops as follows: Traffic from Area 2 to Area 0 should use R6 as the ABR. Traffic from Area 0 to Area 1 should use R4 as the ABR.o Configure static routing so that XR2 uses the tunnel to route towards R1’sLoopback0.
- #15 • Configure IS-IS routing in the network as follows:o R1, R2, R3, and R4 should use NET address 00.0000.0000.000Y.00 where Y isthe router number.o R5, R6, XR1, and XR2 should use NET address 01.0000.0000.000Y.00 where Yis the router number; for XR1 use 19 and for XR2 use 20.o Level-2 consists of links interconnecting R3 & R4, R3 & R6, R4 & R6, R4 & R5,R5 & R6, and all their Loopback0 interfaces.o Level-1 consists of all other links and Loopbacks.• Configure the network to support MPLSTE tunnels as follows:o Enable MPLSTE support for IS-IS Level-1 and Level-2.o Set the IS-IS MPLSTE Router-ID to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces.• Configure an MPLSTE tunnel from R1 to XR2 as follows:o Unnumber the tunnel to R1’sLoopback0 interface.o Set the tunnel destination as XR2’sLoopback0 interface.o Configure the tunnel’s explicit path option to use loose next-hops as follows: R1 should use R3 as the L1/L2 router. R3 should use R6 as the next L1/L2 router.o Configure Autoroute Destination so that R1 uses the tunnel to route towardsXR2’s Loopback0.• Configure an MPLSTE tunnel from XR2 to R1 as follows:o Unnumber the tunnel to XR2’sLoopback0 interface.o Set the tunnel destination as R1’sLoopback0 interface.o Configure the tunnel’s explicit path option to use loose next-hops as follows: XR2 should use R5 as the L1/L2 router. R5 should use R4 as the next L1/L2 router.o Configure static routing so that XR2 uses the tunnel to route towards R1’sLoopback0.
- #16 • Configure IS-IS routing in the network as follows:o R1, R2, R3, and R4 should run IS-IS and use NET address00.0000.0000.000Y.00 where Y is the router number.o Level-2 consists of links interconnecting R1 & R2, R2 & R3, R2 & R4, R3 & R4,and all their Loopback0 interfaces.• Configure OSPF routing in the network as follows:o R5, R6, XR1, and XR2 should run OSPF.o Area 0 consists of links interconnecting R5 & R6, R5 & XR1, R6 & XR1, XR1 &XR2, and all their Loopback0 interfaces.• Configure the network to support MPLSTE tunnels as follows:o Enable MPLSTE support for IS-IS Level-2 on R1, R2, R3, and R4.o Enable MPLSTE support for OSPF Area 0 on R5, R6, XR1, and XR2.o Set the MPLSTE Router-IDs to be the Loopback0 interfaces.o Enable support for RSVP and MPLSTE on all transit interfaces.• Configure Inter-AS MPLSTE support as follows:o Do not advertise the Inter-AS links (R3 & R6, R4 & R5, and R4 & R6) into IGP.o Instead, configure these links as passive interfaces for the MPLSTE process.o Use the routers’ Loopback0 interfaces as the neighbor TE ID.• Configure an MPLSTE tunnel from R1 to XR2 as follows:o Unnumber the tunnel to R1’sLoopback0 interface.o Set the tunnel destination as XR2’sLoopback0 interface.o Configure the tunnel’s explicit path option to use loose next-hops as follows: R1 should use R3 as the first ASBR. R3 should use R6 as the next ASBR.o Configure Autoroute Destination so that R1 uses the tunnel to route towardsXR2’s Loopback0.• Configure an MPLSTE tunnel from XR2 to R1 as follows:o Unnumber the tunnel to XR2’sLoopback0 interface.o Set the tunnel destination as R1’sLoopback0 interface.o Configure the tunnel’s explicit path option to use loose next-hops as follows: XR2 should use R6 as the first ASBR. R6 should use R4 as the next ASBR.o Configure static routing so that XR2 uses the tunnel to route towards R1’sLoopback0.• Once complete you should be able to ping and traceroute between the Loopback0networks of R1 and XR2.