Service discovery failing for built-in and custom services in VCF Operations 9.0.2.0

Products

• VCF Operations

Issue/Introduction

VCF Operations 9.0.2.0 experiences inconsistent service discovery, where both built-in (such as Active Directory and MS SQL) and custom services fail to collect. Discovery processes for these services fail, preventing the system from building necessary service-to-service relationships.

The ServiceDiscoveryAdapter logs may indicate empty port arrays for affected processes, confirming the discovery engine perceives no valid connection data.

Example log output:

DEBUG ... Build remote connection Data : ... Service: name = SCOM Agent, process = HealthService.exe, ports = [], listeningPorts = [],...
ERROR ... Not able to find the child remoteMachineService with resourcekey : {resName=SCOM Agent, resKind=Services, adKind=APPLICATIONDISCOVERY, ids={PORT=[], VMMOR=vm-######}}

Environment

• VCF Operations 9.0.2.0

Cause

This issue is caused by one or both of the following conditions:

• The Service Discovery Management Pack (SDMP) namespace is corrupted.
• Required network connection entries (either permanent listening TCP ports or established UDP connections) are missing from the Managed Object Browser (MOB) for the affected virtual machines under the connection-info-1 key.

Resolution

To resolve service discovery collection failures, perform the following two-step validation:

1. Determine if the SDMP namespace is corrupted by reviewing the namespace integrity. Refer to KB "Namespace is not ready" or "Auth Failure" during Aria Operations Service Discovery with VMware Tools 13.x and 12.5.x for steps on identifying and resolving stale or corrupted namespaces via the vCenter Managed Object Browser (MOB).

2. Ensure the discovery engine can retrieve the necessary port data for the affected virtual machine.

   1. Navigate to the vCenter Managed Object Browser (MOB). See Accessing the MOB
   2. Locate the affected virtual machine.
   3. Check the connection-info-1 key for valid TCP or UDP connection entries that align with the ProcessId and port for the service .
   4. Custom service discovery requires either a permanent listening TCP port or an established UDP connection to be populated in the MOB. If these entries are missing, the discovery engine cannot establish the service-to-service relationship.
      
      
      

Subscribe to this knowledge article to get updates on this issue.

Additional Information

For more information on service discovery, refer to the VCF Operations documentation regarding Workload Monitoring and Observability.

To receive updates on this or related issues, you can subscribe to notifications by following the steps in this guide: Subscribe to a Broadcom knowledge article by article or product.