VC 3.51 woes

[ricdanger21]

Hi there,

After I updated from VC 3.30 to VC 3.51 half of my uplinks on ESX where down.

My other servers, running XenServer and Windows, still had all the uplinks up.

I could only get the uplinks back after a reboot of the ESX servers.

Regards.

[Hongjun Ma]

I'm not aware of similar problems on VC3.51 upgrade.

what's the environment?

1) stacking/no stacking?

2) Flex-10 or Flex-fabric? how many in one enclosure?

3) OA version and server BIOS/NIC firmware version and ESX driver version if you know?

4) what's the vswitch teaming method?

5) other details you'd like to share

did you get a chance to open a HP support case to track this down?

[Bjorn44]

I had the same problem on my Flex-10 modules. Also, I could see some errors "unintegrated" and "not in sync" running vcsu healthcheck.

Reset of the modules solved it for me.

[ricdanger21]

Hi there,

About the details of my environment:

1) stacking/no stacking? -> "horizontal" stacking on the two VCs I have on my enclosure

2) Flex-10 or Flex-fabric? how many in one enclosure? -> Flexfabric, 2

3) OA version and server BIOS/NIC firmware version and ESX driver version if you know? -> Latest; 3.32 for OA; latest drivers on ESXi

4) what's the vswitch teaming method? -> Virtual Port ID;

5) other details you'd like to share -> There was no link on the uplinks after update. They were marked with an X on vCenter. Not using any FlexHBA. Used vcsu in automatic mode, and it didn't throw any error

Thanks.

[Tusc]

This is why we also put hosts in MM prior to any hp fw update. Luckily our clusters are laid out across several chassis so we have this luxury.

[Hongjun Ma]

I checked internally and there are not other customers reporting the same issue. In case this problem happens, please log a HP support case so we can investigate.