The HA pair site location id for paired devices is derived from the paired devices that are in deployed state. It picks up the paired id if one exists from the inventory table (Postgres).

If you don’t see the redundant pair device name on the Monitor page of one the HA pairs device. Then it is mostly because the HA pair devices are not able to recognize each other.

One issue could be mainly due to the different paired site ID. Ideally the paired site ID should be identical between HA pair devices

HAB-1 - 1st device of the HA pair

HAB-2 - 2nd device of the HA pair

To verify this issue:

Check the device bind data of the both the device workflows of the HA pair. They should have identical paired site ID

HA Pair 1^st device

HA pair  2^nd device

In this case, the 2^nd Ha pair has a different site ID.

You can verify the same in postgres DB

inventory_ asset - Postgres table name for the asset inventory

HAB-1 - Device name 

Root cause:

If the user creates the device workflow of the 1st device in the HA pair but just saves instead of deploy then go ahead creates the device workflow for the 2nd device of the HA pair. In this case, both the devices will assume themselves as the first device of the HA pair and generate their own paired site ID, this results in unidentical paired site ID between the HA pair

Fix:

Copy the HA paired site ID from the 1^st device of HA Pair’s device bind data to the 2^nd device bind data to make the HA paired site ID identical and redeploy the template