Re-Configuring Transport Node Profile or Sub Transport Node Profiles assigned to cluster/sub-cluster to match configuration of the Transport Nodes that are in "Mismatch"
Article ID: 416356
Updated On:
Products
Issue/Introduction
Cluster and Sub cluster in NSX have Esxi host transport nodes that are configured with TNP and Sub TNPs and also consists of hosts/ Transport Nodes that reporting a "Mismatch" state in NSX manager UI, the TNP/Sub TNP need to be reconfigured to match the configuration of the hosts/ Transport Nodes in the Mismatch state without impacting the datapath
Environment
VMware NSX
Cause
The cluster was initially configured with a TNP/SUBTNP, however, later the Transport Nodes/hosts were re-configured manually (either changing the IP allocation, Uplink Profile etc) which caused the Transport Nodes/hosts to go into a "Mismatch State"
Resolution
The following options are available to resolve the issue
Option 1: Match the configuration on the TN to match the configuration on the TNP
Option 2: Reconfigure the TNP to match the configuration set on the TN
Option 3: If there are mixed collection of hosts in the cluster (TNs which have the config matching the TNP and TNs that must have configuration different from TNP), configure a Sub Cluster and associate the Subcluster with the Sub TNP
If "Option 2" mentioned above is selected, please follow the steps outlined below.
NOTE: BEFORE MAKING THE CHANGES MENTIONED BELOW,ENSURE THAT THE CONFIGURATION ON THE TRANSPORT NODES/ESXI HOSTS IS CONSISTENT (I.E, ALL THE NODES SHOULD HAVE THE SAME CONFIGURATION)
1. Execute the following GET API call "https://<NSX-manager-IP>/policy/api/v1/infra/host-transport-node-profiles/<TNP>"
the sample output is pasted below
{ "host_switch_spec": { "host_switches": [ { "host_switch_name": "########-VDS7", "host_switch_id": "## ## ## 40 3f c0 6b 24-a0 ec d8 07 9a ## ## ##", "host_switch_type": "VDS", "host_switch_mode": "STANDARD", "ecmp_mode": "L3", "host_switch_profile_ids": [ { "key": "UplinkHostSwitchProfile", "value": "/infra/host-switch-profiles/#####-TEST-UPLINK" } ], "uplinks": [ { "vds_uplink_name": "Uplink 1", "uplink_name": "Uplink-1" }, { "vds_uplink_name": "Uplink 2", "uplink_name": "Uplink-2" } ], "is_migrate_pnics": false, "ip_assignment_spec": { "ip_pool_id": "/infra/ip-pools/host-tep-pool", "resource_type": "StaticIpPoolSpec" }, "cpu_config": [], "transport_zone_endpoints": [ { "transport_zone_id": "/infra/sites/default/enforcement-points/default/transport-zones/Overlay-TZ", "transport_zone_profile_ids": [] }, { "transport_zone_id": "/infra/sites/default/enforcement-points/default/transport-zones/ESXi-VLan-TZ", "transport_zone_profile_ids": [] } ], "not_ready": false, "portgroup_transport_zone_id": "/infra/sites/default/enforcement-points/default/transport-zones/#######-974f-####-a582-88fdc25e5237", "transport_node_profile_sub_configs": [ { "name": "#####-SUB-TNP", "host_switch_config_option": { "host_switch_id": "## ## ## 40 3f c0 6b 24-a0 ec d8 07 9a ## ## ##"", "host_switch_profile_ids": [ { "key": "UplinkHostSwitchProfile", "value": "/infra/host-switch-profiles/nsx-esxi-vds-uplink-profile" } ], "uplinks": [ { "vds_uplink_name": "Uplink 1", "uplink_name": "Uplink-1" }, { "vds_uplink_name": "Uplink 2", "uplink_name": "Uplink-2" } ], "ip_assignment_spec": { "ip_pool_id": "/infra/ip-pools/####-tep-pool", "resource_type": "StaticIpPoolSpec" } } } ] } ], "resource_type": "StandardHostSwitchSpec" }, "ignore_overridden_hosts": false------------------------------------------------------------------------> (by default the value is false ) "resource_type": "PolicyHostTransportNodeProfile", "id": "#####-TNP", "display_name": "#####-TNP", "description": "test-2", "path": "/infra/host-transport-node-profiles/#####-TNP", "relative_path": "#####-TNP", "parent_path": "/infra", "remote_path": "", "unique_id": "#######-79c7-4258-####-###########", "realization_id": "#######-79c7-4258-####-###########", "owner_id": "#######-82cc-4b01-####-d38b166eccbd", "marked_for_delete": false, "overridden": false, "_system_owned": false, "_protection": "NOT_PROTECTED", "_create_time": 1757296233203, "_create_user": "admin", "_last_modified_time": 1761026524487, "_last_modified_user": "admin", "_revision": 44}
2. Change the highlighted value from false to true and execute the PUT API, and the execute the GET api call again to ensure the value has changed and post confirmation, proceed to step 3
3. Change the TNP/SubTNP configuration to match the configuration of the TN and then save the changes, this will trigger a reconfiguration of the TNs in the UI, however, if the TNP/SUBTNP and the TN configurations do match there will be no impact to the datapath and post the reconfiguration the "Mismatch" error will no longer been seen
NOTE: IT IS VERY IMPORTANT TO EXECUTE THE API CALL MENTIONED IN STEP ONE. IN CASE THE API IS NOT EXECUTED ANY CHAGES MADE TO THE TNP, WHILE THE TNs ARE IN A MISMATCH STATE COULD PUSH THE TNP CONFIGURATION ON ALL THE TNS AND THE TNS WILL GET RECONFIGURED AGAIN.
ANY CHANGE ON THE TN WILL ALSO BE PUSHED TO TNS WHICH ARE A PART OF THE SUB-CLUSTER AND SUB-TNP AS WELL
Additional Information
For information about "Creating and Configuring NSX Sub Transport Node Profiles on NSX Transport Node Sub Clusters" (Option 3) refer the below kb
https://knowledge.broadcom.com/external/article/403564
Feedback
