VLANs use the 802.1Q standard to tag traffic as associated with a
particular VLAN. There are three main ways of using VLANs with vSphere:
Tagging allows you to send traffic belonging to multiple networks/subnets along the same cable/switch port. Before VLANs were available, to give your virtual machines access to different networks you would have had to have a separate physical cable (or 2) for each network you needed to place your VMs on. VLANs allow these networks/subnets to be trunked down a single physical connection. The tag is used to identify which subnet/segment the traffic belongs to. VLAN trunking has been common place in networks for quite a while, often used on connections between two Layer 2 network devices. The advantage of VLANs when it comes to virtualisation is that because you have a limited number of network cards available on your host’s hardware, it isn’t usually feasible to dedicate a physical network connection to just one network segment. By using VLANs to logically separate your hosts network traffic, you can provide access to many VLANs/network segments by using the same number of physical NICs.
VLAN tagging in vSphere is defined on the portgroups. A VLAN can contain multiple port groups, but a port group can only be associated with one VLAN at any given time. A prerequisite for VLAN functionality on a vSwitch is that the uplinks have to be connected to a trunk port on the physical switch. The trunk port will also need to be configured so that it carries the correct VLANS (if it is filtered).
- Virtual guest tagging (VGT) – requires VLAN driver support in the guest OS
- Virtual Switch tagging (VST) – common option, requires VLAN trunking on external switches
- External switch tagging (EST) – less flexible and requires more physical NICs
Tagging allows you to send traffic belonging to multiple networks/subnets along the same cable/switch port. Before VLANs were available, to give your virtual machines access to different networks you would have had to have a separate physical cable (or 2) for each network you needed to place your VMs on. VLANs allow these networks/subnets to be trunked down a single physical connection. The tag is used to identify which subnet/segment the traffic belongs to. VLAN trunking has been common place in networks for quite a while, often used on connections between two Layer 2 network devices. The advantage of VLANs when it comes to virtualisation is that because you have a limited number of network cards available on your host’s hardware, it isn’t usually feasible to dedicate a physical network connection to just one network segment. By using VLANs to logically separate your hosts network traffic, you can provide access to many VLANs/network segments by using the same number of physical NICs.
VLAN tagging in vSphere is defined on the portgroups. A VLAN can contain multiple port groups, but a port group can only be associated with one VLAN at any given time. A prerequisite for VLAN functionality on a vSwitch is that the uplinks have to be connected to a trunk port on the physical switch. The trunk port will also need to be configured so that it carries the correct VLANS (if it is filtered).
Creating a new Portgroup on a dvSwitch
- In vCenter browse to the network configuration page
- Right-click the appropriate switch, click New Port Group.
- On the Create Distributed Switch Port Group screen, enter the appropriate Name and Number of Ports. For VLAN type, select VLAN trunking. Enter the appropriate VLAN trunk range, click Next then click Finish.
Comments
Post a Comment