Attachment information on the port
Detail information about port attachment
Indicate how IP will be allocated for the port
|string||Enum: IP_POOL, MAC_POOL, BOTH, NONE, DHCP|
ID used to identify/look up a child attachment behind a parent attachment
|bms_interface_config||Application interface configuration for Bare metal server
Indicate application interface configuration for Bare Metal Server.
|context_id||Context ID based on the type
If type is CHILD and the parent port is on the same segment as the child port, then this
field should be VIF ID of the parent port.
If type is CHILD and the parent port is on a different segment, then this
field should be policy path of the parent port.
If type is INDEPENDENT/STATIC, then this field should be transport node ID.
Set to PARENT when type field is CHILD. Read only field.
|evpn_vlans||Evpn tenant VLAN IDs the Parent logical-port serves.
List of Evpn tenant VLAN IDs the Parent logical-port serves in Evpn Route-Server mode. Only effective when attachment type is PARENT and the logical-port is attached to vRouter VM.
|array of string||Minimum items: 0
Maximum items: 1000
Flag to indicate if hyperbus configuration is required.
|string||Enum: ENABLE, DISABLE
|id||Port attachment ID
VIF UUID on NSX Manager. If the attachement type is PARENT, this property is required.
Not valid when type field is INDEPENDENT, mainly used to identify
traffic from different ports in container use case.
Type of port attachment. STATIC is added to replace INDEPENDENT. INDEPENDENT type and PARENT type are deprecated.
|string||Enum: PARENT, CHILD, INDEPENDENT, STATIC|