The VNIC's availability domain.
Example: {@code Uocm:PHX-AD-1}
The OCID of the compartment containing the VNIC.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
The hostname for the VNIC's primary private IP. Used for DNS. The value is the hostname portion of the primary private IP's fully qualified domain name (FQDN) (for example, {@code bminstance1} in FQDN {@code bminstance1.subnet123.vcn1.oraclevcn.com}). Must be unique across all VNICs in the subnet and comply with RFC 952 and RFC 1123.
For more information, see [DNS in Your Virtual Cloud Network](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/dns.htm).
Example: {@code bminstance1}
The OCID of the VNIC.
Whether the VNIC is the primary VNIC (the VNIC that is automatically created and attached during instance launch).
The current state of the VNIC.
The MAC address of the VNIC.
If the VNIC belongs to a VLAN as part of the Oracle Cloud VMware Solution, the MAC address is learned. If the VNIC belongs to a subnet, the MAC address is a static, Oracle-provided value.
Example: {@code 00:00:00:00:00:01}
A list of the OCIDs of the network security groups that the VNIC belongs to.
If the VNIC belongs to a VLAN as part of the Oracle Cloud VMware Solution (instead of belonging to a subnet), the value of the {@code nsgIds} attribute is ignored. Instead, the VNIC belongs to the NSGs that are associated with the VLAN itself. See Vlan.
For more information about NSGs, see NetworkSecurityGroup.
The private IP address of the primary {@code privateIp} object on the VNIC. The address is within the CIDR of the VNIC's subnet.
Example: {@code 10.0.3.3}
The public IP address of the VNIC, if one is assigned.
Whether the source/destination check is disabled on the VNIC. Defaults to {@code false}, which means the check is performed. For information about why you would skip the source/destination check, see Using a Private IP as a Route Target.
If the VNIC belongs to a VLAN as part of the Oracle Cloud VMware Solution (instead of belonging to a subnet), the {@code skipSourceDestCheck} attribute is {@code true}. This is because the source/destination check is always disabled for VNICs in a VLAN.
Example: {@code true}
The OCID of the subnet the VNIC is in.
The date and time the VNIC was created, in the format defined by RFC3339.
Example: {@code 2016-08-25T21:10:29.600Z}
A virtual network interface card. Each VNIC resides in a subnet in a VCN. An instance attaches to a VNIC to obtain a network connection into the VCN through that subnet. Each instance has a primary VNIC that is automatically created and attached during launch. You can add secondary VNICs to an instance after it's launched. For more information, see Virtual Network Interface Cards (VNICs).
Each VNIC has a *primary private IP* that is automatically assigned during launch. You can add *secondary private IPs* to a VNIC after it's created. For more information, see {@link #createPrivateIp(CreatePrivateIpRequest) createPrivateIp} and [IP Addresses](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/managingIPaddresses.htm).
If you are an Oracle Cloud VMware Solution customer, you will have secondary VNICs that reside in a VLAN instead of a subnet. These VNICs have other differences, which are called out in the descriptions of the relevant attributes in the {@code Vnic} object. Also see Vlan.
To use any of the API operations, you must be authorized in an IAM policy. If you're not authorized, talk to an administrator. If you're an administrator who needs to write policies to give users access, see [Getting Started with Policies](https://docs.cloud.oracle.com/iaas/Content/Identity/Concepts/policygetstarted.htm).