False alerts are being raised in the AON indicating “No transport zone attached on the transport node”

Products

• VMware Aria Operations for Networks

Issue/Introduction

When reviewing alerts in AON/vRNI, the following alert can be seen :

• This alert informs there is no longer transport zone attached to a host transport node, it lasts a few minutes then get auto-resolved (closed).
• The alert get re-opened every 24 hours
• On the NSX side, no change is being done on the transport node, the transport zone is still attached to the transport node
• In the AON collector logs, we see:
  • 2024-11-11T01:03:48.420Z WARN nsxt.tasks.NSXTUtils NSXT_xxxxxxxxxxxxxx_Config_OpMgr-4 updateInventoryForMetrics:3003 Unable to update the metrics inventory for object type TransportZone due to the fetcher status true 2024-11-11T01:03:48.420Z INFO nsxt.tasks.InventoryHandler NSXT_xxxxxxxxxxxxx_Config_OpMgr-4 invoke:59 Actual inventory size 10, fetched entities size for 5, TransportZone
  • This confirm an issue with inventory size is 10 but the fetched entity is only 5, in working environment, both numbers, inventor and fetched entities should be same.

 

Environment

Aria Operations for Networks 6.x

vRealize Network Insight 6.x

Cause

The issue arises due to how AON/vRNI fetches transport zone details. The system retrieves information from both the global infra and infra levels. While the transport zones in these two sources are identical, the process duplicates the inventory size, inflating it to 10 objects even though there are only 5 unique inventory items. This mismatch leads to transport zone objects being deleted every 24 hours, triggering the alerts.

Resolution

A fix for this issue has been identified and will be included in a future release of VMware Aria Operations for Networks, specifically as part of VMware Cloud Foundation (VCF) 9.0.

As a workaround, the alert can be disabled.