6509 trunk to VMWare virtual switch

Unanswered Question
May 28th, 2008

We have a consultant installing VMWare.

He wants what he is calling a trunk port on the 6509.

He says he will tag both VLANs the the virtual switch will carry to the 6509.

I am taking this as he needs a trunk port on the 6509 allowing both vlans, neither one of them being the native vlan.

Meaning both VLANs will be tagged.

Am I correct in this?

description Trunk


switchport trunk allowed vlan 11,21

switchport mode trunk

switchport nonegotiate

no ip address

speed 1000

duplex full

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
niro@optonline.net Wed, 05/28/2008 - 06:47

Yes that's right...we have our vmware set up the same way. If this is the port carrying your vmware traffic I recommend setting up a two or three port etherchannel to the vmware host for redundancy.

wilson_1234_2 Wed, 05/28/2008 - 06:51

Thanks,that was a fast response.

Thanks for the input, he has specified that we are spanning across two 6509 switches and two blades across the switches.

I did not set a native vlan and the trunk defaulted to vlan 1.

I am wondering if I should change this.

niro@optonline.net Wed, 05/28/2008 - 07:05

you shouldn't have to. When he sets up the virtual switches in vmware he'd add the vlan ID to them.

chris.ramirez Wed, 05/28/2008 - 07:17

Is that the trick with vmware, an etherchannel for redundancy? We've currently been testing servers created using vmware. They run successfully for anywhere from 20-30 hours before encountering a network error that breaks there established connection to the main VM host. Any suggestions?

niro@optonline.net Wed, 05/28/2008 - 07:35

What kind of network error? What do you need to do to bring it back up? If you do set up an etherchannel make sure you change the load balancing on the virtual switch to match your cisco switch.

chris.ramirez Wed, 05/28/2008 - 07:41

Unfortunately there were no visible errors on the network that indicated any kind of problems. The server admin running these test brought to our attention that there was a "glitch" that caused his virtual machines to crash and assumed it was network related. I tried to explain that all the port statistics between vmserver and regular server. The glictch seemed to occur between his virtual machine and the physicial server running vmware.


This Discussion