Vlan trunking on VMWare Server (1.x 2.x)

Posted on November 13th, 2008 by Luke Sheldrick.
Categories: IT / Tech.
Tags: , , , , .

13 11 2008

Someone was telling me the other day how they’d setup vlan trunking on the linux server, using the 802.1q kernel module, and then binding the ‘virtual’ interfaces to the vmnet’s. This wasn’t something I’d thought about before, as I’d gone a different route (sticking a few 4 port nics) in my servers, which also meant I didn’t have the bandwidth limitation. However this was all on a linux server, so is pretty straight forward.

I was rather bored on the grave yard shift last night, and needed an extra vlan on my lab vmhost at home, so set off to see how easy it is to do under Windows 2003, which my vmhost is currently built as. My lab server in question is a HP xw6000, so comes with the Broadcom NetXtreme chipset. Looking around they have a suite you can install, BACS (Broadcom Advance Control Suite). This allows you to setup virtual interfaces, which the OS (and VMWare) just see as being an additional nic.

So all I needed to do is setup the switch port as a trunk, on my Cisco C2948 in the lab, add the vlans I wanted to BACS, and then assign the new nics to a vmnet. All is working quiet well.

Also tried it on a Intel PRO nic, with equally pleasing results. A few pic’s below:



Comment on November 13th, 2008.

That’s how we had the old GSX servers set up.

Luke Sheldrick

Comment on November 15th, 2008.

Would also seem like pFsense doesn’t like to run on one of the ‘virtual virtual’ interfaces, which kind of sucks. Not really a huge problem as I can either run it of the actual trunked nic, or one of the other nics I have on the server, being assigned to a vmnet.


Comment on November 19th, 2008.

Hi, Luke
How it does works in VMWare Server 2.0. on the Web Admin interface it doesn’t appear on network list, only physical NICs 🙁

Luke Sheldrick’s Blog » Vlan trunking on VMWare Server (1.x 2.x)… Continued

Pingback on November 20th, 2008.

[…] Vlan trunking on VMWare Server (1.x 2.x) […]

Leave a comment

Comments can contain some xhtml. Names and emails are required (emails aren't displayed), url's are optional.