13 HP blade servers in a VM- ESXi5 cluster. 2 of the blades are in Blade Center #2. All servers have: 2 paired/redundant nics for vMotion and vMgmt, on 2 vLans 2 paired/redundant nics for Dat...
See more...
13 HP blade servers in a VM- ESXi5 cluster. 2 of the blades are in Blade Center #2. All servers have: 2 paired/redundant nics for vMotion and vMgmt, on 2 vLans 2 paired/redundant nics for Data network supporting 3 vLANs Without any apparent reason, One of the Data vLANs stopped working for the two blades in BC#2. It is the "Default" vLAN ( "0" ) for that segment. The other vLANs continue to work fine. vLan 0 works fine in the other blade center. vMotion, management, console, etc all work. We've rebooted the ESX boxes and the HP blade switches and no change. Nosed around logs, configs, etc and nothing apparent. ESX does not report a disconnect or any other issues. Infact, before I remembered to turn off DRS, it pushed one of the affected VMs back while I was clearing for a reboot :smileysilly: Because it's both blades in one chassis, I'm leaning towards a chassis issue, or the next step out. Network guys say "Not Us", VM guys say "Not Us" .. any ideas where to look or pin this down further? Thanks.