NetScaler Displays - "[Warning]: Force Failover may cause configuration loss, peer health not optimum"
Article ID: CTX125720
Updated On:
Description
When you attempt to force failover a NetScaler high availability setup, the following warning message is displayed:
[Warning]: Force Failover may cause configuration loss peer health not optimum
Please confirm whether you want force-failover (Y/N)? [N]:
Resolution
The preceding warning message might be displayed due to any of the following conditions. You can use this information to determine the next set of troubleshooting steps to resolve this issue.
-
If there is a synchronization failure between the appliances.
When you display the status of the high availability nodes by running the following command, the output of the command displays the synchronization status as FAILED:
> sh node1) Node ID: 0 IP: 10.217.146.190 (ReproEV-05_NS-190) Node State: UP Master State: Primary INC State: DISABLED Sync State: ENABLED Propagation: ENABLED Enabled Interfaces : 1/1 1/2 Disabled Interfaces : 1/3 1/4 0/1 HA MON ON Interfaces : 1/1 ½ SSL Card Status: UP Hello Interval: 200 msecs Dead Interval: 3 secs Node in this Master State for: 0:0:4:1 (days:hrs:min:sec) 2) Node ID: 1 IP: 10.217.146.191 Node State: UP Master State: Secondary INC State: DISABLED Sync State: FAILED Propagation: ENABLED Enabled Interfaces : 1/1 1/2 Disabled Interfaces : 1/3 1/4 0/1 HA MON ON Interfaces : 1/1 ½ SSL Card Status: UP Local node information: Critical Interfaces: 1/1 1/2 Done
-
If the peer appliance is not detected or has failed.
When you display the status of the high availability nodes by running the following command, the output of the command displays the peer node status as NOT UP:
> sh node1) Node ID: 0 IP: 10.217.146.190 (ReproEV-05_NS-190) Node State: UP Master State: Primary INC State: DISABLED Sync State: ENABLED Propagation: ENABLED Enabled Interfaces : 1/1 1/2 Disabled Interfaces : 1/3 1/4 0/1 HA MON ON Interfaces : 1/1 1/2 SSL Card Status: UP Hello Interval: 200 msecs Dead Interval: 3 secs Node in this Master State for: 0:20:43:30 (days:hrs:min:sec) 2) Node ID: 1 IP: 10.217.146.191 Node State: NOT UP Master State: Secondary INC State: DISABLED Sync State: SUCCESS Propagation: ENABLED Enabled Interfaces : 1/1 1/2 Disabled Interfaces : 1/3 1/4 0/1 HA MON ON Interfaces : 1/1 1/2 Interfaces causing Partial Failure: 1/1 SSL Card Status: UP Local node information: Critical Interfaces: 1/1 ½ Done
-
If the peer appliance is set to stay as secondary.
When you display the status of the high availability nodes by running the following command, the output of the command displays the peer node status as STAYSECONDARY:
> sh node1) Node ID: 0 IP: 10.217.146.190 (ReproEV-05_NS-190) Node State: UP Master State: Primary INC State: DISABLED Sync State: ENABLED Propagation: ENABLED Enabled Interfaces : 1/1 1/2 Disabled Interfaces : 1/3 1/4 0/1 HA MON ON Interfaces : 1/1 1/2 SSL Card Status: UP Hello Interval: 200 msecs Dead Interval: 3 secs Node in this Master State for: 0:20:48:56 (days:hrs:min:sec) 2) Node ID: 1 IP: 10.217.146.191 Node State: STAYSECONDARY Master State: Secondary INC State: DISABLED Sync State: SUCCESS Propagation: ENABLED Enabled Interfaces : 1/1 1/2 Disabled Interfaces : 1/3 1/4 0/1 HA MON ON Interfaces : 1/1 1/2 SSL Card Status: UP Local node information: Critical Interfaces: 1/1 1/2 Done
- There should not be any missing heartbeats on the interfaces and HA monitoring should be disabled on all the disabled/down interfaces
Issue/Introduction
