Transport Node Profile (TNP) was created and applied to the Host cluster post upgrade from 4.2.1 to 4.2.3.3 as a part of VCF upgrade (5.2.2 to 5.2.3)

Products

• VMware NSX

Issue/Introduction

During or following a VMware Cloud Foundation (VCF) upgrade (specifically transitioning from VCF 5.2.2 to 5.2.3, which includes NSX 4.2.3.3), users may observe new Transport Node Profiles (TNP) created in the NSX Manager UI that were not manually initiated by an administrator.

Checking the NSX manager logs /var/log/nsx-audit-write.log

NSX-Manager NSX 77478 FABRIC [nsx@6876 audit="true" comp="nsx-manager" entId="2####a63-###-4864-###-55#####e8" level="INFO" reqId="9#####-ab8a-####-9ba0-7######be" subcomp="manager" update="true" username="admin"] UserName="admin", Src="x.193.x.3", ModuleName="PolicyHostTransportNodeProfile", Operation="CreateOrUpdatePolicyHostTransportNodeProfile", Operation status="success", New value=["2####a63-###-4864-###-55#####e8" {"override_nsx_ownership":false} {"host_switch_spec":{"host_switches":[{"host_switch_name":"nsxDefaultHostSwitch","host_switch_id":"<host_switch-id>","host_switch_type":"VDS","host_switch_mode":"STANDARD","ecmp_mode":"L3","host_switch_profile_ids":[{"key":"UplinkHostSwitchProfile","value":"/infra/host-switch-profiles/<ID>"}],"uplinks":[{"vds_uplink_name":"uplink2","uplink_name":"uplink-2"},{"vds_uplink_name":"uplink1","uplink_name":"uplink-1"}],"is_migrate_pnics":false,"ip_assignment_spec":{"resource_type":"AssignedByDhcp"},"transport_zone_endpoints":[{"transport_zone_id":"/infra/sites/default/enforcement-points/default/transport-zones/<ID>"},{"transport_zone_id":"/infra/sites/default/enforcement-points/default/transport-zones/<ID>"}],"{"vds_uplink_name":"uplink1","uplink_name":"uplink-1"}],"ip_assignment_spec":{"resource_type":"AssignedByDhcp"}}}]}],"resource_type":"StandardHostSwitchSpec"},"display_name":"<NEW>-Transport-Node-Profile","marked_for_delete":false,"overridden":false}]

 

• Audit logs in NSX Manager show Operation="CreateOrUpdatePolicyHostTransportNodeProfile" initiated by the admin user from the SDDC Manager IP address.

• A new TNP appears with a naming convention similar to <cluster-name>-Transport-Node-Profile.

• The Src IP in the audit log matches the SDDC Manager appliance IP (e.g., x.193.x.3).

 

Environment

NSX Version: 4.2.x

SDDC Manager: 5.2.x

Cause

This behavior is an intentional part of the VCF automated workflow for the VLCM cluster, as VLCM requires an TNP on the Host clusters if there is no existing TNP on the Hosts clusters.

Resolution

If the automatically created TNP does not meet specific organizational requirements (e.g., specific uplink naming or teaming changes), it can be modified or reconfigured without impacting SDDC Manager's visibility, provided the fundamental cluster-to-TNP association remains valid.

Additional Information

Please refer to the doc for more information why we require a TNP for the VLCM cluster : https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/installation-guide/vsphere-lifecycle-manager-with-nsx/prepare-a-cluster-with-vsphere-lifecycle-manager.html