Description

This software is used to upgrade the OM version of theB16000 OM/UIS9000 server

Installation steps

Publish Description

Restrictions and cautions

Usage limitations

None.

Restrictions and guidelines

If the interconnect module version or OM management software version is earlier than 1.03.09, the interconnect module cannot synchronize time settings from the NTP server if the primary NTP server configured on OM cannot be reached but the secondary NTP server is available. To resolve the issue, make sure both the interconnect module version and OM version are 1.03.09 or later.

Version information

Version number

The target file name and MD5 checksum for this version are:

OM-3.00.17.ipe: 6d1a93987b621c71f2567f458706529c

Figure 1 OM version

Supported browsers

Browsers below are recommended:

Chrome 58 and later versions

Supported languages

English

Chinese

Supported devices

H3C UniServer B16000

H3C UIS 9000

Hardware and software compatibility matrix

Table 1 Compatibility matrix

ISSU upgrade type matrix

Table 2 ISSU version compatibility matrix

Version upgrade suggestions

This version is recommended.

Upgrade restrictions and guidelines

1.Understand the principles of version upgrade and make sure upgrades are compatible.

2.When you upgrade the OM management software from a version earlier than 1.00.09 to version 1.00.09 or later, you must upgrade the HDM version on the node to HDM-1.11.22P01 or later. If you do not do so, the operating system on the HDM node cannot start up correctly.

3.The OM management software supports direct upgrade. From a version earlier than 1.01.04 to version 1.01.04 or later, ISSU upgrade is not supported. You can use BOOT-LOADER to upgrade the software from the Web interface.

4.When the OM management software is upgraded from a version earlier than 1.01.xx to version 1.03.xx, ISSU upgrade is not supported. You can upgrade the OM management software to version 1.02.xx first, and then to version 1.03.xx, or use BOOT-LOADER to upgrade from the Web interface. All OM management software versions released prior to 1.03.10 do not support upgrading to 1.03.10 through ISSU.

5.If the OM management software version is 1.02.04 or later and the BX500S interconnect module version is 0.1.4.26 or later, use the NSDR method to upgrade the BX500S interconnect module from the OM Web interface, which does not interrupt service continuity. For other version combinations, use the hard reset method to upgrade the BX500S interconnect module from the Web interface, and service interruption will occur during the upgrade process.

6.The OM and interconnect modules are not recommended to cooperate across major versions. For example, OM versions 1.00.0X or 1.01.0X are not recommended to be used together with interconnect modules of version 1.02.0X, and vice versa.

7.If all firmware versions of devices in the chassis are upgraded in a unified way, make sure that the version upgrade of the OM devices is the last step of all firmware upgrade steps.

8.If the interconnect module version or OM management software version is earlier than 1.03.09, the interconnect module cannot synchronize time settings from the NTP server if the primary NTP server configured on OM cannot be reached but the secondary NTP server is available. To resolve the issue, make sure both the interconnect module version and OM version are 1.03.09 or later.

9.As from OM-3.00.13, network policy modes added support for FCoE Offload for ETH682i network adapters. If the network policy mode is non-QinQ mode, the network policy mode is non-QinQ mode and FCoE Offload after a version n earlier than OM-3.00.13 is upgraded to OM-3.00.13 or later. If the configuration of your network policy file includes the network policy file for the ETH682i network adapter, you must cold restart or shut down and start up the blade server to activate the FCoE Offload mode. If you fail to do so, you must restart the blade server twice for the configuration to take effect.

Problems Solved

202506190067

Symptom: The OM reports the fan full speed log alarm of OM received the full fan speed request from device.

Condition: This symptom might occur if you perform the stress test on CPUs when G5 nodes are installed on the blade server chassis.

202412290046

Symptom: Only one of blade server chassis can be logged in correctly, while other blade server chassis display user authentication and authorization failures for login.

Condition: This symptom might occur if multiple blade server chassis are configured with the same LDAP users, and use the BindDN used when the LDAP server is set up. 

202412290045

Symptom: Emails failed to be sent.

Condition: This symptom might occur if you send an email to a specific email address when the Exchange email server is used and the B16000 OM module is configured with SMTP email alarming.

202409191891

Symptom: The OM ran out of memory, triggering a master/backup switchover.

Condition: This symptom might occur if the server receives a large amount of Layer 2 packets with an abnormal length for a long period.

202404290654

Symptom: The temperature information for power supplies are displayed incorrectly when the blade server nodes are powered off.

Condition: This symptom might occur if all B5700 G6 nodes are powered off.

None.

202403210090

Symptom: After Nessus scans the chassis management module, the medium-risk vulnerability named Network Time Protocol (NTP) Mode 6 Scanner was found.

Condition: This symptom might occur if you enable and then disable the NTP service.

202311210491

Symptom: During the compute node upgrade, the HDM reset task is deployed on the OM page. Although the page shows the task as successful, the log indicates that the task actually failed.

Condition: This symptom might occur if the B5700 G6 is powered on correctly.

202310270117

Symptom: The application of the blade server policy template to the B5700 G3 node with RAID-P5408-Mf-8i-4G storage controller failed, resulting in the inability to identify the storage controller. 

Condition: This symptom might occur if the RAID-P5408-Mf-8i-4G storage controller changes to JBOD mode.

202312061172

Symptom: After the BIOS setup phase on the B5700 G6, OM sends FEC and NPAR settings. Then, an alarm occurs because the configuration for FEC and NPAR fails.

Condition: This symptom might occur if the B5700 G6 is powered on with the primary power supply.

202310191504

Symptom: Network policies can be deleted when switching fabric modules in an IRF fabric are powered off.

Condition: This symptom might occur if switching fabric modules are powered off.

New Functions