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:
Related Posts (auto generated)
The post Vlan trunking on VMWare Server (1.x 2.x) appeared first on Luke Sheldrick's Blog.