INE MPLS TE DRAFT

Alp ISIK

5.2 MPLS TE with IS-IS

R2 config.txtR3 config.txtR4 config.txtR5 config.txtR6 config.txtXR1 config.txt

MPLS TEISIS Level 2RSVP, Dynamic Tunnel optionAutoroute Announcelo0

lo0

E0/0

E1/0

G0/0/0/0

G0/0/0/0

G0/0/0/2

G0/0/0/3

E0/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PEPE

MPLS TEISIS Level 2RSVP, Dynamic Tunnel optionAutoroute Announce

lo0

lo0

5.3 MPLS TE Explicit Paths

R2 config.txt R3 config .txt R4 config .txtR5 config .txtR6 config .txt XR1 config .txt

E0/0

E1/0

G0/0/0/0

G0/0/0/0

G0/0/0/2

G0/0/0/3

E0/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PEPE

MPLS TEISIS Level 2RSVP, Dynamic Tunnel optionAutoroute Announcelo0

lo0

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 tunnel0R2(config-if)#tunnel mpls traffic-eng path-option 2 dynamicRP/0/0/CPU0:XR1(config)#interface tunnel-te0RP/0/0/CPU0:XR1(config-if)#path-option 2 dynamic

5.4 MPLS TE Bandwidth Reservations

R2 config .txtR3 config .txt R4 config .txtR5 config .txt R6 config .txt XR1 config .txt

E0/0

E1/0

G0/0/0/0

G0/0/0/0

G0/0/0/2

G0/0/0/3

E0/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PEPE

MPLS TEISIS Level 2RSVP, Dynamic Tunnel optionAutoroute Announce

lo0 lo0

30Mbpsvia RSVP

30Mbpsvia RSVP

75Mbpsvia RSVP

75Mbpsvia RSVP

75Mbpsvia RSVP

50 Mbps

35 Mbps75Mbpsvia RSVP

5.5 MPLS TE Metric Manipulation

R2 .txt R3 .txt R4 .txt R5 .txt R6 .txt XR1 .txt

E0/0

E1/0

G0/0/0/0

G0/0/0/0

G0/0/0/2

G0/0/0/3

E0/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PEPE

MPLS TEISIS Level 2RSVP, Dynamic Tunnel optionAutoroute Announce

lo0 lo0

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.

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: 0x0IGP 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: 0x0IGP 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: 0x0IGP 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: 0x0IGP 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

5.6 MPLS TE with Static Routing

R2.txt R3.txt R4.txt R5.txt R6.txt XR1.txt XR2.txt

E0/0

E1/0

G0/0/0/0

G0/0/0/0

G0/0/0/2

G0/0/0/3

E0/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PEPE

MPLS TEISIS Level 2RSVP, Dynamic Tunnel optionAutoroute Announce

lo0 lo0

Static route to XR1 over TE tunnel

Static route to R2 over TE tunnel

5.6 MPLS TE with Static Routing

R2#show ip route 19.19.19.19Routing 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.2Thu 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.

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/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

Static route via tunnel to XR1Static route via tunnel to R2

ldp ldpPE

PE

RSVPMPLS TE

ldp

ldp

Target ldp

Target ldp

R2.txt R3.txt R4.txt R5.txt

R6.txt

XR1.txt XR2.txtR1.txt

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/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PE

PE

MPLS TEL3VPNRSVP

lo0

Autoroute announce

lo0

Autoroute announce

FRRlo0

BFD >1sec

FRRlo0

BFD >1sec

R4.txtR1.txt

R2.txt R3.txtR5.txt XR1.txt XR2.txtR6.txt

5.9 Inter-Area MPLS TE with OSPF

E0/0

E1/0

G0/0/0/0

G0/0/0/0

G0/0/0/2

G0/0/0/3

E0/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

AutorouteOSPF area 0MPLS TE RSVP

OSPF area 1Mpls TERSVP

OSPF area 2MPLS TE RSVP

ABR

ABR

ABR

ABR

R1.txt R2.txt R3.txt R4.txt R5.txt R6.txt XR1.txtXR2.txt

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/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

IS-IS NET00.0000.0000.000Y.00

IS-IS NET01.0000.0000.000Y.00

Level-2

Level-2

Leve

l-2

Level-2

Level-2

Level-1

Leve

l-1

Level-1

Level-1Level-1

Level-1

MPLS TERSVPAutoroute

L1/L2L1/L2

L1/L2 L1/L2

R1.txt R2.txt R3.txt R4.txt R5.txt R6.txt XR1.txt XR2.txt

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/1.24

E0/2.34

E0/0.23

E1/2.36

E0/3.46

E1/2.45

E0/1

E0/0

E0/2

.56

PE

MPLS TE, RSVP on transit int

lo0IS-IS NET00.0000.0000.000Y.00

Level-2

Level-2

Level-2

Level-2

OSPFAREA 0

Passive interface MPLS TE

autoroute

Static to R1 via tunnel

R1.txt R2.txt R3.txt R4.txt R5.txt R6.txt XR1.txt XR2.txt