Log collection enabling failure for vCenter Server in VCF Operations

Products

• VCF Operations

Issue/Introduction

Enabling log collection for a vCenter Server in VCF Operations (formerly VMware Aria Operations) via the VCF Adapter settings fails. The following symptoms are observed:

• UI Error: The configuration wizard displays the error: Failed to configure log collection.
• Status Display: Under Configurations > Log Collection, the status displays as Not Available with no accompanying error message in the grid.
• Integration Missing: No vCenter integration is automatically configured within the VCF Operations for Logs UI.
• Log Entry: Cloud proxy logs located at /vcf-log-forwarder/log/log-forwarder.log contain the following 503 error:
  
  

  [vert.x-eventloop-thread-2] ERROR c.v.l.l.c.LogCollectionConfigScheduler:207 - Error while fetching and applying log collection configurations. com.vmware.log.forwarder.httpclient.APIException: Got status 503 while retrieving session.

Environment

VCF Operations 9.0.x

Cause

The issue is typically caused by required network ports being closed on the firewall between the Cloud Proxy appliance and the VCF Operations for Logs nodes, preventing the log forwarder from establishing a session.

Resolution

Ensure the required network ports are open on the firewall between the Cloud Proxy appliance and the VCF Operations for Logs nodes to allow the log forwarder to establish a session.

1. Verify Port Connectivity: Confirm the following ports are open:

   • 443 (HTTPS)
   • 9543 (Integration Service)
   • 514, 1514, 6514 (Syslog/Ingestion)

2. Test Connectivity from Cloud Proxy: SSH into the Cloud Proxy appliance as root and run the following command for each port and each VCF Operations for Logs node:

   curl -v telnet://[VCF_Ops_Logs_Node_IP]:[Port]

3. Re-save Configuration: Once connectivity is confirmed, return to VCF Operations and re-save the vCenter Adapter log collection settings to trigger a new configuration push.