Re-Configuring Transport Node Profile or Sub Transport Node Profiles assigned to cluster/sub-cluster to use IP POOL from DHCP for IP allocation of VTEP vmkernels without having any downtime

Products

• VMware NSX

Issue/Introduction

• Cluster and Sub cluster with Esxi host transport nodes in NSX configured with TNP and Sub TNPs are configured to use DHCP IP  for IP allocation of VTEP vmkernels and need to be reconfigured to use an IP POOL 

Environment

VMware NSX

Cause

The TNP was initially configured to use the DHCP for IP allocation of VTEP vmkernel and now needs to be re-configured to use a TEP IP POOL 

Resolution

The steps to be followed are as below 

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. Place one host at a time into maintenance and reconfigure the host and change the IP allocation from DHCP to IP Pool. This will reconfigure the host and the NSX manager UI will report a "Mismatch" (as seen in screen shot pasted below). The "Mismatch" will be addressed after the execution of the Step 7 and ensure steps 3-6 are executed on all the hosts before executing step 7

4. Post the change check the confirm if the TEP has the new IP from the IP Pool 

5. Take the host out on maintenance mode migrate a vm to the reconfigured host and ensure the connectivity to the vm 

6. Follow the same steps (3,4 and 5) on all the hosts that require the re-configuration

7. Once the reconfiguration is completed on all the hosts, 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 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" refer the below kb 

 https://knowledge.broadcom.com/external/article/403564