InlineEdgeNode1

JSON Example

{
    "allocation_list": [
        "string"
    ],
    "deployment_config": {
        "form_factor": "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"
        }
    },
    "deployment_type": "string",
    "node_settings": "EdgeNodeSettings Object"
}

array of string

allocation_list

Optional

List of logical router ids to which this edge node is allocated.

EdgeNodeDeploymentConfig

deployment_config

Optional

deployment_config

string

deployment_type

Optional

Supported edge deployment type.

Possible values are : VIRTUAL_MACHINE, PHYSICAL_MACHINE, UNKNOWN,

EdgeNodeSettings

node_settings

Required

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

Used By

EdgeNode