SNIP shows as active on both nodes of the HA piar
Article ID: CTX223799
Updated On:
Description
HA nodes are configured in PRIMARY and SECONDARY states. All incoming traffic should be passing through the primary node only.
Actual Behavior
==============
HA synchronization and propagation work as expected. However secondary node DOES NOT use primary node's monitor probes to determine vServer/service states.
Secondary node sends monitor probes with SNIP address at the same time as the primary node.
Resolution
1. Break HA configuration. Run the following command on each NetScaler
rm node 1
2. Clear config on the node designated to be the Secondary
clear config -full
3. Recreate HA. Run the following command, first on Primary, then on Secondary:
add ha node 1
Problem Cause
SNIP was active in HA on the SecondaryMost likely, the SNIP was configured on both devices before creating the HA pair.
Was this article helpful?
Yes
No
Powered by
