Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-Text | 2.66 MB |
Upgrade goals and available modules
Upgrade a server from the OM Web interface
Upgrade multiple blade servers from the OM Web interface
Upgrade an AE module from the OM Web interface
Upgrade multiple AE modules from the OM Web interface
Upgrade an AE module from OM CLI
Upgrade an HDD Bay from the OM Web interface
Upgrade multiple HDD Bays from the OM Web interface
Upgrade the interconnect module from OM
Upgrade the interconnect module from the OM Web interface
Upgrade the interconnect module from the interconnect module CLI
About the interconnect module software
Download the startup software package or patch package to the master device
Upgrade the startup software package or patch package
Upgrade the startup software package
Manage files from the BootRom menu
Troubleshooting software upgrade failures
Upgrade the AMC firmware for the interconnect module from the AMC CLI
Upgrade the AMC firmware for the interconnect module
View the current AMC firmware version
Configure the AMC management IPv4 address
Upgrade the BX1020B IB switch module
Upgrade the BX1020B IB switch module
Log in to the blade server operating system
Upload the firmware file and the MFT tool
Upgrade the firmware of the IB switch module
Upgrade the BX500S SAS switch module
Upgrade from the OM Web interface
Upgrade the BX1020B IB switch module
Upgrade the fan firmware through OM
Check the system before the upgrade
Upgrade the OM firmware through OM
Upgrade from the OM Web interface
Perform a whole-package upgrade
About the upgrade
Software interfaces displayed in this document are for illustration only and might change without notice.
This document applies to H3C UniServer B16000 blade servers and H3C UIS 9000 servers. The software interfaces, output information, and names have slight differences for the two types of servers. This document takes an H3C UniServer B16000 blade server as an example.
Version compatibility is strongly correlated among the chassis modules. You must strictly perform upgrade operations for the modules as what the compatibility matrixes regulate in the release notes (obtained from the official website).
Upgrade goals and available modules
This document guides you to upgrade chassis modules or components and to verify the operation of basic features and services after the upgrade. Modules and components that are referenced in this document are as follows:
Table 1 Modules and components
|
Modules |
Components available for upgrade |
|
OM module |
N/A |
|
Blade server |
HDM, BIOS, and CPLD |
|
HDD Bay |
AMC_Firmware, AMC_BOOT, and Firmware |
|
AE module |
HDM, BIOS, and CPLD |
|
Interconnect module NOTE: Interconnect modules that are available for upgrade include switch modules (excluding IB switch modules and SAS switch modules) and direct connect modules. |
AMC_Firmware, AMC_BOOT, and Firmware NOTE: Direct connect modules supports only AMC upgrade. |
|
BX1020B IB switch module |
Switch module firmware |
|
BX500S SAS switch module |
Switch module firmware |
|
LCD module |
N/A |
|
Fan module |
N/A |
Upgrade flowchart
No strong correlation exists among the upgrade sequence of chassis modules. As a best practice, use the following upgrade sequence:
Figure 1 Upgrade sequence
|
|
NOTE: The recommended upgrade sequence for AE modules is consistent with the sequence of blade servers. |
Expected upgrade duration
The expected upgrade durations provided in this document are for referenced only.
OM modules
Table 2 Expected upgrade duration for an OM module
|
Task |
Time consumed (min) |
Remarks |
|
Preparation |
10 |
Obtain the firmware version, related documents, tools, and site information. |
|
Check before the upgrade |
2 |
Check the status and diagnosis information and the current version of the OM module. |
|
OM module upgrade |
10 |
N/A. |
|
Verification |
1 |
Verify the status and diagnosis information and the version of the OM module after the upgrade. |
AE modules
Table 3 Expected upgrade duration for an AE module
|
Task |
Time consumed (min) |
Remarks |
|
Preparation |
10 |
Obtain the firmware versions, related documents, tools, and site information. |
|
Check before the upgrade |
2 |
Check the status and diagnosis information and the current firmware versions of the AE module. |
|
HDM upgrade |
5 |
N/A. |
|
BIOS upgrade |
5 |
N/A. |
|
CPLD upgrade |
5 |
N/A. |
|
Verification |
2 |
Verify the status and diagnosis information and the firmware versions of the AE module after the upgrade. |
Blade servers
Table 4 Expected upgrade duration for a blade server
|
Task |
Time consumed (min) |
Remarks |
|
Preparation |
10 |
Obtain the firmware versions, related documents, tools, and site information. |
|
Check before the upgrade |
2 |
Check the status and diagnosis information and the current firmware versions of the blade sever. |
|
HDM upgrade |
5 |
N/A. |
|
BIOS upgrade |
5 |
N/A. |
|
CPLD upgrade |
5 |
N/A. |
|
Verification |
2 |
Verify the status and diagnosis information and the firmware versions of the blade sever after the upgrade. |
HDD Bays
Table 5 Expected upgrade duration for an HDD bay
|
Task |
Time consumed (min) |
Remarks |
|
Preparation |
10 |
Obtain the firmware versions, related documents, tools, and site information. |
|
Check before the upgrade |
2 |
Check the status and diagnosis information and the current firmware versions of the HDD bay. |
|
HDD bay firmware upgrade |
5 |
N/A. |
|
Verification |
2 |
Verify the status and diagnosis information and the firmware versions of the HDD bay after the upgrade. |
Interconnect modules
Table 6 Expected upgrade duration for an interconnect module
|
Task |
Time consumed (min) |
Remarks |
|
Preparation |
10 |
Obtain the firmware versions, related documents, tools, and site information. |
|
Check before the upgrade |
2 |
Check the status and diagnosis information and the current firmware versions of the interconnect module. |
|
AMC upgrade |
5 |
N/A. |
|
BootRom program and startup software package upgrade |
10 |
N/A. |
|
Verification |
2 |
Verify the status and diagnosis information and the firmware versions of the interconnect module after the upgrade. |
LCD modules
Table 7 Expected upgrade duration for an LCD module
|
Task |
Time consumed (min) |
Remarks |
|
Preparation |
10 |
Obtain the firmware versions, related documents, tools, and site information. |
|
HMIStudio installation |
10 |
N/A. |
|
USB driver update |
5 |
N/A. |
|
Configure upgrade |
5 |
N/A. |
|
Firmware upgrade |
5 |
N/A. |
Upgrade blade servers from OM
Upgrade a server from the OM Web interface
Upgrade flowchart
Figure 2 Upgrade flowchart for HDM/BIOS/CPLD firmware of a blade server
Prepare for the upgrade
Prepare tools
Tools required for the upgrade are as follows:
Table 8 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. As a best practice, use a Chrome browser of Chrome 58 or later versions and a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website. |
Set up the environment
As shown in Figure 3, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC IP address and the OM module IP address are in the same subnet.
Figure 3 Setting up the environment
Data planning
Table 9 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· To ensure a successful firmware version verification, make sure the firmware version is consistent with the firmware type.
· As a best practice, to avoid the loss of HDM configuration, back up the HDM configuration file before the upgrade.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· Images must contain signatures for firmware upgrade through OM. During the upgrade, the system verifies the validity of the uploaded firmware. The upgrade can succeed only when the system identifies that the firmware version is provided by the vendor and is not tempered with. If the system cannot verify the signature, the upgrade is terminated.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the upgrade.
· To avoid firmware upgrade failures, only one user can perform upgrade operations on the firmware at a time.
· CPLD firmware upgrade failures might cause the blade server to be unavailable. Use this feature with caution. If any exception occurs, contact Technical Support.
· During the BIOS firmware upgrade, if the blade server is shut down, you must start the server after BIOS firmware image uploading for the server to perform upgrade operations correctly.
After the upgrade
· For the device to operate with a consistent firmware version, upgrade both the primary and backup HDM firmware and make sure the version is the same.
· After HDM firmware upgrade, to view the updated HDM firmware version, you must reset HDM manually or automatically.
· The system can retain user-configured settings after a BIOS upgrade but cannot retain the settings after a BIOS rollback.
· After the BIOS firmware upgrade, the system cannot retain all settings for the connected components. For example, storage controller and network adapter configurations are saved on the modules themselves, and the Overwrite All Config option cannot retain such configurations.
· After the CPLD firmware upgrade, you must remove and then reinstall the corresponding blade server for the new firmware version to take effect.
Check before the upgrade
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. Identify current firmware versions for the blade server.
a. Click Blade Servers.
b. Select the blade server for firmware upgrade.
3. View the blade server status and diagnosis information.
a. Click Blade Servers.
b. Select the blade server for firmware upgrade.
c. Click State Diagnosis.
4. Verify if the server is in a state unavailable for upgrade. For example, the blade server is in abnormal state.
¡ If the server is unavailable for upgrade, resolve the issues and then proceed to the next step.
¡ If the server is available for upgrade, proceed to the next step.
5. Perform one of the following tasks as needed:
Upgrade HDM firmware
1. Select Blade Servers > Target_blade_server > Firmware Update.
2. Upload the most recent HDM firmware image and configure the following parameters:
a. Select HDM as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the upgrade image file and select it.
c. Select Immediately for HDM Configure Update.
d. Do not enable Overwrite All Config.
|
|
NOTE: · HDM Configure Update: Reset HDM automatically or manually after the update. This option is required. · Overwrite All Config: Select whether to restore default settings. If you enable this feature, the system replaces the configured settings with the default settings. In this case, you must use the first-time-login method to log in to HDM after the update. Be cautious to enable this feature if you are not a professional. If you disable this feature, the system retains the user-configured settings after the update. |
3. After the uploading, click Verify Firmware.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, check whether the uploaded HDM firmware version is correct (the suffix is .bin).
4. After the verification, click Update.
Upgrade BIOS firmware
Procedure
1. Select Blade Servers > Target_blade_server > Firmware Update.
2. Upload the most recent BIOS firmware image and configure the following parameters:
a. Select BIOS as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for BIOS Configure Update.
d. Select Retain for Overwrite All Config.
|
|
NOTE: · BIOS Configure Update: Restart the BIOS automatically or manually after the update. This option is required when you update the BIOS with the server up. · Overwrite All Config: Select Retain, Restore, and Force Restore as needed: To retain the user-configured BIOS settings, select Retain. To remove the user-configured BIOS settings and restore default settings, select Restore. To remove the user-configured BIOS settings and restore default settings, select Force Restore. This option enables BMC to rewrite the BIOS flash and can be used when the BIOS is operating incorrectly and cannot be updated in any other ways. |
3. After the uploading, click Verify Firmware.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, check whether the uploaded BIOS firmware image version is correct.
4. After the verification, click Update.
Upgrade CPLD firmware
1. Select Blade Servers > Target_blade_server > Firmware Update.
2. Upload the most recent CPLD firmware image and configure the following parameters:
a. Select CPLD as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
3. After the uploading, click Verify Firmware.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, check whether the uploaded CPLD firmware image version is correct.
4. After the verification, click Update.
Verification
1. Select Blade Servers > Target_blade_server and verify that the firmware has been updated to the target versions.
2. If not, perform the corresponding update operations again and verify the firmware versions.
3. If the issue persists, contact Technical Support.
Upgrade multiple blade servers from the OM Web interface
Upgrade flowchart
Figure 4 Update flowchart for HDM/BIOS/CPLD firmware of blade servers
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 10 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. As a best practice, use a Chrome browser of Chrome 58 or later versions and a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website. |
Set up the environment
As shown in Figure 5, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC IP address and the OM module IP address are in the same subnet.
Figure 5 Setting up the environment
Data planning
Table 11 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· To ensure a successful firmware version verification, make sure the firmware version is consistent with the firmware type.
· As a best practice, to avoid the loss of HDM configuration, back up the HDM configuration file before the upgrade.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· Images must contain signatures for firmware upgrade through OM. During the upgrade, the system verifies the validity of the uploaded firmware. The upgrade can succeed only when the system identifies that the firmware version is provided by the vendor and is not tempered with. If the system cannot verify the signature, the upgrade is terminated.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· CPLD firmware upgrade failures might cause the blade server to be unavailable. Use this feature with caution. If any exception occurs, contact Technical Support.
· During the BIOS firmware upgrade, if the blade server is shut down, you must start the server after BIOS firmware image uploading for the server to perform upgrade operations correctly.
After the upgrade
· For the device to operate with a consistent firmware version, update both the primary and backup HDM firmware and make sure the version is the same.
· After HDM firmware update, to view the updated HDM firmware version, you must reset HDM manually or automatically.
· The system can retain user-configured settings after a BIOS upgrade but cannot retain the settings after a BIOS rollback.
· After the BIOS firmware upgrade, the system cannot retain all settings for the connected components. For example, storage controller and network adapter configurations are saved on the modules themselves, and the Overwrite All Config option cannot retain such configurations.
· After the CPLD firmware update, you must remove and then reinstall the corresponding blade server for the new firmware version to take effect.
Check before the update
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. Access the Blade Servers > Firmware page. Identify current firmware versions for all blade servers.
3. Identify the states for all blade servers.
a. Click Blade Servers.
b. Verify if the server is in a state unavailable for upgrade. For example, the blade server is in abnormal state.
- If the server is unavailable for upgrade, resolve the issues and then proceed to the next step.
- If the server is available for upgrade, proceed to the next step.
4. Perform one of the following tasks as needed:
Upgrade HDM firmware
1. On the Firmware Update page, specify Blade Servers for Select Object for Update and select all blade servers that require HDM update.
2. Click Update. In the dialog box that opens, perform the following tasks:
a. Select HDM as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for HDM Configure Update.
d. Do not enable Overwrite All Config.
e. Click OK.
|
|
NOTE: · HDM Configure Update: Reset HDM automatically or manually after the update. This option is required. · Overwrite All Config: Select whether to restore default settings. If you enable this feature, the system replaces the configured settings with the default settings. In this case, you must use the first-time-login method to log in to HDM after the update. Be cautious to enable this feature if you are not a professional. If you disable this feature, the system retains the user-configured settings after the update. |
After the uploading, the system will verify the HDM firmware version automatically.
¡ If the verification succeeds, the system starts updating firmware automatically.
¡ If the verification fails, check whether the uploaded HDM firmware version is correct.
After a successfully verification, the system starts updating the firmware automatically.
The HDM firmware update succeeds.
Upgrade BIOS firmware
Procedure
1. On the Firmware Update page, specify Blade Servers for Select Object for Update and select all blade servers that require BIOS update.
2. Click Update. In the dialog box that opens, perform the following tasks:
a. Select BIOS as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for BIOS Configure Update.
d. Select Retain for Overwrite All Config.
e. Click OK.
|
|
NOTE: · BIOS Configure Update: Restart the BIOS automatically or manually after the update. This option is required when you update the BIOS with the server up. · Overwrite All Config: Select Retain, Restore, and Force Restore as needed. To retain the user-configured BIOS settings, select Retain. To remove the user-configured BIOS settings and restore default settings, select Restore. To remove the user-configured BIOS settings and restore default settings, select Force Restore. This option enables BMC to rewrite the BIOS flash and can be used when the BIOS is operating incorrectly and cannot be updated in any other ways. |
After the uploading, the system will verify the BIOS firmware version automatically.
¡ If the verification succeeds, the system starts updating firmware automatically.
¡ If the verification fails, check whether the uploaded BIOS firmware version is correct.
After a successfully verification, the system starts updating the firmware automatically.
The BIOS firmware update succeeds.
Upgrade CPLD firmware
1. On the Firmware Update page, specify Blade Servers for Select Object for Update and select all blade servers that require CPLD update.
2. Click Update. In the dialog box that opens, perform the following tasks:
a. Select CPLD as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Click OK.
After the uploading, the system will verify the CPLD firmware version automatically.
¡ If the verification succeeds, the system starts updating firmware automatically.
¡ If the verification fails, check whether the uploaded CPLD firmware version is correct.
After a successfully verification, the system starts updating the firmware automatically.
The BIOS firmware update succeeds.
Verification
1. Select Enclosure Manage > Firmware and verify that the firmware has been updated to target versions.
2. If not, perform the corresponding update operations again and verify the firmware versions.
3. If the issue persists, contact Technical Support.
Upgrade a server from OM CLI
Upgrade flowchart
Figure 6 Upgrade flowchart for HDM/BIOS/CPLD firmware of a blade server
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 12 Required tools
|
Tool |
Remarks |
|
PC and software for remote login |
Used to log in to the OM CLI remotely. |
|
FTP tool |
Tool for remote file transmission. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website. |
Data planning
Table 13 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
|
Blade server slot |
This document takes slot 1 as an example. For more information, see the slot numbers on the chassis front. |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· To ensure a successful firmware version verification, make sure the firmware version is consistent with the firmware type.
· As a best practice, to avoid the loss of HDM configuration, back up the HDM configuration file before the update.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· CPLD firmware upgrade failures might cause the blade server to be unavailable. Use this feature with caution. If any exception occurs, contact Technical Support.
After the upgrade
· For the device to operate with a consistent firmware version, update both the primary and backup HDM firmware and make sure the version is the same.
· After HDM firmware update, to view the updated HDM firmware version, you must reset HDM manually or automatically.
· The system can retain user-configured settings after a BIOS update and cannot retain the settings after a BIOS rollback.
· After the BIOS firmware upgrade, the system cannot retain all settings for the connected components. For example, storage controller and network adapter configurations are saved on the modules themselves, and the Overwrite All Config option cannot retain such configurations.
· After the CPLD firmware upgrade, you must remove and then reinstall the corresponding blade server for the new firmware version to take effect.
Upgrade HDM firmware
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 14 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key for the OM module is enabled. |
|
After login, OM CLI displays as follows:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Enter the display blade detail blade blade-id command to identify current HDM firmware version for the blade server.
<OM>display blade detail blade 1
Product name : B5700 G3
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
Blade name : Blade1
3. Enter the display blade status blade blade-id command and the display blade diagnosis blade blade-id command to view the state and diagnosis information for the server, respectively. Verify whether states that do not support the update exist, such as the Abnormal state in the Blade status field. If states unavailable for the update exist, remove the alarms before proceeding to the next step.
<OM>display blade status blade 1
Blade status : Normal
PSU : On
Power(W) : 80
<OM>display blade diagnosis blade 1
Connect status : Normal
Board type status : Matched
System health status : Normal
Device identification data : Normal
Temperature health status : Normal
Voltage health status : Normal
Current health status : Normal
CPU health status : Normal
Memory health status : Normal
Disk health status : Normal
Network card health status : Ok
4. Enter the access-method ftp command to enable FTP for the OM module.
<OM>access-method ftp
5. Use the FTP tool on the PC to upload the most recent HDM firmware version to the flash root directory of the OM module.
6. Enter the update-blade firmware firmware configuration { default | reserve } file file blade blade-id command to start updating HDM firmware. Configure the parameters as follows:
¡ firmware: Specifies the firmware type for the update. Options include:
- 1—HDM.
- 2—BIOS.
- 3—CPLD.
¡ default: Configures the system to use the original settings after the update when the firmware type is HDM or BIOS. This parameter does not take effect when the firmware type is CPLD.
¡ reserve: Overwrites the system settings after the update when the firmware type is HDM or BIOS. Be cautious to use this feature if you are not a professional. This parameter does not take effect when the firmware type is CPLD.
¡ file: Specifies the firmware name.
<OM>update-blade firmware 1 configuration default file HDM-1.11.20_signed.b
in blade 1
Start to upload .................................Upload success.
Confirm whether to upgrade [Y/N] :y
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N] :y
Start to upgrade ....................
Upgrade success
Start to reset..........
Reset blade success
7. After the update, enter the display blade detail blade blade-id command to view the HDM firmware version and verify that the firmware has been updated to the target version.
<OM>display blade detail blade 1
Product name : B5700 G3
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.20 HDM V100R001B01D020
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
Blade name : Blade1
Upgrade BIOS firmware
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 15 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key for the OM module is enabled. |
|
After login, OM CLI displays as follows:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Enter the display blade detail blade blade-id command to identify current BIOS firmware version for the blade server.
<OM>display blade detail blade 1
Product name : B5700 G3
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
Blade name : Blade1
3. Enter the display blade status blade blade-id command and the display blade diagnosis blade blade-id command to view the state and diagnosis information for the server, respectively. Verify whether states that do not support the update exist, such as the Abnormal state in the Blade status field. If states unavailable for the update exist, remove the alarms before proceeding to the next step.
<OM>display blade status blade 1
Blade status : Normal
PSU : On
Power(W) : 80
<OM>display blade diagnosis blade 1
Connect status : Normal
Board type status : Matched
System health status : Normal
Device identification data : Normal
Temperature health status : Normal
Voltage health status : Normal
Current health status : Normal
CPU health status : Normal
Memory health status : Normal
Disk health status : Normal
Network card health status : Ok
4. Enter the access-method ftp command to enable FTP for the OM module.
<OM>access-method ftp
5. Use the FTP tool on the PC to upload the most recent BIOS firmware version to the flash root directory of the OM module.
6. Enter the update-blade firmware firmware configuration { default | reserve } file file blade blade-id command to start updating the BIOS firmware. Configure the parameters as follows:
¡ firmware: Specifies the firmware type for the update. Options include:
- 1—HDM.
- 2—BIOS.
- 3—CPLD.
¡ default: Configures the system to use the original settings after the update when the firmware type is HDM or BIOS. This parameter does not take effect when the firmware type is CPLD.
¡ reserve: Overwrites the system settings after the update when the firmware type is HDM or BIOS. Be cautious to use this feature if you are not a professional. This parameter does not take effect when the firmware type is CPLD.
¡ file: Specifies the firmware name.
<OM>update-blade firmware 2 configuration default file 2.00.11.BIOS_D011_signed.b
in blade 1
Start to upload .................................Upload success.
Confirm whether to upgrade [Y/N] : y
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N] : y
Start to upgrade ..................
Upgrade success
7. After the update, enter the display blade detail blade blade-id command to view the BIOS firmware version and verify that the firmware has been updated to the target version.
<OM>display blade detail blade 1
Product name : B5700 G3
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.20 HDM V100R001B01D020
BIOS version : 2.00.11 V100R001B01D011
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
Blade name : Blade1
Upgrade CPLD firmware
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 16 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key for the OM module is enabled. |
|
After login, OM CLI displays as follows:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Enter the display blade detail blade blade-id command to identify current CPLD firmware version for the blade server.
<OM>display blade detail blade 1
Product name : B5700 G3
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
Blade name : Blade1
3. Enter the display blade status blade blade-id command and the display blade diagnosis blade blade-id command to view the state and diagnosis information for the server, respectively. Verify whether states that do not support the update exist, such as the Abnormal state in the Blade status field. If states unavailable for the update exist, remove the alarms before proceeding to the next step.
<OM>display blade status blade 1
Blade status : Normal
PSU : On
Power(W) : 80
<OM>display blade diagnosis blade 1
Connect status : Normal
Board type status : Matched
System health status : Normal
Device identification data : Normal
Temperature health status : Normal
Voltage health status : Normal
Current health status : Normal
CPU health status : Normal
Memory health status : Normal
Disk health status : Normal
Network card health status : Ok
4. Enter the access-method ftp command to enable FTP for the OM module.
<OM>access-method ftp
5. Use the FTP tool on the PC to upload the most recent CPLD firmware version to the flash root directory of the OM module.
6. Enter the update-blade firmware firmware configuration { default | reserve } file file blade blade-id command to start updating the CPLD firmware. Configure the parameters as follows:
¡ firmware: Specifies the firmware type for the update. Options include:
- 1—HDM.
- 2—BIOS.
- 3—CPLD.
¡ default: Configures the system to use the original settings after the update when the firmware type is HDM or BIOS. This parameter does not take effect when the firmware type is CPLD.
¡ reserve: Overwrites the system settings after the update when the firmware type is HDM or BIOS. Be cautious to use this feature if you are not a professional. This parameter does not take effect when the firmware type is CPLD.
¡ file: Specifies the firmware name.
<OM>update-blade firmware 3 configuration default file CPLD_D009_signed.b
in blade 1
Start to upload .................................Upload success.
Confirm whether to upgrade [Y/N] : y
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N] : y
CPLD is upgrading,this operation will take some time
7. After the update, enter the display blade detail blade blade-id command to view the CPLD firmware version and verify that the firmware has been updated to the target version.
<OM>display blade detail blade 1
Product name : B5700 G3
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00009
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
Blade name : Blade1
Upgrade AE modules from OM
Upgrade an AE module from the OM Web interface
Upgrade flowchart
Figure 7 Upgrade flowchart for HDM/BIOS/CPLD firmware of an AE module
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 17 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. As a best practice, use a Chrome browser of Chrome 58 or later versions and a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website. |
Set up the environment
As shown in Figure 8, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC IP address and the OM module IP address are in the same subnet.
Figure 8 Setting up the environment
Data planning
Table 18 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· To ensure a successful firmware version verification, make sure the firmware version is consistent with the firmware type.
· As a best practice, to avoid the loss of HDM configuration, back up the HDM configuration file before the update.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· Images must contain signatures for firmware upgrade through OM. During the upgrade, the system verifies the validity of the uploaded firmware. The upgrade can succeed only when the system identifies that the firmware version is provided by the vendor and is not tempered with. If the system cannot verify the signature, the upgrade is terminated.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· CPLD firmware upgrade failures might cause the blade server to be unavailable. Use this feature with caution. If any exception occurs, contact Technical Support.
· During the BIOS firmware update, if the AE module is shut down, you must start the module after BIOS firmware image uploading for the module to perform update operations correctly.
After the upgrade
· For the device to operate with a consistent firmware version, update both the primary and backup HDM firmware and make sure the version is the same.
· After HDM firmware update, to view the updated HDM firmware version, you must reset HDM manually or automatically.
· After the CPLD firmware upgrade, you must remove and then reinstall the corresponding blade server for the new firmware version to take effect.
Check before the update
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. Identify current firmware versions for the AE module.
a. Click AE Modules.
b. Select the AE module for firmware update.
3. View the AE module status and diagnosis information.
a. Click AE Modules.
b. Select the AE module for firmware update.
c. Click State Diagnosis.
4. Verify if the AE module is in a state unavailable for upgrade. For example, the AE module is in abnormal state.
¡ If the AE module is unavailable for upgrade, resolve the issues and then proceed to the next step.
¡ If the AE module is available for upgrade, proceed to the next step.
5. Perform one of the following tasks as needed:
Upgrade HDM firmware
1. Select AE Modules > Target_AE_module > Firmware Update.
2. Upload the most recent HDM firmware image and configure the following parameters:
a. Select HDM as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for HDM Configure Update.
d. Do not enable Overwrite All Config.
|
|
NOTE: · HDM Configure Update: Reset HDM automatically or manually after the update. This option is required. · Overwrite All Config: Select whether to restore default settings. If you enable this feature, the system replaces the configured settings with the default settings. In this case, you must use the first-time-login method to log in to HDM after the update. Be cautious to enable this feature if you are not a professional. If you disable this feature, the system retains the user-configured settings after the update. |
3. After the uploading, click Verify Firmware.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, check whether the HDM firmware version is correct (the suffix is .bin).
4. After the verification, click Update.
Upgrade BIOS firmware
Procedure
1. Select AE Modules > Target_AE_module > Firmware Update.
2. Upload the most recent BIOS firmware image and configure the following parameters:
a. Select BIOS as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for BIOS Configure Update.
d. Select Retain for Overwrite All Config.
|
|
NOTE: · BIOS Configure Update: Restart the BIOS automatically or manually after the update. This option is required when you update the BIOS with the AE module up. · Overwrite All Config: Select Retain, Restore, and Force Restore as needed. To retain the user-configured BIOS settings, select Retain. To remove the user-configured BIOS settings and restore default settings, select Restore. To remove the user-configured BIOS settings and restore default settings, select Forcedly restore. This option enables BMC to rewrite the BIOS flash and can be used when the BIOS is operating incorrectly and cannot be updated in any other ways. |
3. After the uploading, click Verify Firmware.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, check whether the BIOS firmware image version is correct.
4. After the verification, click Update.
Upgrade CPLD firmware
1. Select AE Modules > Target_AE_module > Firmware Update.
2. Upload the most recent CPLD firmware image and configure the following parameters:
a. Select CPLD as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
3. After the uploading, click Verify Firmware.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, check whether the CPLD firmware image version is correct.
4. After the verification, click Update.
Verification
1. Select AE Modules > Target_AE_module and verify that the firmware has been updated to the target versions.
2. If not, perform the corresponding update operations again and verify the firmware versions.
3. If the issue persists, contact Technical Support.
Upgrade multiple AE modules from the OM Web interface
Upgrade flowchart
Figure 9 Upgrade flowchart for HDM/BIOS/CPLD firmware of AE modules
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 19 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. As a best practice, use a Chrome browser of Chrome 58 or later versions and a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website. |
Set up the environment
As shown in Figure 10, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC IP address and the OM module IP address are in the same subnet.
Figure 10 Setting up the environment
Data planning
Table 20 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· To ensure a successful firmware version verification, make sure the firmware version is consistent with the firmware type.
· As a best practice, to avoid the loss of HDM configuration, back up the HDM configuration file before the update.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· Images must contain signatures for firmware upgrade through OM. During the upgrade, the system verifies the validity of the uploaded firmware. The upgrade can succeed only when the system identifies that the firmware version is provided by the vendor and is not tempered with. If the system cannot verify the signature, the upgrade is terminated.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· CPLD firmware upgrade failures might cause the blade server to be unavailable. Use this feature with caution. If any exception occurs, contact Technical Support.
· During the BIOS firmware update, if the AE module is shut down, you must start the module after BIOS firmware image uploading for the module to perform update operations correctly.
After the upgrade
· For the device to operate with a consistent firmware version, update both the primary and backup HDM firmware and make sure the version is the same.
· After HDM firmware update, to view the updated HDM firmware version, you must reset HDM manually or automatically.
· After the CPLD firmware upgrade, you must remove and then reinstall the corresponding blade server for the new firmware version to take effect.
Check before the update
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. Access the Blade Servers > Firmware page. Identify current firmware versions for all AE modules.
3. Identify the states for all AE modules.
a. Click AE Modules.
b. Verify if the AE module is in a state unavailable for upgrade. For example, the AE module is in abnormal state.
- If the AE module is unavailable for upgrade, resolve the issues and then proceed to the next step.
- If the AE module is available for upgrade, proceed to the next step.
4. Perform one of the following tasks as needed:
Upgrade HDM firmware
1. On the Firmware Update page, specify AE Modules for Select Object for Update and select all AE modules that require HDM update.
2. Click Update Firmware. In the dialog box that opens, perform the following tasks:
a. Select HDM as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for HDM Configure Update.
d. Do not enable Overwrite All Config.
e. Click OK.
|
|
NOTE: · HDM Configure Update: Reset HDM automatically or manually after the update. This option is required. · Overwrite All Config: Select whether to restore default settings. If you enable this feature, the system replaces the configured settings with the default settings. In this case, you must use the first-time-login method to log in to HDM after the update. Be cautious to enable this feature if you are not a professional. If you disable this feature, the system retains the user-configured settings after the update. |
After the uploading, the system will verify the HDM firmware version automatically.
¡ If the verification succeeds, the system starts updating firmware automatically.
¡ If the verification fails, check whether the uploaded HDM firmware version is correct.
After a successfully verification, the system starts updating the firmware automatically.
The HDM firmware update succeeds.
Upgrade BIOS firmware
1. On the Firmware Update page, specify AE Modules for Select Object for Update and select all AE modules that require BIOS update.
Figure 11 Firmware update page
2. Click Update. In the dialog box that opens, perform the following tasks:
a. Select BIOS as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Select Immediately for BIOS Configure Update.
d. Select Retain for Overwrite All Config.
e. Click OK.
|
|
NOTE: · BIOS Configure Update: Restart the BIOS automatically or manually after the update. This option is required when you update the BIOS with the AE module up. · Overwrite All Config: Select Retain, Restore, and Force Restore as needed. To retain the user-configured BIOS settings, select Retain. To remove the user-configured BIOS settings and restore default settings, select Restore. To remove the user-configured BIOS settings and restore default settings, select Force Restore. This option enables BMC to rewrite the BIOS flash and can be used when the BIOS is operating incorrectly and cannot be updated in any other ways. |
After the uploading, the system will verify the BIOS firmware version automatically.
¡ If the verification succeeds, the system starts updating firmware automatically.
¡ If the verification fails, check whether the uploaded BIOS firmware version is correct.
After a successfully verification, the system starts updating the firmware automatically.
The BIOS firmware update succeeds.
Upgrade CPLD firmware
1. On the Firmware Update page, specify AE Modules for Select Object for Update and select all AE modules that require CPLD update.
2. Click Update. In the dialog box that opens, perform the following tasks:
a. Select CPLD as the firmware type.
b. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
c. Click OK.
After the uploading, the system will verify the CPLD firmware version automatically.
¡ If the verification succeeds, the system starts updating firmware automatically.
¡ If the verification fails, check whether the uploaded CPLD firmware version is correct.
After a successfully verification, the system starts updating the firmware automatically.
The BIOS firmware update succeeds.
Verification
1. Select Enclosure Manage > Firmware and verify that the firmware has been updated to target versions.
2. If not, perform the corresponding update operations again and verify the firmware versions.
3. If the issue persists, contact Technical Support.
Upgrade an AE module from OM CLI
Upgrade flowchart
Figure 12 Upgrade flowchart for HDM/BIOS/CPLD firmware of an AE module
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 21 Required tools
|
Tool |
Remarks |
|
PC and software for remote login |
Used to log in to the OM CLI remotely. |
|
FTP tool |
Tool for remote file transmission. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website. |
Data planning
Table 22 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
|
AE module slot |
This document takes slot E 1 as an example. For more information, see the slot numbers on the chassis front. |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· To ensure a successful firmware version verification, make sure the firmware version is consistent with the firmware type.
· As a best practice, to avoid the loss of HDM configuration, back up the HDM configuration file before the update.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· CPLD firmware upgrade failures might cause the blade server to be unavailable. Use this feature with caution. If any exception occurs, contact Technical Support.
After the upgrade
· For the device to operate with a consistent firmware version, update both the primary and backup HDM firmware and make sure the version is the same.
· After HDM firmware update, to view the updated HDM firmware version, you must reset HDM manually or automatically.
· The system can retain user-configured settings after a BIOS update and cannot retain the settings after a BIOS rollback.
· After the CPLD firmware upgrade, you must remove and then reinstall the corresponding blade server for the new firmware version to take effect.
Upgrade HDM firmware
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 23 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key is enabled for the OM module. |
|
After login, OM CLI displays as follows:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Enter the display app detail app app-id command to identify current HDM firmware version for the AE module.
<OM>display app detail app 1
Product name : AE101
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
app name : app1
3. Enter the display app status app app-id command and the display app diagnosis app app-id command to view the state and diagnosis information for the server, respectively. Verify whether states that do not support the update exist, such as the Abnormal state in the App status field. If states unavailable for the update exist, remove the alarms before proceeding to the next step.
<OM>display app status app 1
App status : Normal
PSU : On
Power(W) : 80
<OM>display app diagnosis app 1
Connect status : Normal
Board type status : Matched
System health status : Normal
Device identification data : Normal
Temperature health status : Normal
Voltage health status : Normal
Current health status : Normal
CPU health status : Normal
Memory health status : Normal
Disk health status : Normal
Network card health status : Ok
4. Enter the access-method ftp command to enable FTP for the OM module.
<OM>access-method ftp
5. Use the FTP tool on the PC to upload the most recent HDM firmware version to the flash root directory of the OM module.
6. Enter the update-app firmware firmware configuration { default | reserve } file file app app-id command to start updating HDM firmware. Configure the parameters as follows:
¡ firmware: Specifies the firmware type for the update. Options include:
- 1—HDM.
- 2—BIOS.
- 3—CPLD.
¡ default: Configures the system to use the original settings after the update when the firmware type is HDM or BIOS. This parameter does not take effect when the firmware type is CPLD.
¡ reserve: Overwrites the system settings after the update when the firmware type is HDM or BIOS. Be cautious to use this feature if you are not a professional. This parameter does not take effect when the firmware type is CPLD.
¡ file: Specifies the firmware name.
<OM>update-app firmware 1 configuration default file HDM-1.11.20_signed.b
in app 1
Start to upload .................................Upload success.
Confirm whether to upgrade [Y/N] :y
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N] :y
Start to upgrade ....................
Upgrade success
Start to reset..........
Reset app success
7. After the update, enter the display app detail app app-id command to view the HDM firmware version and verify that the firmware has been updated to the target version.
<OM>display app detail app 1
Product name : AE101
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.20 HDM V100R001B01D020
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
App name : app1
Upgrade BIOS firmware
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 24 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key for the OM module is enabled. |
|
After login, OM CLI displays as follows:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Enter the display app detail app app-id command to identify current BIOS firmware version for the AE module.
<OM>display app detail app 1
Product name : AE101
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
App name : app1
3. Enter the display app status app app-id command and the display app diagnosis app app-id command to view the state and diagnosis information for the server, respectively. Verify whether states that do not support the update exist, such as the Abnormal state in the App status field. If states unavailable for the update exist, remove the alarms before proceeding to the next step.
<OM>display app status app 1
App status : Normal
PSU : On
Power(W) : 80
<OM>display app diagnosis app 1
Connect status : Normal
Board type status : Matched
System health status : Normal
Device identification data : Normal
Temperature health status : Normal
Voltage health status : Normal
Current health status : Normal
CPU health status : Normal
Memory health status : Normal
Disk health status : Normal
Network card health status : Ok
4. Enter the access-method ftp command to enable FTP for the OM module.
<OM>access-method ftp
5. Use the FTP tool on the PC to upload the most recent BIOS firmware version to the flash root directory of the OM module.
6. Enter the update-app firmware firmware configuration { default | reserve } file file app app-id command to start updating the BIOS firmware. Configure the parameters as follows:
¡ firmware: Specifies the firmware type for the update. Options include:
- 1—HDM.
- 2—BIOS.
- 3—CPLD.
¡ default: Configures the system to use the original settings after the update when the firmware type is HDM or BIOS. This parameter does not take effect when the firmware type is CPLD.
¡ reserve: Overwrites the system settings after the update when the firmware type is HDM or BIOS. Be cautious to use this feature if you are not a professional. This parameter does not take effect when the firmware type is CPLD.
¡ file: Specifies the firmware name.
<OM>update-app firmware 2 configuration default file 2.00.11.BIOS_D011_signed.b
in app 1
Start to upload .................................Upload success.
Confirm whether to upgrade [Y/N] : y
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N] : y
Start to upgrade ..................
Upgrade success
7. After the update, enter the display app detail app app-id command to view the BIOS firmware version and verify that the firmware has been updated to the target version.
<OM>display app detail app 1
Product name : AE101
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.20 HDM V100R001B01D020
BIOS version : 2.00.11 V100R001B01D011
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
App name : app1
Upgrade CPLD firmware
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 25 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key for the OM module is enabled. |
|
After login, OM CLI displays as follows:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Enter the display app detail app app-id command to identify current CPLD firmware version for the AE module.
<OM>display app detail app 1
Product name : AE101
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00008
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
App name : App1
3. Enter the display app status app app-id command and the display app diagnosis app app-id command to view the state and diagnosis information for the server, respectively. Verify whether states that do not support the update exist, such as the Abnormal state in the App status field. If states unavailable for the update exist, remove the alarms before proceeding to the next step.
<OM>display app status app 1
App status : Normal
PSU : On
Power(W) : 80
<OM>display app diagnosis app 1
Connect status : Normal
Board type status : Matched
System health status : Normal
Device identification data : Normal
Temperature health status : Normal
Voltage health status : Normal
Current health status : Normal
CPU health status : Normal
Memory health status : Normal
Disk health status : Normal
Network card health status : Ok
4. Enter the access-method ftp command to enable FTP for the OM module.
<OM>access-method ftp
5. Use the FTP tool on the PC to upload the most recent CPLD firmware version to the flash root directory of the OM module.
6. Enter the update-app firmware firmware configuration { default | reserve } file file app app-id command to start updating the CPLD firmware. Configure the parameters as follows:
¡ firmware: Specifies the firmware type for the update. Options include:
- 1—HDM.
- 2—BIOS.
- 3—CPLD.
¡ default: Configures the system to use the original settings after the update when the firmware type is HDM or BIOS. This parameter does not take effect when the firmware type is CPLD.
¡ reserve: Overwrites the system settings after the update when the firmware type is HDM or BIOS. Be cautious to use this feature if you are not a professional. This parameter does not take effect when the firmware type is CPLD.
¡ file: Specifies the firmware name.
<OM>update-app firmware 3 configuration default file CPLD_D009_signed.b
in app 1
Start to upload .................................Upload success.
Confirm whether to upgrade [Y/N] : y
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N] : y
CPLD is upgrading,this operation will take some time
7. After the update, enter the display app detail app app-id command to view the CPLD firmware version and verify that the firmware has been updated to the target version.
<OM>display blade detail app 1
Product name : AE101
Serial number : 210235A1Q70000000001
Manufacturer : ***
Main board part number : 0231A111
CPLD version : V00009
HDM version : 1.11.19 HDM V100R001B01D019
BIOS version : 2.00.10 V100R001B01D010
UUID : e02ebb76-debf-d311-b703-1ddf5b5a5301
App name : app1
Upgrade HDD Bays from OM
Upgrade an HDD Bay from the OM Web interface
Upgrade flowchart
Figure 13 Upgrade flowchart for HDD Bay firmware
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 26 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. As a best practice, use a Chrome browser of Chrome 58 or later versions and a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website to obtain a firmware image of the latest version for the HDD Bay. |
Set up the environment
As shown in Figure 14, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC IP address and the OM module IP address are in the same subnet.
Figure 14 Setting up the environment
Data planning
Table 27 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· Make sure the SDS switch module is present.
· To update both SAS Expanders, make sure the two SDS Expanders are present simultaneously in active/standby mode.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and operating systems, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· Some components can restrict the update of each other and they cannot be updated simultaneously.
¡ You cannot update any two of the AMC system firmware, AMC BOOT-LOADER firmware, and system firmware of a single HDD Bay simultaneously.
¡ The HDD Bay system firmware update is dependent on the SAS switch module. Therefore, the HDD Bay system firmware and the SAS switch module cannot be updated simultaneously.
¡ You cannot update multiple HDD Bay system firmware at the same time and you can only update the firmware one by one.
Check before the update
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. Identify current firmware versions for the HDD Bay.
a. Click Blade Servers.
b. Select the HDD Bay for firmware update.
3. View the HDD Bay status and diagnosis information.
a. Click Blade Servers.
b. Select the HDD Bay for firmware update.
c. Click State Diagnosis.
4. Verify if the HDD Bay is in a state unavailable for upgrade. For example, the HDD Bay is in abnormal state.
¡ If the HDD Bay is unavailable for upgrade, resolve the issues and then proceed to the next step.
¡ If the HDD Bay is available for upgrade, proceed to the next step.
Updating HDD Bay firmware
1. Select Blade Servers > Target_HDD Bay > Firmware Update
2. In Firmware Type, specify a firmware type for update. Options include:
¡ AMC_Firmware(*.mfi)—Updates the AMC system firmware for the HDD Bay.
¡ AMC_BOOT(*.img)—Updates the AMC BOOT-LOADER firmware for the HDD Bay.
3. Select From PC and click Browse. In dialog box that opens, browse to the update image file and select it.
4. Click Update
The HDD Bay firmware update succeeds.
Upgrade multiple HDD Bays from the OM Web interface
Upgrade flowchart
Figure 15 Upgrade flowchart for HDD Bay firmware
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 28 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. As a best practice, use a Chrome browser of Chrome 58 or later versions and a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, log in to the official website to obtain a firmware image of the latest version for the HDD Bay. |
Set up the environment
As shown in Figure 16, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC IP address and the OM module IP address are in the same subnet.
Figure 16 Setting up the environment
Data planning
Table 29 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
Restriction and guidelines
Before the upgrade
· Obtain the most recent firmware version files for the blade server from the official website and make sure the blade server is in a normal state.
· Make sure the SDS switch module is present.
· To update both SAS Expanders, make sure the two SDS Expanders are present simultaneously in active/standby mode.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on the firmware at a time.
· Some components can restrict the update of each other and they cannot be updated simultaneously.
¡ You cannot update any two of the AMC system firmware, AMC BOOT-LOADER firmware, and system firmware of a single HDD Bay simultaneously.
¡ The HDD Bay system firmware update is dependent on the SAS switch module. Therefore, the HDD Bay system firmware and the SAS switch module cannot be updated simultaneously.
¡ You cannot update multiple HDD Bay system firmware at the same time and you can only update the firmware one by one.
Check before the update
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. Select Blade Servers > Firmware. Identify current firmware versions for all HDD Bays.
3. Click Blade Servers. Verify if the HDD Bay is in a state unavailable for upgrade. For example, the HDD Bay is in abnormal state.
¡ If the HDD Bay is unavailable for upgrade, resolve the issues and then proceed to the next step.
¡ If the HDD Bay is available for upgrade, proceed to the next step.
Upgrade HDD Bay firmware
1. Click Firmware Update. In Select Object for Update, select HDD Bay and select all HDD Bays for update.
2. Click Browse. In dialog box that opens, browse to the update image file and select it.
3. Click Update.
The firmware update for HDD Bays succeeds.
Upgrade the interconnect module from OM
Upgrade the interconnect module from the OM Web interface
Upgrade flowchart
Figure 17 Upgrade flowchart for the firmware of an interconnect module
Prepare for the upgrade
Prepare tools
Tools required for the update are as follows:
Table 30 Required tools
|
Tool |
Remarks |
|
PC |
Used to log in to the OM Web interface. |
|
TFTP server |
Used to transfer files remotely for interconnect module backup. |
|
Interconnect module firmware version file |
To obtain the most recent firmware version file (an .ipe file), log in to the official website. Download the file to the PC. |
Set up the environment
As shown in Figure 18, connect an Ethernet interface of the PC to the respective MGMT ports of the active and standby OM modules through the LAN. Make sure that the PC and the OM module management addresses can reach each other in Layer 3.
Figure 18 Setting up the environment
Data planning
Some statistics in this section are for illustration only.
Table 31 Data planning
|
Parameter |
Remarks |
|
Management IP address of the OM module |
IP address (default): 192.168.100.100/24 |
|
Username and password for OM Web interface login |
· Username (default): admin · Password (default): Password@_ |
|
Interconnect module slot |
This section takes slot 1 as an example. For more information, see the slot numbers on the chassis rear. |
|
Management IP address of the TFTP server |
Make sure the respective management IP addresses of the TFTP sever and the interconnect module can reach each other in Layer 3. This section takes IP address 192.168.1.1 as an example. |
Restriction and guidelines
Before the upgrade
· Back up the configuration file for the interconnect module in advance.
· To avoid update failures or the loss of the configuration, update the configuration (excluding the SAS switch module) first.
· To upload the firmware version from the OM module to the interconnect module, make sure the respective IPv6 addresses of the OM module and the interconnect module can reach each other.
· Obtain the latest firmware image for the interconnect module from the official website and make sure the interconnect module is in a correct status.
· Before uploading a firmware image, make sure the available space is more than 20% of the total space in the flash root directory of the active OM module. You can access the Enclosure Manage > File Management page to verify and release the space.
· During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
· The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
· When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
· To avoid failures for OM features and the operating system, do not perform power actions or disconnect the power cords during the update.
· To avoid firmware update failures, only one user can perform update operations on an interconnect module at a time.
· During the update, you cannot edit the management IP address of the interconnect module, configure a virtual power supply, or configure the UID LED.
· Some components can restrict the update of each other and they cannot be updated simultaneously.
¡ You cannot update any two of the AMC system firmware, AMC BOOT-LOADER firmware, and system firmware of a single interconnect module simultaneously.
¡ The HDD Bay system firmware update is dependent on the SAS switch module. Therefore, the HDD Bay system firmware and the SAS switch module cannot be updated simultaneously.
After the upgrade
· The interconnect module restarts automatically after the upgrade.
Procedure
Check before the update
1. Open the browser and enter the login address of the OM Web interface in https://OM_ip_address format. Enter the administrator username and password and click Login.
2. View the status and diagnosis information for the interconnect module.
a. Click Interconnect Module Manage.
b. Select the interconnect module for update.
c. Click State Diagnosis.
3. Verify if the interconnect module is in a state unavailable for upgrade. For example, the interconnect module is in abnormal state.
¡ If the interconnect module is unavailable for upgrade, resolve the issues and then proceed to the next step.
¡ If the interconnect module is available for upgrade, proceed to the next step.
4. Select Interconnect Module Manage > Target_interconnect_module > Firmware Update and view the current firmware version of the interconnect module.
5. For OM versions that are earlier than 1.01.xx, make sure the respective management IP addresses of the OM module and the interconnect module can reach each other before the update. If not, edit the network settings first.
Back up the interconnect module configuration file
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 32 displays the login parameters.
|
Parameters |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, SSH secret key is enabled for the OM module. |
|
After login, the OM CLI displays the following information:
******************************************************************************
* Copyright (c) 2004-2019 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Execute the sol connect command to access the CLI for the interconnect module in slot 1.
<OM>sol connect io 1
Begin to edit commands.
<OM>%Jul 29 13:42:35:975 2013 *** SHELL/5/SHELL_LOGIN: Console logged in from c
on1.
<Sysname>
3. Execute the save command in any view to save the current interconnect module configuration.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
<Sysname>
4. Execute the dir command in user view to check the current interconnect module file system. Confirm the startup and configuration file names and the remaining space of the flash and make sure the flash has enough space for new startup files.
<Sysname> dir
Directory of flash:
0 drw- - Apr 17 2019 17:43:29 diagfile
1 drw- - Apr 08 2019 14:49:27 flyfishlog
2 -rw- 412 Apr 29 2019 10:50:54 ifindex.dat
3 drw- - Apr 17 2019 17:43:29 logfile
4 drw- - Apr 08 2019 14:51:51 pki
5 drw- - Apr 08 2019 14:49:17 seclog
6 -rw- 2649 Apr 29 2019 10:50:54 startup.cfg
7 -rw- 669171 Apr 29 2019 10:50:55 startup.mdb
8 -rw- 5705728 Apr 28 2019 14:35:55 uis-cmw710-boot-1.00.10.bin
9 -rw- 108381184 Apr 28 2019 14:36:52 uis-cmw710-system-1.00.10.bin
10 -rw- 7168 Apr 29 2019 14:06:09 uis.db
11 -rw- 7168 Apr 29 2019 14:06:09 uis_bak.db
12 drw- - Apr 22 2019 11:19:19 versionInfo
<Sysname>
5. Execute the save command in any view to save the current configuration information.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait...
Saved the current configuration to mainboard device successfully.
<Sysname>
6. Execute the tftp put command in user view to back up the system file and startup file to the TFTP server.
<Sysname>tftp 192.168.1.1 put flash:/uis-cmw710-system-1.00.10.bin
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
84 103M 0 0 84 87.0M 0 851k 0:02:04 0:01:44 0:00:20 837k
<Sysname>tftp 192.168.1.1 put flash:/uis-cmw710-boot-1.00.10.bin
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 5572k 0 0 100 5572k 0 832k 0:00:06 0:00:06 --:--:-- 828k
<Sysname>
7. Execute the tftp put command in user view to back up configuration file startup.cfg to the TFTP server.
<Sysname>tftp 192.168.1.1 put startup.cfg
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 6549 0 0 100 6549 0 270k --:--:-- --:--:-- --:--:-- 319k
<Sysname>
Upgrade an interconnect module
1. Select Interconnect Module Manage > Target_interconnect_module > Firmware Update.
2. Click Browse. In dialog box that opens, browse to the update image file and select it.
3. During the uploading, in the dialog box that opens, select BOOT-LOADER and click OK.
|
|
NOTE: Interconnect module firmware upgrade methods include: · Compatibility: For an interconnect module configured with an IRF fabric that is working correctly, applying this method can ensure continuous services during the upgrade. If the OM Web interface does not display this method, this indicates that the current OM version does not support the method. · BOOT-LOADER: This is a general upgrade method that applies to all released versions, but services will be interrupted during the upgrade. |
4. After the uploading, click Update. You can view the upgrade process in the corresponding column.
Verification
1. Select Interconnect Module Manage > Target_interconnect_module >Firmware Update and verify that the firmware has been updated to the target version.
Note that for the update using BOOT-LOADER, you must wait for the interconnect module to restart before identifying the most recent firmware version.
2. If not, perform the corresponding update operations again and verify the firmware versions.
3. If the issue persists, contact Technical Support.
Upgrade the interconnect module from the interconnect module CLI
About the interconnect module software
The interconnect module software includes a BootRom program and startup software packages. After the device is powered on, the system runs the BootRom program, initializes hardware, and then runs the startup software packages. The BootRom program and the startup packages are required for device startup and running and provide support, management, and service functions to the entire device.
Figure 19 shows the relations between the BootRom program and startup software packages.
Figure 19 BootRom program and startup software packages relations
Startup software packages
Startup software packages provide drivers and hardware compatibility and support service features. Startup software packages include the following types:
· Boot software package—Includes the OS kernel package and provides process management, memory management, file system management, and emergency Shell.
· System software package—Includes modules and basic functions required for device operation, such as device management, interface management, configuration management, and routing.
The boot package and system package are required for a device to operate correctly. The packages can be released separately or released together in an Image Package Envelope (IPE) file.
|
|
NOTE: · The boot software package and BootRom file of the device are packaged in an .ipe startup software package, for example, uis.ipe. · If you specify an IPE file as the next-startup software package, the system automatically extracts .bin software packages in the IPE file and sets the packages as the next-startup software packages. |
Patch packages
A patch package is used to fix system vulnerabilities in a fast way without restarting the device. It is a fast and low-cost method for fixing product software vulnerabilities. Compared with upgrading the startup software packages that require device restart, the main advantage of patch packages is that services will not be interrupted.
BootRom program
A complete BootRom includes basic BootRom and extended BootRom. Basic BootRom is the minimum program required for system startup and extended BootRom is used for hardware initialization and can provide abundant operation menus.
|
|
NOTE: The BootRom files are not released together with product software. To obtain a BootRom file, contact Technical Support. |
Software upgrade methods
Table 33 Software upgrade methods
|
Method |
Supported actions |
Description |
|
Upgrade the startup software packages |
Requires device restart. This method causes service interruption. |
|
|
Install a patch |
Does not interrupt services. This method can fix only vulnerabilities in a specific software package. |
|
|
Upgrade the BootRom program Upgrade the startup software packages |
Can be used to upgrade the device software without accessing the CLI. This method can upgrade only one device at a time. To upgrade an IRF fabric, use the CLI method instead. |
|
|
NOTE: Terminal display information in this section is for illustration only. For example: · The boot software package is named boot.bin in this section even if the actual name is in the uis-cmw710-boot-1.00.01.bin format. · The system software package is named system.bin in this section even if the actual name is in the uis-cmw710-system-1.00.01.bin format. |
Upgrade from the CLI
|
|
NOTE: · This section uses an IRF fabric that contains two members as an example. · To upgrade a single device, skip procedures for subordinate device configuration. · If the IRF fabric contains more than two member devices, repeat the procedures for subordinate device configuration to configure the other devices. Modify the member IDs as needed. |
Prepare for an upgrade
# Log in to the IRF through Telnet or the Console port from a PC. (Details not shown.)
# Use the display irf command in any view to view IRF information, and obtain the member device quantity, member role, and member ID.
<Sysname> display irf
MemberID Role Priority CPU-Mac Description
*+1 Master 5 0023-8927-afdc ---
2 Standby 1 0023-8927-af43 ---
--------------------------------------------------
* indicates the device is the master.
+ indicates the device through which the user logs in.
The Bridge MAC of the IRF is: 0023-8927-afdb
Auto upgrade : no
Mac persistent : 6 min
Domain ID : 0
In this example, two devices are in the IRF fabric. Member 1 is the master device, and member 2 is the subordinate device.
# Use the dir command in user view to view the remaining storage space on each member device.
· View the remaining storage space of the storage media (flash) on the master device:
<Sysname> dir
Directory of flash:
0 -rw- 41424 Jan 01 2011 02:23:44 startup.mdb
1 -rw- 3792 Jan 01 2011 02:23:44 startup.cfg
2 -rw- 53555200 Aug 23 2013 09:53:48 system.bin
3 drw- - Aug 23 2013 00:00:07 seclog
4 drw- - Aug 23 2013 00:00:07 diagfile
5 drw- - Aug 23 2013 00:00:07 logfile
6 -rw- 9959424 Aug 23 2013 09:53:48 boot.bin
7 -rw- 9012224 Aug 23 2013 09:53:48 backup.bi n
524288 KB total (453416 KB free)
· View the remaining storage space of the storage media (flash) on the slave device:
<Sysname> dir slot2#flash:/
Directory of slot2#flash:/
0 -rw- 41424 Jan 01 2011 02:23:44 startup.mdb
1 -rw- 3792 Jan 01 2011 02:23:44 startup.cfg
2 -rw- 93871104 Aug 23 2013 16:00:08 system.bin
3 drw- - Jan 01 2011 00:00:07 seclog
4 drw- - Jan 01 2011 00:00:07 diagfile
5 drw- - Jan 02 2011 00:00:07 logfile
6 -rw- 13611008 Aug 23 2013 15:59:00 boot.bin
7 -rw- 9012224 Nov 25 2011 09:53:48 backup.bin
524288 KB total (453416 KB free)
Make sure the remaining space is a minimum twice the size of the upgrade software package. If the space is insufficient on a device, you can use the delete command in user view to delete useless files to release space.
|
|
CAUTION: · To avoid configuration loss, do not delete the current configuration file. To view the current configuration file, use the display startup command in any view. · Software packages deleted by using the delete /unreserved file-url command are deleted completely and cannot be restored. Please be cautious. · Software packages deleted by using the delete file-url command are saved in the recycle bin and still occupy storage space. To completely delete a file in the recycle bin, use the undelete command to restore the file first, and then use the delete /unreserved file-url command to delete the file completely. |
· Delete files on the master device:
<Sysname> delete /unreserved flash:/backup.bin
The file cannot be restored. Delete flash:/backup.bin?[Y/N]:y
Deleting the file permanently will take a long time. Please wait...
Deleting file flash:/backup.bin...Done.
· Delete files on the subordinate device:
<Sysname> delete /unreserved slot2#flash:/backup.bin
The file cannot be restored. Delete slot2#flash:/backup.bin?[Y/N]:y
Deleting the file permanently will take a long time. Please wait...
Deleting file slot2#flash:/backup.bin...Done.
Download the startup software package or patch package to the master device
|
|
NOTE: · Before performing an upgrade operation, you must first upload the startup software package or patch package and save the package to the root directory of the storage media (flash) of the master device. If the package already exists in the root directory, skip this section. · The downloading method is the same for a startup software package and a patch package from the CLI. This section downloads a startup software package (IPE file) as an example. |
You can use one of the following methods to download the package:
· Download the package with the device acting as an FTP client
· Download the package with the device acting as an FTP server
· Download the package with the device acting as a TFTP client
Download the package with the device acting as an FTP client
1. Run the FTP server program on the PC (IP address 10.10.110.1 for example), configure an FTP client username and password, and specify the working directory accessible for the user. Save the startup software package to the directory.
|
|
NOTE: The device does not come with the FTP server software. You must purchase and install the software yourself. |
2. Make sure the PC and the IRF fabric can reach each other.
3. Download the startup software package (newest.ipe for example) to the root directory of the storage media on the master device.
# In user view, use the ftp command in user view, and enter the username and password as prompted. The device connects to the FTP server as a client.
<Sysname> ftp 10.10.110.1
Trying 10.10.110.1...
Press CTRL+K to abort
Connected to 10.10.110.1
220 FTP service ready.
User(10.10.110.1:(none)):username // Enter username
331 Password required for username.
Password: // Enter password
230 User logged in
# In FTP client view, use the binary command to set the transmission mode to binary.
ftp> binary
200 Type set to I.
# In FTP client view, use the get command to download the startup software package to the root directory of the storage media (flash) on the master device.
ftp> get newest.ipe
227 Entering Passive Mode (10,10,110,1,17,97).
125 BINARY mode data connection already open, transfer starting for /newest.ipe
226 Transfer complete.
32133120 bytes received in 35 seconds (896. 0 kbyte/s)
ftp> bye
221 Server closing.
Download the package with the device acting as an FTP server
1. Make sure the PC and the IRF fabric can reach each other.
2. Configure the IRF fabric as the FTP server and add a local user.
# In system view, use the ftp server enable command to enable the FTP service.
[Sysname] ftp server enable
# In system view, use the local-user command to add a local user. In this example, the local user name is abc.
[Sysname] local-user abc
# In local user view, use the password command to set the user password. In this example, the password is pwd.
[Sysname-luser-manage-abc] password simple pwd
# In local user view, use the service-type command to set the service type to FTP for the user.
[Sysname-luser-manage-abc] service-type ftp
# In local user view, use the authorization-attribute command to set the user role to network-admin. Users of this role can upload files to the server's working directory.
[Sysname-luser-manage-abc] authorization-attribute user-role network-admin
# In local user view, use the quit command to return to system view.
[Sysname-luser-manage-abc] quit
# In system view, use the quit command to return to user view.
[Sysname] quit
3. Use the PC as the FTP client to visit the device, and upload the startup software package to the FTP server.
# Log in to the FTP server.
c:\> ftp 1.1.1.1
Connected to 1.1.1.1.
220 FTP service ready.
User(1.1.1.1:(none)):abc // Enter username
331 Password required for abc.
Password: // Enter password
230 User logged in.
# Set the file transmission mode to binary.
ftp> binary
200 TYPE is now 8-bit binary.
# Upload the startup software package (newest.ipe for example) to the root directory of the storage media on the master device.
ftp> put newest.ipe
200 PORT command successful
150 Connecting to port 10002
226 File successfully transferred
ftp: Sent 32133120 bytes, consumed 64.58Seconds 497.60Kbytes/sec.
Download the package with the device acting as a TFTP client
1. Run a TFTP server program on the PC (IP address 10.10.110.1 for example), set the working directory, and save the startup software package to the directory.
|
|
NOTE: The device does not come with the TFTP server program. You must purchase and install the software yourself. |
2. Make sure the PC and the IRF fabric can reach each other.
3. Upload the startup software package (newest.ipe for example) to the root directory of the storage media on the master device.
<Sysname> tftp 10.10.110.1 get newest.ipe
Press CTRL+C to abort.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 30.6M 0 30.6M 0 0 143k 0 --:--:-- 0:03:38 --:--:-- 142k
Upgrade the startup software package or patch package
Upgrade the startup software package
# Specify the main next-startup software package as newest.ipe on the master device.
<Sysname> boot-loader file flash:/newest.ipe slot 1 main
Verifying image file..........Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to target slot.
Decompressing file boot.bin to flash:/boot.bin....................Done.
Decompressing file system.bin to flash:/system.bin................Done.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on slot 1.
# Specify the same main next-startup software package for the subordinate device. The system will automatically copy the file from the master device to the root directory of the storage media on the subordinate device.
<Sysname> boot-loader file flash:/newest.ipe slot 2 main
Verifying image file..........Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to target slot.
Decompressing file boot.bin to flash:/boot.bin....................Done.
Decompressing file system.bin to flash:/system.bin................Done.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on slot 2.
# In system view, use the irf auto-update enable command to enable the IRF fabric to automatically load the startup software package.
<Sysname> system-view
[Sysname] irf auto-update enable
[Sysname] quit
|
|
NOTE: The auto loading feature enables a new member to download the startup software package from the master device if the new member uses a different software version from the master. After obtaining the package, the member device restarts and joins the IRF again. |
# In any view, use the save command to save the current configuration to avoid configuration loss caused by device restarts.
<Sysname> save
The current configuration will be written to the device. Are you sure? [Y/N]:y
Please input the file name(*.cfg)[flash:/startup.cfg]
(To leave the existing filename unchanged, press the enter key):
flash:/startup.cfg exists, overwrite? [Y/N]:y
Validating file. Please wait.................
Saved the current configuration to mainboard device successfully.
Slot 2:
Save next configuration file successfully.
# In user view, use the reboot command to restart the IRF fabric.
<Sysname> reboot
Start to check configuration with next startup configuration file, please wait.
........DONE!
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait...
# In any view, use the display version command to verify that the software version has been updated successfully. (Details now shown.)
|
|
NOTE: · After you specifying the main next-startup software package, you must restart the devices for the package to take effect. During the restart, if the BootRom file contains updates, the system prompts you to update the basic BootRom and the extended BootRom. · To avoid compatibility issues, upgrade the basic BootRom and the extended BootRom at the same time as a best practice. · If you select not to upgrade BootRom, the system prompts you to upgrade BootRom again after you power cycle the server or restart the server from the CLI. If you do not enter any option in time, the system upgrades the complete BootRom by default. |
Install the patch package
# Activate patch package system-patch.bin on the master and subordinate devices.
<Sysname> install activate patch flash:/system-patch.bin slot 1
<Sysname> install activate patch flash:/system-patch.bin slot 2
# Verify that the software packages have been activated.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/system-patch.bin
Active packages on slot 2:
flash:/boot.bin
flash:/system.bin
flash:/system-patch.bin
# Commit the software changes.
<Sysname> install commit
# Verify that the software changes have been committed.
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/system-patch.bin
Committed packages on slot 2:
flash:/boot.bin
flash:/system.bin
flash:/system-patch.bin
Upgrade from the BootRom menu
If you cannot access the CLI, use the BootRom menu to perform an upgrade task.
|
|
NOTE: · You cannot use the BootRom menu to install a patch package. · For a single device, you can use the BootRom menu or the CLI to upgrade the startup software package. · You can upgrade only one device at a time. To upgrade an IRF fabric, use the CLI method. |
Upgrade the startup software package
You can use one of the following methods to upgrade the startup software package from the BootRom menu:
· Use the TFTP method to upgrade the startup software package
· Use the FTP method to upgrade the startup software package
· Use the XModem method to upgrade the startup software package
Use the TFTP method to upgrade the startup software package
1. Connect the console port of the device to the configuration terminal, and the management Ethernet port of the device to a PC. You can also use the PC as the configuration terminal.
2. Run the TFTP server program on the PC, set the TFTP server working directory, and save the startup software package to the directory.
|
|
NOTE: The device does not come with the TFTP server program. Purchase and install the program yourself. |
3. Run the terminal simulation program on the configuration terminal, start the device, and access the BootRom main menu.
For information about accessing the BootRom main menu, see "Access the BootRom menu."
4. View the remaining space of the storage media on the device.
The remaining space must be a minimum twice the size of the software package. If the space is insufficient, use the BootRom menu to delete useless files to release space.
For information about viewing files and the remaining space and deleting files, see "Manage files from the BootRom menu."
5. Enter 1 in the BootRom main menu, and press Enter to access the downloading protocol submenu.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):
6. Enter 1 to select the TFTP protocol, and then press Enter.
|
|
NOTE: · Specify the software package name and IP address based on the actual configuration. · If you leave a field empty, the system uses the default setting for the field. · If the device and the PC are on the same subnet, configure the device to use any unused IP address in the subnet and the gateway address is not required. If the device and the PC are on different subnets, you must specify a gateway address for the device. |
Load File Name :update.ipe
Server IP Address :192.168.0.3
Local IP Address :192.168.0.2
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
Table 34 TFTP parameters
|
Parameter |
Description |
|
Load File Name |
Software package name. In this example, the name is update.ipe. |
|
Server IP Address |
IP address of the TFTP server. In this example, the address is 192.168.0.3. |
|
Local IP Address |
IP address of the device. In this example, the address is 192.168.0.2. |
|
Subnet Mask |
Subnet mask of the device IP address. In this example, the mask is 255.255.255.0. |
|
Gateway IP Address |
IP address of the gateway. |
7. Configure the parameters and press Enter. At the confirmation prompt, you can enter Y to start downloading the startup software package, or enter N to return to the BootRom main menu.
8. Enter Y. The system starts to download the software package.
Loading.........................................................................
................................................................................
................................................................................
................................................................Done!
9. Specify the package attribute (M, B, or N) and then press Enter. Enter M, B, or N to specify the main, backup, or none attribute, respectively. In this example, M is entered and the package is specified as the main startup software package.
Please input the file attribute (Main/Backup/None) M
Image file boot.bin is self-decompressing...
Free space: 534980608 bytes
Writing flash...................................................................
................................................................................
...................................................................Done!
Image file system.bin is self-decompressing...
Free space: 525981696 bytes
Writing flash...................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.......................................................................Done!
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
0. Reboot
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
Enter your choice(0-8): 0
|
|
NOTE: If a startup software package of the same attribute already exists on the device, the system changes the attribute of the existing package to none. |
10. On the BootRom main menu, enter 0 and press Enter. The device loads the new startup software package and restarts.
Use the FTP method to upgrade the startup software package
1. Connect the console port of the device to the configuration terminal, and the management Ethernet port of the device to a PC. You can also use the PC as the configuration terminal.
2. Run the FTP server program on the PC, set the FTP client username and password, specify the working directory accessible to the client, and save the startup software package to the directory.
|
|
NOTE: The device does not come with the FTP server program. Purchase and install the program yourself. |
3. Run the terminal simulation program on the terminal, start the device, and access the BootRom main menu. For more information about accessing the BootRom main menu, see "Access the BootRom menu."
4. View the remaining space of the storage media on the device.
The remaining space must be a minimum twice the size of the software package. If the space is insufficient, use the BootRom menu to delete useless files to release space.
For information about viewing files and the remaining space and deleting files, see "Manage files from the BootRom menu."
5. Enter 1 in the BootRom main menu, and press Enter to access the downloading protocol submenu.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):
6. Enter 2 to select the FTP protocol, and then press Enter.
|
|
NOTE: · Specify the software package name and IP address based on the actual configuration. · If you leave a field empty, the system uses the default setting for the field. · If the device and the PC are on the same subnet, configure the device to use any unused IP address in the subnet and the gateway address is not required. If the device and the PC are on different subnets, you must specify a gateway address for the device. |
Load File Name :update.ipe
Server IP Address :192.168.0.3
Local IP Address :192.168.0.2
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
FTP User Name :switch
FTP User Password :***
Table 35 TFTP parameters
|
Parameter |
Description |
|
Load File Name |
Name of the software package to be downloaded. In this example, the name is update.ipe. |
|
Server IP Address |
IP address of the FTP server. In this example, the address is 192.168.0.3. |
|
Local IP Address |
IP address of the device. In this example, the address is 192.168.0.2. |
|
Subnet Mask |
Subnet mask of the device IP address. In this example, the mask is 255.255.255.0. |
|
Gateway IP Address |
IP address of the gateway. |
|
FTP User Name |
Username used to log in to the FTP server. Make sure the name is consistent with the configured username on the FTP server. |
|
FTP User Password |
User password used to log in to the FTP server. Make sure the password is consistent with the configured password on the FTP server. |
7. Configure the parameters and press Enter. At the confirmation prompt, you can enter Y to start downloading the startup software package, or enter N to return to the BootRom main menu.
8. Enter Y. The system starts to download the software package.
Loading.........................................................................
................................................................................
................................................................................
................................................................Done!
9. Specify the package attribute (M, B, or N) and then press Enter. Enter M, B, or N to specify the main, backup, or none attribute, respectively. In this example, M is entered and the package is specified as the main startup software package.
Please input the file attribute (Main/Backup/None) M
Image file boot.bin is self-decompressing...
Free space: 534980608 bytes
Writing flash...................................................................
................................................................................
................................................................Done!
Image file system.bin is self-decompressing...
Free space: 525981696 bytes
Writing flash...................................................................
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
.......................................................................Done!
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
0. Reboot
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
Enter your choice(0-8): 0
|
|
NOTE: If a startup software package of the same attribute already exists on the device, the system changes the attribute of the existing package to none. |
10. On the BootRom main menu, enter 0 and press Enter. The device loads the new startup software package and restarts.
Use the XModem method to upgrade the startup software package
|
|
NOTE: XModem file transmission is slow through the console port and the startup software package integrated with the BootRom file has a large size. As a best practice, use the management Ethernet port instead of the console port. This section uses the console port as an example. |
1. Connect the console port of the device to the configuration terminal, and the management Ethernet port of the device to a PC. You can also use the PC as the configuration terminal.
2. Run the hyper terminal software on the terminal, start the device, and access the BootRom main menu. For more information about accessing the BootRom main menu, see "Access the BootRom menu."
3. View the remaining space of the storage media on the device.
The remaining space must be a minimum of twice the size of the software package. If the space is insufficient, use the BootRom menu to delete useless files to release space.
For information about viewing files and the remaining space and deleting files, see "Manage files from the BootRom menu."
4. Enter 1 in the BootRom main menu, and press Enter to access the downloading protocol submenu.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):
5. Enter 3 to select the XModem protocol, and then press Enter.
Please select your download baudrate:
1.* 9600
2. 19200
3. 38400
4. 57600
5. 115200
0. Return to boot menu
Enter your choice(0-5):5
6. Select the download baudrate and then press Enter. In this example, 5 is entered to select 115200 bit/s.
Download baudrate is 115200 bps
Please change the terminal's baudrate to 115200 bps and select XMODEM protocol
Press enter key when ready
If the console port baudrate on the device is different from the baudrate of the terminal, the device and the terminal cannot communicate with each other. Change the terminal baudrate accordingly for the terminal and the device port to use the same baudrate.
|
|
NOTE: If you select download baudrate 9600 bps, you do not need to change the baudrate of the hyper terminal software. In this case, skip steps 7 through 9. |
7. Click Call > Terminate to disconnect the hyper terminal software from the device.
8. Access the Files > Attribute menu. Click Configure and set the bits per second field. In this example, set the value to 115200.
9. Click Call > Call to reconnect the hyper terminal software to the device.
10. As prompted, enter Y to download the software package, or enter N to return to the BootRom main menu. In this example, Y is entered.
Are you sure to download file to flash? Yes or No (Y/N):Y
The system starts to download the software package.
Now please start transfer file with XMODEM protocol
If you want to exit, Press <Ctrl+X>
Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC
|
|
NOTE: To exit downloading, press Ctrl+X. |
11. Click Forward > Send File. In the dialog box that opens, browse to the software package to be downloaded and set the protocol to XModem. In this example, the software package name is update.ipe.
12. Click Send.
13. After the software package is downloaded, specify the package attribute (M, B, or N) and then press Enter. Enter M, B, or N to specify the main, backup, or none attribute, respectively. In this example, M is entered and the package is specified as the main startup software package.
Please input the file attribute (Main/Backup/None) m
The boot.bin image is self-decompressing...
Load File name : default_file boot-update.bin // Specify the downloaded Boot software package
Free space: 470519808 bytes
Writing flash...................................................................
.............Done!
The system-update.bin image is self-decompressing...
Load File name : default_file system-update.bin // Specify the downloaded system software package
Free space: 461522944 bytes
Writing flash...................................................................
.............Done!
Your baudrate should be set to 9600 bps again!
Press enter key when ready
|
|
NOTE: If a startup software package of the same attribute already exists on the device, the system changes the attribute of the existing package to none. |
14. Refer to steps 7 through 9 to set the baudrate of the hyper terminal software to 9600 bps, and reconnect the hyper terminal software to the device.
|
|
NOTE: If the download baudrate is 9600 bps, skip this step. |
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
0. Reboot
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
15. On the BootRom main menu, enter 0 and press Enter. The device loads the new startup software package and restarts.
Enter your choice(0-8): 0
Upgrade the BootRom program
You can use one of the following methods to upgrade the BootRom program from the BootRom menu:
· Use the TFTP method to upgrade the BootRom program
· Use the FTP method to upgrade the BootRom program
· Use the XModem method to upgrade the BootRom program
Use the TFTP method to upgrade the BootRom program
1. Connect the console port of the device to the configuration terminal, and the management Ethernet port of the device to a PC. You can also use the PC as the configuration terminal.
2. Run the TFTP server program on the PC, set the TFTP server working directory, and save the startup BootRom file to the directory.
|
|
NOTE: The device does not come with the TFTP server program. Purchase and install the program yourself. |
3. Run the terminal simulation program on the configuration terminal, start the device, and access the BootRom main menu.
For information about accessing the BootRom main menu, see "Access the BootRom menu."
4. View the remaining space of the storage media on the device.
The remaining space must be a minimum of twice the size of the BootRom file. If the space is insufficient, use the BootRom menu to delete useless files to release space.
For information about viewing files and the remaining space and deleting files, see "Manage files from the BootRom menu."
|
|
CAUTION: In the BootRom menu, the main next-startup software package has an asterisk (*) mark. When you delete useless files, do not delete the main next-startup software package. If the package is deleted, the device cannot start up correctly. |
5. Enter 6 in the BootRom main menu, and press Enter to access the BootRom upgrade submenu.
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
0. Return to boot menu
Enter your choice(0-3):
6. Enter 1 to select updating the full BootRom, and then press Enter.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):
7. Enter 1 to select the TFTP protocol, and then press Enter.
|
|
NOTE: · Specify the BootRom file name and IP address based on the actual configuration. · If you leave a field empty, the system uses the default setting for the field. · If the device and the PC are on the same subnet, configure the device to use any unused IP address in the subnet and the gateway address is not required. If the device and the PC are on different subnets, you must specify a gateway address for the device. |
Load File Name :update.btm
Server IP Address :192.168.0.3
Local IP Address :192.168.0.2
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
Table 36 TFTP parameters
|
Parameter |
Description |
|
Load File Name |
BootRom file name. In this example, the name is update.btm. |
|
Server IP Address |
IP address of the PC on which the BootRom file resides. In this example, the address is 192.168.0.3. |
|
Local IP Address |
IP address of the device. In this example, the address is 192.168.0.2. |
|
Subnet Mask |
Subnet mask of the device IP address. In this example, the mask is 255.255.255.0. |
|
Gateway IP Address |
IP address of the gateway. In this example, the gateway IP address is not specified. |
8. Configure the parameters and press Enter. The system starts to download the BootRom file.
Loading.................................................Done!
9. After downloading, enter Y as prompted to upgrade the basic BootRom.
Will you Update Basic BootRom? (Y/N):Y
Updating Basic BootRom...........Done.
10. After upgrading the basic BootRom, enter Y as prompted to upgrade the extended BootRom.
Updating extended BootRom? (Y/N):Y
Updating extended BootRom.........Done.
After upgrading the extended BootRom, the system returns to the BootRom upgrade menu.
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
0. Return to boot menu
Enter your choice(0-3):
11. Enter 0 and press Enter to return to the BootRom main menu.
12. Enter 0 and press Enter. The new BootRom program takes effect after the device restarts.
Use the FTP method to upgrade the BootRom program
1. Connect the console port of the device to the configuration terminal, and the management Ethernet port of the device to a PC. You can also use the PC as the configuration terminal.
2. Run the FTP server program on the PC, set the FTP client username and password, specify the working directory accessible to the client, and save the BootRom file to the directory.
|
|
NOTE: The device does not come with the FTP server program. Purchase and install the program yourself. |
3. Run the terminal simulation program on the terminal, start the device, and access the BootRom main menu. For more information about accessing the BootRom main menu, see "Access the BootRom menu."
4. View the remaining space of the storage media on the device.
The remaining space must be a minimum of twice the size of the BootRom file. If the space is insufficient, use the BootRom menu to delete useless files to release space.
For information about viewing files and the remaining space and deleting files, see "Manage files from the BootRom menu."
|
|
CAUTION: In the BootRom menu, the main next-startup software package has an asterisk (*) mark. When you delete useless files, do not delete the main next-startup software package. If the package is deleted, the device cannot start up correctly. |
5. Enter 6 in the BootRom main menu and press Enter to access the BootRom upgrade submenu.
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
0. Return to boot menu
Enter your choice(0-3):
6. Enter 1 in the BootRom upgrade menu and press Enter to upgrade the full BootRom.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):
7. Enter 2 to select the FTP protocol, and then press Enter.
|
|
NOTE: · Specify the BootRom file name and IP address based on the actual configuration. · If you leave a field empty, the system uses the default setting for the field. · If the device and the PC are on the same subnet, configure the device to use any unused IP address in the subnet and the gateway address is not required. If the device and the PC are on different subnets, you must specify a gateway address for the device. |
Load File Name :update.btm
Server IP Address :192.168.0.3
Local IP Address :192.168.0.2
Subnet Mask :255.255.255.0
Gateway IP Address :0.0.0.0
FTP User Name :switch
FTP User Password :***
Table 37 TFTP parameters
|
Parameter |
Description |
|
Load File Name |
Name of the BootRom file to be downloaded. In this example, the name is update.btm. |
|
Server IP Address |
IP address of the PC on which the BootRom file is saved. In this example, the address is 192.168.0.3. |
|
Local IP Address |
IP address of the device. In this example, the address is 192.168.0.2. |
|
Subnet Mask |
Subnet mask of the device IP address. In this example, the mask is 255.255.255.0. |
|
Gateway IP Address |
IP address of the gateway. |
|
FTP User Name |
Username used to log in to the FTP server. Make sure the name is consistent with the configured username on the FTP server. |
|
FTP User Password |
User password used to log in to the FTP server. Make sure the password is consistent with the configured password on the FTP server. |
8. Configure the parameters and press Enter. The system starts to download the BootRom file.
Loading..................................................Done!
9. After downloading, enter Y at the prompt to upgrade the basic BootRom.
Will you Update Basic BootRom? (Y/N):Y
Updating Basic BootRom...........Done.
10. After upgrading the basic BootRom, enter Y at the prompt to upgrade the extended BootRom.
Updating extended BootRom? (Y/N):Y
Updating extended BootRom.........Done.
After the extended BootRom is upgraded, the system returns to the BootRom upgrade submenu.
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
0. Return to boot menu
Enter your choice(0-3):
11. Enter 0 and press Enter to return to the BootRom main menu.
12. Enter 0 and press Enter. The new BootRom program takes effect after the device restarts.
Use the XModem method to upgrade the BootRom program
1. Connect the console port of the device to the configuration terminal, and the management Ethernet port of the device to a PC. You can also use the PC as the configuration terminal.
2. Run the hyper terminal software on the terminal, start the device, and access the BootRom main menu. For more information about accessing the BootRom main menu, see "Access the BootRom menu."
3. View the remaining space of the storage media on the device.
The remaining space must be a minimum of twice the size of the BootRom software package. If the space is insufficient, use the BootRom menu to delete useless files to release space.
For information about viewing files and the remaining space and deleting files, see "Manage files from the BootRom menu."
|
|
CAUTION: In the BootRom menu, the main next-startup software package has an asterisk (*) mark. When you delete useless files, do not delete the main next-startup software package. If the package is deleted, the device cannot start up correctly. |
4. Enter 6 in the BootRom main menu, and press Enter to access the BootRom upgrade submenu.
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
0. Return to boot menu
Enter your choice(0-3):1
5. Enter 1 and press Enter to upgrade the full BootRom.
1. Set TFTP protocol parameters
2. Set FTP protocol parameters
3. Set XMODEM protocol parameters
0. Return to boot menu
Enter your choice(0-3):3
6. Enter 3 and press Enter to select the XModem protocol.
Please select your download baudrate:
1.* 9600
2. 19200
3. 38400
4. 57600
5. 115200
0. Return to boot menu
Enter your choice(0-5):5
7. Select the download baudrate and then press Enter. In this example, 5 is entered to select 115200 bit/s.
Download baudrate is 115200 bps
Please change the terminal's baudrate to 115200 bps and select XMODEM protocol
Press enter key when ready
If the console port baudrate on the device is different from the baudrate of the terminal, the device and the terminal cannot communicate with each other. Change the terminal baudrate accordingly for the terminal and the device port to use the same baudrate.
|
|
NOTE: If you select download baudrate 9600 bps, you do not need to change the baudrate of the hyper terminal software. In this case, skip steps 8 through 10. |
8. Click Call > Terminate to disconnect the hyper terminal software from the device.
9. Access the Files > Attribute menu. Click Configure and set the bits per second field. In this example, set the value to 115200.
10. Click Call > Call to reconnect the hyper terminal software to the device.
11. View the terminal display. After pressing Enter, the system starts to download the BootRom file.
Now please start transfer file with XMODEM protocol
If you want to exit, Press <Ctrl+X>
Loading ...CCCCCCCCCCCCCCCCCCCCCCCCC
|
|
NOTE: To exit downloading, press Ctrl+X. |
12. Click Forward > Send File. In the dialog box that opens, browse to the software package to be downloaded and set the protocol to XModem. In this example, the software package name is update.btm.
13. Click Send.
14. After downloading, enter Y and press Enter as prompted to upgrade the basic BootRom.
Loading ...CCCCCCCCCCCCCC ...Done.
Will you Update Basic BootRom? (Y/N):Y
Updating Basic BootRom...........Done.
15. After upgrading the basic BootRom, enter Y and press Enter as prompted to upgrade the extended BootRom.
Updating extended BootRom? (Y/N):Y
Updating extended BootRom.........Done.
16. After upgrading the extended BootRom, refer to steps 8 through 10 to change the baudrate of the hyper terminal software to 9600 bps as prompted.
Please change the terminal's baudrate to 9600 bps, press ENTER when ready.
|
|
NOTE: If the download baudrate is 9600 bps, skip this step. |
17. Press Enter. The system returns to the BootRom main menu.
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
0. Return to boot menu
Enter your choice(0-3):
18. Enter 0 and press Enter to return to the BootRom main menu.
19. Enter 0 and press Enter. The new BootRom program takes effect after the device restarts.
Access the BootRom menu
1. Connect a terminal (PC for example) to the console port of the device, run the terminal simulation program on the terminal, and configure the following terminal parameters:
¡ Baudrate: 9600
¡ Data bits: 8
¡ Parity: None
¡ Stop bits: 1
¡ Data flow control: None
¡ Terminal simulation: VT100
2. Power on the device. The device runs the BootRom program.
Starting......
Press Ctrl+D to access BASIC BOOT MENU
Starting......
Press Ctrl+D to access BASIC BOOT MENU
********************************************************************************
* *
* *** UIS uisbs03em BOOTROM, Version 1.01 *
* *
********************************************************************************
Copyright (c) 2004-2019 Hangzhou *** Technologies Co., Ltd.
Creation Date : Jan 16 2015,13:38:39
CPU Clock Speed : 1000MHz
Memory Size : 2048MB
Flash Size : 512MB
CPLD Version : 002/002
PCB Version : Ver.A
Mac Address : 0CDA415E232E
Press Ctrl+B to access EXTENDED BOOT MENU...1
3. Press Ctrl+D within 1 second at the prompt of Press Ctrl+D to access BASIC BOOT MENU to enter the basic BootRom menu.
|
|
NOTE: If the BootRom program is corrupted and the extended BootRom menu cannot be accessed, you can use the basic BootRom menu to fix or upgrade the extended BootRom. |
********************************************************************************
* *
* BASIC BOOTROM, Version 1.01 *
* *
********************************************************************************
BASIC BOOT MENU
1. Update full BootRom
2. Update extended BootRom
3. Update basic BootRom
4. Boot extended BootRom
0. Reboot
Ctrl+U: Access BASIC ASSISTANT MENU
Enter your choice(0-4):
Table 38 Basic BootRom menu options
|
Option |
Description |
|
1. Update full BootRom |
Upgrade the full BootRom. You can only use XModem to perform this task through the console port. For more information, see "Use the XModem method to upgrade the BootRom program." |
|
2. Update extended BootRom |
Upgrade the extended BootRom. You can only use XModem to perform this task through the console port. For more information, see "Use the XModem method to upgrade the BootRom program." |
|
3. Update basic BootRom |
Upgrade the basic BootRom. You can only use XModem to perform this task through the console port. For more information, see "Use the XModem method to upgrade the BootRom program." |
|
4. Boot extended BootRom |
Access the extended BootRom menu. To enter the extended BootRom menu, press Ctrl+B at the prompt. |
|
0. Reboot |
Restart the device. |
|
Ctrl+U: Access BASIC ASSISTANT MENU |
Press Ctrl+U to access the basic BootRom assistant menu. You can configure the system to perform memory self-test from the menu. For more information, see Table 39. |
Table 39 Basic BootRom assistant menu
|
Option |
Description |
|
1. RAM Test |
Perform memory self-test. |
|
0. Return to boot menu |
Return to the basic BootRom menu. |
4. Press Ctrl+B at the prompt of Press Ctrl+B to access EXTENDED BOOT MENU... to access the extended BootRom menu.
|
|
NOTE: · By default, the system starts in fast startup mode and the waiting time for user action is 1 second. If the system startup mode is full startup, the waiting time is 5 seconds. · If you fail to press Ctrl+B within the waiting time, restart the device. · The terminal display varies by device model. |
Password recovery capability is enabled.
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
0. Reboot
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
Enter your choice(0-8):
Table 40 Extended BootRom menu options
|
Option |
Description |
|
· Password recovery capability is enabled · Password recovery capability is disabled |
Indicates whether the password recovery capability is enabled. · Password recovery capability is enabled—The capability is enabled. You can use all menu options in the extended BootRom menu except for option 5. · Password recovery capability is disabled—The capability is disabled. You can use only specific menu options in the extended BootRom menu. |
|
1. Download image to flash |
Download the startup software package to the flash: · When the password recovery capability is enabled, you can download the startup software package of any version to the flash. · When the password recovery capability is disabled, you can download only startup software packages of version E2309 or later to the flash. |
|
2. Select image to boot |
If you select this option, you can perform the following tasks: 1. Select the main or backup startup software package for the next startup. ¡ If password recovery is enabled, you can specify a startup software package of any version. ¡ If password recovery is disabled, you can specify only a startup software package of version E2309 or later. 2. Select the main or backup configuration file for the next startup. ¡ If password recovery is enabled, this option is supported. ¡ If password recovery is disabled, this option is not supported. |
|
3. Display all files in flash |
Display all files in the flash. |
|
4. Delete file from flash |
Delete files from the flash. |
|
5. Restore to factory default configuration |
Delete the configuration file used at device startup and restart the device with the factory defaults. · If password recovery is enabled, this option is not supported. · If password recovery is disabled, this option is supported. |
|
6. Enter BootRom upgrade menu |
Access the BootRom upgrade menu. · If password recovery is enabled, you can upgrade BootRom of any version. · If password recovery is disabled, you can upgrade only BootRom of Version 123 or later. |
|
7. Skip current system configuration |
Configure the system to ignore the configuration file at this startup. This configuration takes effect only once. · If password recovery is enabled, this option is supported. · If password recovery is disabled, this option is not supported. |
|
8. Set switch startup mode |
Set the device startup mode, fast startup or full startup. |
|
0. Reboot |
Restart the device. |
|
Ctrl+F: Format file system |
Press Ctrl+F to format the storage media. |
|
Ctrl+P: Change authentication for console login |
Press Ctrl+P to configure the system to ignore the user password for console login at this startup. This configuration takes effect only once. · If password recovery is enabled, this option is supported. · If password recovery is disabled, this option is not supported. |
|
Ctrl+R: Download image to SDRAM and run |
Press Ctrl+R to download the startup software package to the memory and use the package to start the device. · If password recovery is enabled, this option is supported. · If password recovery is disabled, this option is not supported. |
|
Ctrl+Z: Access EXTEND-ASSISTANT MENU |
Press Ctrl+Z to access the extended BootRom assistant menu. In this menu, you can view memory information. For more information, see Table 41. |
Table 41 Extended BootRom assistant menu options
|
Option |
Description |
|
1. Display memory |
Display data in the memory. |
|
2. Search memory |
Search data from the memory. |
|
0. Return to boot menu |
Return to the extended BootRom menu. |
Manage files from the BootRom menu
In BootRom, you can display, delete, and change the main and backup attribute of files and view the remaining space the storage media while displaying files.
Display files
In the BootRom main menu, enter 3 and press Enter to display all files in the flash.
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
0. Reboot
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
Enter your choice(0-8): 3
Display all file(s) in flash:
File Number File Size(bytes) File Name
================================================================================
1 8177 flash:/testbackup.cfg
2(*) 53555200 flash:/system.bin
3(*) 9959424 flash:/boot.bin
4 3678 flash:/startup.cfg_backup
5 30033 flash:/default.mdb
6 42424 flash:/startup.mdb
7 18 flash:/.pathfile
8 232311 flash:/logfile/logfile.log
9 5981 flash:/startup.cfg_back
10(*) 6098 flash:/startup.cfg
11 20 flash:/.snmpboots
Free space: 464298848 bytes
The current image is boot.bin
(*)-with main attribute
(b)-with backup attribute
(*b)-with both main and backup attribute
The Free space field displays the remaining space of the flash.
Delete files
1. In the BootRom main menu, enter 4 and press Enter.
Deleting the file in flash:
File Number File Size(bytes) File Name
================================================================================
1 8177 flash:/testbackup.cfg
2(*) 53555200 flash:/system.bin
3(*) 9959424 flash:/boot.bin
4 3678 flash:/startup.cfg_backup
5 30033 flash:/default.mdb
6 42424 flash:/startup.mdb
7 18 flash:/.pathfile
8 232311 flash:/logfile/logfile.log
9 5981 flash:/startup.cfg_back
10(*) 6098 flash:/startup.cfg
11 20 flash:/.snmpboots
Free space: 464298848 bytes
The current image is boot.bin
(*)-with main attribute
(b)-with backup attribute
(*b)-with both main and backup attribute
2. Enter the number of the file to be deleted. In this example, the file to be deleted is testbackup.cfg.
Please input the file number to change: 1
3. Enter Y at the prompt to confirm the deletion.
The file you selected is testbackup.cfg,Delete it? (Y/N):Y
Deleting....................................Done!
Set the main and backup attribute for a file
1. In the BootRom main menu, enter 2 and press Enter.
EXTENDED BOOT MENU
1. Download image to flash
2. Select image to boot
3. Display all files in flash
4. Delete file from flash
5. Restore to factory default configuration
6. Enter BootRom upgrade menu
7. Skip current system configuration
8. Set switch startup mode
0. Reboot
Ctrl+Z: Access EXTENDED ASSISTANT MENU
Ctrl+F: Format file system
Ctrl+P: Change authentication for console login
Ctrl+R: Download image to SDRAM and run
Enter your choice(0-8): 2
1. Set image file
2. Set bin file
3. Set configuration file
0. Return to boot menu
Enter your choice(0-3):
2. Enter 1 or 2 to set the attribute for a startup software package, or enter 3 to set the attribute for a configuration file. In this example, 2 is entered.
1. Set image file
2. Set bin file
3. Set configuration file
0. Return to boot menu
Enter your choice(0-3): 2
3. Enter the number of files to be edited. In this example, files boot-update.bin and system-update.bin are selected.
File Number File Size(bytes) File Name
================================================================================
1(*) 53555200 flash:/system.bin
2(*) 9959424 flash:/boot.bin
3 13105152 flash:/boot-update.bin
4 91273216 flash:/system-update.bin
Free space: 417177920 bytes
(*)-with main attribute
(b)-with backup attribute
(*b)-with both main and backup attribute
Note:Select .bin files. One but only one boot image and system image must be included.
Enter file No.(Allows multiple selection):3
Enter another file No.(0-Finish choice):4
4. Enter 0 to stop selecting files.
Enter another file No.(0-Finish choice):0
You have selected:
flash:/boot-update.bin
flash:/system-update.bin
5. Enter M or B and press Enter to specify the files as the main or backup startup software packages. In this example, M is entered.
Please input the file attribute (Main/Backup) M
This operation may take several minutes. Please wait....
Next time, boot-update.bin will become default boot file!
Next time, system-update.bin will become default boot file!
Set the file attribute success!
Troubleshooting software upgrade failures
If the startup software package fails to be upgraded, the system runs with the current startup software package.
To resolve the upgrade failure issue:
1. Verify that the physical ports are connected correctly.
2. If you use console login, verify that the hyper terminal software parameters, such as baudrate and data bits, are configured correctly.
3. Review the terminal display on the hyper terminal software for possible errors:
¡ When XModem is used, the baudrate of the hyper terminal software is inconsistent with the baudrate of the console port.
¡ When TFTP is used, the specified IP address, software package name, or working directory on the TFTP server is incorrect.
¡ When FTP is used, the specified IP address, software package name, working directory on the FTP server, FTP username, or FTP password is incorrect.
4. Verify that the FTP server or TFTP server software is operating correctly and is configured correctly.
5. Verify that the remaining space of the flash is sufficient for saving the downloaded software package.
6. Verify that the software package is applicable to the device model and is of the correct type.
7. Verify that the version of the startup software package and the BootRom version are correct. For more information about the software compatibility, see the corresponding release notes.
Upgrade the AMC firmware for the interconnect module from the AMC CLI
|
|
CAUTION: The procedures in this section are applicable only to professional technical support engineers. |
Upgrade flowchart
Figure 20 Upgrade flowchart for the AMC firmware of the interconnect module
Prepare for the upgrade
Prepare tools
Table 42 Tool list
|
Tool |
Description |
|
PC |
Used to log in to the interconnect module AMC |
|
Network cable |
Used to connect the PC to the OM management network |
|
Serial port cable |
Used to connect the PC to the AMC serial port on the interconnect module |
|
Remote access software |
Used to access the AMC CLI of the interconnect module |
|
TFTP server |
Inter-platform file transmission tool NOTE: You can install the TFTP software on the PC and use the PC as the TFTP server for upgrading the AMC firmware. |
|
AMC firmware version file |
Used to upgrade the interconnect module AMC firmware. To obtain the most recent AMC firmware version file, visit the official website. |
Data planning
Table 43 Data planning
|
Data |
Example |
|
TFTP server address |
· IPv4 address: 192.168.10.111 · Mask: 255.255.255.0 |
|
AMC management IP address |
By default, the AMC management IP address is an IPv6 address. To upgrade the AMC firmware, you must specify an IPv4 address. · IPv4 address: 192.168.10.1 · Mask: 255.255.255.0 |
|
AMC CLI login username and password |
· Username (Default): admin · Password (Default): Password_UIS |
|
AMC version |
· Current firmware version: V1.00.04 · Target firmware version: V1.00.05 |
Upgrade the AMC firmware for the interconnect module
Set up the environment
As shown in Figure 21, use a serial port cable to connect the PC serial port to the AMC serial port on the interconnect module. Use a network cable to connect the Ethernet port on the PC to the management network of the OM module.
Figure 21 Setting up the environment
|
(1) OM module management port |
(2) Interconnect module AMC serial port |
View the current AMC firmware version
1. Run the remote login software, specify serial port login parameters, and access the AMC CLI.
Table 44 AMC serial port login parameters
|
Value |
|
|
Serial Line to connect to |
COMn, where n represents the serial port number. A serial port number is an integer. Set the port number based on the actual configuration. |
|
Speed (baud) |
115200 |
|
Data bits |
8 |
|
Stop bits |
1 |
|
Parity |
None |
|
Flow control |
None |
2. Press Enter as prompted, enter the username, leave the password field empty, and press Enter to access user mode.
Press ENTER to get started
Username: admin
Password:
>
3. Use the show version brief command to view the current AMC version of the interconnect module.
>show version brief
Version:SMBStaXdev-build by root@ubuntu2018-12-03T11:35:59+08:00 Config:smb_ocelot_10 SDK:2017.02-017-smb
Build Date: 2018-12-03T11:35:59+08:00
Code Revision: V1.00.04
Configure the AMC management IPv4 address
1. In user mode, use the enable command, and enter the password to enter privilege mode.
> enable
Password: ************
#
2. In privilege mode, use the configure terminal command to enter global mode.
# configure terminal
(config)#
3. In global mode, use the interface vlan 4094 command to enter VLAN mode. VLAN 4094 is the AMC management VLAN.
(config)# interface vlan 4094
4. In VLAN mode, use the ip address command to configure the AMC management IPv4 address, and then use the end command to return to privilege mode.
(config-if-vlan)# ip address 192.168.10.1 255.255.255.0
(config-if-vlan)# end
#
Upgrade the AMC firmware
In privilege mode, use the firmware upgrade tftp://TFTP IPv4 address/smb_ocelot_10.mfi command to start upgrading the AMC firmware. After the upgrade, the interconnect module restarts automatically.
· TFTP IPv4 address: Specifies the management IPv4 address of the TFTP server.
· smb_ocelot_10.mfi: Specifies the name of the AMC firmware file.
# firmware upgrade tftp://192.168.10.111/smb_ocelot_10.mfi
Downloading...
Got 10538761 bytes
Starting flash update - do not power off device!
Erasing flash...done
Programming flash...done
Swapping images...done
Restarting, please wait...
Verifying the upgrade
In a view with the display privilege, use the show version brief command to view the current AMC version of the interconnect module.
>show version brief
Version:SMBStaXdev-build by root@ubuntu2018-12-03T11:35:59+08:00 Config:smb_ocelot_10 SDK:2017.02-017-smb
Build Date: 2018-12-03T11:35:59+08:00
Code Revision: V1.00.05
Upgrade the BX1020B IB switch module
Upgrade flowchart
Figure 22 Upgrade flowchart for the BX1020B IB switch module
Prepare for the upgrade
Set up the environment
The BX1020B IB switch module is a non-management IB switch and does not support direct management. To manage the module, you must access the operating system of the blade server where the peer IB Mezz network adapter resides. Before upgrading the BX1020B IB switch module, make sure the IB Mezz network adapter is present on the blade server.
Only Linux operating systems support IB cluster management.
· If the compute node in the local enclosure has a Linux system installed, you can upgrade the module from the local enclosure. For the hardware deployment, see Figure 23.
· If the compute node in the local enclosure does not have a Linux system installed, use another server that has an IB interface and has a Linux system installed for the upgrade. This document uses a blade server as an example. For the hardware deployment, see Figure 24.
Figure 23 Local enclosure upgrade
Figure 24 Inter-enclosure upgrade
Prepare tools
Table 45 Tool list
|
Tool |
Description |
|
PC |
Used to log in to the OM Web interface. As a best practice, use Google Chrome 58 or a higher version and use a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent firmware version file, visit the official website. |
|
Operating system |
Installed on the blade server to manage the IB cluster. Only Linux systems support upgrading the firmware of the BX1020B IB switch module. |
|
MFT tool |
Installed in the operating system of a blade server to manage the firmware of the BX1020B IB switch module. |
Upgrade the BX1020B IB switch module
Log in to the blade server operating system
1. Visit https://OM_ip_address through a browser on the PC, enter the administrator username and password, and then click Log In.
2. Access the Blade Servers > Blade Server Name > Remote Consoles.
3. Click H5 KVM to launch the remote console.
Upload the firmware file and the MFT tool
|
|
NOTE: You can upload the file through KVM virtual media, a USB disk, or FTP. This section uses KVM virtual media as an example. |
1. Click Select File, select the target image file, and then click Connect.
You must first compress the firmware file and MFT tool into an image file.
2. Copy the file to the operating system of the blade server. In this example, the file is saved to /home/uis.
Figure 25 Copying the file to the operating system
3. Repeat the steps 1 and 2 to copy both the firmware file and MFT tool to the directory.
Install the MFT tool
1. Access the /home/uis directory, and use the tar -xvf mft-4.13.0-104-x86_64-rpm.tgz command to decompress the general MFT tool package.
Figure 26 Decompressing the MFT tool package
2. Access the /home/uis/mft-4.13.0-104-x86_64-rpm directory, and use the ./install.sh - -oem command to install the MFT tool.
Figure 27 Installing the MFT tool
3. Use the mst start command to run the MFT tool.
Figure 28 Running the MFT tool
Upgrade the firmware of the IB switch module
1. Use the /etc/init.d/opensmd start command to run the subnet manager.
For more information about the manager, see H3C UniServer BX1020B IB Switch Module Configuration Guides.
Figure 29 Running the subnet manager
2. Use the mst ib add command to add all IB devices in the cluster to the manager.
Figure 30 Adding IB devices to the cluster
3. Use the mst status –v command to identify the IB switch module name. In this example, the name is /dev/mst/SW_MT54000_Quantum_Mellanox_Technologies_lid-0x0002.
Figure 31 Viewing the IB switch module name
4. Use the flint -d <IB device> -i < fw version> burn command to install the firmware. The <IB device> argument represents the IB switch module name and the < fw version> argument represents the firmware file name.
Figure 32 Installing the firmware
5. After the installation is complete, restart the switch module for the new firmware to take effect.
Figure 33 Completing the upgrade
Verifying the upgrade
Use the flint -d <IB device> query command to view the firmware version of the switch module, where <IB device> represents the IB switch module name.
Figure 34 Viewing the firmware version
Upgrade the BX500S SAS switch module
Upgrade from the OM Web interface
Upgrade flowchart
Figure 35 Upgrade flowchart for the BX500S SAS switch module
Prepare for the upgrade
Prepare tools
Table 46 Tool list
|
Tool |
Description |
|
PC |
Used to log in to the OM Web interface. |
|
BX500S SAS switch module firmware version file |
To obtain the most recent firmware version file (.img file), visit the official website. Download the file to the PC. |
Set up the environment
As shown in Figure 36, connect the Ethernet ports of the PC to MGMT ports on the primary and backup OM modules. Make sure the PC and the OM management modules can reach each other at Layer 3.
Figure 36 Setting up the environment
Data planning
|
|
NOTE: Data in this section are for illustration only. Modify the settings based on the actual configuration. |
Before using the OM modules to upgrade the BX500S SAS switch module, you must obtain user and site information as shown in .
Table 47 Data planning
|
Data |
Description |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
BX500S SAS switch module slot |
In this example, the interconnect module is installed in slot 3. For the slot locations, see the marks on the device rear panel. |
Restrictions and guidelines
Before the upgrade
Make sure the OM module and the BX500S SAS switch module can reach each other for the OM module to upload the firmware version file to the interconnect module.
To avoid upgrade failure or version errors, make sure the firmware version file is correct. The file name must have a suffix of .img.
During the upgrade
To avoid firmware uploading failure, do not leave the firmware upgrade page during firmware uploading.
To avoid firmware upgrade failure, do not remove or restart the BX500S SAS switch module or perform any other tasks that might disconnect the switch module from the OM module.
To avoid firmware upgrade failure, only one user can perform firmware upgrade at a time.
The BX500S SAS switch module does not support management IP address change, virtual power setting, and UID LED setting.
Do not upgrade the HDD Bay and the BX500S SAS switch module at the same time.
During the upgrade, the primary/backup state of the two BX500S SAS modules becomes unavailable. The state is restored after the upgrade. If the state is not restored, restart the switch modules or perform an upgrade again.
Upgrade the BX1020B IB switch module
Check the system before the upgrade
1. Visit https://OM_ip_address through a browser on the PC, enter the administrator username and password, and then click Log In.
2. Access the Interconnect Module Manages > Interconnect Module Name > State Diagnosis page.
3. View the state and diagnosis information of the switch module. Verify if the module is in a state unavailable for upgrade. For example, the power state of the module is off or the connection state is abnormal.
¡ If the module is unavailable for upgrade, proceed to step 4.
¡ If the module is available for upgrade, proceed to step 5.
4. Process the module alarms and proceed to step 5.
5. Access the Interconnect Module Manage > Target BX500S SAS Module Name > Firmware Update page. View and record the current firmware version.
Upgrade the switch module firmware
1. Access the Interconnect Module Manage > Target BX500S SAS Module Name > Firmware Update page.
2. Browse to the switch module firmware file and upload the file.
3. After the firmware file is uploaded, click Firmware Update. You can view the upgrade progress in the Update Progress column.
Verifying the upgrade
1. View the current firmware version of the BX500S SAS switch module on the Firmware Update page. If the module fails to be upgraded to the target version, proceed to the next step.
2. Upgrade the switch module firmware again.
3. If the upgrade fails again, contact Technical Support.
Upgrade the LCD module
|
|
CAUTION: The procedures in this section are applicable only to professional technical support engineers. |
Upgrade flowchart
Figure 37 Upgrade flowchart for the LCD module
Prepare for the upgrade
Prepare tools
Table 48 Tools
|
Tool |
Description |
|
PC |
Used to connect to the LCD module and perform the upgrade operation. |
|
USB cable |
Used to connect the PC to the LCD module. |
|
Image package |
LCD images, including: · LCD Configure software—.knr file. · LCD firmware—.bin file. · HMIStudio—LCD upgrade tool. |
Upgrade the LCD module
Set up the environment
As shown in Figure 38, connect the USB 2.0 port on the PC to the Micro USB port on the LCD module.
Figure 38 Setting up the environment
|
(1) Micro USB port |
Install HMIStudio
1. Double-click the HMIStudio installer (HMI_Setup_V1.6.exe).
2. Install HMIStudio as instructed.
Figure 39 Installation completed
Update the USB driver
1. Right-click the This PC icon, and then click Manage.
2. Click Device Manager to open the device list.
3. Select USB MSC > Update driver.
Figure 42 Accessing the driver update screen
4. Click Browse my computer for drivers.
Figure 43 USB driver update screen
5. Browse to the usbdriver folder in the HMIStudio installation directory, and then click Next.
Figure 44 Selecting the driver program
6. Click Install this driver software anyway if the security prompt opens.
Figure 45 Windows security prompt
7. Click Close.
Upgrade LCD Configure
1. Access the official website and obtain the most recent image file for LCD Configure, and decompress the file to obtain the .knr file.
2. Run HMIStudio, and click File(F) > Pack/Unpack.
3. Browse to the .knr file in the compressed file field.
4. Browse to the save path, and specify the decompressed file name. The file name must have a suffix of .hs.
5. Click Start UnZip.
6. After unpacking, click File(F) > Open Project(O).
Figure 48 Opening the project file
7. Select the .hs file and then click Open.
8. Click the 
icon
to start compiling the project file.
After compilation, the Download dialog box opens.
9. Click Download to start upgrading LCD Configure.
Upgrade the LCD firmware
1. Access the official website and obtain the most recent LCD firmware file (.bin file).
2. Run HMIStudio, and click Tool(T) > upgrade.
3. rowse to the .bin file, select the USB download option, and then click Start Upgrade.
Upgrade the fan firmware through OM
Upgrade flowchart
Figure 49 Upgrade flowchart for the fan firmware
Prepare for the upgrade
|
|
NOTE: This section displays recommended tools. You can use other tools as needed. |
Prepare tools
Table 49 Tool list
|
Tool |
Description |
|
PC |
Used to log in to the OM Web interface. |
|
Network cable |
Used to connect the PC to the OM modules |
|
Fan firmware version |
Used to upgrade the fan firmware |
Set up the environment
As shown in Figure 50, connect the Ethernet ports of the PC to MGMT ports on the primary and backup OM modules. Make sure the IP address of the PC and IP address of the OM modules are on the same subnet.
Figure 50 Setting up the environment
Data planning
Before using the OM modules to upgrade the fan firmware, you must obtain site information as shown in Table 50.
|
Data |
Description |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
Procedures
Check the system before the upgrade
1. Visit https://OM_ip_address through a browser on the PC, enter the administrator username and password, and then click Log In.
2. Access the Power Supplies and Fans > Fan System page.
3. View the state of the fan modules. Verify if the modules are in a state unavailable for upgrade. For example, a fan module is being upgraded or initialized.
¡ If the modules are unavailable for upgrade, proceed to step 4.
¡ If the modules are available for upgrade, proceed to step 5.
4. Wait for the upgrade or initialization process to finish, and proceed to step 5.
5. Record the fan firmware version.
Upgrade the fan firmware
1. Click Firmware Update.
2. Select the fan system as the object.
3. Browse to the fan firmware file.
4. Select the target fan modules. After the firmware file is uploaded, click Firmware Update.
5. After the upgrade process is finished, verify that the fan firmware has been updated successfully. If the fan firmware is not updated successfully, proceed to the next step.
6. Upgrade the fan firmware again.
7. If the upgrade fails again, contact Technical Support.
Upgrade the OM firmware through OM
|
|
NOTE: If both the primary and backup OM modules are present, the upgrade operation upgrades both modules. |
Upgrade from the OM Web interface
Upgrade flowchart
Use Table 51 to identify the corresponding upgrade flowchart.
Table 51 Versions and the corresponding upgrade flowchart
|
Current version |
Target version |
Flowchart |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.00.XX |
See Figure 51. |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.01.01 |
|
|
Other versions |
See Figure 52. |
|
Figure 51 Upgrade flowchart for the OM module (1)
Figure 52 Upgrade flowchart for the OM module (2)
Prepare for the upgrade
Prepare tools
Table 52 Tool list
|
Tool |
Description |
|
PC |
Used to log in to the OM Web interface. As best practice, use Google Chrome 58 or a higher version and use a resolution ratio of 1600*900 or higher. |
|
Firmware version file |
To obtain the most recent OM firmware version file, access the official website. The firmware version file name has a suffix of .ipe. |
|
Configuration file |
Packaged in the OM firmware version file obtained from the official website. The configuration file name has a suffix of .cfg. You must upload the configuration file during the upgrade process. |
Set up the environment
As shown in Figure 53, connect the Ethernet ports of the PC to MGMT ports on the primary and backup OM modules. Make sure the IP address of the PC and IP address of the OM modules are on the same subnet.
Figure 53 Setting up the environment
Data planning
Before upgrading the OM modules, you must obtain site information as shown in Table 53.
|
Data |
Description |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
Restrictions and guidelines
Before the upgrade
Obtain the most recent OM module firmware image and make sure the OM modules are operating correctly.
To avoid firmware version check failures, make sure the firmware version is consistent with the firmware type.
Before upgrading the firmware image, make sure a minimum of 20% space is available in the root directory of the flash on the primary OM module. You can access the Enclosure Manage > File Manage page to view the space usage and release spaces.
During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the upgrade_firmware folder in the root directory of the flash on the primary OM module.
The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
When you select the upgrade file source, selecting a file from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or uploaded to the upgrade_firmware directory through file management.
During the upgrade
Do not disconnect connections to the OM modules. If you do so, the OM modules might fail.
To avoid upgrade failures, only one user can perform firmware upgrade at a time.
After the upgrade
After the firmware is upgraded successfully, the system restarts. You can wait for the system to restart and then try to log in to OM again.
If both the primary and backup OM modules are present, firmware upgrade might cause primary/backup switchover.
Procedures
Check the system before the upgrade
1. Visit https://OM_ip_address through a browser on the PC, enter the administrator username and password, and then click Log In.
2. Access the OM Modules > State Diagnosis page.
3. View the state of the OM modules. Verify if an OM module alarm is present.
¡ If an alarm is present, proceed to step 4.
¡ If no alarm is present, proceed to step 5.
4. Process the alarms, and proceed to step 5.
5. Click OM Modules, and view and record the current OM firmware version.
Upgrade the OM module firmware
1. Identify the current version and the target version.
Table 54 Upgrade procedures for different versions
|
Current version |
Target version |
Procedures |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.00.XX |
Start from step 2. |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.01.01 |
|
|
Other versions |
Start from step 4. |
|
2. Access the Enclosure Manage > File Manage page.
3. Click Upload File and then upload the configuration files compatible with the firmware version. In this example, files startup0.cfg and startup1.cfg are uploaded.
4. Access the OM Modules > Firmware Update page.
5. Browse to the most recent version file obtained from the official website. The system then uploads and verifies the firmware version.
¡ If the verification succeeds, proceed to the next step.
¡ If the verification fails, examine that the uploaded file. The version file name must have a suffix of .ipe.
6. After the firmware version file is uploaded, click Firmware Update.
7. Select BOOT-LOADER in the dialog box that opens, and then click OK.
|
|
NOTE: OM firmware upgrade methods include: · Compatible Upgrade (ISSU)—If two correctly operating OM modules are present, you can use this method to avoid service interruption. If the option is not displayed on the OM webpage, it indicates that this method is not supported. · BOOT-LOADER—This method causes temporary service interruption and is applicable to all versions. |
After the primary and backup OM modules are upgraded, the OM modules restart. During the restart, you cannot view information in the enclosure management software or configure the software. After the restart, you will be redirected to the login page.
Verifying the upgrade
1. Re-log in to OM.
2. Access the OM module page and verify that the OM module firmware has been upgraded to the target version.
3. If the version is not updated, upgrade the OM modules again.
4. If the upgrade fails again, contact Technical Support.
Upgrade from the OM CLI
Upgrade flowchart
Use Table 55 to identify the corresponding upgrade flowchart.
Table 55 Versions and the corresponding upgrade flowchart
|
Current version |
Target version |
Flowchart |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.00.XX |
See Figure 54. |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.01.01 |
|
|
Other versions |
See Figure 55. |
|
Figure 54 Upgrade flowchart for the OM module firmware (1)
Figure 55 Upgrade flowchart for the OM module firmware (2)
Prepare for the upgrade
Prepare tools
Table 56 Tool list
|
Tool |
Description |
|
PC |
Used to log in to the OM CLI. |
|
Firmware version file |
To obtain the most recent OM firmware version file, access the official website. The firmware version file name has a suffix of .ipe. |
|
Configuration file |
Packaged in the OM firmware version file obtained from the official website. The configuration file name has a suffix of .cfg. You must upload the configuration file during the upgrade process. |
Data planning
Before upgrading the OM modules, you must obtain site information as shown in Table 53.
Table 57 Data planning
|
Data |
Description |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
Restrictions and guidelines
Before the upgrade
Obtain the most recent OM module firmware file from the official website.
Make sure the OM modules are operating correctly.
During the upgrade
To avoid operation failures, do not leave the page during firmware file uploading.
Do not disconnect connections to the OM modules. If you do so, the OM modules might fail.
To avoid upgrade failures, only one user can perform firmware upgrade at a time.
After the upgrade
After the firmware is upgraded successfully, the system restarts. You can wait for the system to restart and then log in to OM again.
If both the primary and backup OM modules are present, firmware upgrade might cause primary/backup switchover.
Procedures
1. Open the remote access software, specify SSH login parameters, and access the OM CLI. Table 58 displays the login parameters.
|
Parameter |
Value |
|
Protocol |
SSH |
|
Port number |
22 |
|
OM management IP address |
IP address (default): 192.168.100.100/24 |
|
OM username and password |
· Username (default): admin · Password (default): Password@_ |
|
By default, OM access through SSH is enabled. |
|
After login, the OM CLI displays the following:
******************************************************************************
* Copyright (c) 2004-2020 New *** Technologies Co., Ltd. All rights reserved.*
* Without the owner's prior written consent, *
* no decompiling or reverse-engineering shall be allowed. *
******************************************************************************
<OM>
2. Use the access-method ftp command to enable access through FTP.
<OM>access-method ftp
3. Run the cmd.exe, enter C:\Windows\system64>ftp ip address, where ftp ip address represents the management IP address of the OM modules, and then enter the OM username and password.
C:\Windows\system64>192.168.100.100
Connecting to 192.168.100.100
220 FTP service ready
Username: admin
331 Password required for admin
Password:
230 User logged in.
ftp>
4. Identify the current and target versions.
|
Current version |
Target version |
Procedures |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.00.XX |
Start from step 5. |
|
UN_BLADE-OM-1.00.XX |
UN_BLADE-OM-1.01.01 |
|
|
Other versions |
Start from step 6. |
|
5. Use put file_path file_name to upload the configuration files to the OM modules.
ftp> put C:\Users\User1\Desktop\startup0.cfg
200 PORT command successful
150 Connecting to port 59196
226 File successfully transferred
ftp: Transferred 15651776 bytes, consumed 15.37 seconds, 1019.50 kilobytes/second
ftp> put C:\Users\User1\Desktop\startup1.cfg
200 PORT command successful
150 Connecting to port 59196
226 File successfully transferred
ftp: Transferred 15651776 bytes, consumed 15.37 seconds, 1019.50 kilobytes/second
6. Use the put firmware path firmware name command to upload the OM firmware version file to the OM modules.
ftp> put C:\Users\User1\Desktop\uis.ipe
200 PORT command successful
150 Connecting to port 59196
226 File successfully transferred
ftp: Transferred 35651776 bytes, consumed 34.97 seconds, 1019.50 kilobytes/second
7. Use the display manager firmware command to view the current OM firmware version.
<OM>display manager firmware
Manager ID Manager name Firmware version
1 OM100 H3C OM100-1.00.08
2 OM100
8. Use the manager firmware-update firmware name command to start to upgrade the OM modules.
<OM>manager firmware-update uis.ipe
Start to unpack the file...................................................................................................................................................
Start to check the file..........
The device will be rebooted after the upgrade is completed. Please wait.....................................................................................................................................................................................................................................................
After the primary and backup OM modules are upgraded, the OM modules restart.
9. After the restart, access the OM CLI again, and use the display manager firmware command to verify that the OM firmware has been upgraded successfully.
<OM>display manager firmware
Manager ID Manager name Firmware version
1 OM100 H3C OM100-1.00.09
2 OM100
Perform a whole-package upgrade
About whole-package upgrade
|
|
NOTE: As from release OM-1.03.03, the whole-package upgrade feature is supported. |
This feature allows users to upgrade all modules at a time, including the OM modules, fan system, interconnect modules, blade servers, and AE modules.
Procedures
Export the configuration file
1. Click Firmware Update.
2. Select Whole Package Upgrade as the upgrade object.
3. (Optional.) To use the configuration file to generate a firmware upgrade package, export the configuration file.
a. Select the modules to be upgraded.
b. Click Export Configuration.
Obtain the upgrade package
Before performing whole-package upgrade, you must obtain the upgrade package in either of the following methods:
· Access supportrepo.h3c.com, specify configurations, and download the upgrade package.
· Use the whole-package upgrade feature on the OM Web interface to filter modules to be upgraded, export the configuration, upload the configuration file to supportrepo.h3c.com, and generate the upgrade package.
To obtain the upgrade package:
1. Access the REPO Web page, click OM firmware customization, and export the OM component package (.tar.gz file).
2. Access the customization page, and import the configuration file.
a. Select the file upload method. Browse to the .json file in the exported server configuration inventory. The system automatically displays available components.
b. To further filter components, specify the component filtering criteria.
3. Select the target components, click Add to Resource Library.
The number on the box at the bottom right corner of the page indicates the number of components added to the library.
4. Click the box icon, and confirm the resources in the dialog box that opens.
5. Enter the repository name and version, and then select the component to be exported as a REPO.
6. Click Download.
Import the configuration file
1. Upload the firmware upgrade package from the PC. Browse to the package. The system will automatically upload the firmware upgrade package.
2. Click Parse Firmware Package. Space insufficiency and manual package modification can cause package parsing failure. If the operation fails, release space or re-download the REPO and then try again.
3. After the package is parsed, click Firmware List and view information about the firmware upgrade package.
4. Select the modules to be upgraded, and select the firmware version.
5. Click Firmware Update to upgrade the selected modules.
6. (Optional.) Access the Enclosure Manage > System Logs and Settings page. You can view detailed log information for the upgrade. If the upgrade fails, you can view the failure reason.
Restrictions and guidelines
Decompressing the firmware upgrade package requires extra space. Before uploading the firmware upgrade package to the flash of the OM module or the external USB, make sure the available space is a minimum twice of the packet size. As a best practice, clear the space before the upgrade.
To avoid firmware package decoding failure, do not edit the firmware upgrade package.
To avoid upgrade errors, during packet parsing or whole-package upgrade, do not perform any tasks on any modules as a best practice.
During file uploading, do not leave the page or log off from OM. If you do so, file uploading fails and residual files exist in the flash:/upgrade_firmware folder of the root directory in the flash on the primary OM module.
The uploaded firmware image is saved in the upgrade_firmware folder in the root directory of the flash on the primary OM module. To use the image to perform firmware upgrade, you can browse to the file directory without re-uploading.
When you select the upgrade file source, selecting from the OM module is applicable only to scenarios where the file has been uploaded during a previous upgrade process or saved in the root directory of a USB device connected to the primary or backup OM module.
