(SSP)Security Intelligence - Recommendation fails with Discovery Failed error: "A compute <UUID> is neither vm nor bm"
search cancel

(SSP)Security Intelligence - Recommendation fails with Discovery Failed error: "A compute <UUID> is neither vm nor bm"

book

Article ID: 440687

calendar_today

Updated On:

Products

VMware vDefend Firewall with Advanced Threat Prevention VMware vDefend Firewall

Issue/Introduction

When running Security Intelligence recommendations, the discovery process fails. The UI displays a Discovery Failed alert with a red exclamation mark.

Clicking the failure link reveals the following error message popup:

A compute <UUID> is neither vm nor bm

Environment

Security Services Platform version 5.1.1

Cause

This issue occurs due to a synchronization gap between the SSP and NSX Manager inventory when a Virtual Machine (VM) is deleted.

When a VM mapped to a Static Logical Switch Port (LSP) is deleted, the intermediate database object relationships are broken prematurely in the registry.

Because these relationship pointers are lost during the deletion flow, the parent Container (Group) is never triggered for re-evaluation.

As a result:

  • The deleted VM remains as a stale, ghost entry within the group's effective members list.

  • The control plane fails to send a GroupingNotification update to the Security Intelligence component.

  • Security Intelligence attempts to discover a VM compute entity that no longer exists in the infrastructure, triggering the validation error.

Resolution

A permanent software fix is planned for a future release. To resolve the issue immediately for the affected groups, you can force an inventory re-evaluation by modifying the group configuration.

For executing the workaround, kindly contact Broadcom via a support ticket.