200
next hop by default. However, you can configure Router B to set it (1.1.1.2/24) as the next hop for routes
sent to Router A by using the peer next-hop-local command as needed.
Figure 55 NEXT_HOP attribute configuration
IMPORTANT:
If you have configured BGP load balancing, the router sets itself as the next hop for routes sent to an IBGP
peer or peer group regardless of whether the peer next-hop-local command is configured.
To configure the NEXT_HOP attribute (IPv4):
Ste
Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view or BGP-VPN
instance view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN instance view:
a. bgp as-number
b. ip vpn-instance
vpn-instance-name
N/A
3. Enter BGP IPv4 unicast
instance view or BGP-VPN
IPv4 unicast instance view.
ipv4-family [ unicast ] N/A
4. Specify the router as the next
hop for routes sent to a peer
or peer group.
peer { group-name | ip-address }
next-hop-local
By default, the router sets itself as
the next hop for routes sent to an
EBGP peer or peer group, but does
not set itself as the next hop for
routes sent to an IBGP peer or peer
group.
To configure the NEXT_HOP attribute (IPv6):
Ste