IBM JS20 - BladeCenter - 8842 Maintenance And Troubleshooting Manual

Also see for BladeCenter JS20: Configuration and options guide Installation and user guide Installation and user guide

Contents

that you want to download be put into the /etc/microcode directory on the system. Ifthere is not enough space in the /var file system for the new flash update imagefile, an error is reported. If this error occurs, exit the service aid, increase the size ofthe /var file system, and retry the service aid. After the file is copied, a screenrequests confirmation before continuing with the flash update. When you continuethe update flash, the system reboots using the shutdown -u command. The systemdoes not return to the diagnostics, and the current flash image is not saved. Afterthe reboot, you can remove the /var/update_flash_image file.When this service aid is run from standalone diagnostics, the flash update imagefile is copied to the file system from diskette, optical media, or from the NIM server.Using a diskette, the user must provide the image on backup format diskettebecause the user does not have access to remote file systems or any other filesthat are on the system. If using the NIM server, the microcode image must first becopied onto the NIM server in the /usr/lib/microcode directory pointed to the NIMSPOT (from which you plan to have the NIM client boot standalone diagnostics)prior to performing the NIM boot of diagnostics. Next, a NIM check operation mustbe run on the SPOT containing the microcode image on the NIM server. Afterperforming the NIM boot of diagnostics, one can use this service aid to update themicrocode from the NIM server by choosing the /usr/lib/microcode directory whenprompted for the source of the microcode that you want to update. If not enoughspace is available, an error is reported stating that additional system memory isneeded. After the file is copied, a prompt requests confirmation before continuingwith the flash update. When you continue with the update, the system reboots usingthe reboot -u command. You might receive a ″Caution: Some process(es) wouldn’tdie″ message during the reboot process; you can ignore this message. The currentflash image is not saved.You can use the update_flash command in place of this service aid. The commandis located in the /usr/lpp/diagnostics/bin directory. The command syntax is asfollows:update_flash [-q | -v] -f file_nameupdate_flash [-q | -v] -D device_name -f file_nameupdate_flash [-q | -v] -Dupdate_flash [-l]update_flash -cupdate_flash -rImportant: The update_flash command reboots the entire system. Do not use thiscommand if more than one user is logged in to the system.Flag descriptions are as follows:Flag Description-D Specifies that the flash update image file is on diskette. The device_namevariable specifies the device. The default device_name is /dev/fd0.-f Flash update image file source. The file_name variable specifies the fullyqualified path of the flash update image file.-l Lists the files on a diskette, from which the user can choose a flash updateimage file.-q Forces the update_flash command to update the flash EPROM and reboot thesystem without asking for confirmation.-v Validates the flash update image. No update will occur.66 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide