VMware Cloud Community
fgl
Enthusiast
Enthusiast
Jump to solution

Intel VGT vlan tagging

Hello all,

I have any interesting dilemma in which I inherited a VM that is on multiple vlans via VGT vlan tagging within the OS on the VM and the vNic is tagged to a vlan trunk of 4095 which allows it to pass all vlan traffic through and this is fine and working as expected. Now for my dilemma I can not figure out how the previous admin (how is no longer here) setup and define the vlans inside the OS of the VM as there are no vlan interface nor any kind of vlan tab in the properties of the network adapter nor any kind of advance setting tabs that I can find, there is nothing under the start menu nor under device managers and etc... I am at a puzzle on how he setup the vlans in the first place, is there some hidden Intel application I need to run? I have the VGT driver and installer he used "pro2kxp_v14_0.exe" that I can run again but I'm concerning that if I reinstall on top it would wipe out all the existing vlans definitions and there are about 15 vlans which would be bad for me. Any ideas or suggestions?

Thanks in advance.

Reply
0 Kudos
1 Solution

Accepted Solutions
bwaterhouse
Enthusiast
Enthusiast
Jump to solution

To configure the guest OS you need the Intel Proset software installed. Which by the sounds of it you do.

To access the confiugration you usally go to Device Manager then bring up the properties for the actual network card. From memory you may need to do this from a Console session rather than RDP connection as the Intel software may not load in terminal services.

-ben

View solution in original post

Reply
0 Kudos
4 Replies
AndreTheGiant
Immortal
Immortal
Jump to solution

Have a look at:

http://kb.vmware.com/kb/1004252 - Sample configuration of virtual machine(VM) VLAN Tagging (VGT Mode) in ESX

Andre

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
bwaterhouse
Enthusiast
Enthusiast
Jump to solution

To configure the guest OS you need the Intel Proset software installed. Which by the sounds of it you do.

To access the confiugration you usally go to Device Manager then bring up the properties for the actual network card. From memory you may need to do this from a Console session rather than RDP connection as the Intel software may not load in terminal services.

-ben

Reply
0 Kudos
fgl
Enthusiast
Enthusiast
Jump to solution

Andre, thanks for the info but I am already aware of that KB.

Ben, you are the man. Yes I had to login as a console session in order for the additional Intel tabs to show up. Thanks.

Reply
0 Kudos
bwaterhouse
Enthusiast
Enthusiast
Jump to solution

Happy to help. I have got caught by the same thing on a physical server before.

Reply
0 Kudos