R3166-R3206-HP High-End Firewalls Network Management Configuration Guide-6PW101

343
Configuring BGP keepalive interval and holdtime
After establishing a BGP connection, two routers send keepalive messages periodically to each other to
keep the connection. If a router receives no keepalive or update message from the peer within the
holdtime, it tears down the connection.
If the holdtime settings on the local and peer routers are different, the smaller one is used.
Follow these steps to configure BGP keepalive interval and holdtime:
To do… Use the command…
Remarks
Enter system view system-view
—
Enter BGP view bgp as-number
—
Configure the global keepalive interval
and holdtime
timer keepalive keepalive hold
holdtime
Optional
By default, the keepalive
interval is 60 seconds, and
holdtime is 180 seconds.
Configure the keepalive interval and
holdtime for a peer/peer group
peer { group-name | ip-address }
timer keepalive keepalive hold
holdtime
CAUTION:
• The maximum keepalive interval should be one third of the holdtime and no less than one second. The
holdtime is no less than three seconds unless it is set to 0.
• The intervals set with the peer timer command are preferred to those set with the timer command.
• If the router has established a neighbor relationship with a peer, you must reset the BGP connection to
validate the new set timers.
Configuring the interval for sending the same update
Follow these steps to configure the interval for sending the same update to a peer/peer group:
To do… Use the command…
Remarks
Enter system view system-view
—
Enter BGP view bgp as-number
—
Configure the interval for
sending the same update
to a peer/peer group
peer { group-name | ip-address }
route-update-interval interval
Optional
The intervals for sending the same
update to an iBGP peer and an eBGP
peer default to 15 seconds and 30
seconds respectively.
Configuring BGP soft-reset
After modifying a route selection policy, reset BGP connections to make the new one take effect.
The current BGP implementation supports the route-refresh capability that enables dynamic route refresh
without tearing down BGP connections. If a BGP peer does not support route-refresh, you need to save
updates from the peer on the local router. After that, when a route selection policy is modified, the router
can refresh its BGP routing table by using such updates without tearing down BGP connections.
1. Configure automatic soft-reset
After route refresh is enabled for peers and then a policy is modified, the router advertises a route-refresh
message to the peers, which then resend their routing information to the router. After receiving the routing
information, the router can perform dynamic route update by using the new policy.