Unable to enable latency metric collection for NSXT on Aria operations for networks

Products

• VCF Operations for Networks
• VMware NSX-T Data Center

Issue/Introduction

While enabling latency metric collection for NSXT from Aria operations for Networks it was observed that the latency profile couldn't be applied to specific transport zones. On Aria Operations for Networks, after ticking the option in the settings, the data source fails with the following error 

Below error observed in "nsxapi" logs of NSX manager for the specific transport zone that is configured on the transport node profile which is used to prepare ESXi hosts for NSXT 

2025-03-11T11:26:14.395Z ERROR http-nio-127.0.0.1-7440-exec-306 TransportZoneServiceImpl 77007 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP8106" level="ERROR" reqId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx" subcomp="manager" username="XXXXX"] TransportZone host switch mode update is not allowed for TransportZone TransportZone/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx.

This issue impacts while fetching the switch port stats for the virtual distributed switches on ESX host

Environment

NSXT - 4.2.1.1.0.24405893

VMware Aria Operations for Networks - 6.14.0 

Cause

The issue could occur due to the presence of field "switchMode" in transportZone corfu table which was deprecated in NSX 3.2 release and moved to TransportNode table. So NSX environments which were upgraded from 3.1 releases may still have this field in the TZ table.

While updating the "transport_zone_profile_paths" for such transportzones, a validation is kicked in and this results in error as shown above and thus failing to enable latency metric collection.

Resolution

When such issues are observed while enabling latency metric collection from Aria operations for networks for NSX-T open a case with Broadcom Support and reference this KB article. See Creating and managing Broadcom support cases. 

Broadcom Support will have to review and evaluate this further and make changes to the impacted NSXT transport zone. 

Additional Information

This issue will be fixed in NSX releases 4.2.2 and 9.1 versions