DITGUY2012 wrote:
Wow Josh. If only you had written the documentation. That's the trouble with it. People like me look for definitive instructions because we're not 24x7 network guys. Great documentation would layout the reasons to go this way or that like you just did. That being said, here's my summary based on this discussion.
1. We have multiple VLANs running down 3 links on the etherchannel. Thus we should use trunk mode since it's not a single one.
2. We have another etherchannel with just 1 vlan (vmotion), but across two links. that should be access mode. Or is it still trunk because it's multiple links?
3. I'm not sure what crash dump logger is nor how it applies to my situation.
4. I've seen the bpduguard setting before what is the exact syntax to use for us? 6500 series.
5. I'm not sure if our switch would want to route on this port. How do I tell? Right now I have switchport setting in there.
Thanks!
No problems 
For reference, the other documentation issue is one of language. On HP networking hardware, "trunk" is their word for etherchannel, and has nothing to do with the "access vs trunk" port debate, which they refer to as "tagged vs untagged"
1. Yes
2. You could certainly make this an access port.
3. If your server ever starts to have a problem with crashing, VMware may want a copy of the crash log in order to debug it. You can see an article on setting it up here: Setting up the ESXi 5.0 Dump Collector | VMware vSphere Blog - VMware Blogs.
4. Sorry I'm not familiar with that model
5. I believe if the switchport setting is there and connectivity seems to work you can consider yourself safe