l
When advertising a route to an EBGP peer, a BGP speaker sets the Next_Hop of the route
to the address of the local interface through which the BGP peer relationship is established.
l
When advertising a locally generated route to an IBGP peer, a BGP speaker sets the
Next_Hop of the route to the address of the local interface through which the BGP peer
relationship is established.
l
When advertising a route learned from an EBGP peer to an IBGP peer, the BGP speaker
does not modify the Next_Hop of the route.
Modifying the Next_Hop
In some scenarios, the Next_Hop needs to be modified.
Next_Hop needs to be modified in specific scenarios.
Table 8-14
Next_Hop processing
Objectives
Command
Usage Scenarios
Remarks
To enable an
ASBR to
modify the
Next_Hops of
the routes to be
advertised to
IBGP peers.
peer
{
ipv4-address
|
group-name
}
next-
hop-local
By default, when an ASBR
forwards a route learned
from an EBGP peer to its
IBGP peers, the ASBR
does not change the
Next_Hop of the route.
Therefore, the Next_Hop
address of the route
remains the EBGP peer IP
address. After being
forwarded to the IBGP
peers, the route cannot
become active as the
Next_Hop is unreachable.
To address this issue,
configure the ASBR to
modify the Next_Hop of
the route to the local IP
address before advertising
the route to IBGP peers.
After being forwarded to
the IBGP peers, the route
can be active because the
Next_Hop is reachable (an
IGP is configured in the
AS).
If BGP load
balancing has been
configured using the
maximum load-
balancing
number
command, the router
modifies the
Next_Hop of each
route to the local IP
address through
which the IBGP peer
relationship is
established before it
advertises the route
to IBGP peers,
regardless of whether
the
peer next-hop-
local
command is
configured. For
details, see
.
HUAWEI NetEngine80E/40E Router
Configuration Guide - IP Routing
8 BGP Configuration
Issue 02 (2014-09-30)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
897
