Configuring The Bgp Next Hop Delayed Response - Huawei Quidway NetEngine80E Configuration Manual

HUAWEI NetEngine80E/40E Router
Configuration Guide - IP Routing
Last keepalive sent
Last update
Last update
Minimum route advertisement interval is 15 seconds
Optional capabilities:
Route refresh capability has been enabled
4-byte-as capability has been enabled
Peer Preferred Value: 0
Routing policy configured:
No routing policy is configured
Path MTU discovery has been configured

8.19 Configuring the BGP Next Hop Delayed Response

Configuring the BGP next hop delayed response can minimize traffic loss during route changes.
Context
Configuring the BGP next hop delayed response can speed up BGP route convergence and
minimize traffic loss.
As shown in
PE1 and PE2. PE1 and PE2 advertise their routes to CE2 to the RR. The RR advertises the route
from PE1 to PE3. PE3 has a route to CE2 only and advertises this route to CE1. After the route
exchange, CE1 and CE2 can communicate. If PE1 fails, PE3 detects that the next hop is
unreachable and instructs CE1 to delete the route to CE2. Traffic is interrupted. After BGP route
convergence is complete, the RR selects the route advertised by PE2 and sends a route update
message to PE3. PE3 then advertises this route to CE1, and traffic forwarding is restored to the
normal state. A high volume of traffic will be lost during traffic interruption because BGP route
convergence is rather slow.
If the BGP next hop delayed response is enabled on PE3, PE3 does not reselect a route or instruct
CE1 to delete the route to CE2 immediately after detecting that the route to PE1 is unreachable.
After BGP convergence is complete, the RR selects the route advertised by PE2 and sends the
route to PE3. PE3 then reselects a route and sends a route update message to CE1. Traffic
forwarding is restored to the normal state. After the BGP next hop delayed response is enabled
on PE3, PE3 does not need to delete the route or instruct CE1 to delete the route. This delayed
response speeds up BGP route convergence and minimizes traffic loss.
Issue 02 (2014-09-30)
received: 2012-03-06 19:17:43 UTC-8:00
sent
NOTE
The message of Path MTU discovery has been configured will be displayed only after the display bgp
peer ipv4-address verbose command is run on the router where path MTU auto discovery has been enabled.
Figure 8-6, PE1, PE2, and PE3 are the clients of the RR. CE2 is dual-homed to
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
: 2012-03-06 19:17:37 UTC-8:00
: 2012-03-06 19:17:37 UTC-8:00
8 BGP Configuration
852