System Administration > Configuration > Fabric > Transport Zones

List Transport Zones (Deprecated)

Returns information about configured transport zones. NSX requires at
least one transport zone. NSX uses transport zones to provide connectivity
based on the topology of the underlying network, trust zones, or
organizational separations. For example, you might have hypervisors that
use one network for management traffic and a different network for VM
traffic. This architecture would require two transport zones. The
combination of transport zones plus transport connectors enables NSX to
form tunnels between hypervisors. Transport zones define which interfaces
on the hypervisors can communicate with which other interfaces on other
hypervisors to establish overlay tunnels or provide connectivity to a VLAN.
A logical switch can be in one (and only one) transport zone. This means
that all of a switch's interfaces must be in the same transport zone.
However, each hypervisor virtual switch (OVS or VDS) has multiple
interfaces (connectors), and each connector can be attached to a different
logical switch. For example, on a single hypervisor with two connectors,
connector A can be attached to logical switch 1 in transport zone A, while
connector B is attached to logical switch 2 in transport zone B. In this
way, a single hypervisor can participate in multiple transport zones. The
API for creating a transport zone requires that a single host switch be
specified for each transport zone, and multiple transport zones can share
the same host switch.
Deprecated: This api is now deprecated. Please use new api - /policy/api/v1/infra/sites/<site-id>/enforcement-points/ <enforcementpoint-id>/transport-zones

Request:

Method:
GET
URI Path(s):
/api/v1/transport-zones
Request Headers:
n/a
Query Parameters:
TransportZoneListParameters+
Request Body:
n/a

Example Request:

GET https://<nsx-mgr>/api/v1/transport-zones/

Successful Response:

Response Code:
200 OK
Response Headers:
Content-type: application/json
Response Body:
TransportZoneListResult+

Example Response:

{ "results": [ { "_revision": 0, "id": "c08d57bf-247d-4a5e-9acd-c5f2860e2872", "resource_type": "TransportZone", "transport_type": "OVERLAY", "_last_modified_user": "admin", "_last_modified_time": 1412873095391, "_create_time": 1412873095391, "_create_user": "admin", "_schema": "/v1/schema/TransportZone" }, { "_revision": 0, "id": "7c57c5a7-c742-4ee2-8fae-a9ac6a01309c", "resource_type": "TransportZone", "transport_type": "OVERLAY", "_last_modified_user": "admin", "_last_modified_time": 1412873062407, "_create_time": 1412873062407, "_create_user": "admin", "_schema": "/v1/schema/TransportZone" }, { "_revision": 0, "id": "c55ec097-0b53-4103-9426-18e135250c29", "resource_type": "TransportZone", "transport_type": "OVERLAY", "_last_modified_user": "admin", "_last_modified_time": 1412877285032, "_create_time": 1412877285032, "_create_user": "admin", "_schema": "/v1/schema/TransportZone" } ] }

Required Permissions:

read

Feature:

transport_zones_transport_zones

Additional Errors: