mplste-130112120119-phpapp02.pdf
0 likes74 views
This document discusses MPLS Traffic Engineering (TE) configurations using IS-IS as the IGP. It covers topics such as MPLS TE tunnel setup with IS-IS, explicit paths, bandwidth reservations, metric manipulation, static routing, targeted LDP, fast reroute, inter-area MPLS TE using IS-IS areas, and inter-AS MPLS TE. Diagrams are provided to illustrate the various MPLS TE concepts and configurations.
More Related Content
Similar to mplste-130112120119-phpapp02.pdf (20)
More from Huynh MVT (20)
Recently uploaded (20)
mplste-130112120119-phpapp02.pdf
- 1. INE MPLS TE DRAFT Alp ISIK
- 2. 5.2 MPLS TE with IS-IS MPLS TE ISIS Level 2 RSVP, Dynamic Tunnel option Autoroute Announce lo0 lo0 E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE PE MPLS TE ISIS Level 2 RSVP, Dynamic Tunnel option Autoroute Announce lo0 lo0
- 3. 5.3 MPLS TE Explicit Paths E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE PE MPLS TE ISIS Level 2 RSVP, Dynamic Tunnel option Autoroute Announce lo0 lo0
- 4. 5.3 MPLS TE Explicit 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 TE Bandwidth Reservations E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE PE MPLS TE ISIS Level 2 RSVP, Dynamic Tunnel option Autoroute Announce lo0 lo0 30Mbps via RSVP 30Mbps via RSVP 75Mbps via RSVP 75Mbps via RSVP 75Mbps via RSVP 50 Mbps 35 Mbps 75Mbps via RSVP
- 6. 5.5 MPLS TE Metric Manipulation E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE PE MPLS TE ISIS Level 2 RSVP, Dynamic Tunnel option Autoroute Announce lo0 lo0
- 7. 5.5 MPLS TE Metric 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-eng topology | 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 frag_id: 0, Intf Address: 20.3.6.3 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 IGP Id: 0000.0000.0004.00, MPLS TE Id:4.4.4.4 Router Node (isis level-2) frag_id: 0, Intf Address: 20.3.4.4 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.2.4.4 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.4.5.4 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.4.6.4 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.5.19.5 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.4.5.5 TE metric: 1000, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.5.6.5 TE metric: 1000, 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.6.19.6 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.5.6.6 TE metric: 10, IGP metric: 10, attribute flags: 0x0 frag_id: 0, Intf Address: 20.4.6.6 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 TE with Static Routing E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE PE MPLS TE ISIS Level 2 RSVP, Dynamic Tunnel option Autoroute Announce lo0 lo0 Static route to XR1 over TE tunnel Static route to R2 over TE tunnel
- 10. 5.6 MPLS TE with 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 TE with Targeted LDP Adjacencies E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 Static route via tunnel to XR1 Static route via tunnel to R2 ldp ldp PE PE RSVP MPLS TE ldp ldp Target ldp Target ldp
- 12. 5.8 MPLS TE Fast Reroute E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE PE MPLS TE L3VPN RSVP lo0 Autoroute announce lo0 Autoroute announce FRR lo0 BFD >1sec FRR lo0 BFD >1sec
- 14. 5.10 Inter-Area MPLS TE with IS-IS E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 IS-IS NET 00.0000.0000.000Y.00 IS-IS NET 01.0000.0000.000Y.00 Level-2 Level-2 Level-2 Level-2 Level-1 Level-1 MPLS TE RSVP Autoroute L1/L2 L1/L2 L1/L2 L1/L2
- 15. 5.11 Inter-AS MPLS TE E0/0 E1/0 G0/0/0/0 G0/0/0/0 G0/0/0/2 G0/0/0/3 E0/2.34 E1/2.36 E1/2.45 E0/1 E0/0 E0/2.56 PE MPLS TE, RSVP on transit int lo0 IS-IS NET 00.0000.0000.000Y.00 Level-2 Level-2 OSPF AREA 0 Passive interface MPLS TE autoroute Static to R1 via tunnel