IBM JS20 Hardware Maintenance Manual - Page 76

that you want to download be put into the /etc/microcode directory on the system. If there is not enough space in the /var file system for the new flash update image file, an error is reported. If this error occurs, exit the service aid, increase the size of the /var file system, and retry the service aid. After the file is copied, a screen requests confirmation before continuing with the flash update. When you continue the update flash, the system reboots using the shutdown -u command. The system does not return to the diagnostics, and the current flash image is not saved. After the reboot, you can remove the /var/update_flash_image file. When this service aid is run from standalone diagnostics, the flash update image file 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 diskette because the user does not have access to remote file systems or any other files that are on the system. If using the NIM server, the microcode image must first be copied onto the NIM server in the /usr/lib/microcode directory pointed to the NIM SPOT (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 must be run on the SPOT containing the microcode image on the NIM server. After performing the NIM boot of diagnostics, one can use this service aid to update the microcode from the NIM server by choosing the /usr/lib/microcode directory when prompted for the source of the microcode that you want to update. If not enough space is available, an error is reported stating that additional system memory is needed. After the file is copied, a prompt requests confirmation before continuing with the flash update. When you continue with the update, the system reboots using the reboot -u command. You might receive a ″Caution: Some process(es) wouldn't die″ message during the reboot process; you can ignore this message. The current flash image is not saved. You can use the update_flash command in place of this service aid. The command is located in the /usr/lpp/diagnostics/bin directory. The command syntax is as follows: update_flash [-q | -v] -f file_name update_flash [-q | -v] -D device_name -f file_name update_flash [-q | -v] -D update_flash [-l] update_flash -c update_flash -r Important: The update_flash command reboots the entire system. Do not use this command if more than one user is logged in to the system. Flag descriptions are as follows: Flag -D -f -l -q -v Description Specifies that the flash update image file is on diskette. The device_name variable specifies the device. The default device_name is /dev/fd0. Flash update image file source. The file_name variable specifies the fully qualified path of the flash update image file. Lists the files on a diskette, from which the user can choose a flash update image file. Forces the update_flash command to update the flash EPROM and reboot the system without asking for confirmation. Validates the flash update image. No update will occur. 66 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide