A TNP (Transport Node Profile) is applied to a cluster and the cluster is prepared for NSX due to VCF/SDDC

Products

• VMware NSX

Issue/Introduction

• A Transport Node Profile was created in NSX and source of creation is unknown.
• In VMware NSX, a cluster that previously was not configured with NSX, unexpectedly has a TNP applied and the cluster is now prepared for NSX.
• The following API call will list all TNP's:

GET /policy/api/v1/infra/host-transport-node-profiles

• From the result check the TNP that was added to the cluster, it will provide details such as the create_user and create_time (in Epoch value).

Environment

VMware NSX

VCF NSX 9.x

Cause

SDDC manager detects clusters with no TNP applied during sync operations and applies a TNP to clusters which do not have one, once the TNP was applied to the cluster, the cluster was then configured with NSX.

Resolution

This is expected behavior.

Additional Information

Cloud Foundation Cluster NSX Transport Node Profile Attachment

Modification of Transport Node Profile in NSX managed by SDDC Manager