NSX-T Data Center REST API

Patch a new LCM Edge Transport Node under Enforcement Point

If the passed Edge Transport Node does not already exist, create a new Edge Transport Node.
If it already exists, patch it.
Transport nodes are hypervisor NSX Edges that will participate
in an NSX-T overlay.this means that it will have Tier0/TIer1 uplinks and downlinks.

This API creates/updates the edge node (router) in the transport network.

Additional documentation on creating a transport node can be found
in the NSX-T Installation Guide.

In order for the transport node to forward packets,
the switch_spec property must be specified.

When creating a edge transport node, you need to specify if the edge TN switches
are already manually preconfigured on the node, or if NSX should create
and manage the edge TN switches. You specify this choice by the type
of host switches you pass in the switch_spec property of the
Edge Transport Node request payload.

For a NSX edge node, NSX Manager always configures the edge TN switch.

To allow NSX to manage the Edge TN switch configuration on NSX Edge nodes,
pass an array of switches
objects in the switch_spec property, and NSX will automatically
create edge TN switches with the properties you provide. In the current
NSX-T release, up to 16 host switches can be automatically managed.
See the switch_spec schema definition for documentation on
the properties that must be provided.

If the edge node (router) is already added in
system then it can be converted to transport node by providing node_id in
request.

If edge transport node (router) is not already present in
system then new edge transport node can be created using this API.

Request:

Method:

PATCH

URI Path(s):

/policy/api/v1/infra/sites/{site-id}/enforcement-points/{enforcementpoint-id}/edge-transport-nodes/{edge-transport-node-id}

Request Headers:

n/a

Query Parameters:

n/a

Request Body:

PolicyEdgeTransportNode+

PolicyEdgeTransportNode (schema)

Name	Description	Type	Notes
_create_time	Timestamp of resource creation	EpochMsTimestamp	Readonly Sortable
_create_user	ID of the user who created this resource	string	Readonly
_last_modified_time	Timestamp of last modification	EpochMsTimestamp	Readonly Sortable
_last_modified_user	ID of the user who last modified this resource	string	Readonly
_links	References related to this resource The server will populate this field when returing the resource. Ignored on PUT and POST.	array of ResourceLink	Readonly
_protection	Indicates protection status of this resource Protection status is one of the following: PROTECTED - the client who retrieved the entity is not allowed to modify it. NOT_PROTECTED - the client who retrieved the entity is allowed to modify it REQUIRE_OVERRIDE - the client who retrieved the entity is a super user and can modify it, but only when providing the request header X-Allow-Overwrite=true. UNKNOWN - the _protection field could not be determined for this entity.	string	Readonly
_revision	Generation of this resource config The _revision property describes the current revision of the resource. To prevent clients from overwriting each other's changes, PUT operations must include the current _revision of the resource, which clients should obtain by issuing a GET operation. If the _revision provided in a PUT request is missing or stale, the operation will be rejected.	int
_schema	Schema for this resource	string	Readonly
_self	Link to this resource	SelfResourceLink	Readonly
_system_owned	Indicates system owned resource	boolean	Readonly
advanced_configuration	Array of additional specific properties for advanced or cloud-specific deployments in key-value format.	array of KeyValuePair
appliance_config	The settings are used during deployment and consequent update of an edge, unless indicated otherwise.These settings are editable for manually deployed edge nodes as well.	PolicyVmApplianceConfig
children	Subtree for this type within policy tree Subtree for this type within policy tree containing nested elements. Note that this type is applicable to be used in Hierarchical API only.	array of ChildPolicyConfigResource Children are not allowed for this type
credentials	Username and password settings for the node. Note - these settings will be honored only during node deployment. Post deployment, CLI must be used for changing the user settings, changes to these parameters will not have any effect. If a password is not provided, then cli,root and audit passwords will get auto-generated. In order to login into a VM, need to reset the password using API https://<nsx-mgr>/api/v1/transport-nodes/<transport-node-id>/node/users/<userid>?action=reset_password Passwords explicitly reset after deployment will need to be reset again post-redeployment using the above API.	PolicyEdgeTransportNodeCredential
deployment_type	The edge node deployment type may be physical or virtual.	EdgeDeploymentType	Readonly
description	Description of this resource	string	Maximum length: 1024 Sortable
display_name	Identifier to use when displaying entity in logs or GUI Defaults to ID if not set	string	Maximum length: 255 Sortable
failure_domain_path	Path of the failure domain Set failure domain of edge transport node which will help in auto placement of TIER1 logical routers, DHCP Servers and MDProxies, if failure domain based allocation is enabled in edge cluster API. In case failure domain is not set by user explicitly, it will be always assigned with default system created failure domain.	string
form_factor		EdgeFormFactor	Default: "MEDIUM"
hostname	Host name or FQDN for edge node. Desired host name/FQDN for the VM to be deployed.	string	Required Pattern: "^(?=.{1,255}$)[0-9A-Za-z](?:(?:[0-9A-Za-z]|-){0,61}[0-9A-Za-z])?(?:\.[0-9A-Za-z](?:(?:[0-9A-Za-z]|-){0,61}[0-9A-Za-z])?)*?$"
id	Unique identifier of this resource	string	Sortable
management_interface	Applicable For LCM managed Node and contains the management interface info.	PolicyEdgeTransportManagementInterface
marked_for_delete	Indicates whether the intent object is marked for deletion Intent objects are not directly deleted from the system when a delete is invoked on them. They are marked for deletion and only when all the realized entities for that intent object get deleted, the intent object is deleted. Objects that are marked for deletion are not returned in GET call. One can use the search API to get these objects.	boolean	Readonly Default: "False"
node_type	Edge transport node type This field contains the info of type of edge transport node.	EdgeTransportNodeType	Default: "EDGE_NODE"
origin_site_id	A unique identifier assigned by the system for knowing which site owns an object This is a UUID generated by the system for knowing which site owns an object. This is used in NSX+.	string	Readonly
overridden	Indicates whether this object is the overridden intent object Global intent objects cannot be modified locally by the user. However, certain global intent objects can be overridden locally by use of this property. In such cases, the overridden local values take precedence over the globally defined values for the properties.	boolean	Readonly Default: "False"
owner_id	A unique identifier assigned by the system for the ownership of an object This is a UUID generated by the system for knowing who owns this object. This is used in NSX+.	string	Readonly
parent_path	Path of its parent Path of its parent	string	Readonly
path	Absolute path of this object Absolute path of this object	string	Readonly
realization_id	A unique identifier assigned by the system for realizing intent This is a UUID generated by the system for realizing the entity object. In most cases this should be same as 'unique_id' of the entity. However, in some cases this can be different because of entities have migrated their unique identifier to NSX Policy intent objects later in the timeline and did not use unique_id for realization. Realization id is helpful for users to debug data path to correlate the configuration with corresponding intent.	string	Readonly
relative_path	Relative path of this object Path relative from its parent	string	Readonly
remote_path	Path of the object on the remote end. This path is populated only in case of multi-site scenario. Currently it is supported only for LM objects. When LM is onboarded to multi-site platform like NAPP or GM, remote_path will be set to the globally unique path across multi-site topology . It is generated based on local site-name and uses /org tree namespace. Note: It is populated only for LM objects. Not supported on the GM.	string	Readonly
resource_type	Must be set to the value PolicyEdgeTransportNode	string
switch_spec	Edge Transport node switch specification This property is used to either create edge TN switches or to inform NSX about preconfigured edge TN switches that already exist on the transport node.	PolicyEdgeTransportNodeSwitchSpec
tags	Opaque identifiers meaningful to the API user	array of Tag	Maximum items: 30
unique_id	A unique identifier assigned by the system This is a UUID generated by the GM/LM to uniquely identify entities in a federated environment. For entities that are stretched across multiple sites, the same ID will be used on all the stretched sites.	string	Readonly
vm_deployment_config	VM deployment configuration for LCM nodes	PolicyVmDeploymentConfig (Abstract type: pass one of the following concrete types) PolicyVmDeploymentConfig PolicyVsphereDeploymentConfig

