Disabling Bgp Routing Policies From Automatically Taking Effect - HPE FlexNetwork HSR6800 Configuration Manual

Step
Enable BGP route refresh for
3.
a peer or peer group.
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.
Save all route updates from
3.
a peer or peer group.
Return to user view.
4.
Perform manual soft-reset
5.
on BGP sessions.
Disabling BGP routing policies from automatically
taking effect
During BGP network optimization or upgrade, each change of BGP routing policies triggers route
refreshing, which burdens BGP routers and the network.
This task disables the policies from automatically taking effect. After modifying all policies, execute
the refresh bgp or reset bgp command to make the new polices take effect.
The following shows BGP routing policies:
•
peer as-path-acl
•
peer filter-policy
•
peer ip-prefix
•
peer route-policy
•
filter-policy export
•
filter-policy import
•
peer default-route-advertise
Command
peer { group-name | ip-address }
capability-advertise
route-refresh
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
peer { group-name | ip-address }
keep-all-routes
return
refresh bgp { all | ip-address | group
group-name | external | internal }
{ export | import }
226
Remarks
Optional.
Enabled by default.
Remarks
N/A
Use either method.
Not saved by default.
N/A
N/A