MPLS TE

In the past i have done VPN tunnels & GRE tunnels, but MPLS TE tunnel…..now thats something new for me.
Unlike the above where you set up the source and the destination and point them to each other, with traffic engineering tunnels you only configure the source router with the destination information. TE tunnels configured on routers are unidirectional!
The four main messages used in implementation of RSVP for TE are:

RSVP PATH -Generated by the headend router and is forwarded through the network along the path of a future TE LSP.

RSVP RESERVATION – Created by the tailend router in the MPLS TE domain and used to confirm the reservation request that was sent earlier with the PATH messages.

RSVP ERROR – In the event of unavailability of the requested resources, the router generates RSVP error messages and sends them to the router from which the request or reply was received.

RSVP TEAR – RSVP creates two types of tear messages, namely, the PATH tear message and the RESERVATION tear message. These tear messages clear the PATH or RESERVATION states on the router instantaneously.

This is how i set up my lab.

The rules.
You must use OSPF or IS-IS (under the RP enable MPLS traffic-eng too)
You must enable each router for IP CEF, MPLS IP & MPLS traffic-eng tunnels
You must enable each router with MPLS IP, MPLS traffic-eng tunnels & ip rsvp bandwidth

From PE1

interface Tunnel1
ip unnumbered Loopback0
tunnel destination 2.2.2.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 7 7
tunnel mpls traffic-eng bandwidth 50
tunnel mpls traffic-eng path-option 1 explicit name high
tunnel mpls traffic-eng path-option 2 dynamic
!
interface Tunnel2
ip unnumbered Loopback0
tunnel destination 2.2.2.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 50
tunnel mpls traffic-eng path-option 1 explicit name low
tunnel mpls traffic-eng path-option 2 dynamic

ip explicit-path name high enable
next-address 192.168.12.1
next-address 192.168.12.2
next-address 192.168.23.3
!
ip explicit-path name low enable
next-address 192.168.21.1
next-address 192.168.21.2
next-address 192.168.16.2

Here we see both the tunnels up, note that i have ran this cmd on the head end (source end) as it tells you on the bottom line. 🙂 Nice.
PE1#sh mpls traffic-eng tunnels brief
Signalling Summary:
LSP Tunnels Process: running
RSVP Process: running
Forwarding: enabled
Periodic reoptimization: every 3600 seconds, next in 3350 seconds
Periodic auto-bw collection: disabled
TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROT
PE1_t1 2.2.2.2 - Se0/1 up/up
PE1_t2 2.2.2.2 - Fa0/0 up/up
Displayed 2 (of 2) heads, 0 (of 0) midpoints, 0 (of 0) tails

BE.

Advertisements

~ by bigevil on November 15, 2010.

 
%d bloggers like this: