Topic
  • 10 replies
  • Latest Post - ‏2013-03-23T13:19:03Z by SystemAdmin
SystemAdmin
SystemAdmin
3234 Posts

Pinned topic BladeCenter S CLI

‏2012-10-23T11:44:52Z |
I am trying to upgrade the firmware on the SAS Controllers in a Bladecenter S and everything refers to a CLI utility.

Where can i get this from?

or any hints and tips how to get the upgrade working i tried the following

C:\codeload\ibm_fw_bcsw_s0cl-1.2.4.009_windows_noarch.bat -i 192.168.100.170 -n

it says Unpacking ........ then just goes back to the prompt C:\codeload

i have installed Python and Cygwin with the relavent packages.

Please help!!!
Updated on 2013-03-23T13:19:03Z at 2013-03-23T13:19:03Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2012-10-23T13:58:09Z  
    Ok i have got it to unpack but now i get the following message:

    Initializing firmware update - please wait
    MSG: ./Sbinst.py failed in function runTelnetCmd, rc = 8.

    Any ideas?
  • Novikov_Alexander
    Novikov_Alexander
    1147 Posts

    Re: BladeCenter S CLI

    ‏2012-10-23T18:34:26Z  
    Ok i have got it to unpack but now i get the following message:

    Initializing firmware update - please wait
    MSG: ./Sbinst.py failed in function runTelnetCmd, rc = 8.

    Any ideas?
    Dear David,

    what is the Windows version used?

    Regards,
    Alexander Novikov
    Russia, Moscow
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-01-29T21:32:49Z  
    Dear David,

    what is the Windows version used?

    Regards,
    Alexander Novikov
    Russia, Moscow
    Hi, I'm having the same issue.

    Windows 7 x64
  • gez
    gez
    275 Posts

    Re: BladeCenter S CLI

    ‏2013-01-30T16:58:47Z  
    Hi, I'm having the same issue.

    Windows 7 x64
    MSG: ./Sbinst.py failed in function runTelnetCmd, rc = 8
    This means that there is an issue telnetting to the specified IP address.
    Make sure that the IP address specified is the RAID IP and not the SAS IP.
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-01-30T18:01:55Z  
    • gez
    • ‏2013-01-30T16:58:47Z
    MSG: ./Sbinst.py failed in function runTelnetCmd, rc = 8
    This means that there is an issue telnetting to the specified IP address.
    Make sure that the IP address specified is the RAID IP and not the SAS IP.
    Thanks, that was it.
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-03-15T20:59:52Z  
    For future reference, anyone having an issue with the command line update can check the SbInst.py.log file in the directory you ran the .bat from (README says to create C:\codeload so it would be C:\codeload\SbInst.py.log). It will tell you real reason for the failure.
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-03-16T15:30:56Z  
    Storage Configuration Manager can also update the firmware for the SAS RAID Controller as well. However, looks like you have taken the CLI path.

    Key points:
    1. Halt all IO activity to the drives.
    2. Best to shutdown all blades to achieve this.
    3. Check you have no active alerts on the RAID controller. (SCM has it nicely displayed, but you can access via the CLI too).
    4. Alerts need to be cleared. Update fails if alerts present.
    5. Put controllers in service mode.

    What state is the RAID controller in when you attempt the firmware upgrade? You can find out by using the following command in the CLI once you logged into the RAID controller:
    list controller

    or

    Under SCM go to BCS RAID Controller-> Health ->Physical View-> Highlight Controller-> and select one of them. Will give you state.

    The readme file for the firmware update walks you through the steps on how to prepare the controller cards before attempting the update.
    IMPORTANT:
    What current firmware are you running? You need to be at 1.2.1.015 or higher. See readme file ibm_fw_bcsw_s0cl-.2.4.009_windows_noarch.txt section 2.3.1.

    To get your version from winthin the CLI type swversion
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-03-22T17:00:44Z  
    Storage Configuration Manager can also update the firmware for the SAS RAID Controller as well. However, looks like you have taken the CLI path.

    Key points:
    1. Halt all IO activity to the drives.
    2. Best to shutdown all blades to achieve this.
    3. Check you have no active alerts on the RAID controller. (SCM has it nicely displayed, but you can access via the CLI too).
    4. Alerts need to be cleared. Update fails if alerts present.
    5. Put controllers in service mode.

    What state is the RAID controller in when you attempt the firmware upgrade? You can find out by using the following command in the CLI once you logged into the RAID controller:
    list controller

    or

    Under SCM go to BCS RAID Controller-> Health ->Physical View-> Highlight Controller-> and select one of them. Will give you state.

    The readme file for the firmware update walks you through the steps on how to prepare the controller cards before attempting the update.
    IMPORTANT:
    What current firmware are you running? You need to be at 1.2.1.015 or higher. See readme file ibm_fw_bcsw_s0cl-.2.4.009_windows_noarch.txt section 2.3.1.

    To get your version from winthin the CLI type swversion
    Hello, it is better to you the last actual Version 1.2.4.014
    see https://www-947.ibm.com/support/entry/myportal/docdisplay?lndocid=MIGR-5087717

    T.P.
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-03-22T17:02:11Z  
    Hello, it is better to you the last actual Version 1.2.4.014
    see https://www-947.ibm.com/support/entry/myportal/docdisplay?lndocid=MIGR-5087717

    T.P.
    ... and be carreful = the SCM isn't working under Windows 7 ... use Windows server or Windows XP
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: BladeCenter S CLI

    ‏2013-03-23T13:19:03Z  
    Hello, it is better to you the last actual Version 1.2.4.014
    see https://www-947.ibm.com/support/entry/myportal/docdisplay?lndocid=MIGR-5087717

    T.P.
    As mentioned before, check what version you are currently on to confirm you can do a straight upgrade to the 1.2.4.011 or 1.2.4.014. You may have to do a 2 step upgrade of firmware.