HostSwitchConfigOption

Host Switch configuration option specification

JSON Example

{
    "host_switch_id": "string",
    "host_switch_profile_ids": [
        {
            "key": "string",
            "value": "string"
        }
    ],
    "ip_assignment_spec": {
        "resource_type": "string"
    },
    "ipv6_assignment_spec": {
        "resource_type": "string"
    },
    "uplinks": [
        {
            "uplink_name": "string",
            "vds_lag_name": "string",
            "vds_uplink_name": "string"
        }
    ]
}

string

host_switch_id

Optional

This field is writable only in case of VDS type HostSwitch and system generated for NVDS type. For VDS type host switch, This field is used to lookup a VDS from corresponding Compute Manager and then can be configured for logical networking. For NVDS type host switch, This field is system generated and if provided will be overwritten.

array of HostSwitchProfileTypeIdEntry

host_switch_profile_ids

Optional

Host switch profiles bound to this host switch. If a profile ID is not provided for any HostSwitchProfileType that is supported by the transport node, the corresponding default profile will be bound to the host switch. If transport node is created using Policy APIs, use policyPaths instead of UUIDs.

IpAssignmentSpec

ip_assignment_spec

Optional

Abstract base type for specification of IPs to be used with host switch virtual tunnel endpoints

Ipv6AssignmentSpec

ipv6_assignment_spec

Optional

Abstract base type for specification of IPv6 IPs to be used with host switch virtual tunnel endpoints

array of VdsUplink

uplinks

Optional

If VDS is used as a HostSwitch this attribute must be specified. You can associate uplinks from UplinkHostSwitchProfile to either VDS uplink or LAG. VDS uplink or LAG will inherit the global VDS level teaming policy from vSphere. NSX managed uplink or LAG will have NSX teaming policy configured through UplinkHostSwitchProfile.

Property Of

TransportNodeProfileSubConfig