1-33
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
Configure the keepalive interval and
holdtime for a peer/peer group
peer
{
group-name |
ip-address
}
timer
keepalive
keepalive hold holdtime
Optional
By default, the keepalive
interval is 60 seconds,
and holdtime is 180
seconds.
z
The maximum keepalive interval should be one third of the holdtime and no less than 1 second.
The holdtime is no less than 3 seconds unless it is set to 0.
z
The intervals set with the
peer timer
command are preferred to those set with the
timer
command.
z
If the router has established a neighbor relationship with a peer, you need to 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, you have to reset BGP connections to make the new one take
effect, causing short time disconnection.
The current BGP implementation supports the route-refresh capability, with which, a router can
dynamically refresh its BGP routing table when the route selection policy is modified, 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.
Summary of Contents for S7906E - Switch
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist...
Page 598: ...ii...
Page 1757: ...4 9...
Page 1770: ...6 4...
Page 2017: ...2 11 Figure 2 3 SFTP client interface...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002...