Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1010726.1
Update Date:2017-03-29
Keywords:

Solution Type  Technical Instruction Sure

Solution  1010726.1 :   Sun Fire[TM]: Replacing CPU / Memory or I/O boards requires that the firmware matches existing boards  


Related Items
  • Sun Fire 15K Server
  •  
  • Sun Fire E20K Server
  •  
  • Sun Fire E25K Server
  •  
  • Sun Fire 3800 Server
  •  
  • Sun Fire 6800 Server
  •  
  • Sun Fire 4810 Server
  •  
  • Sun Fire 12K Server
  •  
  • Sun Fire 4800 Server
  •  
  • Sun Fire E4900 Server
  •  
  • Sun Fire E6900 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: Exx00
  •  
  • _Old GCS Categories>Sun Microsystems>Servers>High-End Servers
  •  
  • _Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
  •  

PreviouslyPublishedAs
214805


Description
Replacing CPU / Memory or I/O boards requires that the firmware matches existing boards

When replacing a CPU memory board (also known as a uniboard) in a LW8 system (Sun Fire [TM] 2900, Sun Fire [TM] V1280, Netra [TM] 1290) or a CPU memory board and I/O Board in a midrange system (Sun Fire[TM] 3800 - Sun Fire[TM] 6800, Sun Fire[TM] E3900 - Sun Fire[TM] E6900), it is necessary to ensure the firmware (FW) on the new board matches that on the other boards in the system.

It is also necessary to match the FW on a uniboard being replaced in a high end server Sun Fire[TM] 12K, Sun Fire[TM] 15K, Sun Fire[TM] E20K, and Sun Fire[TM] E25K).



Steps to Follow
Failure to make the FW match will prevent the board from being added to the domain.

The correct procedure for replacing a uniboard or I/O Board is documented in the corresponding service manual (including information on how to use dynamic reconfiguration to avoid a system outage to do so) but a step is missing after the new board has been installed and before the domain can been initialized or the dynamic reconfiguration can been performed to put the board in use. The technician must check the FW on the board and make it match that of the other boards in the system.

The next three sections outline that step for the LW8, the midrange and high end servers.

LW8 SERVERS

The following commands must be executed on the SC:

SC> poweron <HPU>

SC> showboards -p proms

At this point you can tell if the FW is correct or not - if it is the rest of this procedure can be skipped.

SC> flashupdate -c <source board> <destination board>

SC> poweroff <HPU>

SC> poweron <HPU>

It is necessary to power cycle the board for the new FW to take effect.

MIDRANGE SERVERS

The following commands must be executed on the SC:

SC> poweron <board name>

SC> showboards -p proms

At this point you can tell if the FW is correct or not - if it is the rest of this procedure can be skipped.

SC> flashupdate -c <source board> <destination board>

SC> poweroff <board name>

SC> poweron <board name>

It is necessary to power cycle the board for the new FW to take effect.

SC> showboards -p proms

This last command is to verify that the new FW is in effect.

In the event that this system has only one uniboard or I/O Board, it will be necessary to check and update the FW on that board from the correct patch. In this case, the system will be down, so it may also be a good opportunity for the customer to update their FW.

Instructions on how to update the FW is included with the patches.

You are now ready to proceed with the domain initialization or dynamic reconfiguration operation.

HIGH END SERVERS

I/O boards are not affected by FW in these servers. When replacing a uniboard, the following commands need to be executed on the SC:

# poweron <board name>

# flashupdate -f /opt/SUNWSMS/hostobjs/sgcpu.flash <board name>

This command will report the FW on the uniboard and the FW version in the file, then you have to confirm if you want to install the FW on the board. If it already matches, then you can exit and skip the rest of this procedure.

# poweroff <board name>

# poweron <board name>

You are now ready to proceed with the domain initialization or dynamic reconfiguration operation.



Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback