Jump to content
Welcome to our new Citrix community!

Netscaler 13.0.47.24 Crashing when secondary


Simon Simcic

Recommended Posts

Hello, 

 

did anybody observe, following an upgrade to 13.0.47.24, whenever we failover the secondary gets stuck in a reboot loop. 

 

If we add a clean new VM, we add it to the HA Cluster  - it is ok. But when we failover - the Secondary (previously primary)  crashes

 

Anybody observed this?

 

 

Link to comment
Share on other sites

I got this suggestion from a Citrix contact

 

Remove the HA configuration from Primary node (Node 1). After this step, both the nodes in the HA pair will be in standalone mode.

show ha node

rm ha node <node-id>

If there are any syslog policies that are bound to “appfw global”, execute this step. On Primary Node, run the following commands

unbind appFw global <syslog-policy>

bind system global <syslog-policy>
Note: Unbind all the syslog policies bound to appFw global and bind them to system global. 
This will ensure that the logs are sent to the external syslog server.

After Step 1, cyclic reboot of Secondary Node(Node2) should stop, as it will be in standalone mode. Once Node 2 comes up (in standalone mode), execute the following commands.

unbind appFw global <syslog-policy> 
Note: Unbind all the syslog policies bound to appFw global

Bring both the nodes back in the HA pair. Add the required HA configuration on Node 1

add ha node <node-id> <IP> 

After executing above steps, Node 2 will now be Primary and Node 1 will be Secondary.

 

 

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...