Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Performing an In-Service Software Reboot

You can perform an in-service software reboot (ISSR) by following these steps.

Note:

We recommend that you wait at least five minutes between in-service software reboots.

When you request an in-service software reboot (ISSR) on a standalone device:

  1. The management process (MGD) verifies that graceful restart (GR) or non-stop routing and graceful Routing Engine switchover (GRES) are enabled.

  2. The ISSU state machine spawns the backup Routing Engine (RE) with the existing software version.

  3. The ISSU state machine checks to see if the backup RE has synchronized all of the data with the primary RE.

  4. The ISSU state machine requests the routing protocol process (RPD) to notify its readiness for switchover.

  5. RPD initiates the GR or non-stop routing procedures by notifying all of the registered protocols.

  6. RPD notifies the ISSU state machine that its ready for switchover.

  7. The primary role is switched between the REs, so the backup RE becomes the primary RE.

  8. The old primary RE is shut down.

  9. RPD is spawned on the new primary and continues the GR or non-stop routing procedure and exits either GR or non-stop routing after the protocol state synchronizes.

To perform an ISSR:

Issue the request system reboot in-service command.

For example:

Related Documentation