290
3. Enable BGP route refresh for
a peer or peer group.
• Enable BGP route refresh for
the specified peer or peer
group:
peer { group-name |
ipv4-address [ mask-length ] |
ipv6-address
[ prefix-length ] }
capability-advertise
route-refresh
• Enable the BGP route
refresh, multi-protocol
extension, and 4-byte AS
number features for the
specified peer or peer group:
undo peer { group-name |
ipv4-address [ mask-length ] |
ipv6-address
[ prefix-length ] }
capability-advertise
conventional
By default, the BGP route refresh,
multi-protocol extension, and
4-byte AS number features are
enabled.
4. Return to user view.
return
N/A
5. Perform manual soft-reset.
refresh bgp
[
instance
instance-name ] { ipv4-address
[ mask-length ] | ipv6-address
[ prefix-length ] |
all
|
external
|
group
group-name |
internal
}
{
export
|
import
}
link-state
N/A
Protecting an EBGP peer when memory usage reaches level
2 threshold
Memory usage includes the following threshold levels: normal, level 1, level 2, and level 3. When the
level 2 threshold is reached, BGP periodically tears down an EBGP session to release memory
resources until the memory usage falls below the level 2 threshold. You can configure this feature to
avoid tearing down the EBGP session to an EBGP peer when the memory usage reaches the level 2
threshold.
For more information about memory usage thresholds, see Fundamentals Configuration Guide.
To configure BGP to protect an EBGP peer or peer group when the memory usage reaches level 2
threshold (IPv4 unicast/multicast address family):
1. Enter system view.
system-view
N/A
2. Enter BGP instance view or
BGP-VPN instance view.
• Enter BGP instance view:
bgp as-number [ instance
instance-name ]
• Enter BGP-VPN instance
view:
a. bgp as-number
[ instance
instance-name ]
b. ip vpn-instance
N/A