LogicalPortState

LogicalPortState
LogicalPortState

Contians realized state of the logical port. For example, transport node on which the port is located, discovered and realized address bindings of the logical port.

JSON Example
{
    "attachment": {
        "attachers": [
            {
                "entity": "string",
                "host": "string"
            }
        ],
        "id": "string",
        "state": "string"
    },
    "discovered_bindings": [
        {
            "binding": {
                "ip_address": "string",
                "mac_address": "string",
                "vlan": 0
            },
            "binding_timestamp": 0,
            "source": "string"
        }
    ],
    "duplicate_bindings": [
        {
            "binding": {
                "ip_address": "string",
                "mac_address": "string",
                "vlan": 0
            },
            "binding_timestamp": 0,
            "source": "string",
            "conflicting_port": "string"
        }
    ],
    "id": "string",
    "realized_bindings": [
        {
            "binding": {
                "ip_address": "string",
                "mac_address": "string",
                "vlan": 0
            },
            "binding_timestamp": 0,
            "source": "string"
        }
    ],
    "transport_node_ids": [
        "string"
    ]
}
attachment
Optional

VIF attachment state of a logical port

discovered_bindings
Optional

Contains the list of address bindings for a logical port that were automatically dicovered using various snooping methods like ARP, DHCP etc.

duplicate_bindings
Optional

If any address binding discovered on the port is also found on other port on the same logical switch, then it is included in the duplicate bindings list along with the ID of the port with which it conflicts.

string
id
Required

Id of the logical port

realized_bindings
Optional

List of logical port bindings that are realized. This list may be populated from the discovered bindings or manual user specified bindings. This binding configuration can be used by features such as firewall, spoof-guard, traceflow etc.

array of string
transport_node_ids
Optional

Identifiers of the transport node where the port is located