Segments in projects have no transport zone associated.
Can be confirmed using the following GET API.
GET policy/api/v1/orgs/default/projects/[Project Name]/infra/segments/[Segment Name]
"transport_zone_path" is right below the "connectivity_path" entry.
But the result has no "transport_zone_path" entry.
For example:
{
"type": "ROUTED",
"subnets": [
{
"gateway_address": "192.##.##.1/24",
"network": "192.##.##.0/24"
},
{
"gateway_address": "2001:###::1/64",
"network": "2001:###::/64"
}
],
"connectivity_path": "/orgs/default/projects/TestProject/infra/tier-1s/TestprojectT1-GW",
"advanced_config": {
"hybrid": false,
"multicast": true,
"inter_router": false,
"local_egress": false,
"urpf_mode": "STRICT",
"connectivity": "ON"
},
"admin_state": "UP",
"replication_mode": "MTEP",
"resource_type": "Segment",
"id": "TestprojectSegment01",
"display_name": "TestprojectSegment01",
"path": "/orgs/default/projects/TestProject/infra/segments/TestprojectSegment01",
"relative_path": "TestprojectSegment01",
"parent_path": "/orgs/default/projects/TestProject/infra",
"unique_id": "<unique_id>",
"realization_id": "<realization_id>",
"owner_id": "<owner_id>",
"marked_for_delete": false,
"overridden": false,
"_system_owned": false,
"_protection": "NOT_PROTECTED",
"_create_time": 1710869453954,
"_create_user": "admin",
"_last_modified_time": 1710869453954,
"_last_modified_user": "admin",
"_revision": 0
}
VMware NSX 4.0.x
VMware NSX 4.1.x
Segments in projects that are connected to T1 gateway use the edge cluster to determine transport zone.
Thus for a T1 gateway with HA mode "Distributed Only" and edge nodes aren't specified, transport zones cannot be determined.
To Workaround, associate an edge cluster for the T1 Gateway
1. Set edge cluster.
2. Create a segment.
Issue is fixed in NSX 4.2.0.
Wherein, the default overlay transport zone is set when segment is connected to "Distributed Only" T1 gateway.
This change is set during upgrades to NSX 4.2.0 as well.