An upgrade of a CA PAM 2.5.6 cluster to 2.6 was being performed.
The following steps had been undertaken:
Password Authority as part of startup will verify that if the cluster is configured, even if off, the node it is starting in is a member of the cluster. If it fails to find itself in the cluster member list, it will shut down.
When the IP address of the node was changed from 10.1.10.55 to 10.1.10.54, the cluster configuration was not updated so that, as a result, the cluster configuration still contained the 10.1.10.55 address and not the node’s new address of 10.1.10.54.
This resulted in PA failing to start.
Updating the cluster configuration member list to change the node IP from 10.1.10.55 to 10.1.10.54 allowed Password Management to start fine