Choose an RSVP-TE path and verify forwarding This lab compares the ordinary shortest route with a traffic-engineered tunnel across three IOS XR routers. Without a tunnel, traffic goes directly from HEAD to TAIL; the transit router MID is not on that path. OSPF neighbours are established, and traffic engineering is enabled in the same area on all three routers. RSVP can reserve one thousand kilobits per second through MID, but only one hundred on the direct link. On HEAD, create tunnel interface fifteen hundred and use Loopback zero as its unnumbered source. Set the remote loopback as the destination, select a dynamic path and request five hundred kilobits per second. Enable autoroute announce and commit the configuration so eligible OSPF traffic can use the tunnel. The tunnel is operational, and its selected path goes through MID because the direct link cannot satisfy the bandwidth request. The route now names the tunnel, while the MPLS forwarding table on MID contains its transit label. Send traffic to the remote loopback, then inspect the forwarding table again to see the switched byte counter increase. Traceroute also follows MID, confirming that packets take the traffic-engineered path. Now shut the link from HEAD to MID; the tunnel goes down because the remaining path has insufficient reservable bandwidth. Ordinary IP routing still reaches TAIL over the direct link, so underlay reachability alone does not prove the tunnel is up. Restore the link and the tunnel recovers through MID; verify the path and successful traffic again. This walkthrough uses a single-area dynamic IPv4 tunnel with bandwidth admission and autoroute, without fast reroute or priority preemption.