HA Nodes Show Incorrect Current Roles

Issue

In the High Availability section, both application nodes may intermittently show Primary 1 as the Current Role, even when one node is configured as Primary 2.

Cause

This behavior may occur when communication between the two Primary nodes is temporarily unavailable due to:

  • Unplanned or unmanaged server reboots

  • Temporary network interruptions

  • Required HA communication ports being unreachable

When communication is interrupted, a node may independently assume the active role, causing both nodes to display Primary 1 as the Current Role.

Resolution

The following steps may cause a brief service interruption lasting a few seconds.

Make sure direct RDP access to both PAM servers.

  • On the server with System Role-> Primary 2

    • Open IIS Manager.

    • Select Sectona PAM.

    • Stop the Sectona PAM Application Pool.

    • Stop the Sectona PAM Site.

  • On the server with System Role -> Primary 1

    • Open IIS Manager.

    • Select Sectona PAM.

    • Recycle the Sectona PAM Application Pool.

    • Restart the Sectona PAM Site.

  • Log in to the PAM console using an administrator account.

  • Go to High Availability and verify that the system nodes (Application/Vault).

  • Once the roles are restored, on the Primary 2 server, start the Sectona PAM Application Pool and Sectona PAM Site.