Sometimes it may be observed that a virtual chassis, which consists of two QFX5100 member devices, is not able to reboot either members because of the "ISSU in progress" message.
This article explains what must be done so that the virtual chassis can successfully reboot its member devices.
A virtual chassis, which consists of two QFX5100 member devices, is not able to reboot either members because of the "ISSU in progress" message. This is seen when trying to reboot member 0 or member 1. Although ISSU is not being initiated, this message is preventing the virtual chassis from rebooting either members.
{master:0} root@QFX5100-VC> show version | match "Model|^Junos:|local|fpc" localre: -------------------------------------------------------------------------- Model: qfx5100e-48s-6q Junos: 17.3R3.10 fpc1: -------------------------------------------------------------------------- Model: qfx5100e-48s-6q Junos: 17.3R3.10 {master:0} root@QFX5100-VC> show virtual-chassis Preprovisioned Virtual Chassis Virtual Chassis ID: d9fa.0ffe.f79b Virtual Chassis Mode: Enabled Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 0 (FPC 0) Prsnt TA3715440058 qfx5100e-48s-6q 129 Master* N VC 1 vcp-255/0/48 1 vcp-255/0/50 1 (FPC 1) Prsnt TA3715440048 qfx5100e-48s-6q 129 Backup N VC 0 vcp-255/0/48 0 vcp-255/0/50 {master:0} root@QFX5100-VC> request system reboot member 1 warning: ISSU in progress {master:0} root@QFX5100-VC> request system reboot member 0 warning: ISSU in progress
Both non-stop routing and graceful switchover are enabled, and the VC is ready for a Routing Engine switchover:
{master:0} root@QFX5100-VC> request session member 1 Last login: Tue Dec 11 14:32:27 from 172.17.31.80 --- JUNOS 17.3R3.10 Kernel 64-bit JNPR-10.3-20180615.4674357_buil root@QFX5100-VC:BK:1% cli {backup:1} root@QFX5100-VC> show system switchover localre: -------------------------------------------------------------------------- Graceful switchover: On Configuration database: Ready Kernel database: Synchronizing
When performing ISSU upgrade, a flag is set. In this case, the flag has not been cleared, so the system thinks that ISSU is still in progress, which prevents the device from rebooting.
Resetting the ISSU flag will resolve this problem:
{master:0} root@QFX5100-VC> start shell root@QFX5100-VC:RE:0% sysctl hw.re.issu_state hw.re.issu_state: 64
To resolve this problem, reset the ISSU flag to 0:
{master:0} root@QFX5100-VC> start shell root@QFX5100-VC:RE:0% sysctl -w hw.re.issu_state=0 hw.re.issu_state: 64 -> 0 root@QFX5100-VC:RE:0% cli {master:0} root@QFX5100-VC> {master:0} root@QFX5100-VC> request system reboot member 1 Reboot the system ? [yes,no] (no) yes Rebooting fpc1 *** System shutdown message from root@QFX5100-VC *** System going down in 1 minute