Enablement of GR reset bgp session or IGP session?

Procedure

1. Run system-view

   
   

   The system view is displayed.

   
   

2. Run bgp as-number

   
   

   The BGP view is displayed.

   
   

3. Run graceful-restart

   
   

   BGP GR is enabled.

   
   

4. (Optional) Run graceful-restart timer restart time

   
   

   The maximum time for the local end to wait for GR recovery of the peer is set.

   
   

5. (Optional) Run the ipv4-family flow command to enter the BGP-Flow IPv4 address family view, run the ipv4-flow vpn-instance command to enter the BGP-Flow VPN instance IPv4 address family view, run the ipv4-flow vpnv4 command to enter the BGP-Flow VPNv4 address family view, run the ipv6-family flow command to enter the BGP-Flow IPv6 address family view, or run the ipv6-flow vpn-instance command to enter the BGP-Flow VPN instance IPv6 address family view, and then run the peer { ipv4-address | ipv6-address } graceful-restart static-timer restart-time command to configure the maximum time for the local end to wait for GR recovery of the peer.

   
   

    NOTE:

   ipv6-address takes effect only in BGP-Flow IPv6 address family view and BGP-Flow VPN instance IPv6 address family view.

   
   

6. (Optional) Run graceful-restart peer-reset

   
   

   The router is enabled to reset a BGP session in GR mode.

   Currently, BGP does not support dynamic capability negotiation. As a result, each time the BGP capability changes, the BGP peer relationship is re-established. In some scenarios where a BGP IPv4 unicast peer relationship is established and IPv4 services are running, if the BGP capability changes, the BGP IPv4 unicast peer relationship will be re-established. This process will interrupt ongoing IPv4 services. To prevent the service interruptions, run the graceful-restart peer-reset command to enable the router to reset a BGP session in GR mode.

   
   

7. Run commit

   
   

   The configuration is committed.