TransportNodePlacementConfig
TransportNodePlacementConfig
Transport Node placement Config
JSON Example
{
"node_settings": {
"advanced_configuration": [
{
"key": "string",
"value": "string"
}
],
"allow_ssh_root_login": false,
"dns_servers": [
"string"
],
"enable_ssh": false,
"enable_upt_mode": false,
"hostname": "string",
"ntp_servers": [
"string"
],
"search_domains": [
"string"
],
"syslog_servers": [
{
"facility": [
"string"
],
"log_level": "string",
"message_id": [
"string"
],
"name": "string",
"port": "string",
"protocol": "string",
"server": "string",
"structured_data": [
{
"key": "string",
"value": "string"
}
]
}
]
},
"node_user_settings": {
"audit_password": "string",
"audit_username": "string",
"cli_password": "string",
"cli_username": "string",
"root_password": "string"
},
"vm_deployment_config": {
"placement_type": "string"
},
"vm_id": "string"
}
node_settings
Optional
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. If using DHCP, you must leave the following fields unset: search_domains, management_port_subnets, dns_servers and default_gateway_addresses. EdgeNodeSettings reports current values configured on the edge node. If the settings lag with actual state on the edge, these may be refreshed at NSX Manager using API POST api/v1/transport-nodes /<transport-node-id>?action=refresh_node_configuration&resource_type= EdgeNode
string
vm_id
Required
The edge node vm which is a transport node.