NSX logical segment displays a 'failed' status in NSX UI with 'Realization Error'

Products

• VMware NSX

Issue/Introduction

• Logical segment displays a 'failed' status  in NSX UI.
• Realization alarm similar to the below is observed in NSX UI:

  Edge cluster member EdgeTransportNode//infra/sites/default/enforcement-points/default/edge-transport-node/<Edge Transport Node UUID> does not have transport zone endpoint PolicyTransportZone/<Transport Zone UUID>.

• Error similar to the below is observed in NSX Manager:
  
  /var/log/syslog
  

  NSX 76778 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP15023" level="ERROR" subcomp="manager"] Edge Cluster member EdgeTransportNode//infra/sites/default/enforcement-points/default/edge-transport-node/<Edge Transport Node UUID> does not have transport zone endpoint PolicyTransportZone/<Transport Zone UUID>.

• The below API call confirms that a segment bridge profile is using the Transport Zone that is referenced in the above errors:  
  GET /policy/api/v1/infra/segments/<Segment ID>
  

  "bridge_profiles": [
          {
              "bridge_profile_path": "/infra/sites/default/enforcement-points/default/edge-bridge-profiles/<Bridge Profile ID>",
              "vlan_ids": [
                  "<VLAN IDs>"
              ],
              "vlan_transport_zone_path": "/infra/sites/default/enforcement-points/default/transport-zones/<Transport Zone ID>"

  
  

Environment

VMware NSX-T Data Center

VMware NSX

Cause

This issue can occur when a segment bridge profile is configured to use an invalid Tranzport Zone.

 

Resolution

This is a known issue impacting VMware NSX.

 

Workaround
Edit or remove the invalid bridging configuration.