This article described how to locate the ISSU Aborted reason and how to prevent failover of all RGs to node 1 failed.
[Aug 23 01:31:34]: Secondary node1 ready for failover.
Message from syslogd at Aug 23 01:31:34 ...
mgd[54445]: UI_CLUSTER_ISSU_IN_PROGRESS: In progress; secondary node1 ready for failover.
[Aug 23 01:31:34]: Failing over all redundancy-groups to node1
ISSU: Preparing for Switchover
error: remote rg1 priority zero, abort failover.
[Aug 23 01:31:34]: failover all RGs to node node1 failed (error-code: 7.1) (210)
mgd[54445]: UI_CLUSTER_ISSU_ERROR_ABORT_STAY: Abort and stay in ISSU window; failover all RGs to node node1 failed (error-code: 7.1)
error: [Aug 23 01:31:34]: ISSU Aborted!
When performing a chassis cluster ISSU upgrade, ensure that a serial console connection is active; all logs will be displayed in the console output. In this example, the ISSU was aborted because the priority of RG1 on node1 was changed to zero, preventing all RGs from failing over to node1. You can then review the device configuration and JSPRD logs to accurately determine the cause of the zero priority on RG1 of node1.
redundancy-group 1 {
node 0 priority 250;
node 1 priority 155;
gratuitous-arp-count 5;
hold-down-interval 0;
interface-monitor {
xe-0/2/0 weight 130;
xe-7/2/0 weight 130;
xe-0/2/1 weight 130;
xe-7/2/1 weight 130;
xe-0/1/0 weight 130;
xe-7/1/0 weight 130;
xe-7/1/1 weight 130;
xe-0/1/1 weight 130;
9665: Aug 23 01:31:25 Current threshold for rg-1 is -265. Setting priority to 0. Failures: interface-monitoring
9689: Aug 23 01:31:26 Current threshold for rg-1 is -5. Setting priority to 0. Failures: interface-monitoring
Based on the configuration details above and the JSRPD log, we have determined that the root cause is that the monitored interface on node1 went down, causing RG1’s priority to drop to zero or even a negative value.
Therefore, it is recommended that the interface monitor configuration be removed before the ISSU. In this case, the reason the interface on Node 1 went down was that the customer was simultaneously upgrading another device directly connected to Node 1.