Configuring The Rate At Which Bgp4+ Updates Routes In Response To Non-Critical Iteration Changes - Huawei Quidway NetEngine80E Configuration Manual

HUAWEI NetEngine80E/40E Router
Configuration Guide - IP Routing
l
l
Procedure
l
l
----End
9.5.5 Configuring the Rate at which BGP4+ Updates Routes in
Response to Non-critical Iteration Changes
You can configure the rate at which BGP4+ updates routes in response to non-critical iteration
changes to prevent BGP4+ from occupying the Central Processing Unit (CPU) resource of other
protocols, reduce CPU loads, and ensure device reliability.
Context
In most cases, BGP4+ routes do not have directly reachable next hops, and route iteration must
be used. When many BGP4+ routes are iterated to one next hop and a non-critical iteration
Issue 02 (2014-09-30)
The ConnectRetry interval can be reduced in order to lessen the time BGP4+ waits to retry
establishing a TCP connection after the first attempt fails.
To suppress route flapping caused by constant peer flapping, the ConnectRetry interval can
be increased to speed up route convergence.
Set a ConnectRetry interval globally.
1. Run:
system-view
The system view is displayed.
2. Run:
bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
3. Run:
timer connect-retry connect-retry-time
A BGP4+ ConnectRetry interval is set globally.
By default, the ConnectRetry interval is 32s.
Set a ConnectRetry interval on a peer or peer group.
1. Run:
system-view
The system view is displayed.
2. Run:
bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
3. Run:
peer { group-name | ipv6-address } timer connect-retry connect-retry-time
A ConnectRetry interval is set on a peer or peer group.
By default, the ConnectRetry interval is 32s.
The ConnectRetry interval configured on a peer or peer group takes precedence over
a global ConnectRetry interval.
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
9 BGP4+ Configuration
1076