Projects › MPLS Traffic Engineering with RSVP-TE and Fast Reroute
MPLS Traffic Engineering with RSVP-TE and Fast Reroute
A carrier's backbone has four routers in a square: PE1, P1, P2 and PE2, with PE1-P1-PE2 the shortest path (10 Gb/s links) and PE1-P2-PE2 the longer one. A new 4 Gb/s video contract from PE1 to PE2 would overload the shortest path at peak while the other path sits nearly idle. Design MPLS-TE: OSPF-TE flooding, RSVP bandwidth on every core link, a 4 Gb/s tunnel from PE1 to PE2 placed by CSPF, and Fast Reroute protecting the PE1-P1 link with a backup tunnel via P2. Loopback0 is 10.255.0.1 on PE1, .2 on P1, .3 on P2 and .4 on PE2. The four routers are on the canvas with their links addressed; the OSPF underlay the tunnels ride on is yours to build there.
Difficulty: advanced · Time: about 80 minutes
Why it matters
Shortest-path routing puts all traffic on the best path and leaves the rest idle. MPLS-TE places traffic by bandwidth and repairs a failed link locally, in the time it takes to detect the failure, rather than waiting for the network to reconverge. It is core service-provider material.
Technologies
- MPLS-TE
- RSVP-TE
- Fast Reroute (FRR)
- CSPF
- Tunnel Interfaces
Related projects
- Dual-Homed eBGP Edge Routing with AS-Path Prepending
- Service Provider MPLS L3VPN for Two Overlapping Customers
- DDoS Mitigation with BGP Flowspec at a Regional ISP
- Replacing LDP with Segment Routing (SR-MPLS) in a Six-Router Core
- Advanced BGP Traffic Engineering with Standard & Extended Communities
- Junos eBGP Peering at a Regional Internet Exchange
- Arista EOS eBGP Between Two Business Units After a Merger
- Arista EOS BGP Prefix Advertisement to an Upstream Provider