Peer Next-Hop-Local - 3Com 3C13618 Command Reference Manual

Default IBGP peers will be added to the peer group, and it is unnecessary to
configure them. The configuration of the route update policy of any IBGP peer is valid
for other IBGP peers in the group. To be specific, if the router is not a reflector, then
all IBGP peers are in the same group; if the router is not a reflector, all the
route-reflect clients are in one group, and non-clients are in another.
The members of the external peer group must be in the same hop, otherwise some
EBGP peers may drop the route update packets that you have sent.
If no AS number is configured for a peer group, then AS numbers must be configured
for all the peers added to this group. If an AS is configured for the peer, then you must
not configure AS numbers (if configured) different from that for the peer group for all
the peers added to this group.
For the members in a peer group, you must not configure route update policies
different from that for the peer group, but can configure different route import policies.
Note: configure the peer group under the guidance of technical personnel.
Example
# Set a peer group named "test".
[3Com-bgp] peer test group

4.1.41 peer next-hop-local

Syntax
peer { group-name | peer-address} next-hop-local
undo peer { group-name | peer-address} next-hop-local
View
BGP view
Parameter
group-name: Group name.
peer-address: Peer's IP address.
Description
Using the peer next-hop-local command, you can enable the BGP processing of
next hop when sending a route to the peer and take the self-address as the next hop.
Routing Protocol
101