Objectives
The simulator ticks each one as soon as the network meets it.
Find why Tunnel1 is down (show mpls traffic-eng tunnels on PE1).
Fix explicit path BOTTOM: after 10.0.13.2 (P2) it must go to 10.0.34.2 (P3) and then 10.0.45.2 (PE2), every hop strict.
Find the next fault and enable RSVP with 1000000 kbps on P3’s link to PE2 (g0/1).
Tunnel1 comes up on path option 1 through P2 and P3.
Ping 5.5.5.5 from PE1 through the tunnel.
Before you start
A strict hop that is not adjacent to the previous one, a link without RSVP, or a link without enough bandwidth each stop the tunnel. show mpls traffic-eng tunnels prints the last error of every path option; show ip rsvp interface and show ip explicit-paths show what each router has configured.
Concept
RSVP-TE: signalling the tunnel hop by hop
Once CSPF has a path, RSVP-TE builds the label-switched path along it. The head end sends a Path message carrying the explicit route and the bandwidth; the tail end answers with a Resv message that reserves the bandwidth and hands out labels on the way back.
Concept
Explicit paths and path options
A tunnel lists path options in order. A dynamic option lets CSPF choose; an explicit option names the hops the tunnel must take. Strict hops must be directly connected to the previous hop; loose hops can be reached over any TE path. The first option that can be signalled carries the tunnel.
