Create Transport Node
Enables a fabric node to act as a transport node.
Additional documentation on creating a transport node can be found in the NSX-T Installation Guide.
Transport nodes are hypervisor hosts and NSX Edges that will participate in an NSX-T overlay. For a hypervisor host, this means that it hosts VMs that will communicate over NSX-T logical switches. For NSX Edges, this means that it will have logical router uplinks and downlinks.
When creating a transport node, you must provide the node id of an existing fabric node (hypervisor host or NSX Edge node) in the node_id property of the payload. This property is required.
Additionally, in order for the transport node to forward packets, the host_switch_spec property must be specified.
Host switches (called bridges in OVS on KVM hypervisors) are the individual switches within the host virtual switch. Virtual machines are connected to the host switches.
When creating a transport node, you need to specify if the host switches are already manually preconfigured on the node, or if NSX should create and manage the host switches. You specify this choice by the type of host switches you pass in the host_switch_spec property of the TransportNode request payload.
For a KVM host, you can preconfigure the host switch, or you can have NSX Manager perform the configuration. For an ESXi host or NSX Edge node, NSX Manager always configures the host switch.
To preconfigure the host switches on a KVM host, pass an array of PreconfiguredHostSwitchSpec objects that describes those host switches. In the current NSX-T release, only one prefonfigured host switch can be specified. See the PreconfiguredHostSwitchSpec schema definition for documentation on the properties that must be provided. Preconfigured host switches are only supported on KVM hosts, not on ESXi hosts or NSX Edge nodes.
To allow NSX to manage the host switch configuration on KVM hosts, ESXi hosts, or NSX Edge nodes, pass an array of StandardHostSwitchSpec objects in the host_switch_spec property, and NSX will automatically create host switches with the properties you provide. In the current NSX-T release, up to 5 host switches can be automatically managed. See the StandardHostSwitchSpec schema definition for documentation on the properties that must be provided.
Note: previous versions of NSX-T used a property named host_switches to specify the host switch configuration on the transport node. That property is deprecated, but still functions. You should configure new host switches using the host_switch_spec property.
{
"_self": {
"action": "string",
"href": "string",
"rel": "string"
},
"_links": [
{
"action": "string",
"href": "string",
"rel": "string"
}
],
"_schema": "string",
"_revision": 0,
"_system_owned": false,
"display_name": "string",
"description": "string",
"tags": [
{
"scope": "string",
"tag": "string"
}
],
"_create_user": "string",
"_protection": "string",
"_create_time": 0,
"_last_modified_time": 0,
"_last_modified_user": "string",
"id": "string",
"resource_type": "string",
"host_switches": [
{
"pnics": [
{
"uplink_name": "string",
"device_name": "string"
}
],
"host_switch_name": "string",
"static_ip_pool_id": "string",
"host_switch_profile_ids": [
{
"value": "string",
"key": "string"
}
]
}
],
"host_switch_spec": {
"resource_type": "string"
},
"node_id": "string",
"maintenance_mode": "string",
"transport_zone_endpoints": [
{
"transport_zone_id": "string",
"transport_zone_profile_ids": [
{
"profile_id": "string",
"resource_type": "string"
}
]
}
]
}
Created
{
"_self": {
"action": "string",
"href": "string",
"rel": "string"
},
"_links": [
{
"action": "string",
"href": "string",
"rel": "string"
}
],
"_schema": "string",
"_revision": 0,
"_system_owned": false,
"display_name": "string",
"description": "string",
"tags": [
{
"scope": "string",
"tag": "string"
}
],
"_create_user": "string",
"_protection": "string",
"_create_time": 0,
"_last_modified_time": 0,
"_last_modified_user": "string",
"id": "string",
"resource_type": "string",
"host_switches": [
{
"pnics": [
{
"uplink_name": "string",
"device_name": "string"
}
],
"host_switch_name": "string",
"static_ip_pool_id": "string",
"host_switch_profile_ids": [
{
"value": "string",
"key": "string"
}
]
}
],
"host_switch_spec": {
"resource_type": "string"
},
"node_id": "string",
"maintenance_mode": "string",
"transport_zone_endpoints": [
{
"transport_zone_id": "string",
"transport_zone_profile_ids": [
{
"profile_id": "string",
"resource_type": "string"
}
]
}
]
}
{
"details": "string",
"related_errors": [
"ApiError Object"
],
"module_name": "string",
"error_message": "string",
"error_code": 0
}
Additional data about the error
Further details about the error
The module name where the error occurred
A description of the error
A numeric error code
{
"details": "string",
"related_errors": [
"ApiError Object"
],
"module_name": "string",
"error_message": "string",
"error_code": 0
}
Additional data about the error
Further details about the error
The module name where the error occurred
A description of the error
A numeric error code
{
"details": "string",
"related_errors": [
"ApiError Object"
],
"module_name": "string",
"error_message": "string",
"error_code": 0
}
Additional data about the error
Further details about the error
The module name where the error occurred
A description of the error
A numeric error code
{
"details": "string",
"related_errors": [
"ApiError Object"
],
"module_name": "string",
"error_message": "string",
"error_code": 0
}
Additional data about the error
Further details about the error
The module name where the error occurred
A description of the error
A numeric error code
{
"details": "string",
"related_errors": [
"ApiError Object"
],
"module_name": "string",
"error_message": "string",
"error_code": 0
}
Additional data about the error
Further details about the error
The module name where the error occurred
A description of the error
A numeric error code
{
"details": "string",
"related_errors": [
"ApiError Object"
],
"module_name": "string",
"error_message": "string",
"error_code": 0
}
Additional data about the error
Further details about the error
The module name where the error occurred
A description of the error
A numeric error code