Table of Contents
Firmware upgrade on Power server with Linux
If no HMC is available, then you have to manually upgrade firmwares, it required then a downtime (hot upgrade with HMC only).
Server Firmware
Some packages need to be installed : powerpc-utils,…
http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/installtools/home.html http://www.ibm.com/support/knowledgecenter/linuxonibm/liaau/liaau-service-aids.htm?view=embed
To list the current firmware:
[root@xxx ~]# lsmcode Version of System Firmware is FW810.20 (SV810_079) (t) FW810.10 (SV810_076) (p) FW810.20 (SV810_079) (b) The first value (t) is the temporary level. The temporary level is sometimes referred to as the installed level. The second value (p) is the permanent level. The permanent level is sometimes referred to as the backup level. The third value (b) is the booted level. The booted level is sometimes referred to as the activated level.
Download from IBM Central Fix (https://www.ibm.com/support/fixcentral/) the latest firmware for the installed hardware
Install the downloaded rpm
[root@xxx ~]# rpm --ignoreos -Uhv 01SV860_070_056.rpm /tmp/fwupdate/01SV860_070_056.img
Use the following command to update the firmware:
[root@xxx ~]# /usr/sbin/update_flash -f /tmp/fwupdate/01SV860_070_056.img
The server will reboot (about 20-30 minutes downtime)
After reboot if the partition is configured as full system, and is unable to start, then reset the service processor
Error like:
Welcome to Emergency Mode Give root password for maintenance like reboot type control D to Continue
http://emmanuel.iffly.free.fr/doku.php?id=aix:hmc_problem#change_from_hmc_to_non-hmc
adapters and other devices firmware
Misc adapter or devices not supported for upgrade
Microcode Download Procedure for Systems Without AIX Installed:
Use this procedure if the system has no OS installed or the installed OS (e.g., Linux) does not support microcode download for this device.
1) Boot the system via a Standalone Diagnostic's CD a) To obtain a Standalone Diagnostic CD-ROM please go to the following webpage and follow the instructions http://www-304.ibm.com/webapp/set2/sas/f/diags/home.html b) After booting to Standalone Diagnostics, the Diagnostic's CD can be removed. 2) The Diagnostic's CD should be replaced by a CD containing the unpacked microcode image. The CD containing the microcode images should be prepared prior. Create a CD-ROM with the firmware 14104003.EP0220 mentioned in section 8.4 and burn the CD with Joliet CD file system. 3) From the Define a System Console menu either type or select vt320. 4) Select the "Task Selection" from diagnostics menu then select "Download Microcode". 5) Select resource 2-Port 10/100/1000 Base-TX PCI-Express Adapters (14104003) that microcode will be applied to and PRESS ENTER. 6) Press "F7" or "ESC+7" to commit.(The current microcode level of the resource you selected earlier will be displayed at the top of the screen). 7) Select Input Device (CD-ROM or DVD) then choose the Microcode level to download. NOTE: A prompt will ask you to insert the microcode CD-ROM into the CD/DVD drive. Insert the CD-ROM which accompanies these instructions. If this level is already installed in the drive you've selected a message will let you know. A message also may come up to let you know that the CD_ROM does not have the previous level microcode file. This is true and is not required to complete the download. PRESS "F7" or "ESC+7" to commit. 8) You will receive a msg. "Current Microcode is...." and "Download has completed successfully"(this may take a few minutes). 9) Return to the Tasks Selection menu and repeat this procedure for each adapter that requires this microcode. 10) Exit diagnostic and reboot system in normal mode.
SAS adapter
For systems that have LPAR installed, the microcode file must be placed on all partitions that have a SAS device in order to update the code. Follow this procedure for each partition:
Download from IBM Central Fix (https://www.ibm.com/support/fixcentral/) the latest firmware for the installed hardware
To list installed hardware and associated firmware:
[root@xxx ~]# lsmcode -A sys0!system: FW810.33 () (t) FW810.33 (SV810_133) (p) FW810.33 (SV810_133) (b)|service: 11282015050181CF0681 sg16 2:0:1:1 IBMchanger2 !3576-MTL.680G sg17 2:0:2:0 IBMtape10n IBMtape10 !ULT3580-TD6.G350 sg18 2:0:3:0 IBMtape11n IBMtape11 !ULT3580-TD6.G350 enP2p96s0f0 !.5719-v1.24i 0003:70:00.0 pci1014,034A !PCIe3 x8 SAS RAID Internal Adapter 6Gb (57D7).13511e00 sg1 0:0:0:0 !VSBPD12M1.30 ( 03) sg2 0:0:1:0 !VSBPD12M1.30 ( 03) sg3 0:0:2:0 sr0 !CDDVDW.IB03 sg0 0:3:0:0 !57D7001SISIOA.0150 enP7p128s0f3 !.5719-v1.24i
Another command:
lspci -mm -nn
Install the rpm package corresponding to the adapter firmware:
rpm -ihv --ignoreos --force pci.1014034A.51-15511300-1.Linux.noarch.rpm ls -l /lib/firmware/pci.1014034A.51.15511300
For Linux:
A) Log into the target partition. B) Type: "cd /lib/firmware"
Stop all applications and start iprconfig
[root@rh tmp]# iprconfig
IBM Power RAID Configuration Utility
Select one of the following:
1. Display hardware status
2. Work with disk arrays
3. Work with disk unit recovery
4. Work with SCSI bus configuration
5. Work with driver configuration
6. Work with disk configuration
7. Work with adapter configuration
8. Download microcode
9. Analyze log
Follow the menu 8 to update the firmware of SAS adapter. It take about 30 minutes, check in dmesg.
Type choice, press Enter.
1=device to download microcode
OPT Name Resource Path/Address Vendor Product ID Status
--- ------ -------------------------- -------- ------------------- -------------
1 FE IBM 57D7001SISIOA Operational
00-16 IBM VSBPD12M1 6GSAS Active
00-15 IBM VSBPD12M1 6GSAS Active
Choose Microcode Image Adapter to download: IBM 57D7001SISIOA Adapter Location: 0003:70:00.0.0/ The current microcode for this device is: 13511E00 Select the microcode image to download
Type choice, press Enter.
1=download microcode
OPT Version Date Image File
--- --------------- -------- --------------------------
1 15511300 10/27/16 /lib/firmware/pci.1014034A.51.15511300
Confirm Microcode Download ATTENTION: System performance may be affected during the microcode download process
[root@rh tmp]# dmesg [ 2226.340403] ipr: Updating microcode, please be patient. This may take up to 30 minutes. [ 2296.163536] ipr 0003:70:00.0: Initializing IOA. [ 2321.331510] ipr 0003:70:00.0: Starting IOA initialization sequence. [ 2321.336533] ipr 0003:70:00.0: Starting IOA initialization sequence. [ 2321.359864] ipr 0003:70:00.0: Adapter firmware version: 15511300 [ 2321.369445] ipr 0003:70:00.0: IOA initialized.
Finish by rebooting after 30 minutes…
FC adapter Emulex (Broadcom) adapter
Find the type of adapter:
[root@rh ~]# cd /sys/class/scsi_host [root@rh scsi_host]# find -L host* -maxdepth 1 -name "modeldesc" -printf %h: -exec cat {} \; host1:IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter host2:IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter host3:IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter host4:IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter [root@rh scsi_host]# cat host*/fwrev 2.02X7 (U3K2.02X7), sli-3 2.02X7 (U3K2.02X7), sli-3 2.02X7 (U3K2.02X7), sli-3 2.02X7 (U3K2.02X7), sli-3 [root@rh scsi_host]# cat host*/model* IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter 00E0806 IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter 00E0806 IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter 00E0806 IBM 00E0806 8G PCIe Dual Port Fibre Channel Adapter 00E0806
On Broadcom support Website, search for onecommand utilities for PowerPC Linux Group: Storage Adapters, Controllers, and ICs, Family: Fibre Channel Host Bus Adapters, OEM: , Product: LPe16002B FC Host Bus Adapter, Asset type: All, Keyword:
OneCommand Manager Core Application Kit (CLI) for Linux - RHEL for PowerPC
Unpack the tgz archive, by typing:
tar xzf elxcmcore-xxxx-xxxx-x.x.x.x-x.tgz
Change directory to elxocmcore-xxxx-xxxx-x.x.x.x-x and install the utility, by typing:
[root@rh tmp]# ./install.sh Beginning OneCommand Manager Core Kit Installation... Installing ./ppc64/rhel-7/elxocmcorelibs-11.1.217.0-1.ppc64.rpm Installing ./ppc64/rhel-7/elxocmlibhbaapi-32bit-11.1.217.0-1.ppc64.rpm Installing ./ppc64/rhel-7/elxocmlibhbaapi-11.1.217.0-1.ppc64.rpm Installing ./ppc64/rhel-7/elxocmcore-11.1.217.0-1.ppc64.rpm Stopping OneCommand Manager daemons ... Do you want to enable Secure Management feature for OneCommand? (s/u) The secure management feature requires OneCommand groups be configured on the LDAP network or the local host machine to provide for OneCommand operation. Enter 's' to select secure management. (LDAP/NIS OCM group configuration required) Enter 'u' to run without secure management (default). Enter the letter 's' or 'u': u Select desired mode of operation for OneCommand Manager 1 Strictly Local Management : Only manage the adapters on this host. Management of adapters on this host from other hosts is not allowed. 2 Local Management Plus : Only manage the adapters on this host. Management of adapters on this host from other hosts is allowed. 3 Full Management : Manage the adapters on this host and other hosts that allow it. Management of the adapters on this host from another host is allowed. 4 Management Host : Manage the adapters on this host and other hosts that allow it. Management of the adapters on this host from another host is not allowed. Enter the number 1, 2, 3, or 4: 1 You selected: 'Local Only Mode' Do you want to allow user to change management mode using set_operating_mode script located in /usr/sbin/ocmanager ? Enter the letter 'y' if yes, or 'n' if no: y OneCommand Manager Core Kit install completed successfully. Type: /usr/sbin/ocmanager/hbacmd to run the OneCommand Manager CLI utility.
[root@rh tmp]# rpm -Uhv df1000f114100104.203305.Linux.rpm Preparing... ################################# [100%] Updating / installing... 1:df1000f114100104-203305-1 ################################# [100%] [root@rh-tsm1 tmp]# rpm -ql df1000f114100104-203305-1 /lib/firmware/df1000f114100104.203305
Display the utility version to verify the hbacmd command is functional by typing: /usr/sbin/ocmanager/hbacmd version
Ensure that all I/O activity to storage devices controlled by the adapter is stopped prior to proceeding with firmware update as the adapter will be reset after firmware update.
List installed Emulex adapters by typing:
# /usr/sbin/hbacmd listhbas Port WWN : 10:00:00:00:c9:d1:8b:f1 Node WWN : 20:00:00:00:c9:d1:8b:f1 Fabric Name : 10:00:00:05:1e:db:d0:f0 Flags : 8000e200 Host Name : 8205-e6c-1-lp3 Mfg : Emulex Corporation Serial No. : 123456789 Port Number : 1 Mode : Initiator PCI Bus Number : 1 PCI Function : 1 Port Type : FC Model : 74Y2221
List hba attributes and versions of FW Version, SLI2 FW, SLI3 FW as well as Boot Code, all of which will be updated by microcode update.
# /usr/sbin/hbacmd hbaattributes 10:00:00:00:c9:d1:8b:f1 HBA Attributes for 10:00:00:00:c9:d1:8b:f1 Host Name : 8205-e6c-1-lp3 Manufacturer : Emulex Corporation Serial Number : 123456789 Model : 74Y2221 Model Desc : IBM 74Y2221 PCIe2 16Gb 2-Port Fibre Channel Adapter Node WWN : 20 00 00 00 c9 d1 8b f1 Node Symname : Emulex 74Y2221 FV1.1.34.3 DV8.3.7.7.1p HW Version : 0000000b FW Version : 10.2.252.1919 Vendor Spec ID : 10DF Number of Ports : 1 Driver Name : lpfc Device ID : E200 HBA Type : 74Y2221 Operational FW : 1.1.34.1 IEEE Address : 00 00 c9 d1 8b f1 Boot Code : Enabled Boot Version : KT8.02a7 Driver Version : 8.3.7.7.1p; HBAAPI(I) v2.3.b, 07-12-10 Board Temperature : Normal Function Type : FC Sub Device ID : 03F1 PCI Bus Number : 1 PCI Func Number : 1 Sub Vendor ID : 1014 Service Processor FW Name : 10.2.252.1919 ULP FW Name : 10.2.252.1919 FC Universal BIOS Version : KT8.02a7 FC x86 BIOS Version : KA6.01a11 FC EFI BIOS Version : KD6.01a11 FC FCODE Version : KN4.02a14 Flash Firmware Version : 10.2.252.1919
Update microcode on one port per adapter. This step assumes that microcode image .rpm package has been installed on system as described in section 8.2.
Warning: Do not interrupt or power off the system while microcode update(s) are in progress.
Start microcode update on one adapter port, by specifying the WWPN type, and wait:
# /usr/sbin/hbacmd download 10:00:00:00:c9:d1:8b:f1 /lib/firmware/df1000e21410f103.00010000020025201919.grp
Completion of download will be indicated by “Download Complete.” message.
Flash all adapters System must be rebooted for firmware to be loaded. Reboot system
Flash all adapters before rebooting
If, firmware version is not the version you are expecting, carefully retrace steps for omissions and examine console output for errors. Contact IBM support if you need further assistance.
Ethernet adapter adapter
Example for 10Gb ethernet
Use this series of Linux commands to determine which of any installed Network adapters are PCIe3 4-Port 10GbE CU Adapter:
Output will display the association between eth{n} devices and PCI bus device numbers, nnnn:nn:nn.n
[root@rh-ppcle] ~ # for i in `ls /sys/class/net | grep eth` do echo -n "${i}: "; ethtool -i ${i} | grep bus-info done eth0: bus-info: eth1: bus-info: 0000:01:00.0 eth2: bus-info: 0000:01:00.1 eth3: bus-info: 0000:01:00.2 eth4: bus-info: 0000:01:00.3
Output will list PCI bus device numbers for the PCIe3 4-Port 10GbE CU Adapter functions, nn:nn.n
[root@rh-ppcle] ~ # lspci -d 10df:e220 01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 30) 01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 30) 01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 30) 01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 30)
This example shows the four ports of one PCIe3 4-Port 10GbE CU Adapter. Firmware need only be updated on the first port of each adapter,
eth1 in this case.
If more than 4 ports are shown, it is likely you have more than one adapter, so you would need to also update firmware on first port of second adapter.
Stop all applications that use the interface/adapter to be updated
Configure the adapter’s interface, eth1 in this example.
[root@rh-ppcle] ~ # ifconfig eth1 192.168.1.1/24
Check that no errors were reported. If errors were reported verify proper interface was configured and command was entered correctly.
Downloading Microcode to the Adapter
Using the eth{n} configured in previous step use ethtool –flash to update the firmware.
[root@rh-ppcle] ~ # ethtool --flash eth{n} df1020e21410e404.00010000020025201913
Note: eth{n} is the interface previously configured with ifconfig
If flashing is completed successfully, no messages will appear on the screen. You can check messages in system log.
[root@rh-ppcle] ~ # dmesg | grep be2net be2net 0000:01:00.0: Flashing firmware file df1020e21410e404.00010000020025201913 be2net 0000:01:00.0: System reboot required for new FW to be active be2net 0000:01:00.0: Firmware flashed successfully
These messages show flashing is completed successfully.
Reboot the OS instance to activate the updated firmware.
Verify firmware has been activated
Using same eth{n} interface used for ethtool –flash command, type:
[root@rh-ppcle] ~ # ethtool -i eth1 driver: be2net version: 4.4.161.0s firmware-version: 10.2.252.1913 bus-info: 0000:01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: no
Firmware-version must show 10.2.252.1913. If firmware-version is not as expected, carefully retrace steps to confirm no steps were omitted or performed incorrectly. If no errors or omissions were found, contact IBM customer service for assistance.
Attention LED
You are right. usysattn is the right comment. Below is the command usage. usysattn –> gives all fault indicator list. First line in the output system attention indicator location code. Ex :
[root@xxx ~]# usysattn U78A5.001.WIH8464 [on] <- Attention indicator location code U78A5.001.WIH8464-P1 [off] U78A5.001.WIH8464-P1-C1 [off]
usysattn -l <attn indicator location> -s normal --> disables attention indicator.
Ex:
[root@xxx ~]# usysattn -l U78A5.001.WIH8464 -s normal off
