BGP4+ soft reset allows the system to refresh a BGP4+ routing table dynamically without tearing down any BGP4+ connection if routing policies are changed.
Procedure
- Enable the route-refresh capability.
Perform the following steps on a BGP4+ device:
- Run system-view
The system view is displayed.
- Run bgp as-number
The BGP view is displayed.
- Run peer { ipv4-address | ipv6-address | group-name } capability-advertise route-refresh
The route-refresh capability is enabled.
If the route-refresh capability has been enabled on all BGP4+ routers and a BGP4+ routing policy is changed, the local router sends route-refresh messages to its peers. After receiving the messages, the peers resend their routing information to the local router. Based on the received routing information, the local router can refresh its BGP4+ routing table dynamically and apply the new routing policy, without tearing down any BGP4+ connections.
- Run commit
The configuration is committed.
- Configure a BGP4+ device to store all the routing updates received from its peers.
Perform the following steps on a BGP4+ device:
- Run system-view
The system view is displayed.
- Run bgp as-number
The BGP view is displayed.
- Run ipv6-family unicast
The IPv6 unicast address family view is displayed.
- Run peer { ipv4-address | ipv6-address | group-name } keep-all-routes
The device is configured to store all routing updates received from its peers.
After this command is used, all routing updates sent by a specified peer are stored, regardless of whether a filtering policy is used. When the local routing policy is changed, the routing updates can be used to regenerate BGP4+ routes.
- Run commit
The configuration is committed.
- Softly reset a BGP4+ connection.
Perform the following steps on a BGP4+ device:
- Run refresh bgp ipv6 { all | ipv4-address | ipv6-address | group group-name | external | internal } { export | import }
A BGP4+ connection is softly reset.
A BGP4+ connection must be softly reset in the user view.