![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1003856.1 : Sun Fire[TM] v1280/E2900 and Netra[TM] 1280/1290 server: How to flash firmware with lom -G [Video]
PreviouslyPublishedAs 205412 Applies to:Sun Netra 1280 Server - Version All Versions and laterSun Netra 1290 Server - Version All Versions and later Sun Fire V1280 Server - Version All Versions and later Sun Fire E2900 Server - Version All Versions and later All Platforms GoalDescription In order to flash or update the firmware on the Sun Fire[TM] V1280/E2900 or Netra[TM] 1280/1290 servers without using a network connection to the system controller you must use the lom -G command. This procedure is good to utilize if the system controller does not have a connection to the network or if you cannot put an http server or an ftp server on the network the system controller is on. Available for this topic, a Video Tutorial; Brief how-to video tutorials that provide step-by-step instructions answering Sun's most frequently asked questions. View the video answer and/or follow the detailed instructions below.
Sunsolve users must download the attachment to view the video. SolutionSteps to Follow Check that the lom packages are installed: # pkginfo | grep lom system SUNWlomm LOMlite manual pages system SUNWlomr LOMlite driver (root) system SUNWlomu LOMlite Utilities (usr) SUNWlomr and SUNWlomu must be installed. If the packages are not available see: SunFire[TM] V1280, E2900 and Netra[TM] 1280, 1290: Lights Out Management (LOM) packages are missing (Doc ID 1004868.1)
If they are installed, load the files needed to do the flash onto the system. The files are: sgrtos.flash
It is best to have two sessions open:
0. Before starting the flash, reset the system controller from the console. lom> resetsc -y This frees resources on the controller, and places it in a known state, ready to be flashed. Failure to reset the controller before beginning the flash can cause the controller to panic, sending an init 5 to the Solaris O/S, possibly resulting in a unplanned outage. 1. Upgrade the firmware on the system controller (SC): 1.a From the directory with the loaded flash files, run the command. # lom -G sgrtos.flash This program will replace LOM firmware with version 5.11.3 <= CR 6266849 Are you sure you want to continue? Enter 'C' and return to Continue or anything else to Terminate C On the system controller you will see the following output which tells you that you will need to reboot the SC, but DO NOT reset the SC until both rtos and scapp have been updated: lom>Transferring 676 kB image to the system controller. This may take several minutes. Validating image... 676 kB RTOS image transferred. Programming sun.serengeti.RTOSFlash@ffb3105a Comparing image and flash Image and flash are different, proceeding with update. Erasing ............... Done Programming ............... Done Verifying ............... Done Thu Jun 16 17:37:36 hostname lom: sun.serengeti.RTOSFlash@ffb3105a updated with version 5.11.3 05/27/2005. Firmware update complete. The system controller must be rebooted to load the new firmware. At the lom> prompt enter: resetsc -y '''<-- this is misleading, DO NOT RESET at this point''' Note: DO NOT reset the system controller at this point. Resetting the SC at this point would cause a mismatch between the SCapp and RTOS software on the SSC. 1.b Now, flash the SC. From the directory with the flash files, run the command: # lom -G sgsc.flash This program will replace LOM firmware with version 5.18.5 Are you sure you want to continue? Enter 'C' and return to Continue or anything else to Terminate C On the system controller, you will see: lom>Transferring 6209 kB image to the system controller. This may take several minutes. Note: This can take up to 30 minutes, so don't assume it's hung. Validating image... 6209 kB SC image transferred. Programming sun.serengeti.ScAppFlash@ffb64e60 Comparing image and flash Image and flash are different, proceeding with update. Erasing ............... Done Programming ............... Done Verifying ............... Done Thu Jun 16 17:37:36 hostname lom: sun.serengeti.ScAppFlash@ffb64e60 updated with version 5.18.3 05/27/2005. Firmware update complete. The system controller must be rebooted to load the new firmware. At the lom> prompt enter: resetsc -y Note: At this point the system controller has to be reset. IMPORTANT: The system controller will be automatically rebooted if upgrading to fw version 5.18.5 or greater . 2. Escape to lom> and reset the SC: lom> resetsc -y If you are on the system controller serial port, you will see the reset take place. If you used telnet to connect to the system controller, you will need to re-login to the system controller after it has finished. Once you have logged back onto the system controller, and are back to the lom> prompt, it is time to flash the boards in the system. 3. Upgrade the firmware on the system boards: 3.1 From the directory that you loaded the files into, run the command. # lom -G lw8cpu.flash This program will replace LOM firmware with version 5.18.3 Are you sure you want to continue? Enter 'C' and return to Continue or anything else to Terminate C On the system controller you will see: lom>Transferring 925 kB image to the system controller. This may take several minutes. Validating image... 925 kB CPU image transferred. Programming /N0/SB0/FP0 Comparing image and flash Image and flash are different, proceeding with update. Erasing ............... Done Programming ............... Done Verifying ............... Done Fri Jun 17 08:58:23 hostname lom: /N0/SB0/FP0 updated with version 5.18.3 05/27/2005. Programming /N0/SB0/FP1 Comparing image and flash Image and flash are different, proceeding with update. Erasing ............... Done Programming ............... Done Verifying ............... Done Fri Jun 17 08:59:02 hostname lom: /N0/SB0/FP1 updated with version 5.18.3 05/27/2005. It will do this for each board in the system /N0/SB0, /N0/SB2 and /N0/SB4 Firmware update complete. You must reboot Solaris to load the new firmware. NOTE: You will be told to reboot Solaris after the lw8cpu.flash completes. DO NOT REBOOT or power cycle the system until you have applied lw8pci.flash. 3.2 From the directory that you loaded the files into, run the command. # lom -G lw8pci.flash This program will replace LOM firmware with version 5.18.3 Are you sure you want to continue? Enter 'C' and return to Continue or anything else to Terminate C On the system controller you will see: lom>Transferring 347 kB image to the system controller. This may take several minutes. Validating image... 347 kB IO image transferred. Programming /N0/IB6/FP0 Comparing image and flash Image and flash are different, proceeding with update. Erasing ...... Done Programming ...... Done Verifying ...... Done Fri Jun 17 09:11:39 hostname lom: /N0/IB6/FP0 updated with version 5.18.3 05/27/2005. Firmware update complete. You must reboot Solaris to load the new firmware. 4. Now the system should be shut down. Bring the system to the ok prompt with init 0 or the shutdown command. 5. Turn of the system controller Once the system is down the system should be turned off from the system controller. lom> poweroff Powering boards off ... This will take a bit. Once it has finished you need to power back on the boards and boot the system. 6. Power on the system lom> poweron This will run the system in post test all the boards with the new firmware. You are done. Additional Information If the procedure in this article is not performed correctly, the system won't operate. 1005021.1 provides information on how to recover the system. References<NOTE:1005021.1> - Sun Fire[TM] V1280/E2900/Netra[TM] 1280/1290 Server: Incorrect Firmware Upgrade Procedure Can Lead to Incompatible Firmware on System Boards<NOTE:778.1> - Troubleshooting Video Issues in MOS <NOTE:1004868.1> - SunFire[TM] V1280, E2900 and Netra[TM] 1280, 1290: Lights Out Management (LOM) packages are missing Attachments This solution has no attachment |
||||||||||||
|