Slashdot is powered by your submissions, so send in your scoop


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Bug HP Networking

HP Server Killer Firmware Update On the Loose 100

Posted by timothy
from the just-this-one-little-problem dept.
OffTheLip (636691) writes "According to a Customer Advisory released by HP and reported on by the Channel Register website, a recently released firmware update for the ubiquitous HP Proliant server line could disable the network capability of affected systems. Broadcom NICs in G2-G7 servers are identified as potentially vulnerable. The release date for the firmware was April 18 so expect the number of systems affected to go up. HP has not released the number of systems vulnerable to the update."
This discussion has been archived. No new comments can be posted.

HP Server Killer Firmware Update On the Loose

Comments Filter:
  • Hot firmware (Score:5, Interesting)

    by DigiShaman (671371) on Friday April 25, 2014 @07:59AM (#46840053) Homepage

    And this is why I wait at least 2 months before installing firmware updates (unless it's a major security issue). It's not uncommon for a firmware update to be pulled shortly after being published. The 2 month window delay is generally more then enough time to ensure it's a proper update is solid.

  • i got hit by this (Score:4, Interesting)

    by alen (225700) on Friday April 25, 2014 @08:21AM (#46840205)

    didn't brick my server but it screwed up the device list in Windows and caused a cluster not to see the one node where i upgraded the drivers/firmware. put a null device driver into the device manager and i had to delete it and all was OK. just $250 to MS to figure this out since didn't think it was a HP issue

    on the server the network worked and all but the NIC's weren't "seen" by Windows and so the clustering was screwed up

"A child is a person who can't understand why someone would give away a perfectly good kitten." -- Doug Larson