search cancel

Secondary site on Azure nodes always remains in timeout

book

Article ID: 252698

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

There is already a PAM Primary Site with two nodes deployed on-Prem on ESX Vmware Servers.

When creating a Secondary Site with a node in Microsoft Azure.

This Site is added however to the new Secondary Site in Azure the

"Replication Status" column in PAM as "!" with Alert "The connection timed-out checking whether this member's database is consistent with the primary database. This sync status is checked every 5 minutes. Click on the Refresh Replication Status button to check it now". We were clicking but keeping in the same "Replication Status" state.

Environment

Release : 4.0

Resolution

PAM primary site is on-prem, PAM secondary site on Azure.

1. Got tcpdump from both PAM servers involved (on-prem and Azure) and identified that port 443 is communicating but not for ports 8443 nor 3307 that needed be fixed by network team between on prem network and Azure. 

2. With SSH session, On Azure PAM node Support changed OS.EnableFirewal parameter in the /etc/waagent.conf file from "n" to "y" and restarted the OS in this node. This made "Site Member Active" column green (Active) since was inactive.
But yet was showing the "Replication Status" column in PAM as "!" with Alert "The connection timed-out checking whether this member's database is consistent with the primary database. This sync status is checked every 5 minutes. Click on the Refresh Replication Status button to check it now". We were clicking but keeping in the same "Replication Status" state.

3. To resolve the "Replication Status" Error found that for some reason Azure PAM node was trying to reach IP of Primary Site nodes and Vip with different IP address than expected.

Added in Configuration > Network > Host File Entry page to update the /etc/hosts of all Nodes (This is a Global Configuration) with the ip addresses of Primary Site Nodes.

After this the column "Replication Status" for Azure node becomes Green as expected too.

Attachments