Cluster Communication Failure After Enabling Dual-Stack VIP Configuration

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

After enabling dual-stack (IPv4 / IPv6) configuration for the cluster VIPs, the cluster experienced communication issues between the primary node and worker nodes, resulting in instability and service disruption.

Environment

Aria Operations for Logs 8.18.x

Cause

The worker nodes were configured with IPv6 addresses, while the primary node was referenced using its FQDN, which resolved to an IPv4 address.
This mismatch between IPv4 and IPv6 configurations caused inconsistent communication across the cluster nodes in the dual-stack setup.

Resolution

To restore proper communication within the cluster, update the primary node configuration to use its IPv6 address instead of the FQDN.

 

Steps:

1. Access the internal configuration page of the primary node:

https://<vrli_primary>/internal/config

 

2. Locate the Log Insight configuration section.

 

3. Modify the configuration line by replacing the FQDN with the IPv6 address of the primary node.

 

Example:

<daemon host="<hostname_FQDN>" port="16520" token="4a2####-####-####-####-########383a">

 

4. Update to:

<daemon host="<IPv6_address>" port="16520" token="4a2####-####-####-####-########383a">

 

5. Save the configuration.

6. Restart the loginsight service:

systemctl restart loginsight

 

After the update, all nodes will communicate over IPv6, ensuring consistent and stable cluster operation.