VMware NSX-T Federation Stale global Transport Zone may cause MTU configuration check to fail with Error : "TransportZone/UUID could not be found."

Products

• VMware NSX

Issue/Introduction

• You are running an NSX-T Federated environment version 3.2.X.
• You cannot run MTU Configuration Check as it fails with the below error on the UI:

 Error: The requested object: TransportZone/########### could not be found. Object identifiers are case sensitive.

Environment

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

Cause

A global transport zone (TZ) can cause the not found error. There are two causes for this issue:

1.  Stale Global TZ: The local transport Zone is deleted but the global transport zone remains.
2.  Global TZ has different UUID for the policy path and internal Id., Ex. the policy path is "/global-infra/sites/VDCF-SDDC/enforcement-points/default/transport-zones/########-cbbb-44a2-8702-############", and internalId is ########-c4cc-4c81-9318-############.

Resolution

This issue is resolved in VMware NSX 3.2.2

Workaround:

• If you have a stale global Transport Zone, delete it to resolve this issue via UI.
• There is no workaround if the transport Zone has a different UUID for the policy path and internal ID.