To support host-managed VLANs, the vNIC must be created in trunk mode. All vNICs are created and configured using the GUI.
This mode informs the vNIC configuration software on the chassis that the VLANs are configured from the host side and the fabric should honor VLAN configuration requests coming from the host. The fabric can thus allow tagged packets to go across this vNIC which otherwise would get dropped when the vNIC is in the access mode of operation.
Host-managed VLANs are configured and managed from the host server using the native OS tools. This method can help administrators by allowing them to use traditional administrative tools and methods to configure the vNIC accordingly.
A successful VLAN configuration requires you to configure the following parameters:
Ethernet port parameters – Ethernet port parameters are set first.
VNIC parameters – The vNIC parameters are set after the port parameters.
Configuring VLANs requires you to set VLAN properties on an Ethernet port and on any vNICs terminating on that port. The names and definitions of VLAN properties for an Ethernet port and a vNIC are identical. For the syntax, refer to lag in Oracle Fabric OS 1.0.2 Command Reference.
These properties collectively define rules that govern how the fabric operates and handles VLAN tagged and untagged frames.
When you originally configured a VLAN, you set VLAN properties on the Ethernet port before any vNICs are assigned to it. Any mismatch in configuration results in improper handling of data traffic.