lsflash(1m)
lsflash - Download firmware to LS boards
Showing IRIX 6.5.30 (default release). Added in IRIX 6.5.30.
NAME lsflash - Download firmware to LS boards SYNOPSIS /usr/sbin/lsflash fwfile ctlr DESCRIPTION lsflash downloads firmware to LSI boards. On boards which have multiple functions, only one function needs to be downloaded. After a successful download, all functions on the board will be restarted to begin executing the new firmware and the functions will be reprobed. fwfile is the full pathname/filename to the firmware file. ctlr is the number of the controller to download. /hw/scsi_ctlr and bus will be added. If a full pathname from / is used for the argument, it will be used unmodified as the controller filename. The default firmware files will be found in the /usr/firmware/ls directory. Naming will follow the convention of ls<chip number>.fw. LIMITATIONS If a bad image is downloaded, the restart will fail. At that point, the only option is download a good image. Any other operation will return an error. Although this program and the device driver make some attempt to verify the firmware file is correct, the checks are limited. Use care in selecting the image to download. Its recommended that all filesystems on the board's targets be unmounted and the functions idle before issuing this command. This is to prevent problems during the download and if the download fails. Be sure to unmount the devices on all board functions. FILES /usr/sbin/lsflash /usr/firmware/ls/ls1030.fw /usr/firmware/ls/ls949.fw SEE ALSO ioconfig(1M), scsicontrol(1M), scsiha(1M), sesmgr(1M) NOTES You must have CAP_DEVICE_MGMT in addition to privileges on the controller device file in order to use this command. IO will be held during an operational download. After the download completes, IO will resume on a successful restart. Although a download failure can corrupt the board firmware, it will not corrupt any data on devices attached to the controller. Tapes may be repositioned by this operation. In the event a board has corrupt firmware at boot, the controllers will be shown in inventory and their device files will exist. However no targets will be shown and any attempts to do anything but download firmware will return an error. Once successfully downloaded, the board functions will be started and probed. Afterwards, ioconfig will need to be executed manually, as will sesmgr poll for fibre channel controllers. When a board has corrupt firmware, a download process must be used which will not store the firmware image in NVRAM. When this is the case, lsflash will download the firmware twice; once to get the board running and a second time to store the image to NVRAM. In the event that restart fails after the download, target device files and inventory entries will still be present but devices will be inaccessible until a successful download takes place. The Fibre Channel 939 and 949 boards use the same firmware. Boards which use the 1064 and 1068 chips require firmware versions specific to the various types of hbas. Use of the wrong firmware file will render the controller unusable. These files will be made available on Supportfolio.