F3215-HP Load Balancing Module Network Management Configuration Guide-6PW101

272
Figure 161 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:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Specify the router as the next
hop of routes sent to a peer or
peer group.
peer { group-name | ip-address }
next-hop-local
Optional.
By default, the router sets it as the
next hop for routes sent to an EBGP
peer or peer group, but does not
set it as the next hop for routes sent
to an IBGP peer or peer group.
Configuring the AS_PATH attribute
1. Permitting local AS number to appear in routes from a peer or peer group
In general, BGP checks whether the AS_PATH attribute of a route from a peer contains the local AS
number. If so, it discards the route to avoid routing loops.
However, in certain network environments, the AS_PATH attribute of a route from a peer must be allowed
to contain the local AS number; otherwise, the route cannot be advertised correctly.
To permit local AS number to appear in routes from a peer or peer group and specify the appearance
times.
Ste
p
Command Remarks
1. Enter system view.
system-view
N/A
2. Enter BGP view.
bgp as-number N/A
3. Permit local AS number to
appear in routes from a peer
or peer group and specify the
appearance times.
peer { group-name | ip-address }
allow-as-loop [ number ]
Optional.
By default, the local AS number is
not allowed to appear in routes
from a peer or peer group.
2. Disabling BGP from considering AS_PATH during best route selection