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.

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

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?

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.

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.