Latency profile realization fails to propagate to Transport Nodes

Products

• VMware NSX
• VCF Operations for Networks

Issue/Introduction

• User adds NSXT data source on vRNI, and enables latency metric collection.
• User can verify that the latency profile is created, and binds to group successfully by running the following API:

https://{{MP}}/policy/api/v1/infra/latency-profiles

• But the profile is not seen on Hosts, and there is no latency property on the dvs port leading to collection not working.

Environment

VMware NSX

VMware Aria Operations for Networks

Cause

This issue happens because the Policy Provider meets exception when updating or deleting the latency profile in Management Plane

Resolution

This issue is resolved in NSX version 4.2.2 and newer.

If you encounter this issue, please contact Broadcom Support: Broadcom Support Portal

Additional Information

Related KB:

NSX Manager Data Collection Failure in AON/vRNI Due to Latency Profile Deletion Error