Configuring BGP4+ Soft Resetting

When routing policies are changed, the system can refresh the BGP4+ routing table dynamically without interrupting BGP4+ connections.

Procedure

Enable the route-refresh capability.
1. Access the system view.
  system-view
2. Access the BGP view.
  bgp { as-number-plain | as-number-dot }
3. Enable the route-refresh capability.
  peer { ipv4-address | ipv6-address | group-name } capability-advertise route-refresh
  
  By default, the route-refresh capability is enabled.
  
  If the route-refresh capability is enabled on all the BGP4+ devices, the local device advertises the route-refresh messages to its peer if the BGP4+ route policies change. The peer receiving this message sends its routing information to the local device again. In this way, the BGP4+ routing table is updated dynamically and the new policies are applied without interrupting the BGP4+ connections.
Keep all the routing updates of the peers.
1. Access the system view.
  system-view
2. Access the BGP view.
  bgp { as-number-plain | as-number-dot }
3. Access the BGP IPv6 unicast address family view.
  ipv6-family [ unicast ]
4. Keep all route updates of the peers.
  peer { ipv4-address | ipv6-address | group-name } keep-all-routes
  
  After this command is run, all the route updates of the specified peer are kept regardless of whether the filtering policies are used. When the BGP connections are soft reset, this information can be used to generate the BGP4+ routes.
Soft reset a BGP4+ connection.
1. Soft reset a BGP4+ connection.
  refresh bgp ipv6 { all | ipv4-address | ipv6-address | group group-name | external | internal } { export | import }
  
  A BGP4+ connection must be soft reset in the user view.