Understanding VLAN Tagging Options in vSphere

No video

Understanding VLAN Tagging Options in vSphere

Рет қаралды 16,577

VirtualizeStuff

Күн бұрын

Understanding VLAN tagging options in vSphere.

Пікірлер: 16

@keekeh_007_it9 8 ай бұрын

Great content, keep it up!!

@lukesky7934 8 ай бұрын

Excellent video!

@VirtualizeStuff 8 ай бұрын

Glad you liked it!

@hasarangam3045 3 жыл бұрын

This is a great explanation , awsome

@VirtualizeStuff 3 жыл бұрын

Glad it was helpful!!

@leester9487 6 ай бұрын

What diagram software is that? Stencils?

@VirtualizeStuff 6 ай бұрын

The diagrams in this video were created in Adobe Illustrator however now I use Excalidraw. For custom icons are created in Illustrator and then import into Excalidraw.

@vidsjust8349 Жыл бұрын

it's too complicated for me. which books, tutorials do you recommend start learning about this?

@nislau03 Жыл бұрын

Do you need to configure the physical NIC as tagged port to allow port groups VLANS? if the switch uplink port is configured as tagged but the physical VMware NIC is not configured as tagged I am not following how port groups VLANS can communicate out. Thank you

@VirtualizeStuff Жыл бұрын

Hi Nils, Configuration isn't required on the physical NIC. The magic can happen in two places, depending on requirements in this example VST (3:16). The first is the physical switch, where I configured the physical interfaces into Trunk mode. Then tagged all VLANs I wanted to send down to the physical NIC of the ESXi hosts. The second place is the virtual switch on the VMware side, where the physical NIC is connected. To route traffic correctly, you configure the virtual switch port groups by selecting a VLAN type (VLAN, VLAN Trunking, Private VLAN) & specifying VLAN IDs. If you would like, happy to jump on Zoom to discuss it further just reach out to me on Twitter at @VirtualizeStuff

@bumankulu Жыл бұрын

@@VirtualizeStuff hi am using vphere 6.7... i have configured port-grp to vlan 10 and then trunk on the physical port of the switch. Not sure why it's not communicating.

@voktamondal1472 14 күн бұрын

First of all thank you for the video. In your video i think there are some mistakes : at 01:08 we can see that the vmnic2 is connected to an untagged port on the physical switch. But at 3:23, you say that the physical port connected to vmnic2 is tagged with vlan 30. Thats not matching with the drawing. Besides, demoVST uses vmnic2 as active uplink which is connected to an untagged port (drawing). So the traffic comming to demoVST from the untagged port is not tagged anymore when it reachs demoVST. Please tell me if I'm right. Because I'm confused with what you are showing in this video. THANKS

@VirtualizeStuff 9 күн бұрын

I'm tagging all VLANs for ports gi25, gi26, gi27, gi28 as mentioned 0:45 and interfaces gi27-28 have VLAN 50 set to is untagged as shown in 5:05. Before I go into the port details you can see the ports gi25 & gi26 are tagged with the vlans (11T, 30T, 50T, 55T ) while gi27 & gi28 has vlans tagged to but vlan 50 is set to UP (untagged). I agree the diagram could have been better to make this easier to understand as it looks like I am only tagging interface gi25.

@sawww005sa4 3 жыл бұрын

Halo, if tagged trunk on physical switch ,vsphete vds port group untagged, can work?

@VirtualizeStuff Жыл бұрын

No, since your sending a tagged VLAN down the wire from the physical switch something must remove that tag. In that case you would have to configure the port group with VLAN Type: VLAN and specify the VLAN ID: 30 (3:16) that matches the tagged VLAN from physical switch.