- Preface
- Overview
- Installing the Server OS
- Managing the Server
- Viewing Server Properties
- Viewing Sensors
- Managing Remote Presence
- Managing User Accounts
- Configuring Network-Related Settings
- Managing Network Adapters
- Managing Storage Adapters
- Configuring Communication Services
- Managing Certificates and Server Security
- Configuring Platform Event Filters
- Cisco IMC Firmware Management
- Viewing Faults and Logs
- Server Utilities
- BIOS Parameters by Server Model
- BIOS Token Name Comparison for Multiple Interfaces
- Index
- Overview of Firmware
- Obtaining Firmware from Cisco
- Introduction to Cisco IMC Secure Boot
- Installing Cisco IMC Firmware
- Activating Installed CIMC Firmware
- Installing BIOS Firmware
- Activating Installed BIOS Firmware
- Installing VIC Firmware
- Installing CMC Firmware from a Remote Server
- Activating Installed CMC Firmware
- Installing SAS Expander Firmware from a Remote Server
- Activating Installed SAS Expander Firmware
- Installing SAS Expander Firmware from a Remote Server
- Activating Installed SAS Expander Firmware
Cisco IMC Firmware
Management
This chapter includes the following sections:
- Overview of Firmware
- Obtaining Firmware from Cisco
- Introduction to Cisco IMC Secure Boot
- Installing Cisco IMC Firmware
- Activating Installed CIMC Firmware
- Installing BIOS Firmware
- Activating Installed BIOS Firmware
- Installing VIC Firmware
- Installing CMC Firmware from a Remote Server
- Activating Installed CMC Firmware
- Installing SAS Expander Firmware from a Remote Server
- Activating Installed SAS Expander Firmware
- Installing SAS Expander Firmware from a Remote Server
- Activating Installed SAS Expander Firmware
Overview of Firmware
C-Series servers use Cisco-certified firmware that is specific to the C-Series server model that you are using. You can download new releases of the firmware for all supported server models from Cisco.com.
Caution | When you install the new BIOS firmware, it must be from the same software release as the Cisco IMC firmware that is running on the server. Do not install the new BIOS firmware until after you have activated the matching Cisco IMC firmware or the server will not boot. To avoid potential problems, we strongly recommend that you use the Cisco Host Upgrade Utility (HUU), which upgrades the BIOS, Cisco IMC, and other firmware to compatible levels. For detailed information about this utility, see the Cisco Host Upgrade Utility Guide for the version of the HUU that goes with the Cisco IMC software release that you want to install. The HUU guides are available at the following URL: http://www.cisco.com/en/US/products/ps10493/products_user_guide_list.html. |
If you want to update the firmware manually, you must update the Cisco IMC firmware first. The Cisco IMC firmware update process is divided into the following stages to minimize the amount of time that the server is offline:
-
Installation—During this stage, Cisco IMC installs the selected Cisco IMC firmware in the nonactive, or backup, slot on the server.
-
Activation—During this stage, Cisco IMC sets the nonactive firmware version as active, causing a disruption in service. When the server reboots, the firmware in the new active slot becomes the running version.
After you activate the Cisco IMC firmware, you can update the BIOS firmware. You must power off server during the entire BIOS update process, so the process is not divided into stages. Instead, you only need to enter one command and Cisco IMC installs and updates the BIOS firmware as quickly as possible. After the Cisco IMC finishes rebooting, the server can be powered on and returned to service.
Cisco IMC in a secure mode ensures that all the firmware images prior to loading and execution are digitally signed and are verified for authenticity and integrity to protect the device from running tampered software.
Obtaining Firmware from Cisco
Step 1 | Navigate to http://www.cisco.com/. | ||
Step 2 | If you are not already logged in, click Log In at the top right-hand edge of the page and log in using your Cisco.com credentials. | ||
Step 3 | In the menu bar at the top, click Support. | ||
Step 4 | Click All Downloads in the roll down menu. | ||
Step 5 | If your server model is listed in the Recently Used Products list, click the server name. Otherwise, do the following: | ||
Step 6 | Click the Unified Computing System (UCS) Server Firmware link. | ||
Step 7 | (Optional) Select a prior release from the menu bar on the left-hand side of the page. | ||
Step 8 | Click the Download button associated with the Cisco Host Upgrade Utility ISO for the selected release. | ||
Step 9 | Click Accept License Agreement. | ||
Step 10 | Save the ISO
file to a local drive.
We recommend you upgrade the Cisco IMC and BIOS firmware on your server using this ISO file, which contains the Cisco Host Upgrade Utility. For detailed information about this utility, see the Cisco Host Upgrade Utility Guide for the version of the HUU that goes with the Cisco IMC software release that you want to install. The HUU guides are available at the following URL: http://www.cisco.com/en/US/products/ps10493/products_user_guide_list.html. | ||
Step 11 | (Optional)
If you plan to upgrade the
Cisco IMC
and BIOS firmware manually, do the following:
Viewing the GETFW help menu: [root@RHEL65-***** tmp]# cd GETFW/ [root@RHEL65-***** GETFW]# ./getfw -h Help: Usage: getfw {-b -c -C -H -S -V -h} [-s SRC] [-d DEST] -b : Get BIOS Firmware -c : Get CIMC Firmware -C : Get CMC Firmware -H : Get HDD Firmware -S : Get SAS Firmware -V : Get VIC Firmware -h : Display Help -s SRC : Source of HUU ISO image -d DEST : Destination to keep Firmware/s Note : Default BIOS & CIMC get extracted Extracting the BIOS firmware: [root@RHEL65-***** GETFW]# ./getfw -s /root/Desktop/HUU/ucs-c2xxx-huu-3.0.1c.iso -d /tmp/HUU FW/s available at '/tmp/HUUucs-c2xxx-huu-3.0.1c' [root@RHEL65-***** GETFW]# cd /tmp/HUU/ [root@RHEL65-***** HUU]# cd ucs-c2xxx-huu-3.0.1c/ [root@RHEL65-***** ucs-c2xxx-huu-3.0.1c]# ls bios cimc [root@RHEL65-***** ucs-c2xxx-huu-3.0.1c]# cd bios/ [root@RHEL65-***** bios]# ls bios.cap [root@RHEL65-***** bios]# Extracting the CIMC firmware: [root@RHEL65-***** GETFW]# ./getfw -s /root/Desktop/HUU/ucs-c2xxx-huu-3.0.1c.iso -d /tmp/HUU FW/s available at '/tmp/HUUucs-c2xxx-huu-3.0.1c' [root@RHEL65-***** GETFW]# cd /tmp/HUU/ [root@RHEL65-***** HUU]# cd ucs-c2xxx-huu-3.0.1c/ [root@RHEL65-***** ucs-c2xxx-huu-3.0.1c]# ls bios cimc [root@RHEL65-***** ucs-c2xxx-huu-3.0.1c]# cd cimc/ [root@RHEL65-***** cimc]# ls cimc.cap [root@RHEL65-***** cimc]# | ||
Step 12 | (Optional)
If you plan to
install the firmware from a remote server, copy the BIOS installation CAP file
and the
Cisco IMC
installation BIN file to the remote server you want to use.
The server must have read permission for the destination folder on the remote server.
|
What to Do Next
Use the Cisco Host Upgrade Utility to upgrade all firmware on the server or manually install the Cisco IMC firmware on the server.
Introduction to Cisco IMC Secure Boot
About Cisco IMC Secure Mode
Note | Cisco IMC secure boot mode is enabled by default only on some Cisco UCS C-Series servers. |
You can update Cisco IMC to the latest version using Host Upgrade Utility (HUU), web UI, or CLI. If you use HUU to upgrade Cisco IMC, you are prompted to enable secure boot mode. If you choose Yes, the system enters a secure mode and install the firmware twice. If you choose No, it enters a nonsecure mode. If you use either the web UI or CLI to upgrade Cisco IMC, you must upgrade to version 2.0(x). After you boot the system with version 2.0(x), it boots in a nonsecure mode by default. You must enable secure mode. when you enable secure mode, you are automatically reinstalling the firmware. In the web UI, the secure mode option is available as a checkbox within the Cisco IMC firmware update page. In the CLI, you can enable the secure mode by using the update-secure command.
During the first upgrade to Cisco IMC version 2.0, a warning message might display stating that some of the features and applications are not installed correctly and a second upgrade is required. We recommend that you perform the second upgrade with or without the secure boot option enabled to correctly install the Cisco IMC firmware version 2.0(x) in a secure mode. After the installation is complete, you must activate the image. After you boot your system with the secure boot option enabled, Cisco IMC remains in secure mode and you cannot disable it later on. If you do not activate the image and reinstall any other firmware images, Cisco IMC may become unresponsive.
Warning | After you install the firmware with the secure boot migration, you must activate the image before performing any other regular server-based tasks. If you do not activate this image, and if you reinstall any other firmware images, Cisco IMC might become unresponsive. The secure boot is enabled only when the firmware installation is complete and you have activated the image. |
Supported Cisco IMC Version When Downgrading from the Latest Version
The following table lists the Cisco IMC versions in a secure mode that can be downgraded to prior versions.
From Cisco IMC Version | To Cisco IMC Version | Possibility |
---|---|---|
2.0(x) |
Prior to 1.5(1) |
Not possible |
2.0(x) |
1.5(3x) or later |
Possible |
2.0(x) |
Prior to 1.5(3x) |
Not possible |
Note | When the Cisco IMC verison you are using is in a nonsecure mode, you can downgrade Cisco IMC to any prior version. |
Note | If you use HUU to downgrade Cisco IMC versions prior to 1.5(4), you must first downgrade Cisco IMC and then downgrade other firmware. Activate the firmware and then downgrade the BIOS firmware. |
Number of Updates Required for Cisco IMC Version 2.0(1)
This section is valid for Cisco IMC version 2.0(1) and prior releases.
Supported Cisco IMC Version When Upgrading to the Latest Version
The following table lists the number of updates required for Cisco IMC to correctly install all the applications of the latest version.
From Cisco IMC Version | To a Nonsecure Cisco IMC Version 2.0(x) | To a Secure Cisco IMC Version 2.0(x) |
---|---|---|
Prior to 1.5(2) | Double update | Double update |
1.5(2) | Single update | Double update |
1.5(3) | Single update | Double update |
1.5(3x) or Later | Single update | Double update |
Updating Cisco IMC in a Nonsecure Mode
This section is valid for Cisco IMC version 2.0(1) and prior releases.
You can upgrade Cisco IMC to the latest version in a nonsecure mode with all the latest feature and applications installed correctly. When you upgrade Cisco IMC to the latest version using the web UI or CLI, you might need to update the firmware twice manually depending upon the version you are using. See, Supported Cisco IMC Version when Upgrading to the Latest Version. If you use HUU to upgrade the Cisco IMC verison, it gets upgraded to the latest verison automatically.
Note | If you are installing from a Cisco IMC version prior to 1.5(2x), the following message is displayed: |
Warning | "Some of the Cisco IMC firmware components are not installed properly! Please reinstall Cisco IMC firmware version 2.0(1) or higher to recover".
|
When Cisco IMC runs in a nonsecure mode, it implies the following:
Installing Cisco IMC Firmware
-
Log in to the Cisco IMC as a user with admin privileges.
-
Obtain the Cisco Host Upgrade Utility ISO file from Cisco.com and extract the firmware installation files as described in Obtaining Firmware from Cisco.
This example shows how to update the Cisco IMC firmware and to migrate Cisco IMC from a nonsecure boot to secure boot for Cisco IMC version 2.0:
server# scope cimc server /cimc # scope firmware server /cimc /firmware # update ftp 192.0.20.34 //test/dnld-ucs-k9-bundle.1.0.2h.bin Firmware update has started. Please check the status using "show detail" Server /cimc /firmware # update-secure tftp 1.1.1.1 /cimc-pkg.bin Migrating to Cisco IMC Secure Boot option implies: -You can install and boot only signed Cisco IMC firmware images on the server. -You cannot install and boot Cisco IMC firmware versions prior than 1.5(3x). -You cannot disable Secure Boot later on. After installing the firmware with the Secure Boot migration, you must activate the image before performing any other regular server-based tasks. The Secure Boot option is enabled only when the firmware installation is complete and you have activated the image. Continue?[y|N]y Update to Secure Boot selected, proceed with update. Firmware update initialized. Please check the status using "show detail". server /cimc /firmware # show detail Firmware Image Information: Update Stage: DOWNLOAD Update Progress: 5 Current FW Version: 2.0(0.29) FW Image 1 Version: 2.0(0.28) FW Image 1 State: BACKUP INACTIVATED FW Image 2 Version: 2.0(0.29) FW Image 2 State: RUNNING ACTIVATED Boot-loader Version: 2.0(0.9).35 Secure Boot: DISABLED *+-----------------------------------------------------------------------+ + Some of the Cisco IMC firmware components are not installed properly! + + Please reinstall Cisco IMC firmware version 2.0 or higher to recover. + +-----------------------------------------------------------------------+ server /cimc /firmware #
This example shows how to update the Cisco IMC firmware:
server# scope cimc server /cimc # scope firmware server /cimc /firmware # update ftp 10.10.10.10 //test/dnld-ucs-k9-bundle.1.0.2h.bin Firmware update has started. Please check the status using "show detail" server /cimc /firmware #
Activate the new firmware.
Activating Installed CIMC Firmware
Install the CIMC firmware on the server.
While the activation is in progress, do not:
Command or Action | Purpose | |
---|---|---|
Step 1 | Server# scope cimc |
Enters the CIMC command mode. |
Step 2 | Server /cimc # scope firmware |
Enters the firmware command mode. |
Step 3 | Server /cimc/firmware # show detail |
Displays the available firmware images and status. |
Step 4 | Server /cimc/firmware # activate [1 | 2] |
Activates the selected image. If no image number is specified, the server activates the currently inactive image. |
Step 5 | At the prompt, enter y to activate the selected firmware image. |
The BMC reboots, terminating all CLI and GUI sessions until the reboot completes. |
Step 6 | Log back into the CLI and repeat steps 1–3 to verify the activation. | (Optional) |
This example activates firmware image 1 and then verifies the activation after the BMC reboots:
Server# scope cimc Server /cimc # scope firmware Server /cimc/firmware # show detail Firmware Image Information: Update Stage: NONE Update Progress: 100 Current FW Version: 1.3(3a) FW Image 1 Version: 1.4(3j) FW Image 1 State: BACKUP INACTIVATED FW Image 2 Version: 1.3(3a) FW Image 2 State: RUNNING ACTIVATED Boot-loader Version: 1.4(3.21).18 Server /cimc/firmware # activate 1 This operation will activate firmware 1 and reboot the BMC. Continue?[y|N]y . . -- BMC reboot -- . . -- Log into CLI as Admin -- Server# scope cimc Server /cimc # scope firmware Server /cimc/firmware # show detail Firmware Image Information: Update Stage: NONE Update Progress: 100 Current FW Version: 1.4(3j) FW Image 1 Version: 1.4(3j) FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 1.3(3a) FW Image 2 State: BACKUP INACTIVATED Boot-loader Version: 1.4(3.21).18
Installing BIOS Firmware
Note | This procedure is not available on some servers. For other BIOS installation methods, see the Cisco UCS C-Series Rack-Mount Server BIOS Upgrade Guide available at the following URL: http://www.cisco.com/en/US/docs/unified_computing/ucs/c/sw/bios/b_Upgrading_BIOS_Firmware.html. |
-
Log in to the Cisco IMC as a user with admin privileges.
-
Activate the Cisco IMC firmware that goes with the BIOS version you want to install, as described in Activating Installed CIMC Firmware.
-
Power off the server.
Note |
|
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | Server# scope cimc |
Enters the Cisco IMC command mode. | ||
Step 2 | Server /cimc # scope firmware |
Enters the firmware command mode. | ||
Step 3 | Server /cimc/firmware # show detail |
Displays the available firmware images and status. | ||
Step 4 | Make sure the firmware version shown in the Current FW Version field matches the BIOS firmware version you are installing. |
If the Cisco IMC firmware version does not match, activate the Cisco IMC firmware before continuing with this procedure or the server will not boot. For details, see Activating Installed CIMC Firmware. | ||
Step 5 | Server /cimc/firmware # top |
Returns to the server root level. | ||
Step 6 | Server# scope bios |
Enters the BIOS command mode. | ||
Step 7 | Server /bios # update protocol IP Address path |
It specifies the following:
| ||
Step 8 | Server /bios # update usb path and firmware file name |
Updates the BIOS firmware from the connected USB. |
This example updates the BIOS firmware:
Server# scope bios Server /bios# show detail BIOS: BIOS Version: CxxMx.2.0.3.0.080720142114 Backup BIOS Version: CxxMx.2.0.2.68.073120141827 Boot Order: (none) Boot Override Priority: FW Update/Recovery Status: None, OK UEFI Secure Boot: disabled Configured Boot Mode: None Actual Boot Mode: Unknown Last Configured Boot Order Source: UNKNOWN Server /bios # update ftp 10.10.10.10 //upgrade_bios_files/Cxx-BIOS-1-4-3j-0.CAP <CR> Press Enter key Firmware update has started. Please check the status using "show detail" For updating the BIOS using the front panel USB: Server /bios # update usb CxxMx-BIOS-3-1-0-289.cap User Options:USB Path[Cxxmx-BIOS-3-1-0-289.cap] <CR> Press Enter key Firmware update has started. Please check the status using "show detail" Server /bios # show detail BIOS: BIOS Version: CxxMx.3.1.0.289.0530172308 Boot Order: (none) FW Update Status: None, OK UEFI Secure Boot: disabled Configured Boot Mode: Legacy Actual Boot Mode: Legacy Last Configured Boot Order Source: BIOS One time boot device: (none) Server /bios #
Activating Installed BIOS Firmware
Note | Activate BIOS Firmware (activate) option is available only for some C-Series servers. For servers that do not have the this option, rebooting the server activates the installed BIOS firmware. |
While the activation is in progress, do not:
Command or Action | Purpose |
---|
This example activates firmware and then verifies the activation:
Server# scope bios Server /bios # show detail BIOS Version: C240M4.2.0.2.67.072320142231 Backup BIOS Version: C240M4.2.0.2.66.071820142034 Boot Order: (none) Boot Override Priority: FW Update/Recovery Status: None, OK UEFI Secure Boot: disabled Configured Boot Mode: None Actual Boot Mode: Legacy Last Configured Boot Order Source: BIOS Server /bios # activate This operation will activate "C240M4.2.0.2.66.071820142034" after next host power off Continue?[y|N] Server# scope bios Server /bios # show detail BIOS Version: C240M4.2.0.2.66.071820142034 Backup BIOS Version: C240M4.2.0.2.67.072320142231 Boot Order: (none) Boot Override Priority: FW Update/Recovery Status: None, OK UEFI Secure Boot: disabled Configured Boot Mode: None Actual Boot Mode: Legacy Last Configured Boot Order Source: BIOS
Installing VIC Firmware
-
Log in as a user with admin privileges.
-
If you are updating VIC firmware from a front panel USB device, make sure that the Smart USB option has been enabled and a valid VIC firmware is available in the USB device.
-
If you start a new update when an update is already in process, both updates will fail.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | server # scope chassis |
Enters the chassis command mode | ||
Step 2 | server /chassis # update-adapter-fw protocol remote server address image file pathactivate|no-activatePCI slot number |
The VIC firmware will be stored at the specified path and file name on a remote server at the specified IPv4 or IPv6 address or a hostname. The remote server could be one of the following types:
| ||
Step 3 | server /chassis # update-adapter-fw usb image file path activate|no-activate PCI slot number | Provide the image file path in the USB device, and the VIC PCI slot number. | ||
Step 4 | server /cimc # show adapter detail | (Optional)
Displays the progress of the firmware update. |
This example shows how to update the VIC firmware:
Server# scope chassis Server /chassis # update-adapter-fw update ftp 10.10.10.10 cruzfw_new.bin activate MLOM Adapter firmware update has started. Please check the status using "show adapter detail". You have chosen to automatically activate the new firmware image. Please restart your host after the update finish. Server /chassis # show adapter detail PCI Slot MLOM: Product Name: UCS VIC 1387 Serial Number: FCH2102J8SU Product ID: UCSC-MLOM-C40Q-03 Adapter Hardware Revision: 3 Current FW Version: 4.1(3.143) VNTAG: Disabled FIP: Enabled LLDP: Enabled Configuration Pending: no Cisco IMC Management Enabled: yes VID: V03 Vendor: Cisco Systems Inc Description: Bootloader Version: 4.1(2d) FW Image 1 Version: 4.1(3.143) FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: N/A FW Image 2 State: N/A FW Update Status: Update in progress FW Update Error: No error FW Update Stage: Erasing (12%) FW Update Overall Progress: 19% Server /chassis #
Installing CMC Firmware from a Remote Server
-
Log in to the Cisco IMC as a user with admin privileges.
-
Obtain the Cisco Host Upgrade Utility ISO file from Cisco.com and extract the firmware installation files as described in Obtaining Firmware from Cisco.
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | server # scope chassis |
Enters chassis command mode. | ||
Step 2 | server /chassis # scope cmc 1|2 |
Enters CMC on the chosen SIOC controller command mode. | ||
Step 3 | server /chassis/cmc # update protocol IP Address path |
| ||
Step 4 | server /chassis/cmc # show detail | (Optional)
Displays the progress of the firmware update. |
This example shows how to update the CMC firmware:
server # scope chassis server /chassis # scope cmc 1 server /chassis/cmc # update http 10.104.236.99 colusa_cmc.2.0.2a.img CMC Firmware update initialized. Please check the status using "show detail" Server /chassis/cmc # show detail Firmware Image Information: Name: CMC1 Update Stage: DOWNLOAD Update Progress: 25 Current FW Version: 2.0(2a) FW Image 1 Version: 2.0(2a) FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 2.0(2a) FW Image 2 State: BACKUP INACTIVATED server /chassis/cmc #
Activate the new firmware.
Activating Installed CMC Firmware
Note | CMCs are configured to have one in an active state while other acts as a backup, when you activate the backup CMC the previously active CMC changes to backup CMC activating the other. |
Install the CMC firmware on the server.
While the activation is in progress, do not:
Command or Action | Purpose | |
---|---|---|
Step 1 | server # scope chassis |
Enters chassis command mode. |
Step 2 | Server# scope cmc1|2 |
Enters the CMC of the chosen SIOC slot command mode. |
Step 3 | Server /cmc # activate |
Activates the selected image for the chosen CMC. |
Step 4 | At the prompt, enter y to activate the selected firmware image. |
The CMC-1 reboots, terminating all CLI and GUI sessions until the reboot completes, but CMC-2 reboot will not affect any active sessions. |
This example activates CMC firmware on the SIOC slot 1:
Server # scope chassis Server /chassis # scope cmc 1 Server /chassis/cmc # activate Warning: The CMC will be rebooted immediately to complete the activation. The network may go down temporarily till CMC boots up again Continue?[y|N]y
Installing SAS Expander Firmware from a Remote Server
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | Server# scope chassis |
Enters the chassis command mode. | ||
Step 2 | Server /chassis # scope sas-expander {1 | 2} |
Enters the SAS expander command mode. | ||
Step 3 | Server /chassis/sas-expander # show detail |
Displays the available firmware images and status. | ||
Step 4 | Server /chassis/sas-expander # update protocol IP_Address path |
It specifies the following:
|
This example updates the SAS expander firmware:
Server# scope chassis Server /chassis # scope sas-expander 1 Server /chassis/sas-expander # show detail Firmware Image Information: ID: 1 Name: SASEXP1 Update Stage: NONE Update Progress: 0 Current FW Version: 65103900 FW Image 1 Version: 65103900 FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 65103900 FW Image 2 State: BACKUP INACTIVATED Server /chassis/sas-expander # update ftp 192.0.20.34 //upgrade_sas_expander_files/sas-expander-2-0-12a.fw <CR> Press Enter key Firmware update has started. Please check the status using "show detail" Server /chassis/sas-expander #
Activating Installed SAS Expander Firmware
Command or Action | Purpose | |
---|---|---|
Step 1 | Server# scope chassis |
Enters the chassis command mode. |
Step 2 | Server /chassis # scope sas-expander {1 | 2} |
Enters the SAS expander command mode. |
Step 3 | Server /chassis/sas-expander # activate |
Activates the currently inactive image. |
Step 4 | At the prompt, enter y to activate the selected firmware image. |
This example activates firmware and then verifies the activation:
Server# scope chassis Server /chassis # scope sas-expander 1 Server /chassis/sas-expander # show detail ID: 1 Name: SASEXP1 Update Stage: NONE Update Progress: 0 Current FW Version: 65103900 FW Image 1 Version: 65103900 FW Image 1 State: RUNNING INACTIVATED FW Image 2 Version: 65103900 FW Image 2 State: BACKUP INACTIVATED Server /chassis/sas-expander # activate This operation will activate "65103900" after next host power off Continue?[y|N] y Server /chassis/sas-expander # show detail ID: 1 Name: SASEXP1 Update Stage: NONE Update Progress: 0 Current FW Version: 65103900 FW Image 1 Version: 65103900 FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 65103900 FW Image 2 State: BACKUP INACTIVATED Server /chassis/sas-expander #
Installing SAS Expander Firmware from a Remote Server
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | Server# scope chassis |
Enters the chassis command mode. | ||
Step 2 | Server /chassis # scope sas-expander {1 | 2} |
Enters the SAS expander command mode. | ||
Step 3 | Server /chassis/sas-expander # show detail |
Displays the available firmware images and status. | ||
Step 4 | Server /chassis/sas-expander # update protocol IP_Address path |
It specifies the following:
|
This example updates the SAS expander firmware:
Server# scope chassis Server /chassis # scope sas-expander 1 Server /chassis/sas-expander # show detail Firmware Image Information: ID: 1 Name: SASEXP1 Update Stage: NONE Update Progress: 0 Current FW Version: 65103900 FW Image 1 Version: 65103900 FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 65103900 FW Image 2 State: BACKUP INACTIVATED Server /chassis/sas-expander # update ftp 192.0.20.34 //upgrade_sas_expander_files/sas-expander-2-0-12a.fw <CR> Press Enter key Firmware update has started. Please check the status using "show detail" Server /chassis/sas-expander #
Activating Installed SAS Expander Firmware
Command or Action | Purpose | |
---|---|---|
Step 1 | Server# scope chassis |
Enters the chassis command mode. |
Step 2 | Server /chassis # scope sas-expander {1 | 2} |
Enters the SAS expander command mode. |
Step 3 | Server /chassis/sas-expander # activate |
Activates the currently inactive image. |
Step 4 | At the prompt, enter y to activate the selected firmware image. |
This example activates firmware and then verifies the activation:
Server# scope chassis Server /chassis # scope sas-expander 1 Server /chassis/sas-expander # show detail ID: 1 Name: SASEXP1 Update Stage: NONE Update Progress: 0 Current FW Version: 65103900 FW Image 1 Version: 65103900 FW Image 1 State: RUNNING INACTIVATED FW Image 2 Version: 65103900 FW Image 2 State: BACKUP INACTIVATED Server /chassis/sas-expander # activate This operation will activate "65103900" after next host power off Continue?[y|N] y Server /chassis/sas-expander # show detail ID: 1 Name: SASEXP1 Update Stage: NONE Update Progress: 0 Current FW Version: 65103900 FW Image 1 Version: 65103900 FW Image 1 State: RUNNING ACTIVATED FW Image 2 Version: 65103900 FW Image 2 State: BACKUP INACTIVATED Server /chassis/sas-expander #