An issue has been identified where the secondary device in a ADC HA pair enters a state where it continuously reboots (crash loop). The issue occurs under certain conditions when syslog policies are bound to "appfw global".

1. 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>
2. 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.
3. 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
4. Bring both the nodes back in the HA pair. Add the required HA configuration on Node 1
   • add ha node <node-id> <IP> 
5. After executing above steps, Node 2 will now be Primary and Node 1 will be Secondary.

Problem Cause

This is known issue NSHELP-21167. 
The issue occurs on a secondary box if there are SYSLOG policies bound to “appfw global”.