08-06-2014 01:05 PM
We have a C7000 chassis that has 2 HP VC FlexFabric 10Gb/24-Port Modules. We have 4 blades in the chassis running ESXi 5.5 Update 1.
On occassion we will lose pings to/from some of the VM guests running on the chassis. This does not happen to all VMs only some VMs some of the time. I am unable to reproduce the problem, I can only troubleshoot it as it happens.
We have narrowed down the problem to only the ESXi hosts on the chassis. I can migrate the VM amongst the chassis hosts and the problem persists, I migrate the VM to a host not inside the chassis and all is fine.
Right now my goto fix for the problem is to migrate the problem VM off the chassis.
We have done the following things to try and resolve this issue.
1. Upgraded all firmware for VC, OA and the Blades to the recommended firmware specs provided by HP. http://vibsdepot.hp.com/hpq/recipes/HP-VMware-Reci
2. Re-Installed the VMWare hosts using HP's Custom ISO
3. Validated that all drivers conform to HP's recommendations http://vibsdepot.hp.com/hpq/recipes/HP-VMware-Reci
4. We noticed that the Bay 1 flexfabric card is showing as subordinate/invalid. So we replaced the card in Bay 1 and it is still showing as insubordinate/invalid.
5. Validated that the network configuration in the chassis is accurate.
This is getting very frustrating to troubleshoot with HP support. They are convinced it's not a hardware problem even though the FlexFabric card in Bay 1 still shows insubordinate/invalid and the problem still persists.
Does anyone have any ideas on what else to try here?
08-08-2014 03:41 PM
You can the below options to make sure Module Configuration is in Sync. Subordinate is fine.
In a Virtual Connect Domain with a Large Number of Defined Ethernet Networks May Experience a Virtual Connect Network Outage When a Virtual Connect Ethernet Module Is Restarted Under Specific Circumstances
08-23-2014 11:24 PM
hi, try to create new profile in the VC, and reassign for each host.
msh_it | UAE | AbuDhabi
If you feel this was helpful please click the KUDOS! star in the left column!
08-27-2014 12:34 PM
I actually received quite a bit of response over on the VMware communities regarding this issue... https://communities.vmware.com/message/2413193
So far what appears to have resolved my issue was switching from VLAN tunneling to Shared Uplink Sets. Although there is a limit to only being able to map 162 networks in the server profile, and we are very close to reaching this threshold.