SSH sessions to vIDM Primary node redirecting to Standby node

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When attempting to establish an SSH connection to the Primary node (Node 1) in a 3-node VMware Identity Manager (vIDM) cluster, the session is redirected to a Standby node (Node 0).

This occurs in a cluster environment typically configured with one Primary and two Standby nodes.

Environment

VMware Identity Manager 3.3.7

3-node cluster: node 0 - Standby, node 1 - Primary, node 2 - Standby

Cause

The issue is caused by a duplicate IP address configuration.

The IP address assigned to the Primary node (Node 1) was incorrectly used as the delegateIP and applied to eth0:0 on a Standby node (Node 0).

Additionally, the /etc/hosts files across all three nodes incorrectly mapped the Primary node's IP address to the delegateIP.

Resolution

To resolve this issue, you must remove the incorrect interface configuration and update the host files on all nodes in the cluster:

1. Remove incorrect interface: Log in to the Standby node (Node 0) and remove the eth0:0 configuration that is using the Primary node's IP address.

2. Update hosts files: On all three nodes in the cluster, edit the /etc/hosts file.

3. Correct delegateIP: Ensure the delegateIP entry in each /etc/hosts file is set to the correct, unique IP address intended for the delegate function, and not the IP of the Primary node.

4. Verify Connectivity: Attempt to SSH to the Primary node again to ensure the session no longer redirects to the Standby node.