SegmentPortState (type)

{
  "additionalProperties": false, 
  "description": "Contains realized state of the segment port. For example: transport node on which the port is located, discovered and realized address bindings of the port.", 
  "id": "SegmentPortState", 
  "module_id": "PolicyConnectivityStatistics", 
  "properties": {
    "attachment": {
      "$ref": "SegmentPortAttachmentState, 
      "readonly": true, 
      "required": false, 
      "title": "Segment port attachment state"
    }, 
    "discovered_bindings": {
      "description": "Contains the list of address bindings for a segment port that were automatically dicovered using various snooping methods like ARP, DHCP etc.", 
      "items": {
        "$ref": "AddressBindingEntry
      }, 
      "title": "Segment port bindings discovered automatically", 
      "type": "array"
    }, 
    "duplicate_bindings": {
      "description": "If any address binding discovered on the port is also found on other port on the same segment, then it is included in the duplicate bindings list along with the ID of the port with which it conflicts.", 
      "items": {
        "$ref": "DuplicateAddressBindingEntry
      }, 
      "title": "Duplicate segment port address bindings", 
      "type": "array"
    }, 
    "realized_bindings": {
      "description": "List of segment 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.", 
      "items": {
        "$ref": "AddressBindingEntry
      }, 
      "title": "Realized segment port bindings", 
      "type": "array"
    }, 
    "transport_node_ids": {
      "items": {
        "type": "string"
      }, 
      "required": false, 
      "title": "Identifiers of the transport nodes where the port is located", 
      "type": "array"
    }
  }, 
  "title": "Realized state of the segment port on enforcement point", 
  "type": "object"
}