F3215-HP Load Balancing Module Network Management Configuration Guide-6PW101
278
Ste
p
Command
Remarks
3. Enable MD5 authentication
for BGP peers.
peer { group-name | ip-address }
password { cipher | simple }
password
Not enabled by default.
Configuring BGP load balancing
If multiple BGP routes that have the same AS_PATH, ORIGIN, LOCAL_PREF, and MED attributes to a
destination exist, you can use the balance command to configure the maximum number of BGP routes for
load balancing to improve link utilization.
To configure BGP load balancing:
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Configure the maximum
number of BGP routes for load
balancing.
balance [ ebgp | ibgp ] number
By default, load balancing is not
enabled.
Forbidding session establishment with a peer or peer group
This task allows you to temporarily tear down the BGP session to a specific peer or peer group. To recover
the session, execute the undo peer ignore command. In this way, you can implement network upgrade
and maintenance without deleting and then configuring the peer or peer group.
To forbid session establishment with a peer or peer group:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Forbid session establishment
with a peer or peer group.
peer { group-name | ip-address }
ignore
Not forbidden by default.
Configuring BGP soft-reset
After you modify the route selection policy, you must reset BGP sessions to apply the new policy. The reset
operation tears down and re-establishes BGP sessions.
To avoid tearing down BGP sessions, you can use one of the following soft-reset methods to apply the
new policy:
• Enabling route-refresh—The BGP router advertises a route-refresh message to the specified peer
and the peer resends its routing information to the router. After receiving the routing information, the
router filters the routing information by using the new policy.
This method requires that both the local router and the peer support route refresh.
• Saving updates—Use the peer keep-all-routes command to save all route updates from the
specified peer. After modifying the route selection policy, filter routing information by using the new
policy.
This method does not require that the local router and the peer support route refresh but it uses
more memory resources to save routes.