Configuring manual soft-reset
If a BGP peer does not support route-refresh, you must save updates from the peer on the local
router by using the peer keep-all-routes command, and use the refresh bgp command to refresh
the BGP routing table.
If the BGP peer does not support route-refresh and the peer keep-all-routes command is not
configured on the local end, you must decide whether to manually disconnect the session with the
peer to learn routes again according to the impact of the new policy.
To save all route updates from a peer or peer group:
Step
Enter system view.
1.
Enter BGP view or
2.
BGP-VPN instance view.
Disable BGP route-refresh
3.
for a peer or peer group.
Save all route updates from
4.
a peer or peer group.
Return to user view.
5.
Perform manual soft-reset
6.
on BGP sessions.
Configuring a large scale BGP network
In a large-scale BGP network, configuration and maintenance may become difficult due to large
numbers of BGP peers. To facilitate configuration, you can configure peer group, community, route
reflector, or confederation as needed. For how to configure a peer group, see
peer
group."
Configuration prerequisites
Peering nodes are accessible to each other at the network layer.
Command
system-view
•
Enter BGP view:
bgp as-number
•
Enter BGP-VPN instance view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
•
Disable BGP route-refresh:
undo peer { group-name |
ip-address }
capability-advertise
route-refresh
•
Disable multi-protocol extension
capability:
peer { group-name |
ip-address }
capability-advertise
conventional
peer { group-name | ip-address }
keep-all-routes
return
refresh bgp { all | ip-address | group
group-name | external | internal }
{ export | import }
210
Remarks
N/A
Use either approach.
Use either approach.
By default, BGP route-refresh
and multi-protocol extension
capability is enabled for a peer
or peer group.
The peer
capability-advertise
conventional command is not
supported in BGP-VPN
instance view.
Not saved by default.
N/A
N/A
"Configuring a BGP