UPDATE 29/04/2014
HP has released an updated HP Service Pack for Proliant which fixes the issue.
HP has released a very serious customer advisory saying that some Broadcom Nics which are used in G2-G6 servers and blades could be killed by a firmware update component in their HP Service Pack for Proliant 2014.02.
Using HPSUM, HP SPP or Smart Components for VMware to update the “Comprehensive Configuration Management” (CCM) firmware version to 7.8.21 can kill the nics which would require a hardware swap out to fix!
I would suggest immediately removing the update from HPSUM or the SPP.
If you absolutely need to update the firmware, you can run the component manually and chose not to update CCM.
Affected Nics:
Any HP ProLiant server with any of the following Broadcom Nics:
- HP NC373T PCIe Multifunction Gig Server Adapter
- HP NC373F PCIe Multifunction Gig Server Adapter
- HP NC373i Multifunction Gigabit Server Adapter
- HP NC374m PCIe Multifunction Adapter
- HP NC373m Multifunction Gigabit Server Adapter
- HP NC324i PCIe Dual Port Gigabit Server Adapter
- HP NC326i PCIe Dual Port Gigabit Server Adapter
- HP NC326m PCI Express Dual Port Gigabit Server Adapter
- HP NC325m PCIe Quad Port Gigabit Server Adapter
- HP NC320i PCIe Gigabit Server Adapter
- HP NC320m PCI Express Gigabit Server Adapter
- HP NC382i DP Multifunction Gigabit Server Adapter
- HP NC382T PCIe DP Multifunction Gigabit Server Adapter
- HP NC382m DP 1GbE Multifunction BL-c Adapter
- HP NC105i PCIe Gigabit Server Adapter
HP SPP Components
Linux:
- CP018941.scexe and CP018942.scexe - v2.9.21
- CP021160.scexe and CP021161.scexe - v2.9.24
- CP021536.scexe and CP021537.scexe - v2.9.26
- CP021068.scexe and CP021069.scexe - v2.10.15
- CP023112.scexe and CP023113.scexe - v2.10.16
Windows:
- cp018467.exe and cp018468.exe - v4.0.0.22
- cp021534.exe and cp021535.exe - v4.0.0.22 (B)
- cp021547.exe and cp021547.exe - v 4.0.0.26
VMware:
- CP019762.scexe - v1.0.21
- CP021532.scexe - v1.0.21.3
- CP021849.scexe - v1.1.10
Wow, that’s a big one, I thought the days of terrible Broadcom firmware updates were beyond us, I guess not!