F3726, F3211, F3174, R5135, R3816-HP Firewalls and UTM Devices Network Management Configuration Guide-6PW100

497
2. Saving updates
To save all route updates from a peer or peer group:
Ste
p
Command Remarks
602. Enter system view.
system-view
N/A
603. Enter BGP view or BGP-VPN
instance view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN instance view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
Use either approach.
604. Save all route updates from a
peer or peer group.
peer { group-name | ip-address }
keep-all-routes
Not saved by default.
3. Configuring manual soft-reset
If the BGP peer does not support route refresh and the peer keep-all-routes command is not
configured on the local router, determine whether to manually disconnect the session with the peer
according to the impact of the new policy.
To configure manual soft-reset:
Ste
p
Command Remarks
605. Enter system view.
system-view N/A
606. Enter BGP view or BGP-VPN
view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
Use either approach.
607. Enable BGP route refresh for a
peer or peer group.
peer { group-name | ip-address }
capability-advertise route-refresh
By default, BGP route
refresh is enabled.
608. Return to user view.
return N/A
609. Perform manual soft-reset.
efresh bgp { all | ip-address | group
group-name | external | internal }
{ export | import }
N/A
714BConfiguring a large scale BGP network
In a large-scale BGP network, configuration and maintenance might 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 "
2698HConfiguring a BGP peer
group."
1513BConfiguration prerequisites
Peering nodes are accessible to each other at the network layer.