BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

VC Enet Module OA Communication Status Failed after Firmware Upgrade

Steven Clementi
Honored Contributor

VC Enet Module OA Communication Status Failed after Firmware Upgrade

Has anyone run into an issue where you have lets say...

 

A c7000 Blade Enclosure with 4 VC Modules properly stacked... before the upgrade, everything looks "good", but after the firmware update (or during) they modules in bays 5/6 lose their connection to the OA some how.

 

Current Dilemma:

 

c7000 w/:

1: 1/10Gb VC Enet Module   -   2: 1/10Gb VC Enet Module

3: Cisco MDS 9124e   -  4: Cisco MDS 9124e

5: 1/10Gb-F VC Enet Module   -   6: 1/10Gb-F VC Enet Module

7: Empty   -   8: Empty

 

Was running v3.30 firmware and everything was a-ok.

Upgraded to v3.60 and now my CX4 cables on X1 between 1/5 and 2/6 are not being recognized, and VCM is reporting no communications with the OA.

 

When I look at the modules in the Onboard Administrator, their IP addresses are blank.

 

I've reseated the modules, restarted the OA's.

 

I have another identical enclosure that is running 3.30 and is working perfectly.

 

 

Any thoughts?

Steven Clementi
HP Master ASE, Storage and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5)
RHCE
NPP3 (Nutanix Platform Professional)