Iteration of Public IP Addresses to an SR Tunnel
Iteration of Public BGP Routes to an SR Tunnel
If an Internet user uses a carrier network that performs IP forwarding to access the Internet, core carrier devices on the forwarding path need to learn a large number of Internet routes. This imposes a heavy load on core carrier devices and affects the performance of these devices. To solve this problem, you can enable access devices to iterate non-labeled public BGP routes or non-labeled static routes to an SR tunnel so that users can access the Internet through the SR tunnel. The iteration to the SR tunnel prevents the problems induced by insufficient performance, heavy burdens, and service transmission on the core devices on the carrier network.
- Set up a BGP peer relationship on PEs to learn routes to each other.
- Deploy IS-IS and SR on PEs and Ps in an end-to-end manner.
- Iterate BGP service routes to the SR tunnel on PEs.
Iteration of Static Routes to an SR Tunnel
A static route needs to be iterated if its next hop is not directly reachable. If static routes can be iterated to an SR tunnel, label forwarding can be performed.
- Configure a static route on PE1 and specify the next hop as the loopback interface address of PE2.
- Establish an SR tunnel between PE1 and PE2 that the loopback interface address of PE2 is configured as the destination address.
- Encapsulate the label after an IP packet is received and forward the IP packet through the SR tunnel.