Usage Scenario
In an inter-AS VPN Option C scenario where VPNv4 RRs are deployed, the peer next-hop-invariable command needs to be run on the RRs to prevent them from changing the next hop address of a route before they advertises the route to a peer. This ensures that the remote PE can implement recursion to the LSP to the local PE during traffic transmission.
If the
peer next-hop-invariable include-static-route command is run, the BGP speaker retains the original next hop address of an imported public network static route when advertising the route to an IBGP peer under the condition that the original next hop address is valid; if the original next hop address of the public network static route is invalid, the next hop of the public network static route belongs to a VPN instance, or the public network static route is imported from a VPN instance, the BGP speaker uses its interface address as the next hop of the route.
If the
peer next-hop-invariable include-unicast-route command is run, the BGP speaker does not change the next hop address when advertising to an EBGP peer the unicast routes learned from another peer.
Prerequisites
The peer as-number command has been used to create a peer.
Precautions
The peer next-hop-invariable command without the include-static-route keyword configured takes effect only on received routes. In the IPv4 unicast address family view, this command takes effect only on received labeled IPv4 unicast routes, not on the routes that do not carry labels.
After the
peer next-hop-invariable include-static-route command is run, you can run the
undo peer next-hop-invariable command to restore the default configuration or run the peer next-hop-invariable [ include-unicast-route ] command to override the previous configuration.
After the
peer next-hop-invariable include-unicast-route command is run, you can run the
undo peer next-hop-invariable command to restore the default configuration or run the peer next-hop-invariable [ include-static-route ] command to override the previous configuration.
When routes are advertised to IBGP peers, the
peer next-hop-invariable command and the
peer next-hop-local command are mutually exclusive.