Professional Documents
Culture Documents
Code which is programmed into hardware components (to control their operation) is called Firmware or Microcode. Microcode generally initializes the hardware - enabling it to boot up and operate. In many cases it may also provide some of the interface between the hardware and device-drivers or the operating system. Microcode is usually found programmed into modules on cards, adapters, or devices. If these modules are Flash memory, you can update the code rather than having to change the card or device. System Microcode initializes the system hardware and controls the boot process enabling the system to boot up and operate correctly; it also provides the interface between the operating system software and the hardware. Adapter Microcode is the operating code of the adapter; it initializes the adapter when power is applied and it controls many of the ongoing operations executed by the adapter. Device Microcode provides these same functions for devices such as tape drives.
Key Topics for IBM eServer pSeries, and IBM System p5.
These systems (and many other IBM systems) include a Service Processor, which contains System Firmware and other key System code. High-end systems also include "Bulk Power Controllers" (BPC) which each have a separate Service Processor. In addition, a System Power Control Network provides the interface to the BPCs or other power controllers.
The Flexible Service Processor (FSP) firmware provides diagnostics, initialization, configuration, run-time error detection, and correction. The Power Hypervisor firmware (which is based on the pSeries hypervisor) provides VLAN, virtual I/O, and subprocessor partitioning support. The Platform Firmware (PFW) supports the "Power Architecture Platform Requirements+" interface The Bulk Power Control (BPC) firmware controls each bulk power unit in CEC and towers. This firmware is model dependent. The System Power Control Network (SPCN) firmware interfaces with bulk power for power monitoring and control.
In addition, many systems are likely to have a Hardware Management Console (indeed, it is a requirement for all systems which have Bulk Power Controllers). An HMC is required for Logical Partitioning (LPAR), Service Focal Point etc.
The Hardware Management Console (HMC) firmware provides platform configuration, management, and services.
1 Overview
The goal of this paper is to provide easy-to-read instructions to quickly update system firmware on p5 servers. It is assumed the reader has basic p5 skills. There are extensive references that should help with items not covered in this paper. Three firmware update methods will be covered: 1. Update on an HMC managed system 2. Update on a standalone server via OS, without a HMC 3. Update on a standalone server using the Diagnostic CD, without a HMC
Please first read through the prerequisites before getting started on any of these upgrade sections. Then refer to any one section or all sections when choosing the preferred method for updating system firmware.
3. The s service pack level (YY currentl installed on the syste is lower than the las k YY) ly o em st disrupti service p ive pack level (ZZZ) of the new service pack to be installed.. ( e b Exampl Currently installed service pack is SF235_ le: y s k _180_180 an the new service pac is nd ck SF235_ _190_185 An insta allation is c concurrent if: 1. The s service pack level (YY is highe than the service pack level curre k YY) er k ently installe on ed your sy ystem. Exampl Currently installed service pack is SF235_ le: y s k _180_160, new service pack is n SF235_ _185_160.
1.3.4 W are th Why here mult tiple firmw ware strea ams?
Multipl firmware streams (eg SF230, SF le g, F235, SF24 etc) are available fo a given ty 40, a or ypemodel ( 9117-57 (eg, 70). IBM maintains m m multiple para allel firmwa streams s customer can are so rs install f firmware fix while av xes voiding a sc cheduled p5 server outa 5 age. As des scribed on the Managi and inst ing talling syste firmware FAQ web page , IBM releases p em e M parallel firm mware streams (release lev s vels) which are very an h nalogous to the AIX V5.2 and V5..3 release levels. Like AIX V and V5 the firm V5.2 5.3, mware streams perform similar fun m nctions on th same he machine type-mod dels, but SF2 (for exa 240 ample) may have some functions w y which SF23 (for 35 example) does not. There is usually little or no reaso to upgrad from one release to another . u e on de e (eg, SF2 to SF24 but if th upgrade is performe it require an outage of the enti p5 235 40), he ed, es e ire server ( (every LPAR at once). In contrast for system managed by an HMC updating from R t, ms d C, g one serv pack le to anoth (within the same st vice evel her tream releas level) is o se often not disrupti ive.
In this e example the system is currently bo e c ooted from the tempora side of t firmwar image ary the re as deno in the control pane by the lett T. This indicates the firmware is running from the oted el ter i e f tempora side. N indicates th system is booted in normal mod V=F indi ary he n de. dicates the boot speed is set to Fast HMC=1 in s t. ndicates tha the server is managed by and co at r onnected to one HMC. If it has been recen manage by an HM and no HMC is con s ntly ed MC H nnected then it will disp n play HMC=0 If no HM is availab and it is desired to set the serv to unman 0. MC ble s ver naged it mig be ght required to reset th service pr d he rocessor to factory defa using ASMI. ault A
firmware fixes are installed on the temporary side. Copying the temporary firmware level to the permanent side is known as committing or accepting the fix. Conversely, rejecting, or removing the current firmware level consists of copying the permanent firmware image to the temporary side. Note: It is recommended to use a new firmware fix for a period of time before committing (or accepting) it. If firmware fixes are applied consecutively, the first fix will, by default, be copied from the temporary to the permanent side, or accepted. Using an HMC, it is possible to simply replace the temporary image by doing an Install and Activate of the new firmware and indicating that the firmware should not be accepted.
1.6 Be Advised
During a firmware update, the flashing of the NVRAM might take anywhere from ten minutes to one hour. In general, updating to a new release level will take longer. Ensure the system is not interrupted before the flash process is completed. Interrupting this process could result in a service call. For systems that are not managed by a HMC, the installation of system firmware is always disruptive. During the update_flash process, the console output will be displayed. Again, do not interrupt this process.
Restarting system. FLASH: preparing saved firmware image for flash FLASH: flash image is 35191632 bytes FLASH: performing flash and reboot FLASH: this will take several minutes. Do not power off!
2 Requirements
2.1 Software requirements
The table below is a summary of the minimum components required for each method covered in this paper: Method Minimum Requirements 1. A compatible version of HMC. 2. An Ethernet connection from the HMC to the p5 server (HMC1 port). 3. Desired firmware image on CD. The rpm and XML files are required. 1. A running AIX or supported Linux operating system on a single LPAR environment, ie, no attached HMC. 2. Firmware image on a CD or file system. The rpm file only. 3. update_flash executable. For AIX, it is part of the diagnostic aids tool in the /usr/lpp/diagnostics/bin directory. For Linux, it is part of the Service and Productivity Tools.
4. Ser console and connec rial ction agnostic CD D 1. Dia Update via Standal lone 2. Firm mware imag (.img) file on a CD. Remember the rpm file is ge r, fi Diagnostic CD not di irectly comp patible. 3. Ser console and connec rial ction There a two very helpful site that will assist in ga are y es athering the component necessary to ts y update f firmware. V Visiting the Microcode downloads site ( 1) is recommend before s ded perform ming any updates. http://w www14.softw ware.ibm.co om/webapp p/set2/firmw ware/gjsn
Figure 1
To dow wnload the rp and XM files, inp the serve machine type and mo pm ML put er model numbe and er select th latest firm he mware com mponents bas on the below requirements tab (option 1 in Fig sed b ble 3). If plann ning to using the Diagn g nostic CD m method, use option 4 to download t firmwar image the re ISO ima The rpm files are not directly compatible with the Diagnostics CD. For the age. y e D e smalles ISO image take the fo st e ollowing pa using op ath ption 4
Obtain ISO Imag -> Down ge nload P5 M Microcode -> Select one -> G t GO
Next, go to the Pow wer5 Code matrix site ( m (Figure 2) to ensure the existing c t e code levels support s the dow wnloaded fir rmware rele ease. For the purposes of this paper, this appli mostly to HMC e o ies o version level. If an HMC is no being use this is fo informatio only. n ot ed, or on https://w www14.soft ftware.ibm.c com/webapp p/set2/sas/f/ f/power5cm/ /home.html l
Figure 2
The HM is conne MC ected to a p5 system wi a standar TCP/IP Ethernet con 5 ith rd E nnection. Fi igure 1 shows a very simple connectio on.
Figure 4 The HM version can also be checked as hscroot fro the shell prompt as follows: MC e s om l
hscroot@c76v3hm mc01:~> lshmc -V "version= Version: 5 Release: 2.0 HMC Build level 20060210.1 MH00586: Requir red fixes for HMC V V5R2.0 (02 2-14-2006)","base_v version=V5 5.2.0"
3.3 Vie ewing syst tem firmw ware infor rmation using LIC wizard
From th navigatio area, sele License Internal Co Updates. In the con he on ect ode ntent area, click on Change Licensed I e Internal Cod to the cur de rrent release In the Target Object Selection window, e. t w click th target sys he stem, and click OK.
Figure 5 In the C Change Inter Code window, sel View sy rnal w lect ystem inform mation and click OK. From F the main Change In nternal Cod task pane select Vie system information and click OK. To de el, ew i n O he a d ls "None" on the t view th installed, activated, and accepted LIC level on the target, select " Specify LIC Repos y sitory panel and click O l OK.
Figure 6
3.4 Up pgrade sys stem firmw ware to a new relea using HMC ase H
Remem mber, upgrad ding to a new release is a disruptiv upgrade. w s ve
Start by opening th Server an Partition folder in th HMC. Th click on Server y he nd he hen, n Manage ement in tha folder. If the state of the machin is Power off, Ready,, or Standby then at f ne y, proceed Setting th state to Power off is recommend when pe d. he ded erforming a firmware upgrade although it is not req e, quired. Note only HMC managed systems can perform e: C n firmwar upgrades with target system set to Power off state. re s t t o
Figure 7 Next, op the Licensed Intern Code M pen nal Maintenance folder on th Hardwar Managem he re ment Console Then, clic on Licen e. ck nsed Interna Code Upd al dates in that folder. In t example, the t this update w be from our curren firmware level 01SF will m nt e F235_185 to 01SF240_ o _202, so the normal " Chang Licensed Internal Co for the current rele ge d ode ease" feature will not w e work. Select Upgrad Licensed Internal Co to a new release. de ode w
Figure 8 Select t desired t the target managed system and click OK. a m
Figure 9
Insert th CD with the rpm an XML file into the drive. On the Specify LI Reposito he nd es d e IC ory panel, s select DVD drive and click OK. c Next, a Select LIC level panel is shown. C l Click OK.
Figure 11 The nex prompt w be to acc the LIC license ag xt will cept C greement for machine c code. Read the t license and click O to accept. After acc epting the license agreement, conf OK firm the dis sruptive upgrade action. Cli OK to proceed. Wh the firm e ick p hen mware is flas shed, the FS will resta and SP art activate the new fir e rmware level.
Figure 12
A dialog box will a appear to sh howing the e elapsed tim and status of the firm me s mware upgra ade. NING - Duri a disruptive update, the flashin of NVRA might ta from ten ing , ng AM ake n WARN minutes to two hou Do not interrupt th process before the fla process is complete s urs. he ash e.
Figure 13 Once th firmware upgrade ha complete view the system firm he e as ed, mware infor rmation to see how s the upg grade has ch hanged what is availabl e. t
Figure 14 he ft n n sed ntenance fol lder. From th HMC lef navigation area, open the Licens Internal Code Main Click on Licensed Internal Co Updates Select the Change Licensed Inte n ode s. e ernal Code for the f current release feat ture. Highlig the targe managed system and click OK (Figure 15). ght et d
Figure 16 Insert th CD into the drive an on the Sp he nd pecify LIC Repository panel, selec DVD driv and R ct ve click OK K. The foll lowing pane is display providin summary informatio about the update. Note the el yed ng y on e ion Advanc Options button give the optio to view an change the installati type for this ced s es on nd t r update a action. The current install type sel lection is Co oncurrent in nstall and ac ctivate. Oth her installat tion types in nvolve eithe a deferred or an imm er d mediate syst restart t activate the new tem to firmwar level. Th re hose installa ation types a grayed out since thi is a concu are o is urrent updat only. te (See Ma anaged System and Power License Internal Code (LIC) Concurren panel be ed ) ncy elow.) Click N to conti Next inue with Concurrent in C a e greement nstall and activate. Please read the license ag and clic OK to ac ck ccept.
Figure 16 The Ad dvanced Opt tion button displays the Managed System and Power Lic e d censed Inter rnal Code (L LIC) Concu urrency pane el:
Figure 17 After ac ccepting the license agr e reement, co onfirm the concurrent update actio prompt. Click c u on C Finish a Close to proceed. and o
Figure 18 A progr window will appea to show t elapsed time and sta of the f ress w ar the atus firmware up pdate. When th firmware is flashed, the FSP w restart an activate the new firm he e , will nd t mware level.
Figure 19 Once th firmware upgrade ha complete view the system firm he e as ed, mware infor rmation to see how s the upg grade has ch hanged what is availabl e. t
Figure 2 20
The Rem move and a activate feat ture is a one step process to remov the curren active T-side e ve nt firmwar and roll b re back (or cop firmwar from the P-side. Esse py) re entially, und the last do firmwar update an restore th T-side w the P-side firmware version. re nd he with e
Figure 2 21
Figure 2 22. Back vi of p550 server with ports for (left to rig iew 0Q w r ght) serial, S SPCN, HMC USB and Ethernet. C, d Once th serial con he nnection to the system is established, press the <ENTER> key, to be R> e presente with the following ASMI login screen. ed A n
Welcom me Machine type-mo odel: 9133-55A Serial number: 10B7D4G Date: 2006-4-21 Time: 20:12:48
Service Processor: Primary User ID: admin Password: ***** User ID to change: admin Current password for user ID admin: ***** New password for user: ****** New password again: ****** Operation completed successfully. PRESS ENTER TO CONTINUE: Number of columns [80-255, Currently: 80]: Number of lines [24-255, Currently: 24]:
Type the User ID and password to log in to ASMI. If this is the first time logging into ASMI, it might be required to change the default password. The default password is admin
The current activated firmware level is also shown in the ASMI web interface after logging in. To see the firmware level, look in the upper-right corner. Basically, to access the ASMI web interface, connect an Ethernet cable directly to the HMC1 port. For details on accessing the ASMI web interface, see reference 6.
Figure 2 23 The cur rrent active firmware le can also seen from the output of the Disp evel o m play Microc code Level se election on the Diagno ostics CD. D Details of ho to get to the followi screen are ow ing a provide in 4.7 ed
Figure 2 24 The cur rrent active firmware le as seen from the SMS screen: evel n S :
Figure 2 25 Finally, if the serve has a run , er nning AIX o Linux ope or erating system with the Service an e nd Product tivity tool ls svpd installe the lsmc ed, code command can be used as sho own below. More details a provided in section 4.4.2 are d n
linux:~ #/tmp/f fwupdate # lsmcode Version of Syst tem Firmwa are is SF2 235_185 (t SF235_1 t) 185 (p) SF F235_185 (b) ( Version of PFW is 17112005111681C CF0681
Select 1 Power On 1. n/Off System m. On the n screen select 8. Po next n ower on. W for a few seconds to be logged out as the system Wait w o d powers on. Watch boot progre codes as the system comes up. ess s m
Power On/Off Sy ystem Current system power sta ate: Off Current firmwar boot side: Perma re anent Current system server firmware st tate: Not running
1. System boot speed Currently: Fast 2. Firmware boot side for the next boot Currently: Permanent 3. System operating mode Currently: Normal 4. AIX/Linux partition mode boot Currently: Continue to operating system 5. Boot to system server firmware Currently: Standby 6. System power off policy Currently: Stay on 7. i5/OS partition mode boot Currently: A 8. Power on 98. Return to previous menu 99. Log out S1>8
When the system completes the boot process, note the operator control panel. Note that there should be no indication of HMC=. This indicates that the service processor does not expect to be managed by an HMC (see below).
01 N V=F T
Flag Description -f <file_name> Flash update im mage file source. T The file_n name varia able speci ifies the fully qualified path of the flash updat image file. te f -c Commit temporar image to permane ry t ent side. -r Reject temporar image. ry
4.4.1 Upgrade firm mware ima using A age AIX Before installing ch heck the existing firmw ware level. From AIX, use the com F mmand lsmc code. ides in the diagnostic d d directory. An example of the outpu of the lsm A ut mcode This command resi nd lows: comman is as foll
DISPLA MICROCO AY ODE LEVEL 802 2811 IBM,9133-55A The current per rmanent sy ystem firm mware imag is SF23 ge 35_185 The current tem mporary sy ystem firm mware imag is SF23 ge 35_185 The sy ystem is c currently booted fr rom the te emporary firmware i f image. Enter to contin nue.
4.4.2 Upgrade firm mware ima using L age Linux To use lsmcode an update_fl nd lash comma ands in Linu the follo ux, owing minim mum Servic and ce tivity tools h have to be installed, an in this or i nd rder: Product librtas ppc64-u utils lsvpd Note: If the Service and Produ f uctivity tool are not in ls nstalled, they can be do y ownloaded from the f followin location. Choose the appropria Linux dis ng ate stribution an release. nd https://w www14.soft ftware.ibm.c com/webapp p/set2/sas/f/ f/lopdiags/ho ome.html
After downloading the Linux tools into the /tmp directory, install the three packages Platform Enablement Library (librtas), Service Aids (ppc64-utils), and Hardware Inventory (lsvpd) as follows
linux:~ # rpm Uvh librtas-1.1-17.ppc64.rpm linux:~ # rpm Uvh ppc64-utils-2.1-0.ppc64.rpm linux:~ # rpm Uvh lsvpd-0.12.7-1.ppc.rpm
The Hardware Inventory package contains the lsmcode command that allows us to view the current system firmware information. To populate the VPD database and enable this command, type
linux:~ linux:~ linux:~ Version Version # chkconfig lsvpd on # /sbin/update-lsvpd-db #/tmp/fwupdate # lsmcode of System Firmware is SF235_185 (t) SF235_185 (p) SF235_185 (b) of PFW is 17112005111681CF0681
The flash process will reboot the system as part of a disruptive install of the firmware. Do Not Power off or interrupt the flash process. When the new firmware is completely installed, log back into Linux and verify the current firmware configuration.
linux:~ # lsmcode Version of System Firmware is SF240_202 (t) SF235_185 (p) SF240_202 (b) Version of PFW is 13552006011081CF0681
This wi look like a normal AIX boot wi Welcome to AIX sc ill A ith crolling acro the cons oss sole. Once th Diagnost disk has booted, on the functio selection screen, sele Tasks an he tics s n on ect nd Service Aids. e
Figure 2 27 On the t task selectio screen, scroll to the bottom of the list of op on s t ptions, and select Upda and ate Manage Flash. e
Figure 2 28 Insert th CD conta he aining the downloaded firmware img file into the media device, sele d d i o ect Validate and Upda System Firmware an Update System Firm ate F nd S mware menu items. u
Figure 2 29 Press F4 to select a firmware fix image fi from a li of image files. Our C contains only 4 f ile ist CD s one ver rsion of the target firmw update file, and 01SF204_20 ware e 02_201.img is displayed d.
Figure 3 30 Press F7 (commit). The server firmware l 7 r level selecte will be in ed nstalled on t tempora side. the ary
2. Firmware boot side for the next boot Currently: Temporary 3. System operating mode Currently: Normal 4. AIX/Linux partition mode boot Currently: Continue to operating system 5. Boot to system server firmware Currently: Running 6. System power off policy Currently: Automatic 7. i5/OS partition mode boot Currently: A 8. Power on 98. Return to previous menu 99. Log out S1> 2
Select 1. Permanent
Firmware boot side for the next boot Currently: Temporary 1. 2. 98. 99. S1> Permanent Temporary Return to previous menu without saving changes Log out 1
Note that the firmware boot side is now set to Permanent which is our backup copy of the firmware flash. Select 8. Power on. Hit the <ENTER> key. Wait for a few seconds to be logged out as the system powers on.
Power On/Off System Current system power state: Off Current firmware boot side: Temporary Current system server firmware state: Not running 1. System boot speed Currently: Fast 2. Firmware boot side for the next boot Currently: Permanent 3. System operating mode Currently: Normal 4. AIX/Linux partition mode boot Currently: Continue to operating system 5. Boot to system server firmware Currently: Running 6. System power off policy Currently: Automatic 7. i5/OS partition mode boot Currently: A 8. Power on 98. Return to previous menu 99. Log out S1> 8 The system is powering on.
This option will reject the installed T-side firmware, SF240_202 (t), and copy SF235_185 (p) to the T-side copy of the firmware. The system will reboot.
linux:~ # update_flash -r success: Rejected temporary firmware image
Move the highlighted cursor to Reject the Temporary Image and hit <ENTER> key to proceed with rejecting the installed firmware on the T-side.
UPDATE AND MANAGE FLASH The reject operation was successful.
Update Policy in the ASMI. For the HMC LIC method, the policy should be set to HMC. For other methods, the policy should be set to Operating System. 3. Where do I get the DIAG CD and other required components See [14] in 7 References for download sites. 4. Why is the firmware in rpm and xml formatted files? Is rpm command in the AIX toolbox as a separate installation? Isnt rpm an alien format in AIX? The rpm in AIX toolbox has been available on AIX and has been shipped with AIX since v5.2. AIX geninstall command uses the rpm command for installing rpm filesets. 5. Received error: Failed dependencies: messages during installation of Linux Service and Productivity Tools Use the rpm option requires to look for the missing prerequisite rpm package. For instance, the dependency file, librtas rpm, is required by the ppc64-utils package
rpm -qp --requires ppc64-utils-2.1-0.ppc64.rpm /bin/bash /bin/sh /bin/sed /usr/bin/perl librtas >= 1.1-12 /bin/sh ld.so.1 libc.so.6 librtas.so.1 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1)