Newly created segment uses incorrect local Transport Zone when Tier-1 Gateway is set to Distributed only
search cancel

Newly created segment uses incorrect local Transport Zone when Tier-1 Gateway is set to Distributed only

book

Article ID: 431243

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

A stretch segment created on the GM is successfully pushed to all three local sites; however, the segment does not appear within the local Transport Zones (TZ). This prevents the segment from being realized correctly at the local manager level.

Environment

NSX 4.1.2.1

Cause

The Tier 1 didn't have an Edge cluster allocated to it. 

Resolution

As a workaround is to add the edge cluster to the Tier 1 Gateway in question. 

  • Edit the Tier 1 Gateway. 
  • HA mode needs to be on Active Standby or Active Active
  • Add the Edge Cluster and save it. 

Additional Information

NSX Segments in projects displays message "Project Default Transport Zone was assigned at time of Project creation to Transport zone ID: undefined"