MBGP soft resetting allows the system to refresh an MBGP routing table dynamically without tearing down any MBGP connection if routing policies are changed.
Procedure
- Enable the route-refresh capability.
Perform the following steps on an MBGP 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 | 4-byte-as }
The route-refresh capability is enabled.
If all MBGP routers are enabled with the route-refresh capability and an MBGP routing policy changes, the local router sends route-refresh messages to its peers. After receiving the messages, these peers resend their routing information to the local router. Based on the received routing information, the local router refreshes its MBGP routing table dynamically and applies the new policy, without tearing down any MBGP connections.
- Run commit
The configuration is committed.
- Configure an MBGP device to store all routing updates received from its peers.
Perform the following steps on an MBGP router:
- Run system-view
The system view is displayed.
- Run bgp as-number
The BGP view is displayed.
- Run ipv4-family multicast
The BGP-IPv4 multicast 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 route updates sent by a specified peer are stored, regardless of whether a filtering policy is used. When the local routing policy changes, the route updates can be used to regenerate MBGP routes.
- Run commit
The configuration is committed.
- Softly reset an MBGP connection.
Perform the following steps on an MBGP device:
- Run refresh bgp { all | ipv4-address | ipv6 ipv6-address | group group-name | external | internal } { export | import }
An MBGP connection is softly reset.
This command can be run only in the user view.