vSphere Integration targets a specific node instead of the VIP in VCF Operations for Logs

Products

• VCF Operations

Issue/Introduction

When configuring vSphere or vCenter integration within VMware Cloud Foundation (VCF) Operations for Logs (formerly Aria Operations for Logs), you observe the following:

• The integration target is automatically set to the IP or FQDN of the primary node (e.g., node01) rather than the Integrated Load Balancer (ILB) Virtual IP (VIP).
• Consequently, ESXi hosts are configured with the single node IP as their remote syslog target.

Environment

VCF Operations for logs 9.x

Cause

This is by design.

In VCF 9.0.x, when you configure log collection for vCenter/VCF integration through the VCF Operations UI, the system initially targets the primary node of the cluster to establish and verify connectivity.

The integration does not automatically default to the cluster VIP for the generated syslog configuration on ESXi hosts.

Resolution

You can redirect the integration to use the Cluster VIP by using the Override Collector Configuration feature in the VCF Operations interface.

Procedure

1. Log into the VCF Operations UI with administrative privileges.
2. Navigate to Infrastructure Operations > Configurations > Log Collection.
3. Locate the vCenter server integration you wish to modify and click Edit.
4. In the configuration wizard, locate and select the Override Collector Configuration option.
5. Change the target address value from the primary node's IP/FQDN to the Cluster VIP (Virtual IP) address or FQDN.
6. Click Save to apply the changes.

Additional Information

VCF Operations for Logs の「統合」の vSphere でターゲットが VIP ではなく特定ノードになる (446715)