Archive

Posts Tagged ‘HP’

Upgrading iLO 2 Firmware through SSH

May 12, 2014 4 comments

Recently I had a problem upgrading the iLO firmware on one of our servers through the GUI.  This particular server did not have an OS on it at the time so normally I would update through the web interface.  However since the firmware on this machine would not work with IE 11 I had no choice but to upgrade through SSH.

Before you start copy your firmware file (ilo2_225.bin in my case) to a local web server and make note of the URL.

  • Login to the iLO with your favorite SSH client.
  • Once connected type “cd map1/firmware1”
  • Now type the following command replacing the URL with your own URL.

         “load –source http://192.168.1.1/ilo2_225.bin

  • The update will now begin.  It can take up to 10 minutes for the process to complete.  You will be disconnected from your session during the upgrade. 
  • Login to iLO again and type “version” to verify the update has been completed.
Categories: HP Tags: , ,

HP iLO Reset

May 9, 2014 2 comments

Resetting an HP iLO2 using SSH or Telnet isn’t the most obvious thing to do. Recently I had one where the web interface wasn’t responding and I didn’t want to power down the server to reset iLO.

  1. Connect to the iLO IP address using your favorite SSH client. I prefer Putty.
  2. Login with your Administrator account. Don’t forget bother username and password are case sensitive.
  3. Once logged in you need to go to the map1 directory. type cd map1
  4. The type reset. The iLO card will restart immediately after that.

Easy as pie!

Categories: HP Tags: , ,

Using HP Proliant Broadcom NICs in WinPE

June 7, 2012 7 comments

We recently got in a new HP Proliant BL460c Gen8 blade with the HP 530FLB NIC. It’s a great piece of hardware but using the NIC in WinPE is not much fun.  We recently started using MDT to deploy Windows servers now but no matter what I did I could not get the NIC driver to load in WinPE.

Even though the drivers were imported into MDT and I had rebuilt my boot images it would not load.  Finally I ran HP’s driver installation utility from inside WinPE and it came up.  That’s when I discovered that the NIC needs the HP Virtual Bus Device driver loaded before it can load the NIC driver.  Looking at the PnP IDs that the driver supports I noticed they all start with b06bdrv\l2nd instead of the usual pci_<VenID>.  This is because the NIC virtual sits on top of another device. 

So why not just load the HP Virtual Bus Device in MDT?  That’s what I did but the HP Virtual Bus Device is a system-class driver and by default MDT does not copy system-class drivers into the boot images.  image

Sure you can configure it to add them but then your boot images will get much larger.  My solution was to instead put a copy of the HP Virtual Bus Device (evbd.inf) driver into my MDT boot image using the “Extra directory to add” feature in MDT.  I also imported the NIC drivers into MDT as I normally do. 

image

Once the boot image loads press F8 to open a new command window. Navigate to the folder you added to the MDT boot image (it should be right off the root) and enter drvload evbd.inf. After a few seconds the driver will load and the NIC should now be active. It’s not an ideal solution but since we don’t deploy a lot of these servers it works for me.  This same process would also apply to some of the other Broadcom NICs used in HP blades and servers like the NC373i and NC382i. 

Categories: Deployment, HP, MDT, Windows Tags: , , ,
%d bloggers like this: