delivery04.dhe.ibm.com_sar_CMA_XSA_00s24_0_ibm_fw_bcsw_s0cl-1.0.3.025_anyos_noarch.pdf

7/18/2019 delivery04.dhe.ibm.com_sar_CMA_XSA_00s24_0_ibm_fw_bcsw_s0cl-1.0.3.025_anyos_noarch.pdf

http://slidepdf.com/reader/full/delivery04dheibmcomsarcmaxsa00s240ibmfwbcsws0cl-103025anyosnoarchpdf 1/8

IBM BladeCenter S SAS RAID Controller Module Firmware ‐ Version 1.0.3.025 Build ID: S0RC786

CONTENTS‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐1.0 Windows Prerequisite Setup (Setting up the Command Line Firmware Update Utility)2.0 General Linux Prerequisite Setup (Setting up the Command Line Firmware Update Utility)3.0 SLES Linux Prerequisite Setup (Setting up the Command Line Firmware Update Utility)4.0 Install Procedure: Non‐Concurrent Code Load (NCCL)5.0 Trademarks and Notices

6.0 Disclaimer7.0 IBM License Agreement for Machine Code

‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

General Notes‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐The Command Line Firmware Update Utility should be run in a "serial" mode when runningfrom either Windows or Linux. Only one firmware update should be running at any time ona single machine. Running multiple instances of the Command Line Firmware Update Utilitysimultaneously is not supported.

The Command Line Firmware Update Utility must always be run starting from a cleansubdirectory. Any leftover files from previous runs may cause unexpected failureson subsequent attempts.

The Command Line Firmware Update Utility requires a minimum Python level of 2.5.

For a list of supported operating systems for the Command Line Firmware Update Utility,consult the SAS RAID Module Interoperability Guide at:

http://www‐947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR‐5078491&brandind=5000020

1.0 Windows Prerequisite Setup‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

Before installing the Command Line Firmware Update Utility the following utilities must be downloaded and installed on the system which will be used for the upgrade. ‐ Cygwin (www.cygwin.com) ‐ Python (www.python.org) version 2.5 or higher ‐ Pexpect (pexpect.sourceforge.net)

1.1 Windows‐specific prerequisite installation To configure the Windows environment for Command Line Firmware Update Utility:

1.1.1 Download and install Cygwin. Cygwin is a Linux‐like environment for Windows. The Command Line Firmware Update Utility runs from a Cygwin bash shell.

1.1.1.1 Download the Cygwin installer ‐ Open a web browser

‐ Type Ctrl‐L and enter the following address:http://www.cygwin.com/setup.exe.

‐ Save setup.exe in C:\cyg_dnld\ If this directory does not

already exist, create it.

1.1.1.2 Start the Cygwin installer application ‐ Click Start > Run

‐ Type c:\cyg_dnld\setup.exe and press Enter



‐ A new window appears. Verify that this is the Cygwin Setup window.

‐ Click Next.

1.1.1.3 Choose the source of the installation ‐ From the Choose Installation Type window, select Install from Internet.

‐ Click Next

1.1.1.4 Configure the settings ‐ From the Choose Installation Directory window, ensure that the Root Directory is set to C:\cygwin . This is the default setting.

‐ Make Install For set to All Users . This is the default setting.

‐ Make Default Text File Type set to Unix / binary . This is the defaultsetting.

‐ Click Next.

1.1.1.5 Choose a location for Cygwin downloaded files

‐ From the Cygwin Setup ‐ Select Local Package Directory window, ensure that the Local Package Directory is set to C:\cyg_dnld.

‐ Click Next.

1.1.1.6 Configure your network connection type ‐ From the Cygwin Setup ‐ Select Connection Type window select Direct Connection. If you do not have a direct connection to the Internet, consult your system administrator to determine the correct selections.

‐ Click Next.

1.1.1.7 Select the download host for the Cygwin packages ‐ From the Cygwin Setup ‐ Choose Download Site(s) window, click any of the URLs listed in the Available Download Sites list.

‐ Click Next.

1.1.1.8 Choose which packages to install. Packages are listed by category ‐ To view the list of packages within each category, click the expand icon next to the category name.

‐ From the New column in the specified package row, click Skip until the desired version number appears. This sets the packages for installation.

‐ From the Cygwin Setup ‐ Select Packages window, set the following packages for installation:

Cygwin installation packages ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Category Package Minimum version Description ‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ ‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ Devel gcc‐core 3.4.4‐3 C compiler

Devel make 3.81‐2 The GNU version of the makeutility Net openssh 5.0p1‐1 The openSSH server andclient programs Net ping 1.0‐1 A basic networking tool Net inetutils 1.5‐4 A common networking client



and server Python Python 2.5.1‐2 Interactive object‐orientedscripting language Utils ncurses 5.5‐3 Utilities for terminalhandling Web wget 1.10.2‐2 Utility used to retrievefiles from the internet

‐ Click Next.

‐ Complete the Installation. When the installation completes, theCygwin Setup ‐ Installation Status and Create Icons window appears.

‐ Click Finish.

1.1.1.9 Install pexpect for python ‐ Double‐click the Cygwin Bash Shell icon on your desktop.

‐ Download and install pexpect and run the following commands:# wget http://pexpect.sourceforge.net/pexpect‐2.3.tar.gz

# tar ‐xzf pexpect‐2.3.tar.gz # cd pexpect‐2.3

# python ./setup.py install

1.1.2.0 Configure Windows Environment Variable ‐ After the Ccygwin installation completes, configure windows by addingthe following environment variable: # From "start", select "Control Panel" # At the Control Panel, select "System" # From the System Properties window, select the "Advanced" tab # Click on the "Environment Variables" button # Click on the System variables "New" button # Add a new Variable name "CYGWIN" # Add a new Variable value "tty notitle glob"

# Click on the "Ok" button # Click on the "Ok" button from the Environment Variables window # Click o nthe "Ok" button from the System Properties window # Close the Control Panel

‐ If you have any open cygwin windows, close them and re‐open ifnecessary.

1.2 Once the environment is set up, continue with Install Procedure: Non‐ConcurrentCode Load

2.0 General Linux Prerequisite Setup‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 2.1 Install ncurses 5.5‐3 or greater ‐ Use the standard install method provided with the ncurses package

2.2 Install python 2.5 or greater ‐ Use the standard install method provided with the python package

2.3 Install pexpect for python

2.3.1 Open a bash shell to download and install pexpect Run the following commands:

# wget http://pexpect.sourceforge.net/pexpect‐2.3.tar.gz # tar ‐xzf pexpect‐2.3.tar.gz # cd pexpect‐2.3 # python ./setup.py install

2.4 Once the environment is set up, continue with Install Procedure: Non‐Concurrent



Code Load

3.0 SLES Linux Prerequisite Setup‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐ 3.1 Install ncurses 5.5‐3 or greater ‐ Use the standard install method provided with the ncurses package ‐ This package should be included on the SLES distribution CD

3.2 Install python 2.5.4 or greater ‐ Download the latest version from: http://www.python.org/download/releases/2.5.4/ ‐ The download should consist of a single file. Example File: Python‐2.5.4.tgz.

3.2.1 Unpack the source code image ‐ Change to the same dir as the Python source image. ‐ Run "tar ‐zxvf Python‐2.5.4.tgz"

3.2.2 Compile Python: ‐ Change to the unpacked Python directory. ‐ Run the following commands: ./configure

make make install

3.3 Once the environment is set up, continue with Install Procedure: Non‐ConcurrentCode Load

4.0 Install Procedure: Non‐Concurrent Code Load (NCCL)‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

Prior to starting the firmware download and upgrade process all persistent

alerts must be resolved. View the Active Alert List to verify if there are any persistent alert(s) that require resolution. In some instances, a persistent alert may be resolved by upgrading the firmware. Check the release letter content to determine if there are persistent alert(s) that are fixed in this level of code.

Note: A Non‐Concurrent process is one done after shutting down all IO processes.

4.1 The downloaded file should be executable (ibm_fw_bcsw_s0cl‐N.N.N.NNN_anyos_noarch.sh). If it is not executable Run the following: # chmod +x ibm_fw_bcsw_s0cl‐N.N.N.NNN_anyos_noarch.sh

4.2 Put both RAID Controller Modules in service mode ‐ Login to either RAID Controller CLI.

‐ Run the shutdown to service command (only needs to be run on ONE ofthe two controllers). Run the following:

<CLI> shutdown ‐system ‐state servicemode

‐ Wait for the controllers to reboot

‐ Login to one of the RAID Controller CLIs.

‐ Verify both controllers are in service mode. Run the following:

<CLI> list controller

4.3 Start the SAS RAID Controller Firmware Update Package installation ‐ Run the following within the same directory where you downloaded the package. Where NNN is the build number of the downloaded package and XXX.XXX.XXX.XXX is the IP address of either SAS RAID controller. This command assumes that the



default passwords were not changed.

# ./ibm_fw_bcsw_s0cl‐N.N.N.NNN_anyos_noarch.sh ‐i X.XXX.XXX.XXX

‐ If you have custom passwords, run the following within the same directory where you downloaded the package. Where NNN is the build number of the downloadedpackage and X.XXX.XXX.XXX is the IP address of either SAS RAID controller.

# ./ibm_fw_bcsw_s0cl‐N.N.N.NNN_anyos_noarch.sh ‐i X.XXX.XXX.XXX ‐passwd XXXXXXXX‐sas_p1 XXXXXXXX ‐sas_p2 XXXXXXXX ‐ftx_pwd XXXXXXXX

5.0. TradeMarks and Notices‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

5.1 The following terms are trademarks of the IBM Corporation in the United States, or other countries or both: * IBM * BladeCenter

* Netfinity * Netfinity Manager * Advanced System Management

Other company, product, and service names may be trademarks or service marks of others.

6.0. Disclaimer‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

6.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.

6.2 Note to Government users:

Note to U.S. Government users‐‐ Documentation related to restricted rights‐‐ Use, duplication and disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

7.0. IBM License Agreement for Machine Code‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐

You accept the terms of this IBM License Agreement for Machine Code ("Agreement")by your initial use of a Machine that contains Machine Code.

The term "Machine Code" means microcode, basic input/output system code (called

"BIOS"), utility programs, device drivers, and diagnostics delivered with an IBMMachine, and may sometimes be referred to as "Licensed Internal Code" or "LIC" indocumentation or on the Machine with which the Machine Code was delivered. All suchcode, whether referred to or marked as Machine Code, Licensed Internal Code or LIC,

issubject to this license. Machine Code does not include programs and code provided



underseparate license agreements, including but not limited to open source licenseagreements. Acceptance of these license terms authorizes you to use Machine Code

withthe specific product for which it is provided.

The term "Machine" means an IBM machine, its features, conversions, upgrades,elements

or accessories, or any combination of them. A Machine may include computing

resourcesor capabilities that are to remain inactive, or whose use is restricted, until theright to access and use the resources or capabilities is properly acquired for theMachine directly from IBM or through an authorized IBM reseller (called "Built‐in‐

Capacity"). Examples of such computing resources and capabilities include but arenot

limited to processors, memory, storage, processing capacity identified asinteractive

processing capacity, and workload‐specific resources or capabilities (such as aspecific operating system, programming language or application to which use of theMachine is limited).

International Business Machines Corporation or one of its subsidiaries

(collectively"IBM") owns copyrights in Machine Code or has the right to license Machine Code.

IBM ora third party owns all copies of Machine Code, including all copies made from them.

IBMlicenses Machine Code to only one rightful possessor at a time.

If you are the rightful possessor of a Machine, IBM grants you a nonexclusivelicense

to use Machine Code (or any replacement IBM provides) on, or in conjunction with,only

the Machine for which IBM provided it, and only to the extent of IBM authorizations

youhave acquired for access to and use of Built‐in‐Capacity. If your use of Built‐in‐

Capacity exceeds the IBM authorizations you have acquired for the Machine, youagree to

pay IBM or (if applicable) an authorized IBM reseller the full price of permanent,unrestricted use of the Built‐in‐Capacity at the then current price. You are notauthorized to use such Built‐in‐Capacity until such payment is made.

Under each license, IBM authorizes you to do only the following: 1. execute Machine Code to enable the Machine to function according to itsOfficial

Published Specifications (called "Specifications"). 2. use only the Built‐in‐Capacity properly acquired for the Machine directlyfrom

IBM or through an authorized IBM reseller; 3. make a reasonable number of copies of Machine Code to be used solely forbackup

or archival purposes, provided you reproduce the copyright notice and anyother

legend of ownership on any such copies. You may use the copies only toreplace

the original, when necessary; and 4. execute and display Machine Code as necessary to maintain the Machine.

You agree to acquire any replacement for, or additional copy of, Machine Code

directlyfrom IBM in accordance with IBM’s standard policies and practices. You also agree

touse that Machine Code under these terms.

You may transfer possession of Machine Code and its media to another party only



withthe transfer of the Machine on which that Machine Code is authorized. If you do so,

youagree to 1) destroy all your copies of that Machine Code that were not provided by

IBM,2) either give the other party all your IBM‐provided copies of Machine Code or

destroythem, and 3) give the other party a copy of these terms and provide all userdocumentation to that party. IBM licenses the other party to use Machine Code when

that party accepts the terms of this Agreement. These terms apply to all Machine Codeyou

acquire from any source.

Your license for Machine Code terminates when you no longer rightfully possess theassociated Machine.

No other rights are granted under this license.

You agree to use Machine Code only as authorized above. You may not do, forexample,

any of the following:

1. otherwise copy, display, transfer, adapt, modify, or distribute(electronically

or otherwise) Machine Code, except as IBM may authorize in a Machine’s userdocumentation or in writing to you;

2. reverse assemble, reverse compile, or otherwise translate Machine Code,unless

expressly permitted by applicable law without the possibility of contractualwaiver;

3. sublicense or assign the license for Machine Code; or 4. lease Machine Code or any copy of it.

Built‐in‐Capacity is protected by certain technological measures in Machine Code.

Youagree to IBM's implementation of such technological measures to protect Built‐in‐

Capacity, including measures that may impact availability of data or performance ofyour Machine. As a condition of your license to use Machine Code under this

Agreement,you may not circumvent such technological measures, or use a third party or third

partyproduct to do so, or otherwise access or use unauthorized Built‐in‐Capacity. In theevent IBM determines that changes are necessary to the technological measures

designedto limit access to, or use of, Built‐in‐Capacity to that which has been authorized,

IBMmay provide you with changes to such technological measures. As a condition of yourlicense to use Machine Code under this Agreement, you agree, at IBM’s option, to

apply or allow IBM to apply such changes.

If you obtained Machine Code directly from IBM and an IBM Customer Agreement orequivalent agreement is in effect between you and IBM ("ICA"), then the terms of

thisAgreement are incorporated by reference into that ICA. If no ICA is in effect, or

ifyou obtained Machine Code from an IBM authorized reseller or other third party,

thenthe terms of IBM’s Statement of Limited Warranty are incorporated into this

Agreementby reference and apply to any questions or claims regarding warranty, liability,governing law or jurisdiction for Machine Code.

If there is a conflict between the terms of this Agreement and those of the ICA orthose of IBM’s Statement of Limited Warranty, as applicable, the terms of this



Agreement prevail, but only to the extent of such conflict.

delivery04.dhe.ibm.com_sar_CMA_XSA_00s24_0_ibm_fw_bcsw_s0cl-1.0.3.025_anyos_noarch.pdf

Documents

Transcript of delivery04.dhe.ibm.com_sar_CMA_XSA_00s24_0_ibm_fw_bcsw_s0cl-1.0.3.025_anyos_noarch.pdf