INE – MPLS Traffic Engineering

R2 and XR1 are preconfigured as PE routers for the MPLS L3VPN customer routers R1 and XR2, respectively, but the core of the Service Provider network is not running LDP.
Configure the core of the Service Provider network to support MPLS TE tunnels as follows:
Enable MPLS TE support for the IS-IS Level 2 core.
Set the IS-IS MPLS TE Router-ID to be the Loopback0 interfaces.
Enable support for RSVP and MPLS TE on all transit interfaces running IS-IS in the core.
Configure an MPLS TE tunnel from R2 to XR1 as follows:
Unnumber the tunnel to R2’s Loopback0 interface.
Set the tunnel destination as XR1’s Loopback0 interface.
Set the tunnel’s path option to dynamic.
Configure Autoroute Announce on the tunnel so that the IS-IS core can use it for dynamic routing.
Configure an MPLS TE tunnel from XR1 to R2 as follows:
Unnumber the tunnel to XR1’s Loopback0 interface.
Set the tunnel destination as R2’s Loopback0 interface.
Set the tunnel’s path option to dynamic.
Configure Autoroute Announce on the tunnel so that the IS-IS core can use it for dynamic routing.
When complete, the following reachability should be achieved:
R1 and XR2 should have full IP reachability to each other, and a traceroute should indicate that their L3VPN tunnel is transiting over the MPLS TE tunnels in the core of the SP network.