"Error: the requested object Policy Transport Zone...could not be found" Unable to replace or update the transport node in the transport node profile after upgrading to NSX 3.2.2.0

Products

• VMware NSX

Issue/Introduction

• In a federated environment, you see a message similar to the following on a local manager when you try to change the transport zone in the transport node profile:

"Error: the requested object Policy Transport Zone/9501afe9-####-####-####-d9cc60f43f29 could not be found. Object identifiers are case sensitive. (Error code: 600)"

• There is no transport zone in the local manager inventory with the UUID noted in the previous message (9501afe9-####-####-####-d9cc60f43f29)

Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 3.x

Resolution

This issue is resolved in NSX-T 3.2.3 and NSX-T 4.1.1 onwards.

Workaround:

Update the transport zone by using API calls.

1. Fetch the configured transport node profiles:
   
   GET https://<Manager IP>/policy/api/v1/infra/host-transport-node-profiles
   
   
2. Fetch the information related to the particular transport node profile called out previously
   
   GET https://<Manager IP>/policy/api/v1/infra/host-transport-node-profiles/<UUID of the TNP>
   
   
3. Update the particular transport node profile with changes
   
   PUT https://<Manager IP>/policy/api/v1/infra/host-transport-node-profiles/<UUID of the TNP> after making changes to the above get output
   
   
4. Confirm the changes
   
   GET https://<Manager IP>/policy/api/v1/infra/host-transport-node-profiles/<UUID of the TNP> to see the changes
   
   =================================================================================

 

1. To fetch all configured TNPs
   
   GET https://<Manager IP>/policy/api/v1/infra/host-transport-node-profiles
   
   
2. To fetch the information related to particular TNP
   
   GET https://<Manager-IP>/api/v1/transport-node-profiles/6850420f-####-####-####-fad509ed77da

{
    "host_switch_spec": {
        "host_switches": [
            {
                "host_switch_name": "######-vds-####",
                "host_switch_id": "50 3d 41 00 6d b3 40 ea-e0 17 ## ## ## ## ## ##",
                "host_switch_type": "VDS",
                "host_switch_mode": "STANDARD",
                "host_switch_profile_ids": [
                    {
                        "key": "UplinkHostSwitchProfile",
                        "value": "66db6358-####-####-####-1029b9a3dda9"
                    }
                ],
                "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"
                },
                "cpu_config": [],
                "transport_zone_endpoints": [
                    {
                        "transport_zone_id": "c75a6c1d-####-####-####-0787bd95c211",
                        "transport_zone_profile_ids": []
                    }
                ],
                "not_ready": false
            }
        ],
        "resource_type": "StandardHostSwitchSpec"
    },
    "ignore_overridden_hosts": false,
    "resource_type": "TransportNodeProfile",
    "id": "6850420f-####-####-####-fad509ed77da",
    "display_name": "######-####",
    "description": "######-example.com",
    "_create_time": 1675258845572,
    "_create_user": "admin",
    "_last_modified_time": 1675524875116,
    "_last_modified_user": "admin",
    "_system_owned": false,
    "_protection": "NOT_PROTECTED",
    "_revision": 1
}
   
   
3. To make an update to a particular TNP with changes
   
   PUT https://<Manager IP>/policy/api/v1/infra/host-transport-node-profiles/<UUID of the TNP> after making changes in the get API output
   
   Example:
   
   Add VLAN TZ and update (PUT) transport node profile (6850420f-####-####-####-fad509ed77da)
   
   PUT https://<Manager IP>/api/v1/transport-node-profiles/6850420f-####-####-####-fad509ed77da
{
    "host_switch_spec": {
        "host_switches": [
            {
                "host_switch_name": "######-vds-####",
                "host_switch_id": " 50 3d 41 00 6d b3 40 ea-e0 17 ## ## ## ## ## ## ",
                "host_switch_type": "VDS",
                "host_switch_mode": "STANDARD",
                "host_switch_profile_ids": [
                    {
                        "key": "UplinkHostSwitchProfile",
                        "value": "66db6358-####-####-####-1029b9a3dda9"
                    }
                ],
                "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"
                },
                "cpu_config": [],
                "transport_zone_endpoints": [
                    {
                        "transport_zone_id": "c75a6c1d-####-####-####-0787bd95c211",
                        "transport_zone_profile_ids": []
                    },
                    {
                        "transport_zone_id": "128639cb-####-####-####-e88610935809", <-----------------------newly added
                        "transport_zone_profile_ids": []
                    }
                ],
                "not_ready": false
            }
        ],
        "resource_type": "StandardHostSwitchSpec"
    },
    "ignore_overridden_hosts": false,
    "resource_type": "TransportNodeProfile",
    "id": "6850420f-####-####-####-fad509ed77da",
    "display_name": "######-bl-vi1-prod-cl03",
    "description": "######-example.com",
    "_create_time": <epoch time>,
    "_create_user": "admin",
    "_last_modified_time": <epoch time>,
    "_last_modified_user": "admin",
    "_system_owned": false,
    "_protection": "NOT_PROTECTED",
    "_revision": 1
}
   
   
4. To see the changes:
   
   GET https://<Manager IP>/api/v1/transport-node-profiles/6850420f-####-####-####-fad509ed77da
    

Additional Information

Impact/Risks:

You will not be able to update/change the transport zone configuration in the transport node profile