Thanks for the help. Below is some information from the client. Each vSphere server they have has 6 NICs connected and used for VM traffic. I think I mentioned it earlier, but if I didn't...3 NICs connect to one 6500 and 3 NICs connect to another 6500:
Here are the latest findings.
This morning I have been testing the ping results from two 2008 guest vmotioning to and from different vsphere host.
Pings succeed then fail and then will resume.
I used vsphere3 as my test host.
With servers 2008test1 and 2008 test2 on vsphere3 I was dropping pings, in random patterns.
I began removing physical nics from the nexus switch. They were not reassigned to a virtual switch.
Removed all nics except one to Switch1. Pinging began working fine.
Added vmnic8 connected to Switch2. Pings begin failing
Removed vmnic8 , pinging begins working.
I then added vmnic5 on Switch1, pinging remains ok. Added vmnic 6 pinging OK. All Switch1 now connected.
Went back and added vmnic9 to nexus on Switch2 dropped pings begin occurring.
Removed vmnic4 thru 6 (Switch1) ping becomes normal on vmnic9.
Add vmnic8 and vmnic10 to Switch2, pinging OK.
Then vmotioned to different hardware. Pinging then begins acting erratic.
The only system I have had time to test with is vpshere3. I can repeat the same process on other
host if needed.
---------------------------
So it looks to me like if they only connect physical NICs to one switch all is well. When they go to two it gets bad. Here is the config for each port:
description VSPHERE3-TRUNK
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 200-202,320,323,991,992,995
switchport mode trunk
-------------------------
The next thing you're going to ask me for is the N1Kv running-config and I've requested that. The uplink configuration si very straightforward. We're using mac-pinning as the distribution method, but I'll get the config to confirm that with you.
