mpls-05
1 like340 views
This document provides configuration instructions for setting up MPLS-TE tunnels between routers R1, R2, R3 and R4 to enable traffic engineering. It describes: 1. Configuring OSPF on all routers to support MPLS-TE. 2. Creating explicit paths between routers and configuring MPLS-TE tunnels between them with bandwidth reservations. 3. Enabling IP RSVP on all interfaces to reserve bandwidth for MPLS-TE tunnels and ensure tunnels remain up. 4. Configuring a backup dynamic path for tunnels to provide an alternate route if the primary path fails.
![MPLS-TE & OSPF – Setting up Tunnels
R0.1 R0.2
R0.3
R0.4
F0/0 F0/0
F0/1 F0/1
F0/0
F0/0
20.0.0.0/30
20.0.0.4/30
20.0.0.8/30
Tunnel 4
Destination 10.0.0.4
Tunnel 1
Destination 10.0.0.1
MPLS-TE
R1
interface Tunnel4
description TE-R1-R4
ip unnumbered Loopback0
mpls traffic-eng tunnels
tunnel destination 10.0.0.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng bandwidth 500
tunnel mpls traffic-eng path-option 10 explicit name TE-R1-R4
tunnel mpls traffic-eng record-route
no routing dynamic
You will create an
EXPLICIT PATH
R1
ip explicit-path name TE-R1-R4 enable
next-address 20.0.0.2
next-address 20.0.0.6
next-address 20.0.0.10
Create Explicit Path Next-HOP IP
interface FastEthernet0/0
description R1-R2
ip address 20.0.0.1 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 5000 5000
Make your outgoing interface
participate in MPLS-TE
Ip RSVP – very important, will
explain later. Remind Me
R1 – Tun4 Still Down because interfaces on
R2-R4 NOT participating in MPLS-TE
You MUST enable it on ALL interfaces
INGRESS / EGRESS in Fa's R1 – R4
Example on R2
!
interface FastEthernet0/0
description R2-R1
ip address 20.0.0.2 255.255.255.252
mpls traffic-eng tunnels
ip rsvp bandwidth 5000 5000
R1#show mpls traffic-eng tunnels tunnel 4
Name: TE-R1-R4 (Tunnel4) Destination: 10.0.0.4
Status:
Admin: up Oper: down Path: not valid Signalling: Down
path option 10, type explicit TE-R1-R4
…
Prior LSP:
ID: path option 10 [100]
Removal Trigger: path verification failed
Last Error: PCALC:: Explicit path has unknown address, 20.0.0.2
Err Message when the Tun is in
a DOWN state](https://image.slidesharecdn.com/d1cd9d79-492f-48cf-bf08-e133c658db2e-160630083646/85/mpls-05-2-320.jpg)
mpls-05
- 1. MPLS-TE & OSPF R0.1 R0.2 R0.3 R0.4 F0/0 F0/0 F0/1 F0/1 F0/0 F0/0 20.0.0.0/30 20.0.0.4/30 20.0.0.8/30 Minimum configs – get OSPF Ready for MPLS-TE R1 – Loop 10.0.0.1 R2 – Loop 10.0.0.2 R3 – Loop 10.0.0.3 R4 – Loop 10.0.0.4 R1 - R4 router ospf 99 router-id 10.0.0.X log-adjacency-changes redistribute connected subnets network 0.0.0.0 255.255.255.255 area 0 OSPF Ready R1 – R4 ! mpls traffic-eng tunnels ! router ospf 99 mpls traffic-eng router-id Loopback0 mpls traffic-eng area 0 router-id 10.0.0.X log-adjacency-changes redistribute connected subnets network 0.0.0.0 255.255.255.255 area 0 MPLS-TE Ready Tunnel 4 Destination 10.0.0.4 Tunnel 1 Destination 10.0.0.1 MPLS-TE Make sure: OSPF Works “mpls te” statement included Next: Create / Setup Tunnel 4 destination 10.0.0.4
- 2. MPLS-TE & OSPF – Setting up Tunnels R0.1 R0.2 R0.3 R0.4 F0/0 F0/0 F0/1 F0/1 F0/0 F0/0 20.0.0.0/30 20.0.0.4/30 20.0.0.8/30 Tunnel 4 Destination 10.0.0.4 Tunnel 1 Destination 10.0.0.1 MPLS-TE R1 interface Tunnel4 description TE-R1-R4 ip unnumbered Loopback0 mpls traffic-eng tunnels tunnel destination 10.0.0.4 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 tunnel mpls traffic-eng bandwidth 500 tunnel mpls traffic-eng path-option 10 explicit name TE-R1-R4 tunnel mpls traffic-eng record-route no routing dynamic You will create an EXPLICIT PATH R1 ip explicit-path name TE-R1-R4 enable next-address 20.0.0.2 next-address 20.0.0.6 next-address 20.0.0.10 Create Explicit Path Next-HOP IP interface FastEthernet0/0 description R1-R2 ip address 20.0.0.1 255.255.255.252 mpls traffic-eng tunnels ip rsvp bandwidth 5000 5000 Make your outgoing interface participate in MPLS-TE Ip RSVP – very important, will explain later. Remind Me R1 – Tun4 Still Down because interfaces on R2-R4 NOT participating in MPLS-TE You MUST enable it on ALL interfaces INGRESS / EGRESS in Fa's R1 – R4 Example on R2 ! interface FastEthernet0/0 description R2-R1 ip address 20.0.0.2 255.255.255.252 mpls traffic-eng tunnels ip rsvp bandwidth 5000 5000 R1#show mpls traffic-eng tunnels tunnel 4 Name: TE-R1-R4 (Tunnel4) Destination: 10.0.0.4 Status: Admin: up Oper: down Path: not valid Signalling: Down path option 10, type explicit TE-R1-R4 … Prior LSP: ID: path option 10 [100] Removal Trigger: path verification failed Last Error: PCALC:: Explicit path has unknown address, 20.0.0.2 Err Message when the Tun is in a DOWN state
- 3. MPLS-TE & OSPF – Setting up Tunnels | some TE commands R0.1 R0.2 R0.3 R0.4 F0/0 F0/0 F0/1 F0/1 F0/0 F0/0 20.0.0.0/30 20.0.0.4/30 20.0.0.8/30 Tunnel 4 Destination 10.0.0.4 Tunnel 1 Destination 10.0.0.1 MPLS-TE R1#show mpls traffic-eng tunnels tunnel 4 Name: TE-R1-R4 (Tunnel4) Destination: 10.0.0.4 Status: Admin: up Oper: up Path: valid Signalling: connected path option 10, type explicit TE-R1-R4 (Basis for Setup, path weight 30) Config Parameters: Bandwidth: 500 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) AutoRoute: enabled LockDown: disabled Loadshare: 500 bw-based auto-bw: disabled InLabel : - OutLabel : FastEthernet0/0, 17 RSVP Signalling Info: Src 10.0.0.1, Dst 10.0.0.4, Tun_Id 4, Tun_Instance 124 RSVP Path Info: My Address: 20.0.0.1 Explicit Route: 20.0.0.2 20.0.0.5 20.0.0.6 20.0.0.9 20.0.0.10 10.0.0.4 Record Route: Tspec: ave rate=500 kbits, burst=1000 bytes, peak rate=500 kbits RSVP Resv Info: Record Route: 20.0.0.2 20.0.0.6 20.0.0.10 Fspec: ave rate=500 kbits, burst=1000 bytes, peak rate=500 kbits Shortest Unconstrained Path Info: Path Weight: 30 (TE) Explicit Route: 20.0.0.1 20.0.0.2 20.0.0.5 20.0.0.6 20.0.0.9 20.0.0.10 10.0.0.4 Called ERO It should tell you all the IP Address that participates with the “MPLS-TE” statement The ONLY PATH understood by our R1 router. No back up path is configured. We can configure one later. We specified our OWN BW in Tun4 Remember we did: On R2 ! interface FastEthernet0/0 description R2-R1 ip address 20.0.0.2 255.255.255.252 mpls traffic-eng tunnels ip rsvp bandwidth 5000 5000 ! Next Slide will demonstrate MORE
- 4. MPLS-TE & OSPF – Setting up Tunnels | IP RSVP R0.1 R0.2 R0.3 R0.4 F0/0 F0/0 F0/1 F0/1 F0/0 F0/0 20.0.0.0/30 20.0.0.4/30 20.0.0.8/30 Tunnel 4 Destination 10.0.0.4 Tunnel 1 Destination 10.0.0.1 MPLS-TER3#config terminal R3(config)#interface fa 0/0 R3(config-if)#no ip rsvp bandwidth 5000 5000 R3(config-if)#ip rsvp bandwidth 5000 5000 no ip rsvp xxxx MPLS-TE Tunnel is UNIDIRECTIONAL * It only knows how to FORWARD Traffic * The IP RSVP is ONLY concerned with OUTGOING/EGRESS traffic bandwidth. * Your TUN4 will received “signals” that Bandwidth is GONE / Non- existing if your OMIT it from the interface configs Demo below. R1# *Mar 1 02:28:40.383: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel4, changed state to down R3#configure terminal R3(config)#interface fa 0/1 R3(config-if)#no ip rsvp bandwidth 5000 5000 R1#show mpls traffic-eng tunnels tunnel 4 brief TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROT TE-R1-R4 10.0.0.4 - Fa0/0 up/up Still UP The reason for this is that Tun4 only cares about OUTGOING interfaces and whatever bandwidth it has to use. Tun4 does NOT care about INGREE MPLS-TE interfaces. It is UNIDIRECTIONAL. The same will happen on R2 interface FA0/1 when you remove the “ip rsvp” statement. i.e. R1-TUN4 will go DOWN MPLS-TE TU4 RSVP Interfaces participating are? R0.1 R0.2 R0.3 R0.4 RSVP sufficient BW? FA0/0 FA0/1 FA0/0 R3#config terminal R3(config)#interface fa 0/0 R3(config-if)#no ip rsvp bandwidth The “no” statement will Kill R1-Tun4X
- 5. MPLS-TE & OSPF – Setting up Tunnels | MPLS Back-UP / Alternate Route R0.1 R0.2 R0.3 R0.4 F0/0 F0/0 F0/1 F0/1 F0/0 F0/0 20.0.0.0/30 20.0.0.4/30 20.0.0.8/30 Tunnel 4 Destination 10.0.0.4 Tunnel 1 Destination 10.0.0.1 MPLS-TE 1. Enable interface R2 – fa1/0 30.0.0.1/30 2. Enable interface R4 – fa0/1 30.0.0.2/30 Ensure that interfaces participate in MPLS-TE mpls traffic-eng tunnels Ip rsvp bandwidth 3000 3000 You're almost done. Currently ONLY ONE explicit Route configured from R1-R4 We will configure a second router with “dynamic” feature. * Preferred Path is explicit TE-R1-R4 * Secondary is “dynamic” but less preferred even if it is shorter Note: of course we need another link or router – See diagram (right) F1/0 F0/1 30.0.0.0/30 3. Reconfigure R1 – Tun4 Add “backup” dynamic route R1 interface Tunnel4 description TE-R1-R4 ip unnumbered Loopback0 mpls traffic-eng tunnels tunnel destination 10.0.0.4 tunnel mode mpls traffic-eng tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 tunnel mpls traffic-eng bandwidth 500 tunnel mpls traffic-eng path-option 10 explicit name TE-R1-R4 tunnel mpls traffic-eng path-option 20 dynamic tunnel mpls traffic-eng record-route no routing dynamic R1#show mpls traffic-eng tunnels tunnel 4 … InLabel : - OutLabel : FastEthernet0/0, 16 RSVP Signalling Info: Src 10.0.0.1, Dst 10.0.0.4, Tun_Id 4, Tun_Instance 203 RSVP Path Info: My Address: 20.0.0.1 Explicit Route: 20.0.0.2 20.0.0.5 20.0.0.6 20.0.0.9 20.0.0.10 10.0.0.4 Record Route: Tspec: ave rate=500 kbits, burst=1000 bytes, peak rate=500 kbits RSVP Resv Info: Record Route: 20.0.0.2 20.0.0.6 20.0.0.10 Fspec: ave rate=500 kbits, burst=1000 bytes, peak rate=500 kbits Shortest Unconstrained Path Info: Path Weight: 11 (TE) Explicit Route: 20.0.0.1 20.0.0.2 30.0.0.1 30.0.0.2 10.0.0.4 Current ER0 Backup Dynamic If properly setup, turn down R2- F0/1 and watch the tun4 reroute to Backup/Dynamic link! Good Luck!
- 6. MPLS-TE & OSPF – Setting up Tunnels | MPLS Back-UP / Alternate Route - Repeat the same on R4 – Tun1 → R1 10.0.0.1/32 R0.1 R0.2 R0.3 R0.4 F0/0 F0/0 F0/1 F0/1 F0/0 F0/0 20.0.0.0/30 20.0.0.4/30 20.0.0.8/30 Tunnel 4 Destination 10.0.0.4 Tunnel 1 Destination 10.0.0.1 MPLS-TE Alright! We're done! You should take the time to repeat the same on R4 → R1 (10.0.0.1). This will keep traffic symmetrical. Returning traffic will not use the 30.0.0.0/30 network. Kjteoh – 14/02/2016 – Use this page for notes! F1/0 F0/1 30.0.0.0/30