After changing a BGP import policy, you must reset BGP connections for the new import policy to take effect. This, however, interrupts the BGP connections temporarily. BGP route-refresh allows the system to softly reset BGP connections to refresh a BGP routing table without tearing down any BGP connection. If a device's peer does not support route-refresh, configure the device to retain all routing updates received from the peer so that the device can refresh its routing table without tearing down the BGP connection with the peer.
The system view is displayed.
The BGP view is displayed.
(Optional) Run peer { ipv4-address | group-name } capability-advertise route-refresh
Or run peer ipv6-address capability-advertise { 4-byte-as | route-refresh }
Route-refresh is enabled.
By default, route-refresh is enabled.
Return to the system view.
Return to the user view.
Or run refresh bgp ipv6 { all | group group-name | ipv4-address | ipv6-address | external | internal } { export | import }
BGP soft reset is configured.
The system view is displayed.
The BGP view is displayed.
Enter the corresponding address family view based on network type to configure BGP devices on networks.
Run ipv4-family { unicast | multicast }
The IPv4 address family view is displayed.
Run ipv6-family [ unicast ]
The IPv6 address family view is displayed.
If the peer keep-all-routes command is used on the device for the first time, the sessions between the device and its peers are reestablished.
The refresh bgp command takes effect when the peer keep-all-routes command is used on the device supporting route-refresh.
Run peer { ipv4-address | group-name | ipv6-address } keep-all-routes
The device is configured to store all the routing updates received from its peers or peer groups.
By default, the device stores only the routing updates that are received from peers or peer groups and match a configured import policy.