To resolve this this issue, follow these steps:
Depending on your current cluster status, it is possible that step 4 can shut down the whole cluster. The cluster will need to be shut down anyway to bring the effected node(s) back in, so it is recommended to shut the rest of the cluster down first if it is currently running.
- Navigate to the following link in a Web Browser: https://<PAM_Address>/config/?legacy=1 or https://<PAM_Address>/config/
- Login as the config user
- Navigate to: Configuration > Clustering
- Click the button "Turn Cluster Off".
- The cluster will turn off on this node and possibly other nodes if they were still clustered. Ensure clustering is shut down on each effected node before continuing.
- Once clustering is shut down on the effected nodes the standard login page becomes active for logins. Login to confirm everything is working.
- Either restart the Cluster if clustering will continue to be used (Configuration > Cluster > Turn Cluster On) or if this node is being removed from the cluster Unlock it's Database (Configuration > Cluster > Unlock Me)
Tips to prevent this situation from happening again:
- Never pull the power plug or otherwise reboot PAM while the cluster is enabled unless directed to by Support
- Ensure the cluster is turned off or the individual node has been safely removed before patching or other major changes
- Never take LIVE (running) VM snapshots of PAM Appliances (Snapshots taken while PAM is powered off are acceptable)
- Disable vMotion for all PAM Appliances