I ran into an issue yesterday where a GSLB site took down the whole site for a client when the secondary node in the HA active/passive pair rebooted. Where in the config would I fix this? I can’t figure out why it did it.

@Mike Streetz (O_P) by chance were you upgrading from 13.0.x to the latest 13.1.x at this time or was it only a reboot of the secondary NetScaler that did this?

I broke HA and re-established it with a new node and it went down each time it couldn’t talk to a secondary node.

i usually put the primary in 'stay primary' and the secondary in 'stay secondary' when i do that....make sure your links on your secondary match the primary for 'ha monitoring', aka disable HA monitoring on the links you don't want HA going across.

it must be something like that but I just can’t see it