After a TPAM version upgrade, when viewing the Cluster Status in cluster management one or more Replica's show the status "Failing Back" and the version also shows the previous version ie. the Replica has not been upgraded.
This could have happened because of a few situations:
- Appliance failed over due to timeout not being extended
- Cluster member was not healthy prior to update being applied
- Replica required a reboot prior to update being applied
To resolve this situation the version update will need to be applied directly to the Replica.
Log into the Primary /admin interface - Cluster Management
Select the problem Replica - Change the Run Level to Maintenance Mode - Save Changes
Logon to the Replica /admin interface - Reboot the Replica Appliance - then apply the 2.5.9xx update - (Maint - Apply Patch - Apply the 2.5.x patch)
Reboot the Replica again once the patch has applied and the Patch log shows the update has applied successfully.
Log into the Primary /admin interface - Cluster Management
Select the updated Replica - Change the Run Level to Operational Mode - Save Changes
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center