Virtual combat: Two VLAN of network design

VLAN tagging has three implementation options in VMware Network design. The first thing we ask is not what the technology can achieve, but what the customer needs, and then choose the right solution.

Scenario One (Virtual Switch Tagging)

This is one of the most common ways.   Each port group on the vswitch corresponds to a VLAN. The label is removed when the packet passes through the virtual switch from the physical switch. Bind labels when packets pass through a virtual switch to the physical switch.

The biggest benefit is that a ESXi physical network card can support multiple VLANs. The virtual machine does not need any driver to bind to the port group corresponding to a VLAN

A common primary error is to set the VLAN ID on port group, but the ESXi physical network card does not have the VLAN defined in trunk on the physical switch port.

Factors to consider:

In the case of the virtual network Port Group VLAN, try not to use the Nativevlan on the physical switch. That is, Cisco switches are usually vLAN1

Scenario Two (Virtual Guest Tagging)