Example Request:

PATCH https://<policy-mgr>/policy/api/v1/infra/sites/default/enforcement-points/default/edge-transport-nodes/my-edge-tn-id { "failure_domain_path": "/infra/sites/default/enforcement-points/default/failure-domains/my-policy-failure-domain-id", "deployment_type": "VIRTUAL_MACHINE", "node_type": "EDGE_NODE", "form_factor": "SMALL", "hostname": "my-edge-tn-id-host.com", "vm_deployment_config": { "vc_id": "2bab11cd-ee62-407c-948c-1ff3f1e6c397", "compute_id": "domain-c18", "storage_id": "datastore-15", "edge_host_affinity_config": { "host_group_name" : "host-1" }, "reservation_info": { "memory_reservation": { "reservation_percentage": 10 }, "cpu_reservation": { "reservation_in_shares": "LOW_PRIORITY", "reservation_in_mhz": 10 } }, "placement_type": "PolicyVsphereDeploymentConfig" }, "appliance_config": { "search_domains": [ "123.1.1.1" ], "ntp_servers": [ "times.com" ], "allow_ssh_root_login": true, "dns_servers": [ "123.23.2.2", "123.4.5.5" ], ], "enable_ssh": true, "enable_upt_mode": false }, "credentials": { "credentials": { "cli_password": "Admin!23Admin", "root_password": "Admin!23Admin", "root_password": "Admin!23Admin", "cli_username": "admin", "audit_username": "audit", "audit_password": "Admin!23Admin" }, "management_interface": { "management_interface": { "ip_assignment_specs": [ { "management_port_subnets": [ { { "ip_addresses": [ "fc7e:f206:db42:0:0:0:0:2" ], "prefix_length": 48 } ], "default_gateway": [ "fc7e:f206:db42:0:0:0:0:1" ], "ip_assignment_type": "StaticIpv6" }, { "ip_assignment_type": "Dhcpv4" } ], "network_id": "dvportgroup-48" }, "switch_spec": { "switches": [ { "switch_name": "nsxHostSwitch", "profile_paths": [ { "key": "UplinkHostSwitchProfile", "value": "/infra/host-switch-profiles/my-uplink-profile-id" } ], "overlay_transport_zone_paths": [ "/infra/sites/default/enforcement-points/default/transport-zones/my-transport-zone-overlay-id" ], "vlan_transport_zone_paths": [ "/infra/sites/default/enforcement-points/default/transport-zones/my-transport-zone-vlan-id" ], "pnics": [ { "device_name": "fp-eth0", "uplink_name": "uplink1", "datapath_network_id": "dvportgroup-48" } ], "tunnel_endpoints": [ { { { { { { "ip_assignment_specs": [ { "ip_pool": "/infra/ip-pools/ippool-policy-ipv4", "ip_assignment_type": "StaticIpv4Pool" } ] ] } ] } ] } }

Successful Response:

Response Code:

200 OK

Response Headers:

n/a

Response Body:

n/a

Required Permissions:

crud

Feature:

nodes_transport_nodes

Additional Errors:

• 301 Moved Permanently
• 307 Temporary Redirect
• 400 Bad Request
• 403 Forbidden
• 409 Conflict
• 412 Precondition Failed
• 500 Internal Server Error
• 503 Service Unavailable