Enterprise Datacenter Management Voodoo
Posts tagged dx360 M2
updating iDataPlex IMM firmware
Jan 4th
Easiest way is to do it remotely. First, get the package from IBM, then copy the file to some directory. Then do the following:
chmod 755 ibm_fw_imm_yuoo*
./ibm_fw_imm_yuoo48d_linux_32-64.bin -x .
Now you have a bunch of files in this directory. This machine could be a laptop or whatever. Now you can remotely update the IMM as long as you are connected to it through the network.
Do this:
./iflash64 –package imm_yuoo48d.upd –host i01-imm –user xcat –password f00bar
(Here, my host is the IP address of the IMM) Then my userid and password are there. )
The output is as follows:
IBM Command Line IMM Flash Update Utility v1.5
Licensed Materials – Property of IBM
(C) Copyright IBM Corp. 2009 All Rights Reserved.
Connected to IMM at IP address 10.0.0.11.
Update package firmware type: IMM
Update package build level: YUOO48D
Target’s current build level: YUOO24H
Would you like to continue with the update? y/n: y
The IMM is preparing to receive the update.
Transferring image: 100%
Transfer complete.
Validating image.
Updating firmware: 100%
Update complete.
You’ll then need to wait a few seconds for it to become reactivated.
Note: Adding the -s flag will make it so that you are not prompted and works for doing lots of them.
iDataplex dx360 M2 environmentals
Aug 28th
For the IBM iDataplex air cooling is front to back, just like a normal 1U server. The inlet temperature ranges are 10C to 32C. The recommended range is 18C to 26C, and the ideal is 73.4F or 23C.
Thanks to Matt Archibald for helping me dig this up.
Also, the iDataplex Rack, on its casters is 82.4″ tall.
dx360 M2 BIOS updates and manipulations
Aug 27th
Updating the eUFI (BIOS) settings for the dx360 M2 is much easier to do now with the IMM that it comes with. You can even update it and make changes even if there is no operating system installed on the system. There are two files you’ll need:
- ASU tool: This is the tool you use to change eUFI settings.
- Linux BIOS update tool. This can be downloaded at IBM’s web site. There is a tool for updating the eUFI, the IMM, and other things like SAS firmware. The main ones you’ll probably need are teh eUFI and IMM updates.
All three of these tools update a machine through the network.
The first act of bravery you will need is to find the ASU tool and the latest eUFI update on IBM’s web site. I found the ASU update here. The ASU tool will allow you to remotely access nodes and make updates to their BIOS.
The best way to navigate IBM’s site for iDataplex is go to the home page, then at the bottom click on support, then choose System X, then dx360 M2 and never select an Operating system. From there you can see other updates you can do.
Once you find it, you can download the Linux x86_64 image and place it on a linux server that has network access to the IMM of the particular node you are trying to update. Then extract it with tar and you’ll see a file called ‘asu64′. This is the tool we will use.
Change eUFI/IMM Settings
Step 1.
Create a file of all the changes you want to the eUFI. Mine looks like this:
set uEFI.TurboModeEnable Enable set uEFI.ProcessorHyperThreading Disable set uEFI.RemoteConsoleRedirection Enable set uEFI.SerialPortSharing Enable set uEFI.SerialPortAccessMode Dedicated set uEFI.Com1TextEmul VT100 set uEFI.Com1ActiveAfterBoot Enable set uEFI.Com1FlowControl Hardware set uEFI.AdjacentCacheLinePrefetch Disable set uEFI.OperatingMode "Efficiency Mode"
Suppose you don’t know what settings are available to change? Then, you can get the current settings of a machine by running:
./asu64 show all --host 10.0.0.16 --user xcat --password f00bar
The IP address is the IP address of the IMM, the default userid is USERID. The default password is PASSW0RD (P-A-S-S-W-zero-R-D). The IP address is usually set by default in the factory. xCAT is able to set it up automatically too.
2. Update it.
Once you know what you want to update, take that batch file you created and then run:
./asu64 batch settings --host 10.0.0.16 --user xcat --password f00bar
That’s it!
Update eUFI or IMM
This is a similar process to the previous tool. Let’s update the IMM first. On my management server, I just run:
./ibm_fw_imm_yuoo24i_linux_32-64.bin -x .
This will extract all the files we need. Then run:
./iflash64 --package imm_yuoo24i.upd --user xcat --password f00bar --host 10.0.0.16 ... Connected to IMM at IP address 10.0.0.16. Update package firmware type: IMM Update package build level: YUOO24I Target's current build level: YUOO24H Would you like to continue with the update? y/n: y The IMM is preparing to receive the update. Transferring image: 100% Transfer complete. Validating image. Updating firmware: 100% Update complete. Performing activation of the firmware: ......... Waiting up to 240 seconds for the activation to complete: ............................................................ ............................................................ ............................................................ ............................................................ Waiting up to 240 seconds for the IMM to answer to build id requests: ............................................................ ............................ The new version of the targeted firmware is YUOO24I. Firmware flashed successfully
The draw back of this is that it takes forever to do the verifications! If you’re going to do this for a lot of machines, I recommend you fork out the different processes and tee the output to a separate file for each one so you can see the output.
This same proceedure is done for updating the eUFI:
./iflash64 --package ibm_fw_uefi_tme126a_anyos_i386.upd --user xcat --password f00bar --host 10.0.0.16
The output looks the same as when you updated the IMM. Note that this procedure is the same for all IBM Nehalem based products.