No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionServer Tools 2.0 uMate User Guide 36

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
GUI

GUI

Inspecting Servers

Preventive Maintenance Items
  • Table 4-1 describes the BMC preventive maintenance items.
  • Table 4-2 describes the E6000 preventive maintenance items.
  • Table 4-3 describes the E9000 preventive maintenance items.
  • Table 4-4 describes the SULE/RHEL/CentOS preventive maintenance items.
  • Table 4-5 describes the VMware OS preventive maintenance items.
  • Table 4-6 describes the KunLun preventive maintenance items.
Table 4-1 BMC preventive maintenance items

Inspection Item

Inspection Subitem

Inspection Type

Remarks

Power status

-

Configuration check

-

System health status

-

Health check

-

Device information query

Location

Asset information collection

-

Product name

Asset information collection

-

Product serial number

Asset information collection

-

Board serial number

Asset information collection

-

Device serial number

Asset information collection

-

Product part number

Asset information collection

-

Board part number

Asset information collection

-

Board description

Asset information collection

-

BMC version

Asset information collection

-

BIOS version

Asset information collection

-

CPLD version

Asset information collection

-

Other firmware versions

Asset information collection

-

CPU health status

-

Health check

Note1

CPU information

-

Asset information collection

Note1

Memory health status

-

Health check

Note1

Memory information

-

Asset information collection

Note1

RAID controller card health status

-

Health check

Note1

Hard disk health status

-

Health check

Note1

Hard disk information

-

Asset information collection

Note1

Onboard NIC

-

Asset information collection

-

Fan module health status

-

Health check

Note1

PSU health status

-

Health check

-

PSU information

-

Asset information collection

-

Temperature health status

-

Health check

-

TRAP configuration

-

Configuration check

-

Indicator status

-

Configuration check

-

Power information

-

Asset information collection

-

BMC version risk

-

Version risk check

-

BIOS version risk

-

Version risk check

-

CPLD version risk

-

Version risk check

-

System Host Name

-

Asset information collection

Note1

NIC Firmware and Driver Compatibility

-

Version compatibility check

Note1

NIC Ports Link Status

-

Asset information collection

Note1

Remarks:

Note1. uMate does not inspect this item if the server is powered off.

Table 4-2 E6000 preventive maintenance items

Inspection Item

Inspection Subitem

Inspection Type

Remarks

System

System health status

Health check

-

Product name

Asset information collection

-

Chassis

Chassis health status

Health check

-

Location

Asset information collection

-

Chassis ID

Asset information collection

-

Fan speed adjustment mode

Asset information collection

-

Serial number

Asset information collection

-

Part number

Asset information collection

-

HMM

Health status

Health check

-

Product name

Asset information collection

-

Product serial number

Asset information collection

-

Board serial number

Asset information collection

-

Product part number

Asset information collection

-

Board part number

Asset information collection

-

Board description

Asset information collection

-

Active/Standby status

Asset information collection

-

Software version

Asset information collection

-

Software version risk

Version risk check

-

CPLD version risk

Version risk check

-

Fan module

Status of fan modules in the entire chassis

Health check

-

Version information

Asset information collection

-

PSU

Information about PSUs in the entire chassis

Asset information collection

-

Server blade

Health status

Health check

-

Version vulnerability

Version vulnerability check

-

Product name

Asset information collection

-

Product serial number

Asset information collection

-

Board serial number

Asset information collection

-

Product part number

Asset information collection

-

Board part number

Asset information collection

-

Board description

Asset information collection

-

Software version

Asset information collection

-

BMC version risk

Version risk check

-

BIOS version risk

Version risk check

-

CPLD version risk

Version risk check

-

Switch module

Health status

Health check

-

Product name

Asset information collection

-

Product serial number

Asset information collection

-

Board serial number

Asset information collection

-

Product part number

Asset information collection

-

Board part number

Asset information collection

-

Board description

Asset information collection

-

Software version

Asset information collection

-

BMC version risk

Version risk check

-

CPLD version risk

Version risk check

-

Table 4-3 E9000 preventive maintenance items

Inspection Item

Inspection Subitem

Inspection Type

Remarks

System

System health status

Health check

-

TRAP configuration

Configuration check

-

Indicator status

Configuration check

-

Chassis

Chassis health status

Health check

-

Location

Asset information collection

-

Chassis ID

Asset information collection

-

Fan speed adjustment mode

Asset information collection

-

Chassis power capping setting

Asset information collection

-

Serial number

Asset information collection

-

Part number

Asset information collection

-

HMM

Version compatibility

Version compatibility check

-

Health status

Health check

-

Installation status

Asset information collection

-

Host name

Asset information collection

-

Product name

Asset information collection

-

Serial number

Asset information collection

-

Part number

Asset information collection

-

Board description

Asset information collection

-

Active/Standby status

Asset information collection

-

Active MM software version

Asset information collection

-

Standby MM software version

Asset information collection

-

Active/standby MM software version risk

Version risk check

-

Active/standby MM CPLD version risk

Version risk check

-

Fan module

Status of fan modules in the entire chassis

Health check

-

Hardware information

Asset information collection

-

Version information

Asset information collection

-

Firmware version risk

Version risk check

-

PSU

Status of PSUs in the entire chassis

Health check

-

Asset information

Asset information collection

-

Compute node

Power status

Configuration check

-

Health status

Health check

-

Product name

Asset information collection

-

Product serial number

Asset information collection

-

Board serial number

Asset information collection

-

Device serial number

Asset information collection

-

Product part number

Asset information collection

-

Board part number

Asset information collection

-

Board description

Asset information collection

-

Hardware version

Asset information collection

-

CPU health status

Health check

-

CPU information

Asset information collection

-

Memory health status

Health check

-

Memory information

Asset information collection

-

Hard disk health status

Health check

-

Hard disk information

Asset information collection

-

Mezzanine card health status

Health check

-

RAID information

Asset information collection

-

NIC information

Asset information collection

-

HBA information

Asset information collection

-

BMC version risk

Version risk check

-

BIOS version ris

Version risk check

-

CPLD version risk

Version risk check

-

Switch module

Health status

Health check

-

Product name

Asset information collection

-

Product serial number

Asset information collection

-

Board serial number

Asset information collection

-

Product part number

Asset information collection

-

Board part number

Asset information collection

-

Board description

Asset information collection

-

BMC version risk

Version risk check

-

CPLD version risk

Version risk check

-

Switch module (Fabric/Base)

Firmware version

Health check

Note1

Debugging status

Configuration check

Note1

Remote image configuration

Configuration check

Note1

Configuration file

Configuration check

Note1

Observing port

Configuration check

Note1

Duplex port

Health check

Note1

Eth-Trunk port

Health check

Note1

Port cyclic redundancy check (CRC)

Health check

Note1

Stack port

Health check

Note1

Consistency between the active and standby switch module versions

Health check

Note1

CPU

Health check

Note1

Memory

Health check

Note1

Interconnection port on the switching backplane

Health check

Note1

Alarms

Health check

Note1

Flash chip memory

Health check

Note1

Central processor CAR (CPCAR) traffic

Health check

Note1

Software

Health check

Note1

Hardware

Health check

Note1

Data Center Bridging (DCB) configuration

Configuration check

Note1, Note2

FCoE configuration (non-stack)

Configuration check

Note1, Note2

Link Layer Discovery Protocol (LLDP) configuration

Configuration check

Note1, Note2

Access control list (ACL) configuration

Configuration check

Note1, Note2

Traffic classification configuration

Configuration check

Note1, Note2

Traffic behavior configuration

Configuration check

Note1, Note2

Traffic policy configuration

Configuration check

Note1, Note2

Configuration of the port for connecting the MM910

Configuration check

Note1, Note2

Panel port configuration

Configuration check

Note1, Note2

Configuration of backplane ports DCB and FCoE (non-stack)

Configuration check

Note1, Note2

Configuration of the port for connecting the MX510 (non-stack)

Configuration check

Note1, Note2

Interconnection port configuration (non-stack)

Configuration check

Note1, Note2

Stack information collection (stack)

Asset information collection

Note1, Note2

FCoE configuration (stack)

Configuration check

Note1, Note2

Configuration of backplane ports DCB and FCoE (stack master)

Configuration check

Note1, Note2

Configuration of the port for connecting the MX510 (stack master)

Configuration check

Note1, Note2

Configuration of backplane ports DCB and FCoE (stack slave)

Configuration check

Note1, Note2

Configuration of the port for connecting the MX510 (stack slave)

Configuration check

Note1, Note2

Switch module synchronization configuration status

Configuration check

Note1

Ethernet switching plane version risk

Version risk check

-

Switch module (FC MX510)

Host version

Asset information collection

-

Date & Time

Configuration check

-

Device information

Asset information collection

-

VLAN information

Configuration check

-

Network port

Configuration check

-

Post logs

Health check

-

Error information

Health check

-

Alarms

Health check

-

Environment variables

Health check

-

FC switching plane version risk

Version risk check

-

Port error code statistics

Health check

-

Transceiver receiving/transmitting power

Health check

-

Switch modules (FC MX210 & MX220)

Host version

Asset information collection

-

Date & Time

Configuration check

-

Manufacturing information

Asset information collection

-

Device information

Asset information collection

-

Network port

Configuration check

-

Optical module

Configuration check

-

Health status

Health check

-

Error information

Health check

-

Switch module FC switching plane version risk

Version risk check

-

Port error code statistics

Health check

-

Remarks:

Note1. VRP5 is not supported.

Note2. Only the CX311 is involved.

Table 4-4 SLES/RHEL/CentOS/FusionSphere preventive maintenance items

Inspection Item

Inspection Subitem

Inspection Type

Remarks

OS version

Host name

Asset information collection

-

OS and patch versions

Asset information collection

-

Kernel version

Asset information collection

-

Driver and firmware compatibility

-

Version compatibility

-

Network configuration

-

Configuration check

-

System asset

Product name

Asset information collection

-

Universally unique identifier (UUID)

Asset information collection

-

Equipment serial number (ESN)

Asset information collection

-

CPU information

Asset information collection

-

ES3000 health status

-

Health check

Note1

ES3000 e-label

-

Asset information collection

Note1

Overall ES3000 information

-

Asset information collection

Note1

Compatibility between the OS version and CPU models

-

Version compatibility check

-

Kdump configuration

-

Configuration check

-

Serial port configuration

-

Configuration check

-

Log level configuration

-

Configuration check

-

MZ710 NIC VF quantity

-

Configuration check

-

Firmware version risk

-

Version risk check

-

Driver version risk

-

Version risk check

-

SATADOM write lifespan risk

-

Health check

-

DA200 health status

-

Health check

-

Firmware version

-

Asset information collection

-

Remarks:

Note1. Supports ES3000, ES3000 V2, and ES3000 V3.

Note2. Supports CH121 V3, and CH121H V3.

Table 4-5 VMware preventive maintenance items

Inspection Item

Inspection Subitem

Inspection Type

Remarks

OS version

Host Name

Asset information collection

-

Operating System Version

Asset information collection

-

Kernel Version

Asset information collection

-

System asset

Product Name

Asset information collection

-

Universally unique identifier (UUID)

Asset information collection

-

Equipment serial number (ESN)

Asset information collection

-

CPU Information

Asset information collection

-

ES3000 Health

-

Health check

Note1

ES3000 Label

-

Asset information collection

Note1

ES3000 Information

-

Asset information collection

Note1

Firmware and Driver Compatibility Check

-

Version compatibility

-

CPU and OS Compatibility Check

-

Version compatibility

-

SATADOM

-

Health check

-

Firmware Version

-

Asset information collection

-

Network Configuration Check

-

Configuration check

-

Kdump Configuration Check

-

Configuration check

-

Serial Configuration Check

-

Configuration check

-

Firmware Version Risk

-

Version risk check

-

Driver Version Risk

-

Version risk check

-

Remarks:

Note1. Supports ES3000, ES3000 V2, and ES3000 V3.

The preceding inspection items are related to the OS environment and hardware environment deployed on the server. The inspection items that are not involved in the OS environment and hardware environment are automatically skipped. If the DA200 does not exist in the OS environment, the DA200 health status item is skipped and the message "Not involved" is displayed.

Table 4-6 KunLun preventive maintenance items

Inspection Item

Inspection Subitem

Inspection Type

Server Check

System Health

Health check

Device Location

Asset information collection

Serial Number

Asset information collection

Product Type

Asset information collection

Host Name

Asset information collection

UID LED Configuration

Configuration check

Power State

Configuration check

RAID Card Health

Health check

RAID Card Type

Asset information collection

Build-In NIC Health

Health check

Build-In NIC Type

Asset information collection

CPU Info

Asset information collection

HDD Health

Health check

HDD Info

Asset information collection

PCIE Devices Health

Health check

PCIE Description Info

Asset information collection

Memory Health

Health check

Memory Info

Asset information collection

CIM Check

CIM Health

Health check

CIM Version

Asset information collection

CMC Check

CMC Health

Health check

Trap Configuration

Configuration check

CMC Version

Asset information collection

CMC Redundancy

Asset information collection

CPI Check

CPI Health

Health check

CPI Version

Asset information collection

CPI Redundancy

Asset information collection

ACM Check

ACM Health

Health check

ACM Version

Asset information collection

ACM Redundancy

Asset information collection

SCM Check

SCM Health

Health check

SCM Version

Asset information collection

LCD Check

LCD Health

Health check

LCD Version

Asset information collection

LPM Check

LPM Health

Health check

LPM Info

Asset information collection

NCM Check

NCM Health

Health check

NCM Version

Asset information collection

SCE_IO Check

SCE IO Module Health

Health check

SCE IO Module Version

Asset information collection

SCE IO Module Info

Asset information collection

PCIE_Switch Check

RSWA Health

Health check

RSWA Version

Asset information collection

REE_IO Check

REE IO Module Health

Health check

REE IO Module Version

Asset information collection

REE IO Module Info

Asset information collection

PSU Check

PSU Health

Health check

FAN Check

FAN Health

Health check

RHDA Check

RHDA Health

Health check

RHDA Version

Asset information collection

FRU Check

SCE FRU Info

Asset information collection

REE FRU Info

Asset information collection

CPI FRU Info

Asset information collection

CMC FRU Info

Asset information collection

ACM FRU Info

Asset information collection

CIM FRU Info

Asset information collection

Inspecting Servers (Except E9000)
Scenarios

Use uMate to inspect rack servers, high-density servers, E6000 blade servers, TaiShan servers, and server OSs in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • For the supported inspection items, see Preventive Maintenance Items.
  • You are advised to perform a PMI on one server. If the PMI is successful, perform batch PMIs. It is recommended that the number of servers for batch operation be less than 200.
  • The inspection of OSs installed on VMs is not supported.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
Impact on the System

During the inspection process, servers are not powered off and services are not affected.

Prerequisites

Conditions

  • The PC is properly communicating with the BMC or HMM of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC or HMM IP address is pinged from the local PC.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • The PC and OS to be inspected are in the same LAN. Ensure that the OS address is pinged from the local PC. The SSH and SFTP ports are enabled. Enable the SSH port on VMware OSs, see SSH Port Disabled.
  • Check whether the server or OS is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data is required for server inspection:

  • IP address of the server BMC or HMM management network port
  • User name and password of the server BMC or HMM

The following data is required for OS inspection:

  • IP address of the OS
  • User name and password of the OS
Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-1.

    Figure 4-1 uMate main window

  2. Click Inspect.

    The main window for inspecting servers is displayed, as shown in Figure 4-2.

    Figure 4-2 Main window for inspecting servers

    You can click Advanced... to view more parameters. For details, see Table 4-7.

    Table 4-7 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the management module IP address or OS IP address of the start server of the query.

    IP address of the BMC or OS or floating IP address of the HMM. The IP address indicates only the IPv4 address.

    End IP

    Specifies the management module IP address or OS IP address of the end server of the query.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the administrator user name of the BMC, HMM, or OS.

    -

    Password

    Specifies the administrator password of the BMC, HMM, or OS.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Root Password

    Specifies the password of user root.

    You need to enter the password of user root when you perform operations on Linux as a non-root user.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  3. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC/OS IP address or HMM floating IP address and the user name and password (for details, see Table 4-7), as shown in Figure 4-3.
        Figure 4-3 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-4.
        Figure 4-4 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  4. Click Next.

    Servers except E9000 are inspected. The dialog box shown in Figure 4-5 is displayed because no E9000 switch module user name or password is entered.
    Figure 4-5 Dialog box

  5. Click Yes.

    The window for selecting an inspection type is displayed, as shown in Figure 4-6.

    Figure 4-6 Selecting an inspection type
    Table 4-8 Parameter description

    Parameter

    Description

    Quick select

    • Custom: No inspection item is selected by default. You can select inspection items as required. You are advised to select Health Check, Configuration Check, Version Compatibility Check, Version Risk Check, and Asset Information Collection.
    • Inspect: Health Check, Configuration Check, Version Compatibility Check, Version Risk Check, and Asset Information Collection are selected.
    • Log Collect: Only Log Collect is selected.
    • Asset Collect: Only Asset Information Collection is selected.
    • Hardware Information Collect: Health Check and Asset Information Collection are selected.

    Health Check

    Health check

    Configuration Check

    Configuration check

    Version Compatibility Check

    Version compatibility check

    NOTE:

    The CPU and OS as well as the driver and firmware compatibility can be checked.

    Version Risk Check

    Version risk check

    Asset Information Collection

    Asset information collection

    Log Collect

    Log collection

    Baseline Version Check

    Baseline version check

    NOTE:
    • This parameter is used to check the differences between server, OS, or component versions and their baseline versions. It is used to determine the components that need to upgraded to the baseline versions in batches.
    • This parameter can be selected only after Asset Information Collection is selected.
    • KunLun servers do not support baseline version checks.

  6. Select inspection items according to Table 4-8, as shown in Figure 4-7.

    Figure 4-7 Selecting inspection items

    If Baseline Version Check is selected, perform the following operations:

    1. Click Export Template to export the baseline version mapping table BaselineVersion.xls (you do not need to export this file if it already exists). The file contains the board baseline version configuration table and card baseline version configuration table.
      • Figure 4-8 shows the board baseline version configuration table. The table contains the server baseline version configuration. Table 4-9 describes the parameters.
        Figure 4-8 Board baseline version configuration table
        Table 4-9 Parameter description

        Parameter

        Description

        Instruction

        Mandatory

        Product Name

        Product name

        Multiple product names need to be separated by semicolons (;), for example, RH2288 V3;RH2288H V3.

        Yes

        Board Type

        Board type

        This parameter must be set to Common.

        Yes

        Component

        Component

        The supported components include iBMC, iMana, Mainboard CPLD, HDD Backplane CPLD, Front IO Board CPLD, Back IO Board CPLD, RiserCard CPLD, Processor Board CPLD, and BIOS. You need to enter information based on the actual situation.

        Yes

        Version

        Component version

        Enter the component baseline version.

        Yes

        Component Type

        Component type

        Enter the specific component type.

        Yes

        CPU Type

        CPU type

        This parameter needs to be set if a product involves multiple CPU models and the corresponding BIOS versions are different. The format is CPU type+Space +CPU platform, for example, E7 V2. Multiple CPU types need to be separated by semicolons (;), for example, E7 V2;E7 V3.

        No

        URL

        URL

        The URL is the address of the software package of the baseline version of the component on the Support-E website. After the URL is specified, you can link it to the corresponding path in the baseline version detection report. This parameter is optional.

        No

      • Figure 4-9 shows the card baseline version configuration table. The table contains the OS baseline version configuration. Table 4-10 describes the parameters.
        Figure 4-9 Card baseline version configuration table
        Table 4-10 Parameter description

        Name

        Description

        Instruction

        Mandatory

        Product Name

        Product name

        Multiple product names need to be separated by semicolons (;), for example, CX910;CX911;CX912;CX913.

        Yes

        Card Name

        Card name

        Enter the actual card name.

        Yes

        Card Type

        Card type

        The card types include PCIECard, RAIDCard, and ES3000. PCIECard indicates the PCIe card, including the NIC and HBA. RAIDCard indicates the RAID controller card. ES3000 indicates the SSD card.

        Yes

        VID

        Vendor ID

        Enter the actual vendor ID.

        Yes

        DID

        Device ID

        Enter the actual device ID.

        Yes

        SUBVID

        Subsystem vendor ID

        Enter the actual subsystem vendor ID.

        Yes

        SUBSID

        Subsystem ID

        Enter the actual subsystem ID.

        Yes

        Driver Version

        Driver version

        Enter the driver baseline version.

        Yes

        FW Version

        Firmware version

        Enter the firmware baseline version.

        Yes

        OS Type

        OS type

        This parameter needs to be set to a specific version of an OS such as Red Hat, CentOS, SUSE, and VMware. The format is OS name+Space+Version, for example, Red Hat 7.2.

        Yes

        URL

        URL

        The URL is the address of the software package of the baseline version of the component on the Support-E website. After the URL is specified, you can link it to the corresponding path in the baseline version detection report. This parameter is optional.

        No

    2. Edit the BaselineVersion.xls file. For details, see Table 4-9 or Table 4-10.
    3. Click Import to import the BaselineVersion.xls file.

  7. Click Next.

    uMate starts to execute the inspection task. Figure 4-10 shows the inspection progress.

    Figure 4-10 Executing an inspecting task
    NOTE:

    You can click Stop to stop this task.

    The inspection is complete, as shown in Figure 4-11.

    Figure 4-11 Inspection completed
    NOTE:
    • You can click Details to view the inspection results of a device.
    • The inspection results are as follows:
      • OK
      • Warning
      • Minor
      • Major
      • Critical
      • Unknown

  8. Select the server whose inspection report is to be exported, and click Next.

    The window for exporting an inspection report is displayed, as shown in Figure 4-12. You can export an inspection report to a local PC to view the inspection results offline.

    Figure 4-12 Exporting an inspection report
    NOTE:
    • You can click the Preview Report button to view inspection reports in batches. See Figure 4-13.
    • You are advised to use Google Chrome or Internet Explorer 9 or later to view inspection reports.
    Figure 4-13 Viewing inspection reports in batches

    When you view inspection reports in batches:

    • You can click Inspection Statistics to view the inspection summary of inspected servers.
    • You can click Inspection Assets to view the asset information about all inspected servers.
    • You can click Inspection Version to view the version information about all inspected servers.
    • You can click Inspection Baseline Versions to view baseline version inspection reports.
    • You can click Detailed Report to view detailed inspection reports.
    • You can click Appendix to view other information.

  9. Enter inspection report cover information according to Table 4-11, click Generate Report to export the inspection report to the local PC.

    Table 4-11 Inspection report cover information

    Parameter

    Description

    Data Center Name

    Name of the data center

    Data Center Address

    Address of the data center

    Remarks

    Supplementary information

Inspecting Servers (E9000)
Scenarios

Use uMate to inspect the compute nodes, switch modules, management modules, and OSs of E9000 blade servers in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • For the supported inspection items, see Preventive Maintenance Items.
  • You are advised to perform a PMI on one server. If the PMI is successful, perform batch PMIs. It is recommended that the number of servers for batch operation be less than 200.
  • The inspection of OSs installed on VMs is not supported.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
Impact on the System

During the inspection process, servers are not powered off and services are not affected.

Prerequisites

Conditions

  • The PC is properly communicating with the BMC or HMM of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC or HMM IP address is pinged from the local PC.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • The PC and OS to be inspected are in the same LAN. Ensure that the OS address is pinged from the local PC. The SSH and SFTP ports are enabled. Enable the SSH port on VMware OSs, see SSH Port Disabled.
  • Check whether the server or OS is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC or HMM management network port
  • User name and password of the server BMC or HMM

The following data is required for OS inspection:

  • IP address of the OS
  • User name and password of the OS
Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-14.

    Figure 4-14 uMate main window

  2. Click Inspect.

    The main window for inspecting servers is displayed, as shown in Figure 4-15.

    Figure 4-15 Main window for inspecting servers

    You can click Advanced... to view more parameters. For details, see Table 4-12.

    Table 4-12 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the start IP address of servers.

    IP address of the BMC or OS or floating IP address of the HMM. The IP address indicates only the IPv4 address.

    End IP

    Specifies the end IP address of servers.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Administrator user name of the BMC, HMM, or OS

    -

    Password

    Administrator password of the BMC, HMM, or OS

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Root Password

    Password of user root

    You need to enter the password of user root when you perform operations on Linux as a non-root user.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

    During MM910 inspection, if the switch module Fabric/FC/Base plane information needs to be inspected, you need to enter the user name and password of the Fabric/FC/Base plane. There are four switch modules in total. If the required user name and password are not entered, the Fabric/FC/Base plane information will not be inspected.

    Fabric Username

    Fabric plane administrator user name

    -

    Fabric Password

    Fabric plane administrator password

    -

    FC Username

    FC plane administrator user name

    -

    FC Password

    FC plane administrator password

    -

    Base Username

    Base plane administrator user name

    -

    Base Password

    Base plane administrator password

    -

    Use the same configuration for all switch modules

    Specifies that all switch modules use the same user name and password.

    This item is selected by default.

  3. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the blade server BMC/OS IP address or HMM floating IP address and the user name and password. For details, see Table 4-12. During MM910 inspection, if the switch module Fabric/FC/Base plane information needs to be inspected, you need to enter the user names and passwords of the Fabric/FC/Base planes of the four switch modules, as shown in Figure 4-15.
        Figure 4-16 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-17.
        Figure 4-17 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  4. Click Next.

    • (Optional) If the Fabric/FC/Base plane user name/password information of the switch module is not entered, the dialog box shown in Figure 4-18 is displayed.
      Figure 4-18 Dialog box
      • If the Fabric/FC/Base plane information of the switch module does not need to be inspected, click Yes. The page shown in Figure 4-19 is displayed.
      • If the Fabric/FC/Base plane information of the switch module needs to be inspected, click No and enter the Fabric/FC/Base plane user name/password information of the switch module.
    • The window for selecting an inspection type is displayed, as shown in Figure 4-19.
      Figure 4-19 Selecting an inspection type
      Table 4-13 Parameter description

      Parameter

      Description

      Quick select

      • Custom: No inspection item is selected by default. You can select inspection items as required. You are advised to select Health Check, Configuration Check, Version Compatibility Check, Version Risk Check, and Asset Information Collection.
      • Inspect: Health Check, Configuration Check, Version Compatibility Check, Version Risk Check, and Asset Information Collection are selected.
      • Log Collect: Only Log Collect is selected.
      • Asset Collect: Only Asset Information Collection is selected.
      • Hardware Information Collect: Health Check and Asset Information Collection are selected.

      Health Check

      Health check

      Configuration Check

      Configuration check

      Version Compatibility Check

      Version compatibility check

      NOTE:

      The CPU and OS as well as the driver and firmware compatibility can be checked.

      Version Risk Check

      Version risk check

      Asset Information Collection

      Asset information collection

      Log Collect

      Log collection

      Baseline Version Check

      Baseline version check

      NOTE:
      • This parameter is used to check the differences between server, OS, or component versions and their baseline versions. It is used to determine the components that need to upgraded to the baseline versions in batches.
      • This parameter can be selected only after Asset Information Collection is selected.
      • KunLun servers do not support baseline version checks.

  5. Select inspection items according to Table 4-13, as shown in Figure 4-20.

    Figure 4-20 Selecting inspection items

    If Baseline Version Check is selected, perform the following operations:

    1. Click Export Template to export the baseline version mapping table BaselineVersion.xls (you do not need to export this file if it already exists). The file contains the board baseline version configuration table and card baseline version configuration table.
      • Figure 4-21 shows the board baseline version configuration table. It is the configuration of the baseline version of the E9000 (the board types include Switch, HMM, and Blade). Table 4-14 describes the parameters.
        Figure 4-21 Board baseline version configuration table
        Table 4-14 Parameter description

        Parameter

        Description

        Instruction

        Mandatory

        Product Name

        Product name

        Multiple product names need to be separated by semicolons (;), for example, CX910;CX911;CX912;CX913.

        Yes

        Board Type

        Board type

        The board types include Switch, HMM, and Blade.

        Yes

        Component

        Component

        Table 4-15 lists the component names and involved modules. You need to enter information based on the actual situation.

        Yes

        Version

        Component version

        Enter the component baseline version.

        Yes

        Component Type

        Component type

        Enter the specific component type.

        Yes

        CPU Type

        CPU type

        This parameter needs to be set if a product involves multiple CPU models and the corresponding BIOS versions are different. The format is CPU type+Space +CPU platform, for example, E7 V2. Multiple CPU types need to be separated by semicolons (;), for example, E7 V2;E7 V3.

        No

        URL

        URL

        The URL is the address of the software package of the baseline version of the component on the Support-E website. After the URL is specified, you can link it to the corresponding path in the baseline version detection report. This parameter is optional.

        No

        Table 4-15 Component names and involved modules

        Component Name

        Involved Module

        iBMC

        Switch module and blade

        iMana

        Switch module and blade

        Mainboard CPLD

        Switch module, server, and management module

        HDD Backplane CPLD

        Blade

        Front IO Board CPLD

        Blade

        Back IO Board CPLD

        Blade

        RiserCard CPLD

        Blade

        Processor Board CPLD

        Blade

        BIOS

        Blade

        HMM

        Management module

        Fan FW

        Management module

        Switch

        Switch module

        Switch(VRP5)

        Switch module

        Switch FC

        Switch module

      • Figure 4-22 shows the card baseline version configuration table, which is the configuration for the OS baseline version. Table 4-16 describes the parameters.
        Figure 4-22 Card baseline version configuration table
        Table 4-16 Parameter description

        Name

        Description

        Instruction

        Mandatory

        Product Name

        Product name

        Multiple product names need to be separated by semicolons (;), for example, CX910;CX911;CX912;CX913.

        Yes

        Card Name

        Card name

        Enter the actual card name.

        Yes

        Card Type

        Card type

        The card types include PCIECard, RAIDCard, and ES3000. PCIECard indicates the PCIe card, including the NIC and HBA. RAIDCard indicates the RAID controller card. ES3000 indicates the SSD card.

        Yes

        VID

        Vendor ID

        Enter the actual vendor ID.

        Yes

        DID

        Device ID

        Enter the actual device ID.

        Yes

        SUBVID

        Subsystem vendor ID

        Enter the actual subsystem vendor ID.

        Yes

        SUBSID

        Subsystem ID

        Enter the actual subsystem ID.

        Yes

        Driver Version

        Driver version

        Enter the driver baseline version.

        Yes

        FW Version

        Firmware version

        Enter the firmware baseline version.

        Yes

        OS Type

        OS type

        This parameter needs to be set to a specific version of an OS such as Red Hat, CentOS, SUSE, and VMware. The format is OS name+Space+Version, for example, Red Hat 7.2.

        Yes

        URL

        URL

        The URL is the address of the software package of the baseline version of the component on the Support-E website. After the URL is specified, you can link it to the corresponding path in the baseline version detection report. This parameter is optional.

        No

    2. Edit the BaselineVersion.xls file. For details, see Table 4-14 or Table 4-16.
    3. Click Import to import the BaselineVersion.xls file.

  6. Click Next.

    uMate starts to execute the inspection task. Figure 4-23 shows the inspection progress.

    Figure 4-23 Executing an inspecting task
    NOTE:

    You can click Stop to stop this task.

    The inspection is complete, as shown in Figure 4-24.

    Figure 4-24 Inspection completed
    NOTE:
    • You can click Details to view the inspection results of a device.
    • The inspection results are as follows:
      • OK
      • Warning
      • Minor
      • Major
      • Critical
      • Unknown

  7. Select the server whose inspection report is to be exported, and click Next.

    The window for exporting an inspection report is displayed, as shown in Figure 4-25. You can export an inspection report to a local PC to view the inspection results offline.

    Figure 4-25 Exporting an inspection report
    NOTE:
    • You can click the Preview Report button to view inspection reports in batches. See Figure 4-26.
    • You are advised to use Google Chrome or Internet Explorer 9 or later to view inspection reports.
    Figure 4-26 Viewing inspection reports in batches

    When you view inspection reports in batches:

    • You can click Inspection Statistics to view the inspection summary of inspected servers.
    • You can click Inspection Assets to view the asset information about all inspected servers.
    • You can click Inspection Version to view the version information about all inspected servers.
    • You can click Inspection Baseline Versions to view baseline version inspection reports.
    • You can click Detailed Report to view detailed inspection reports.
    • You can click Appendix to view other information.
      NOTE:

      For the inspection of Linux OSs on CH121 V3 and CH121H V3 servers, the Inspection Configuration item will be added to inspection reports. This inspection item is used to check Linux OS configuration information.

  8. Enter inspection report cover information according to Table 4-17, click Generate Report to export the inspection report to the local PC.

    Table 4-17 Inspection report cover information

    Parameter

    Description

    Data Center Name

    Name of the data center

    Data Center Address

    Address of the data center

    Remarks

    Supplementary information

Collecting Server Logs

Collecting Server Logs
Scenarios

Use uMate to collect server logs in the following scenarios:

  • Deployment delivery
  • Routine maintenance

For the log items that can be collected, see Log Collection Items.

NOTE:
  • You are advised to collect logs on one server. If the log collection task is successful, perform batch log collection. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • If the blade server iBMC version is earlier than 2.0, iBMC logs cannot be completely collected by using the HMM IP address. You need to collect logs by using the iBMC IP addresses.
  • If the iMana 200 version is earlier than V720, only administrator root supports BMC log collection in one-click mode. If the iMana 200 version is V720 or later, all administrators support BMC log collection in one-click mode. All administrators on the iBMC platform support BMC log collection in one-click mode.
  • The HMM one-click log collection interface has restrictions on the size of switch logs. When the size of BMC logs of the E9000 switch module exceeds 6 MB or the size of logs of the switching plane exceeds 15 MB, the collected switch logs are empty.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC or HMM of each target server. The IPMI, SNMP, and SSH communication ports are enabled. Ensure that the server BMC or HMM IP address is pinged from the local PC.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • The network communication between the PC and the OS whose logs are to be collected is normal, the SSH and SFTP communication ports are connected, and the OS IP address can be pinged.
  • Check whether the server or OS is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data is required for server log collection:

  • IP address of the server BMC or HMM management network port
  • User name and password of the server BMC or HMM

The following data is required for OS log collection:

  • IP address of the OS
  • User name and password of the OS
Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-27.

    Figure 4-27 uMate main window

  2. Click Log Collect.

    The main window for collecting server logs is displayed, as shown in Figure 4-28.

    Figure 4-28 Main window for collecting server logs

    You can click Advanced... to view more parameters. For details, see Table 4-18.

    Table 4-18 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the management module IP address or OS IP address of the start server of the query.

    IP address of the BMC or OS or floating IP address of the HMM. The IP address indicates only the IPv4 address.

    End IP

    Specifies the management module IP address or OS IP address of the end server of the query.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the administrator user name of the BMC, HMM, or OS.

    -

    Password

    Specifies the administrator password of the BMC, HMM, or OS.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Root Password

    Specifies the password of user root.

    You need to enter the password of user root when you perform operations on Linux as a non-root user.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

  3. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC/OS IP address or HMM floating IP address and the user name and password (for details, see Table 4-7), as shown in Figure 4-29.
        Figure 4-29 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-30.
        Figure 4-30 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  4. Click Next.

    The window for discovering a server is displayed, as shown in Figure 4-31.

    Figure 4-31 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-32.

    Figure 4-32 Discovering servers successfully

    The system automatically collects logs after a server is discovered. After the log collection is complete, the window shown in Figure 4-33 is displayed.

    Figure 4-33 Log collection completed
    NOTE:

    You can click Export to save the results in this window locally (the results are saved in .xlsx format by default).

  5. Click Log directory. The log directory named after an IP address is displayed, as shown in Figure 4-34. You can view the logs of a specific server based on the server IP address.

    Figure 4-34 Log directory
    NOTE:

    You can send the collected server logs to maintenance engineers for analysis.

Log Collection Items
  • Table 4-19 describes the log collection items of iBMC.
  • Table 4-20 describes the log collection items of iMana.
  • Table 4-21 describes the log collection items of Linux.
  • Table 4-22 describes the log collection items of E9000 switch module.
Table 4-19 Log collection items of iBMC

Directory

Subdirectory

File Name

File Content

/

/

dump_app_log

App information collection result list

dump_log

One-click information collection result list

AppDump

Lcd

Lcd_dfl.log

Information about managed objects

User

User_dfl.log

Information about managed objects

card_manage

card_manage_dfl.log

Information about managed objects

card_info

Mezzanine card information

BMC

BMC_dfl.log

Information about managed objects

fruinfo.txt

Information about asset tag

net_info.txt

Information about network interface configuration

PowerMgnt

PowerMgnt_dfl.log

Information about managed objects

UPGRADE

UPGRADE_dfl.log

Information about managed objects

upgrade_info

Upgrade information

BIOS

BIOS_dfl.log

Information about managed objects

bios_info

BIOS configuration information

ClpConfig0.ini

BIOS configuration information

ClpResponse0.ini

BIOS configuration information

options0.ini

BIOS configuration information

changed0.ini

BIOS configuration information

display0.ini

BIOS configuration information

diagnose

diagnose_dfl.log

Information about managed objects

diagnose_info

Port 80 information

Snmp

Snmp_dfl.log

Information about managed objects

cooling_app

cooling_app_dfl.log

Information about managed objects

fan_info.txt

Fan information

CpuMem

CpuMem_dfl.log

Information about managed objects

cpu_info

CPU information

mem_info

Dual in-line memory module (DIMM) information

kvm_vmm

kvm_vmm_dfl.log

Information about managed objects

ipmi_app

ipmi_app_dfl.log

Information about managed objects

Dft

Dft_dfl.log

Information about managed objects

sensor_alarm

sensor_alarm_dfl.log

Information about managed objects

sensor_info.txt

Sensor list

current_event.txt

Current health events

sel.tar

Compressed package of current system event logs (SELs) and historical SELs

sensor_alarm_sel.bin.md5

Integrity check code for original SELs

sensor_alarm_sel.bin.bak.md5

Integrity check code for the backup of original SELs

sensor_alarm_sel.bin.bak

Original backup information and check value of the current SELs

sensor_alarm_sel.bin

Original information and check value of the current SELs

sel.db

Database information of the current SELs

sensor_alarm_sel.bin.tar.gz

Compressed package of historical SELs.

MaintDebug

MaintDebug_dfl.log

Information about managed objects

FileManage

FileManage_dfl.log

Information about managed objects

switch_card

switch_card_dfl.log

Information about managed objects

phy_register_info

Information about PHY registers

port_adapter_info

Information about port adapters

StorageMgnt

StorageMgnt_dfl.log

RAID_Controller_Info.txt

Information about managed objects

rimm

rimm_dfl.log

Information about managed objects

dfm

dfm.log

Information about managed objects and the module

dfm_debug_log

dfm_debug_log.1

Framework debug logs

3rdDump

-

error_log

Apache error logs

access_log

Apache access logs

httpd.conf

Apache HTTP configuration file

httpd-port.conf

Apache HTTP port configuration file

httpd-ssl.conf

Apache HTTPS configuration file

httpd-ssl-port.conf

Apache HTTPS port configuration file

httpd-ssl-protocol.conf

Apache HTTPS protocol version configuration file

CoreDump

-

core-*

Memory core dump files

RTOSDump

sysinfo

cmdline

Kernel command line parameters

cpuinfo

CPU information

devices

Device information

df_info

Partition space usage information

diskstats

Partition information

filesystems

File system information

free_info

Information about memory usage

interrupts

Information about interrupts

ipcs_q

Process queue information

ipcs_q_detail

Detailed process queue information

ipcs_s

Process semaphore information

ipcs_s_detail

Detailed process semaphore information

loadavg

System operating load information

locks

List of the files currently locked by the kernel

meminfo

Memory usage information

modules

Module loading list

mtd

Partition information

partitions

Partition information

ps_info

ps -elf

Displays the process information

slabinfo

Kernel memory management slab information

stat

CPU usage

top_info

top -bn 1

Displays the current process running information

uname_info

uname -a

Displays the current kernel version

uptime

BMC system operating time

version

ROTS version

vmstat

Virtual memory statistic information

versioninfo

ibmc_revision.txt

Compilation node information

app_revision.txt

Version information

build_date.txt

Building events

fruinfo.txt

FRU electronic label information

RTOS-Release

Real-time operating system (RTOS) version information

RTOS-Revision

RTOS version markup

networkinfo

ifconfig_info

ifconfig information

ipinfo_info

IP configuration information

_data_var_dhcp_dhclient.leases

DHCP lease file

dhclient.leases

DHCP lease file

dhclient6.leases

DHCP lease file

dhclient6_eth0.leases

DHCP lease file

dhclient6_eth1.leases

DHCP lease file

dhclient6_eth2.leases

DHCP lease file

dhclient.conf

DHCP configuration file

dhclient_ip.conf

DHCP configuration file

dhclient6.conf

DHCP configuration file

dhclient6_ip.conf

DHCP configuration file

resolv.conf

DHCP configuration file

ipinfo.sh

BMC network configuration script

netstat_info

netstat -a

Displays the current network ports and connection status

route_info

route

Displays the current routing information

services

Service port information

other_info

extern.conf

Log file configuration

remotelog.conf

Syslog configuration file

ssh

SSH service configuration

sshd_config

SSHD configuration file

logrotate.status

File recording the logrotate status

login

Login pam login rules

sshd

SSH pam login rules

sfcb

CIM pam login rules

datafs_log

Data check logs

ntp.conf

NTP service configuration

driver_info

dmesg_info

dmesg information

lsmod_info

Information about loaded drivers

kbox_info

kbox information

edma_drv_info

Statistics of edma driver

cdev_drv_info

Statistics of character device driver

veth_drv_info

Statistics of virtual network card driver

LogDump

-

app_debug_log

app_debug_log.tar.gz

Application module debug logs

linux_kernel_log

linux_kernel_log.1

Linux kernel logs

card_mmio_log

card_mmio_log.tar.gz

MMIO and MMCFG configuration information about peripheral cards

diagnose_log.tar.gz

diagnose_log

Fault diagnosis and management 2.0 log files

remote_log

remote_log.1.gz

Operation logs and SEL logs for Syslog test

operate_log

operate_log.tar.gz

User operation logs

security_log

security_log.1

Security logs

strategy_log

strategy_log.tar.gz

Strategy logs

fdm_log

fdm_log.tar.gz

Fault diagnosis and management (FDM) log files

maintenance_log

Maintenance logs

ipmi_debug_log

ipmi_debug_log.tar.gz

IPMI module logs

ipmi_mass_operation_log

ipmi_mass_operation_log.tar.gz

IPMI module operation logs

app_debug_log_all

app_debug_log_all.1.gz

app_debug_log_all.2.gz

app_debug_log_all.3.gz

App debugging logs

kvm_vmm_debug_log

kvm_vmm_debug_log.tar.gz

KVM module logs

reg_info_log

reg_info_log.tar.gz

Original register information reported by the BIOS

agentless_driver_log

agentless_driver_log.1.gz

agentless_driver_log.2.gz

agentless_driver_log.3.gz

Agentless driver logs

OSDump

-

systemcom.tar

SOL serial port information

img*.jpeg

Image of the last screenshot

*.rep

Screen video file

DeviceDump

i2c_info

*_info

I2C device memory or storage area information

Register

-

cpld_reg_info

Complex programmable logical device (CPLD) register information

OptPme

pram

filelist

List of files in the /opt/pme/pram directory

BIOS_FileName

SMBIOS information

BIOS_OptionFileName

BIOS configuration information

BMC_dhclient.conf

DHCP configuration file

BMC_dhclient.conf.md5

Integrity check code

BMC_dhclient.conf.sha256

Integrity check code

BMC_dhclient6.conf

DHCP configuration file

BMC_dhclient6.conf.md5

Integrity check code

BMC_dhclient6.conf.sha256

Integrity check code

BMC_dhclient_ip.conf

DHCP configuration file

BMC_dhclient_ip.conf.md5

Integrity check code

BMC_dhclient_ip.conf.sha256

Integrity check code

BMC_dhclient6_ip.conf

DHCP configuration file

BMC_dhclient6_ip.conf.md5

Integrity check code

BMC_dhclient6_ip.conf.sha256

Integrity check code

BMC_HOSTNAME

Host name

BMC_HOSTNAME.md5

Integrity check code

BMC_HOSTNAME.sha256

Integrity check code

CpuMem_cpu_utilise

Managed object operating information

CpuMem_mem_utilise

Managed object operating information

cpu_utilise_webview.dat

Managed object operating information

env_web_view.dat

Managed object operating information

fsync_reg.ini

File synchronization configuration file

HwScan_EnvRecWave

Managed object operating information

lost+found

Folder

mdio_lock_file

mdio file lock

md_so_app_debug_log

App debugging logs

md_so_app_debug_log.tar.gz

App debugging log package

md_so_ipmi_debug_log

App debugging logs

md_so_ipmi_debug_log.tar.gz

IPMI debugging log package

md_so_maintenance_log

Maintenance logs

md_so_maintenance_log.tar.gz

Maintenance log package

md_so_mass_operate_log

User operation logs

md_so_mass_operate_log.tar.gz

User operation log package

md_so_operate_log

User operation logs

md_so_operate_log.md5

Integrity check code

md_so_operate_log.tar.gz

User operation log package

md_so_strategy_log

Policy logs

md_so_strategy_log.md5

Integrity check code

md_so_operate_log.sha256

Integrity check code

md_so_strategy_log.tar.gz

Policy log package

memory_webview.dat

Managed object operating information

NetConfig_dhclient.conf

DHCP configuration file

NetConfig_dhclient.conf.md5

Integrity check code

md_so_strategy_log.sha256

Integrity check code

NetConfig_dhclient_ip.conf

DHCP configuration file

NetConfig_dhclient_ip.conf.md5

Integrity check code

per_config.ini

BMC configuration persistence file

per_config.ini.md5

Integrity check code

per_config.ini.sha256

Integrity check code

per_config_permanent.ini

BMC configuration persistence file

per_config_permanent.ini.md5

Integrity check code

per_config_permanent.ini.sha256

Integrity check code

per_config_reset.ini

BMC configuration persistence file

per_config_reset.ini.bak

BMC configuration persistence file

per_config_reset.ini.bak.md5

Integrity check code

per_config_reset.ini.bak.sha256

Integrity check code

per_config_reset.ini.md5

Integrity check code

per_config_reset.ini.sha256

Integrity check code

per_def_config.ini

BMC configuration persistence file

per_def_config.ini.md5

Integrity check code

per_def_config.ini.sha256

Integrity check code

per_def_config_permanent.ini

BMC configuration persistence file

per_def_config_permanent.ini.md5

Integrity check code

per_def_config_permanent.ini.sha256

Integrity check code

per_def_config_reset.ini

BMC configuration persistence file

per_def_config_reset.ini.bak

BMC configuration persistence file

per_def_config_reset.ini.bak.md5

Integrity check code

per_def_config_reset.ini.bak.sha256

Integrity check code

per_def_config_reset.ini.md5

Integrity check code

per_def_config_reset.ini.sha256

Integrity check code

per_power_off.ini

BMC configuration persistence file

per_power_off.ini.md5

Integrity check code

per_power_off.ini.sha256

Integrity check code

per_reset.ini

BMC configuration persistence file

per_reset.ini.bak

BMC configuration persistence file

per_reset.ini.bak.md5

Integrity check code

per_reset.ini.bak.sha256

Integrity check code

per_reset.ini.md5

Integrity check code

per_reset.ini.sha256

Integrity check code

pflash_lock

Flash file lock

PowerMgnt_record

Managed object operating information

powerview.txt

Power statistic file

proc_queue

Process queue ID folder

ps_web_view.dat

Managed object operating information

sel.db

SEL database

sel_db_sync

SEL database synchronization lock

semid

Process semaphore ID folder

sensor_alarm_sel.bin

Original SEL file

sensor_alarm_sel.bin.md5

Integrity check code

sensor_alarm_sel.bin.sha256

Integrity check code

sensor_alarm_sel.bin.tar.gz

Package of historical SEL files

Snmp_http_configure

HTTP Server configuration file

Snmp_http_configure.md5

Integrity check code

Snmp_http_configure.sha256

Integrity check code

Snmp_https_configure

HTTP Server configuration file

Snmp_https_configure.md5

Integrity check code

Snmp_https_configure.sha256

Integrity check code

Snmp_https_tsl

HTTP Server configuration file

Snmp_https_tsl.md5

Integrity check code

Snmp_https_tsl.sha256

Integrity check code

Snmp_snmpd.conf

SNMP configuration file

Snmp_snmpd.conf.md5

Integrity check code

Snmp_snmpd.conf.sha256

Integrity check code

up_cfg

Upgrade configuration folder

User_login

Login pam login rules

User_login.md5

Integrity check code

User_login.sha256

Integrity check code

User_sshd

SSH pam login rules

User_sshd.md5

Integrity check code

User_sshd.sha256

Integrity check code

User_sshd_config

SSH service configuration file

User_sshd_config.md5

Integrity check code

User_sshd_config.sha256

Integrity check code

User_vsftp

FTP pam login rules

User_vsftp.md5

Integrity check code

User_vsftp.sha256

Integrity check code

eo.db

SEL database

save

filelist

List of files in the /opt/pme/pram directory

BIOS_FileName

SMBIOS information

BMC_dhclient.conf.bak

DHCP configuration file

BMC_dhclient.conf.bak.md5

Integrity check code

BMC_dhclient.conf.bak.sha256

Integrity check code

BMC_dhclient.conf.md5

Integrity check code

BMC_dhclient.conf.sha256

Integrity check code

BMC_dhclient6.conf.bak

DHCP configuration file

BMC_dhclient6.conf.bak.md5

Integrity check code

BMC_dhclient6.conf.bak.sha256

Integrity check code

BMC_dhclient6.conf.md5

Integrity check code

BMC_dhclient6.conf.sha256

Integrity check code

BMC_dhclient_ip.conf.bak

DHCP configuration file

BMC_dhclient_ip.conf.bak.md5

Integrity check code

BMC_dhclient_ip.conf.bak.sha256

Integrity check code

BMC_dhclient_ip.conf.md5

Integrity check code

BMC_dhclient_ip.conf.sha256

Integrity check code

BMC_dhclient6_ip.conf.bak

DHCP configuration file

BMC_dhclient6_ip.conf.bak.md5

Integrity check code

BMC_dhclient6_ip.conf.bak.sha256

Integrity check code

BMC_dhclient6_ip.conf.md5

Integrity check code

BMC_dhclient6_ip.conf.sha256

Integrity check code

BMC_HOSTNAME.bak

Host name

BMC_HOSTNAME.bak.md5

Integrity check code

BMC_HOSTNAME.bak.sha256

Integrity check code

BMC_HOSTNAME.bak.md5

Integrity check code

BMC_HOSTNAME.sha256

Integrity check code

BMC_HOSTNAME.md5

Integrity check code

CpuMem_cpu_utilise

Managed object operating information

CpuMem_mem_utilise

Managed object operating information

HwScan_EnvRecWave

Managed object operating information

md_so_operate_log.bak

User operation logs

md_so_operate_log.bak.md5

Integrity check code

md_so_operate_log.bak.sha256

Integrity check code

md_so_operate_log.md5

Integrity check code

md_so_operate_log.sha256

Integrity check code

md_so_strategy_log.bak

Policy logs

md_so_strategy_log.bak.md5

Integrity check code

md_so_strategy_log.bak.sha256

Integrity check code

md_so_strategy_log.md5

Integrity check code

md_so_strategy_log.sha256

Integrity check code

NetConfig_dhclient.conf.bak

DHCP configuration file

NetConfig_dhclient.conf.bak.md5

Integrity check code

NetConfig_dhclient.conf.md5

Integrity check code

NetConfig_dhclient_ip.conf.bak

DHCP configuration file

NetConfig_dhclient_ip.conf.bak.md5

Integrity check code

NetConfig_dhclient_ip.conf.md5

Integrity check code

per_config.ini

BMC configuration persistence file

per_config.ini.bak

BMC configuration persistence file

per_config.ini.bak.md5

Integrity check code

per_config.ini.bak.sha256

Integrity check code

per_config.ini.md5

Integrity check code

per_config.ini.sha256

Integrity check code

per_def_config.ini

BMC configuration persistence file

per_def_config.ini.bak

BMC configuration persistence file

per_def_config.ini.bak.md5

Integrity check code

per_def_config.ini.bak.sha256

Integrity check code

per_def_config.ini.md5

Integrity check code

per_def_config.ini.sha256

Integrity check code

per_power_off.ini

BMC configuration persistence file

per_power_off.ini.bak

BMC configuration persistence file

per_power_off.ini.bak.md5

Integrity check code

per_power_off.ini.bak.sha256

Integrity check code

per_power_off.ini.md5

Integrity check code

per_power_off.ini.sha256

Integrity check code

PowerMgnt_record

Managed object operating information

sensor_alarm_sel.bin

Original SEL file

sensor_alarm_sel.bin.bak

Original SEL file

sensor_alarm_sel.bin.bak.md5

Integrity check code

sensor_alarm_sel.bin.bak.sha256

Integrity check code

sensor_alarm_sel.bin.md5

Integrity check code

sensor_alarm_sel.bin.sha256

Integrity check code

sensor_alarm_sel.bin.tar.gz

Historical SEL package

Snmp_http_configure.bak

HTTP Server configuration file

Snmp_http_configure.bak.md5

Integrity check code

Snmp_http_configure.bak.sha256

Integrity check code

Snmp_http_configure.md5

Integrity check code

Snmp_http_configure.sha256

Integrity check code

Snmp_https_configure.bak

HTTP Server configuration file

Snmp_https_configure.bak.md5

Integrity check code

Snmp_https_configure.bak.sha256

Integrity check code

Snmp_https_configure.md5

Integrity check code

Snmp_https_configure.sha256

Integrity check code

Snmp_https_tsl.bak

HTTP Server configuration file

Snmp_https_tsl.bak.md5

Integrity check code

Snmp_https_tsl.bak.sha256

Integrity check code

Snmp_https_tsl.md5

Integrity check code

Snmp_https_tsl.sha256

Integrity check code

Snmp_snmpd.conf.bak

SNMP configuration file

Snmp_snmpd.conf.bak.md5

Integrity check code

Snmp_snmpd.conf.bak.sha256

Integrity check code

Snmp_snmpd.conf.md5

Integrity check code

Snmp_snmpd.conf.sha256

Integrity check code

User_login.bak

Login pam login rules

User_login.bak.md5

Integrity check code

User_login.bak.sha256

Integrity check code

User_login.md5

Integrity check code

User_login.sha256

Integrity check code

User_sshd.bak

SSH pam login rules

User_sshd.bak.md5

Integrity check code

User_sshd.bak.sha256

Integrity check code

User_sshd.md5

Integrity check code

User_sshd.sha256

Integrity check code

User_sshd_config.bak

SSH service configuration file

User_sshd_config.bak.md5

Integrity check code

User_sshd_config.bak.sha256

Integrity check code

User_sshd_config.md5

Integrity check code

User_sshd_config.sha256

Integrity check code

User_vsftp.bak

FTP pam login rules

User_vsftp.bak.md5

Integrity check code

User_vsftp.bak.sha256

Integrity check code

User_vsftp.md5

Integrity check code

User_vsftp.sha256

Integrity check code

eo.db

SEL database

eo.db.md5

Integrity check code

eo.db_backup

SEL database

eo.db.md5_backup

Integrity check code

NOTE:

The number of collected log files and log file content vary according to the iBMC version. For details, see the iBMC User Guide.

Table 4-20 Log collection items of iMana

Directory

Subdirectory

File Name

File Content

log

RunTime.log

One-click information collection tool run logs

maintenance

bmcstartup.txt

Startup logs

bmcconfiginfo

bmcconfiginfo.txt

iMana configuration information

entity.txt

Sensor entity information

sensor.txt

Sensor entity information

hardwareinfo

bmchardwareinfo.txt

Hardware information

networkinfo

bmcnetworkinfo.txt

Network information

oplog

imana_dbglog

Error logs

imana_fdmlog

Fault diagnosis logs

imana_maintainlog

Maintenance logs

imana_oplog

Operation logs

selinfo

_sel.csv

System events

sysinfo

ldap_auth.conf

LDAP configuration information

ldapgroup.conf

LDAP group configuration information

versioninfo

bmcversioninfo.txt

iMana firmware version information

configinfo

_data_blacklist

ipmcset and ipmcget blacklisted subcommands

_data_cli.conf

Command line configuration information

_data_conf_pcap.conf

Power capping configuration information

_data_conf_systeminfo.conf

CPU, memory, and hard disk usage thresholds reported by the BMA

_data_conf_umconfig.txt

Web configuration information

_data_conf_web_customconfig.ini

Customized web information

_data_etc_bmc_ntp.conf

Network time synchronization configuration information

_data_etc_ddns.conf

Dynamic DNS configuration information

_data_etc_dhclient.conf

DHCP configuration information

_data_etc_dhclient6.conf

DHCP configuration information

_data_etc_dhclient6_ip.conf

DHCP configuration information

_data_etc_dhclient_ip.conf

DHCP configuration information

_data_etc_group

User group information

_data_etc_hostname

Host name information

_data_etc_ipmi.conf

RMCP service enablement status and port configuration information

_data_etc_kvm.conf

KVM service enablement status and port configuration information

_data_etc_openldap_ldap.conf

LDAP configuration information

_data_etc_openldap_slapd.conf

OpenLDAP configuration information

_data_etc_openwsman.conf

WSMan service enablement status and port configuration information

_data_etc_pam.d_login

Login configuration information

_data_etc_pam.d_sshd

SSH login configuration information

_data_etc_pam.d_vsftpd

FTP login configuration information

_data_etc_resolv.conf

DNS resolution configuration information

_data_etc_restore.sh

Manufacturing information backup point

_data_etc_service.conf

Service enablement status configuration information

_data_etc_services

System port information

_data_etc_sfcb.cfg

SNMP configuration information

_data_etc_ssh_sshd_config

SSH configuration information

_data_etc_ssl_openssl.cnf

OpenSSL configuration information

_data_etc_sysctl.conf

Linux kernel configuration information

_data_etc_video.conf

Video service enablement status and port configuration information

_data_etc_vmm.conf

VMM service enablement status and port configuration information

_data_etc_xinetd.d_ftp

FTP login configuration information

_data_etc_xinetd.d_ssh

SSH login configuration information

_data_etc_xinetd.d_telnet

Login configuration information

_data_flash.bin

RMCP workload information

_data_ipmc.d_DeviceRelation.conf

Silkscreen information

_data_ipmc.d_UIP_product.conf

UIP web configuration information about hardware

_data_ipmc.d_bmcproductweb.ini

Web display configuration information

_data_ipmc.d_ldap_auth.conf

LDAP user configuration information

_data_ipmc.d_ldapgroup.conf

LDAP user group configuration information

_data_ipmc.d_menulist.ini

Web page link information

_data_log_fsync_log

Module logs

_data_log_ipmidbg_log

Module logs

_data_log_kvm_log

Module logs

_data_log_snmp_log

Module logs

_data_log_video_log

Module logs

_data_log_vmm_log_file

Module logs

_data_log_web_log

Module logs

_data_mib_indexes_0

SNMP MIB configuration information

_data_pef_v1_0_0.bin

Event filtering configuration information

_data_powerStatistic

Power statistics configuration information

_data_powerview

Power statistics

_data_save_shutdown_file_backup_bmc_ntp.conf

Network time synchronization configuration information backup

_data_save_shutdown_file_backup_ddns.conf

Dynamic DNS configuration information backup

_data_save_shutdown_file_backup_dhclient.conf

DHCP configuration information backup

_data_save_shutdown_file_backup_dhclient6.conf

DHCP configuration information backup

_data_save_shutdown_file_backup_dhclient6_ip.conf

DHCP configuration information backup

_data_save_shutdown_file_backup_dhclient_ip.conf

DHCP configuration information backup

_data_save_shutdown_file_backup_group

User group information backup

_data_save_shutdown_file_backup_hostname

Host name backup

_data_save_shutdown_file_backup_ldapgroup.conf

LDAP user information backup

_data_save_shutdown_file_backup_ldap_auth.conf

LDAP user group information backup

_data_save_shutdown_file_backup_login

Login configuration information backup

_data_save_shutdown_file_backup_sshd

SSH login configuration information backup

_data_save_shutdown_file_backup_umconfig.txt

Web configuration information backup

_data_save_shutdown_file_backup_varlist

Variable configuration information backup

_data_save_shutdown_file_backup_vsftpd

vsftp login configuration information backup

_data_sdr0.bin

Sensor SDR configuration information

_data_sectbl.cfg

Event parsing configuration information

_data_smbios_display0.ini

Setup configuration information reported by the BIOS

_data_smbios_options0.ini

Setup configuration information reported by the BIOS

_data_smbios_smbios0

SMBIOS information reported by the BIOS

_data_usr_script_ddns_config.sh

One-click information collection script

_data_usr_script_dhupdate.sh

One-click information collection script

_data_usr_script_user_config.sh

One-click information collection script

_data_uuser_group

User group information

_data_var_db_dhclient.leases

DHCP client configuration information

_data_var_db_dhclient6.leases

DHCP client configuration information

_data_var_db_dhclient6_eth1.leases

DHCP client configuration information

_data_var_log_dmesg

Power-on information

_data_var_log_lastlog

Last login time

_data_var_log_wsmand.log

WSMan use records

_data_var_log_xferlog

FTP use records

_data_varlist

Variable configuration information

_proc_cmdline

Kernel startup command line

_proc_cpuinfo

CPU information

_proc_devices

Main device numbers and names of character and block devices

_proc_diskstats

Flash memory block status

_proc_filesystems

Supported file system types

_proc_interrupts

Interrupt information

_proc_loadavg

Average system workloads

_proc_locks

Lock information of opened files

_proc_meminfo

Memory status

_proc_modules

Information about kernel modules that can be loaded

_proc_mtd

System hard disk partitioning information

_proc_partitions

Hard disk information

_proc_slabinfo

Memory pool status

_proc_uptime

Duration from the last uptime to the current time

_proc_version

Running kernel version

_proc_vmstat

Virtual memory statistics

NOTE:

The number of collected log files and log file content vary according to the iMana version. For details, see the HUAWEI Server iMana 200 User Guide.

Table 4-21 Log collection items of Linux

Module

Log File

Command

Description

Common

version.txt

-

InfoCollect version and release time

filelist.txt

-

List of collected files

detail.html

-

Collected log files and description of each file

BIOS

version_bios.txt

dmidecode -t bios

BIOS version

BigData

selfdiag_log.txt

/opt/DA200/compress_tools/tools/dcadm selfdiag

DA200 selfdiag information (the DA200 tool is required)

Lspci_log.txt

lspci|grep d501

Model information

/var/log/DA200/

cp /var/log/DA200/

DA200 log information

/var/log/bigdata/

cp /var/log/bigdata/

DA200 log information

BMC

fru.txt

ipmitool fru list

Field replaceable unit (FRU) information

bmc_lan.txt

ipmitool lan print 1

BMC NIC information

mc_info.txt

ipmitool mc info

BMC version

sensor.csv

ipmitool sensor list

All sensor information

sdr.csv

ipmitool sdr list

Sensor data record (SDR) log file

sel.csv

ipmitool sel elist

BMC system event log (SEL)

version_cpld.txt

ipmitool raw0x30 0x90 0x08 0 2 0x00 0x10

CPLD version

time.txt

BMC time bios time OS time

BMC, BIOS, and OS time

BMA

common.log

cat /opt/huawei/ibma/log/common.log

General logs

http_server.log

cat /opt/huawei/ibma/log/http_server.log

HTTP server logs

iBMC_event.log

cat /opt/huawei/ibma/log/iBMC_event.log

BMC event logs

nicErrorStatistics.log

cat /opt/huawei/ibma/log/nicErrorStatistics.log

NIC fault data

runlog

cat /opt/huawei/ibma/log/runlog

Operation-related run logs

service.log

cat /opt/huawei/ibma/log/service.log

iBMA service-related logs

CPU

cpuinfo.txt

cat /proc/cpuinfo

CPU model and frequency

cpu_dmidecode.txt

dmidecode -t processor

CPU information obtained by running the dmidecode command

Disk

disk_smart.txt

smartctl -a /dev/sd*

smartctl -a --device=sat+megaraid,0 /dev/sd*

smartctl -a --device=megaraid,0 /dev/sd*

hwdiag -t disk -s

Hard disk SMART information (the smartctl tool is required)

sys_block.txt

ls -l /sys/block/sd*

Hard disk names

parted_disk.txt

parted /dev/sda print

Partition information of physical hard disks

hwdiag_hdd.txt

hwdiag -t disk -d

Hard disk scores offered by iBMA (applicable only to an OS running iBMA)

es3000_v2.txt

hio_info -d --device=hioa,/dev/hio*

hio_label -d --device=hioa,/dev/hio*

hio_log -d --device=hioa,/dev/hio*

hio_temperature -d --device=hioa,/dev/hio*

ES3000 V2 PCIe SSD information

es3000_v3.txt

modinfo nvme

hioadm info -d device=nvme0,hioadm info

hioadm info -d device=nvme,hioadm info -s

hioadm info -d device=nvme,hioadm info -a

hioadm log -d device=nvme0,hioadm info -a

ES3000 V3 NVMe PCIe SSD information

Mainboard

dmidecode.txt

dmidecode

Hardware information

lspci.txt

lspci

Peripheral Component Interconnect (PCI) device list

lspci -xxx -vvv -t

Detailed PCI device information

lspci -xxxx -vvv -b

Bus-related PCI and interrupt request (IRQ) device information

NIC

lspci_eth.txt

lspci |grep Ethernet

NIC list

ifconfig.txt

ifconfig -a

Configurations of all NICs

/etc/modprobe.d

/etc/modprobe.d/

NIC configuration file

ethtool.txt

ethtool ethX

NIC settings

ethtool -i ethX

ethtool -S ethX

ethtool -g ethX

ethtool -k ethX

/etc/sysconfig/network/*

cp /etc/sysconfig/network/*

NIC configuration files on SLES

/etc/sysconfig/network-scripts/*

cp /etc/sysconfig/network-scripts/*

NIC configuration files on RHEL

netstat.txt

netstat -i -n

Network port status

netstat -avn

netstat -s

netstat -rvn

mezz_info.tar.gz

/bin/date

collect_info/network.txt: NIC information.

mezz.log: running log of mezz_collect.sh.

/usr/bin/uptime

dmidecode

biosdecode

lspci -tv

ifconfig -a

/sbin/ip link show

/sbin/route -n

ethtool -i ethX

ethtool ethX

ethtool -a ethX

ethtool -l ethX

ethtool -d ethX

ethtool -e ethX

ethtool -S ethX

ethtool -g ethX

ethtool -k ethX

/sbin/lspci -xxx -s XX:XX.X

lspci -vvvv -xxx -s XX:XX.X

/bin/netstat -nlp

/bin/netstat -nr

/bin/netstat -i

/sbin/arp -v

/usr/sbin/iptables -t

filter -nvL

x86tool -r pci/bXX:XX.X-0xXXXXX+4-bX

bonding.txt

cp /proc/net/bonding/

NIC binding information

bdf.txt

Ls –l /sys/class/net

NIC BDF information

error_frame_crc.txt

cat /sys/class/net/*/statistics/rx_crc_errors

cat /sys/class/net/*/statistics/rx_frame_errors

NIC error frame and port error code information

Host bus adapter (HBA)

lspci_fc.txt

lspci |grep Fibre

Fibre Channel (FC) models

firmware_fc.txt

cat /sys/class/scsi_host/host*/fwrev

cat /sys/class/scsi_host/host*/fw_version

FC HBA firmware information

driver_fc.txt

cat /sys/class/scsi_host/host*/lpfc_drvr_version

cat /sys/class/scsi_host/host*/driver_version

FC HBA driver information

wwpn.txt

cat /sys/class/fc_host/host*/port_name

cat /sys/class/fc_host/host*/node_name

FC HBA WWPN and WWNN information

bdf.txt

ls –l /sys/class/fc_host/

ls –l /sys/class/iscsi

iSCSI and FC HBA BDF information

error_frame_crc.txt

cat /sys/class/fc_host/host*/statistics/error_frames

cat /sys/class/fc_host/host*/statistics/invalid_crc_count

FC HBA port error code and error frame information

port_state.txt

cat /sys/class/fc_host/host*/port_state

FC HBA port status information

Driver

lsmod.txt

lsmod

Loaded module information

modinfo.txt

modinfo

Driver information of a specific module

Memory

meminfo

/proc/meminfo

Memory information

mem_ecc.txt

mcelog --client

Memory error checking and correcting (ECC) information (empty by default)

memory_dmidecode.txt

dmidecode -t memory

Physical memory information

memory_free.txt

free

Used and available memory space

hwdiag_mem.txt

hwdiag -t mem -d

Memory diagnosis data offered by iBMA (applicable only to an OS running iBMA)

RAID controller card

sashbalog.txt

sas2flash

LSI SAS2308 or LSI SAS3008 controller card log file

sasraidlog.txt

storcli

LSI SAS2208, LSI SAS3108, Avago SAS3408 or Avago SAS3508 controller card log file

diskmap.txt

lsscis

opt/MegaRAID/storcli/storcli c* show

Mapping relationships between logical disks and physical disks of the LSI SAS2208, LSI SAS3108, Avago SAS3408 or Avago SAS3508 RAID controller card

System

runlog

Background running records of the tool

InfoCollect run log file

/var/log/secure

cp /var/log/secure*

Security log files

/var/log/mcelog

cp /var/log/mcelog*

Log files required for locating machine check exceptions (MCEs)

/var/log/message

cp /var/log/message*

General system log files

/var/log/cron

/var/log/cron*

Customized task log files

/var/log/boot.log

/var/log/boot.log

.log file that records information about the current startup process

/var/log/boot.msg

/var/log/boot.msg

.msg file that records information about the current startup process

/var/log/boot.omsg

/var/log/boot.omsg

Log file that records information about the previous startup process

/etc/syslog.conf

/etc/syslog.conf

Configuration file of the syslogd process

/etc/resolv.conf

/etc/resolv.conf

Configuration file of the network proxy

/etc/hosts

/etc/hosts

Host information

/etc/services

/etc/services

OS boot service information

/etc/sysctl.conf

/etc/sysctl.conf

System kernel parameter configuration file, involving network functions, for example, forwarding

/etc/inittab

/etc/inittab

Initialization, involving system configuration

/etc/ntp.conf

/etc/ntp.conf

Network Time Protocol (NTP) configuration file

/etc/ntp/step-tickers

/etc/ntp/step-tickers

NTP configuration file

/etc/ntp/ntpservers

/etc/ntp/ntpservers

NTP server list

/etc/yp.conf

/etc/yp.conf

ypbind configuration file

/etc/fstab

/etc/fstab

File system list

/proc/interrupts

/proc/interrupts

Number of interrupts

/proc/filesystems

/proc/filesystems

Current file system list

/etc/exports

/etc/exports

Network File System (NFS) server configuration

/proc/self/maps

/proc/self/maps

Virtual address space of processes

/proc/self/smaps

/proc/self/smaps

Memory usage of each process

/proc/self/numa_maps

/proc/self/numa_maps

Memory usage of the numa process

/proc/iomap

/proc/iomap

Memory space address segment mapping to I/O ports

/proc/ioports

/proc/ioports

Distribution of I/O ports in use

/proc/swaps

/proc/swaps

Swap partition information

/proc/slabinfo

/proc/slabinfo

Kernel information

/proc/locks

/proc/locks

Locked processes

/proc/modules

/proc/modules

All modules

/proc/mounts

/proc/mounts

Mounted devices

/proc/version

/proc/version

Kernel version

/proc/stat

/proc/stat

Kernel and system statistics

/proc/schedstat

/proc/schedstat

Kernel information about the schedstat process

/proc/zoneinfo

/proc/zoneinfo

Kernel time zone information

/proc/config.gz

/proc/config.gz

Configuration files of the proc file system

/proc/kallsyms

proc/kallsyms

Kernel debugging files

/proc/mtrr

/proc/mtrr

Memory Type Range Register (MTRR) information

/proc/vmstat

/proc/vmstat

Virtual memory status

/proc/buddyinfo

/proc/buddyinfo

Memory fragment information

/proc/cmdline

/proc/cmdline

Kernel startup CLI information

/proc/devices

/proc/devices

Device drivers

/proc/diskstats

/proc/diskstats

Hard disk status

/proc/iomem

/proc/iomem

Physical address allocation

/proc/dma

/proc/dma

Direct memory access (DMA) channel information

/boot/config*

/boot/config*

Kernel configuration files

/etc/grub.conf

/etc/grub.conf

Grand Unified Boot Loader (GRUB) configuration file

/boot/grub/device.map

/boot/grub/device.map

Boot device mapping information

/boot/grub/menu.lst

/boot/menu.lst

Boot menu file

/boot/grub2/grub.cfg

/boot/grub2/grub.cfg

Grub2 information

dump_list.txt

du -ah /var/crash/

Crash file list

dmesg.txt

dmesg

Dmesg file

/root/.bash_history

/root/.bash_history

Historical commands executed

command_log.txt

df -liT

Available disk space

mount

Mounting information

/usr/bin/last -xF | grep "reboot\|shutdown\|runlevel\|system"

Reboot records

nfsstat -cnrs

NFS service status

lsof

List of opened files

ulimit -a

System resource restrictions

ipcs -a

Status of communication facilities between processes

ipcs -l

Shared information memory

sysctl -a

Sysctl settings and kernel parameters in /proc/sys

uptime

Operating duration

uname -a

Kernel information

ps auwx

List of all processes

last

Historical login user records

hostid

Login user IDs

/bin/rpm -qa

List of installed software

printenv

Environment variables

hostname

Host names

/var/log/kern*

cp /var/log/kern*

Kern log information

/var/log/dmesg*

cp /var/log/dmesg*

Dmesg log information

/var/log/syslog*

cp /var/log/syslog*

Syslog log information

SLES

nts_$(hostname)_$(time).tbz

supportconfig (SLES)

Log file collection package for fault diagnosis on SLES

nts_$(hostname)_$(time).tbz.md5

supportconfig (SLES)

Verification code of the log file collection package for fault diagnosis on SLES

sosreport (the sosreport software is required)

sosreport-$(hostname)_$(time).tar.xz

sosreport --batch

Log collection suite for RHEL, CentOS and Ubuntu locating

sosreport-$(hostname)_$(time).tar.xz.md5

sosreport --batch

Verification code of the log collection suite for RHEL, CentOS and Ubuntu locating

NOTE:

The number of collected log files and log file content vary according to the Linux version.

Table 4-22 Log collection items of E9000 Switch module

File

Command

Description

diag-info.txt

display diagnostic-information diag-info.txt

Display information

diagnostic_information.zip

collect diagnostic information

Diagnosis log file

log.log

-

Operation log

diag.log

-

Run log

Configuring IP Address Information

Scenarios

Use uMate to configure IP address information in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • The iBMC version needs to be later than 2.90.
  • This function is not supported if uMate runs on Windows Server 2008, Windows Server 2012, or Windows Server 2016.
Prerequisites

Conditions

  • An IPv6 address is required for a PC, and the address must communicate with the BMC of which an IP address is to be configured. Ensure that the IPMI communication port is connected and the server BMC IP address can be pinged.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data is required for IP address information configuration:
  • IP address, MAC address, and SN of the server BMC management network port
  • User name and password of the server BMC
Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-35.

    Figure 4-35 uMate main window

  2. Click IP Config.

    The configuration main window is displayed, as shown in Figure 4-36.

    Figure 4-36 Configuration main window

  3. Set parameters. Table 4-23 describes the parameters.

    Table 4-23 Parameter description

    Parameter

    Description

    Value

    Remarks

    Connection Type

    Specifies the BMC connection type.

    • Connect directly: The PC is directly connected to the BMC.
    • Connect through switch: The PC is connected to the BMC through a switch.
    • For direct connection, you need to connect a network cable to the local PC.
    • The BMC of the current server and the BMC of the target server must be in the same LAN. The BMCs can be connected across a switch, and the switch supports IPv6.

    Config File

    Enters configuration information directly or import configuration information manually.

    • Enter configuration information directly:

      Click Add and enter configuration information in the list.

    • Import configuration information manually:

      If no template file is available, click Template to generate a template file, save the file to the local PC, edit the file, and click Import to import the file.

    • The configuration file can be in .xls or .xlsx format.
    • You must set IPv4 (columns 6 to 9), IPv6 (columns 10 to 13), or HostName (column 14). These three parts are the items to be modified.
    • If IPv4 or IPv6 is specified, the IP address mode must be static or dhcp. If the IP address mode is set to static, you must set the IP address, mask, prefix, and gateway.
    • When the connection is established through a switch, the MAC address or SN must be set. When the connection is established directly, either the SN, MAC address, or default IP address must be set. If all the three parameters are set, the system preferentially searches for and configures the server based on the MAC address. If the MAC address is not specified, the system searches for and configures the server based on the SN. If neither the MAC address nor SN is specified, the system searches for and configures the server based on the default IP address.
    • The user name and password are mandatory.

    Config Control

    Performs related operations on the configuration content.

    • Click Add to add a configuration record.
    • Click Delete to delete one or more configuration records.
    • Click Start to start the configuration.
    • Click Stop to stop or interrupt the configuration.

    After a record is added or deleted, you can view the result in the list.

  4. Click Start to start the configuration.

    After the configuration is successful, a dialog box is displayed, indicating that the configuration is successful.

    When the BMC connection type is direct connection, the dialog box shown in

    Figure 4-37 is displayed. When the BMC connection type is connection through a switch, the dialog box shown in Figure 4-38 is displayed.

    Figure 4-37 Dialog box indicating that the configuration is successful (1)
    Figure 4-38 Dialog box indicating that the configuration is successful (2)

Checking the Server Configuration

Scenarios

Use uMate to check the server configuration in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • You are advised to check the server configuration on one server. If the server configuration check task is successful, perform a batch server configuration check. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
Prerequisites

Conditions

Data

The following data is required for a server configuration check:

  • IP address of the server BMC management network port
  • User name and password of the server BMC
Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-39.

    Figure 4-39 uMate main window
    NOTE:

    When the pointer is moved over Config Check, the function description is displayed in the right pane.

    Config Check

    • iBMC Config Check
    • BIOS Config Check
    • RAID Config Check

  2. Click Config Check.

    The main window for a configuration check is displayed, as shown in Figure 4-40.

    Figure 4-40 Main window for a configuration check

    You can click Advanced... to view more parameters. For details, see Table 4-24.

    Table 4-24 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the management module IP address of the start server of the query.

    IP address of the BMC. The IP address indicates only the IPv4 address.

    End IP

    Specifies the management module IP address of the end server of the query.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the administrator user name of the BMC.

    -

    Password

    Specifies the administrator password of the BMC.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Root Password

    Specifies the password of user root.

    You need to enter the password of user root when you perform operations on Linux as a non-root user.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  3. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC IP address and the user name and password (for details, see Table 4-24), as shown in Figure 4-41.
        Figure 4-41 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-42.
        Figure 4-42 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  4. Click Next.

    The window for discovering a server is displayed, as shown in Figure 4-43.

    Figure 4-43 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-44.

    Figure 4-44 Discovering servers successfully

  5. Click Next.

    Select the servers and configuration modules for obtaining the configuration information, as shown in Figure 4-45.

    Figure 4-45 Selecting servers and configuration modules
    NOTE:
    • By default, all servers of which the type is V5 and the last three columns are selected.
    • Select at least one server and one configuration module of the server need to be selected. The configuration modules are described as follows:
      • iBMC: obtains the iBMC configuration information of the current server.
      • BIOS: obtains the BIOS configuration information of the current server.
      • RAID: obtains the RAID configuration information of the current server. Before selecting this option, ensure that RAID has been configured on the server. Otherwise, the configuration information may fail to be obtained. RAID controller cards in out-of-band management mode are supported. SoftRAID configuration checks are not supported.

  6. Click Next.

    The window for obtaining configuration information is displayed, as shown in Figure 4-46.

    Figure 4-46 Window for obtaining configuration information
    NOTE:

    You can click Stop to stop an obtaining task.

    The server configuration information is obtained, as shown in Figure 4-47.

    Figure 4-47 Configuration information obtained

    Select one or more servers of which the configuration module execution progress is 100%, and click Next.

  7. Select iBMC, BIOS, and RAID standard files.

    • Select Select a device, and select a server of which the configuration information is successfully obtained in Step 6 as the standard server, as shown in Figure 4-48.
      NOTE:

      If you use this mode to set a standard, at least two servers must be detected successfully.

      Figure 4-48 Selecting a standard server
    • Import a file as the standard file, as shown in Figure 4-49.
      NOTE:

      If you use this mode to set a standard, at least one server must be detected successfully.

    Figure 4-49 Selecting a configuration file

    The files to be imported for the modules are described as follows:

    • iBMC:

      Import config file: Click Select, and import the Config.xml standard file.

    • BIOS:

      Import config file: Click Select, and import the currentvalue.json standard file.

      Import template file: Click Select, and import the registry.json template file.

    • RAID:

      Import config file: Click Select, and import the currentRaidvalue.json standard file.

    NOTE:
    • The server shown in Figure 4-49 is used as an example. The path of the standard file is D:\FusionServer Tools-uMate-Win-V149\work\ConfigCheck.
    • To ensure data uniqueness, do not modify the formats of configuration items in the standard files to be imported.
    • Select at least one standard type.

  8. Click Next.

    The window for displaying template configuration information is displayed. Select check items as required, as shown in Figure 4-50.

    • If you select Select ALL Config, all configuration items of the iBMC, BIOS, and RAID will be selected and compared.
    • If you select Select ALL, all configuration items of the iBMC, BIOS, and RAID will be compared respectively.
    NOTE:
    • You may need to wait a few seconds after clicking Next.
    • Select at least one configuration item for the comparison.
    Figure 4-50 Selecting check items

  9. Click Next.

    The window for displaying comparison results is displayed, as shown in Figure 4-51.

    By default, the configuration information comparison table on the Summary table tab is displayed. To view details, click the Detail information table tab.

    NOTE:

    In Detail information table, if the value of ServerValue is --, the server does not have this configuration item.

    Figure 4-51 Window for displaying comparison results
    • Click report table directory to go to the work/CofigCheck directory. In the directory, you can view the configuration comparison summary table Summary Table.csv and detailed configuration comparison tables iBMC Table.csv, BIOS Table.csv, and RAID Table.csv that are generated automatically.
    • Click Export Summary table.csv to export the configuration comparison summary table.
    • Click Export iBMC table.csv to export the detailed iBMC configuration comparison table.
    • Click Export BIOS table.csv to export the detailed BIOS configuration comparison table.
    • Click Export RAID table.csv to export the detailed RAID configuration comparison table.

Upgrading Server Firmware

Upgrading Server Firmware by Using the BMC
Scenarios

Use uMate to upgrade the server BMC, BIOS, mainboard CPLD as well as rack server PSUs by using the BMC in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • You are advised to upgrade the firmware on one server. If the upgrade is successful, perform batch firmware upgrades. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • If a server discovery failure or file upload failure occurs, reset the BMC and perform the upgrade again.
  • Before upgrading the rack server PSU firmware, ensure that the server has two PSUs and both of them are powered on.
  • If multiple types of servers (rack and high-density) and firmware need to be upgraded at the same time, you can create a software package. For details about the supported server models, see Compatibility List. For details about how to create a software package, see step 1 in Upgrading Rack Server Firmware by Using a Package.
  • For a 2-socket server, if the BIOS is rolled back from V087 to an earlier version, disconnect and then reconnect the AC power supply to make the target version take effect. For a 4-socket server, if the BIOS is rolled back from V099 to an earlier version, disconnect and then reconnect the AC power supply to make the target version take effect.
  • Before the upgrade, check whether power capping is enabled. If power capping fails during the firmware upgrade, services may be interrupted.
  • Perform firmware upgrade and power control operations only when services are offline. Otherwise, services may be interrupted.
  • Do not power on, power off, or reset the server, reset the BMC, or remove or install boards during a firmware upgrade.
  • If the BIOS or CPLD upgrade needs to take effect immediately, you are advised to shut down the system properly before the upgrade because the system will be forcibly powered off and then powered on for the upgrade to take effect.
  • System reset (PowerReset) and system power-off and power-on (PowerOffThenOn) are forcible system operations, which may damage OS files. Exercise caution when performing these operations.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC IP address is pinged from the local PC.
  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC management network port
  • User name and password of the server BMC

Software

Software packages of the server BMC, BIOS, mainboard CPLD or rack server PSU

Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-52.

    Figure 4-52 uMate main window

  2. Click Firmware Upgrade.

    The dialog box shown in Figure 4-53 is displayed, indicating that this function will restart the server and interrupt services.

    Figure 4-53 Dialog box

  3. If services are stopped on the server, click Yes.

    The main window for upgrading firmware is displayed, as shown in Figure 4-54.

    Figure 4-54 Main window for upgrading firmware

    You can click Advanced... to view more parameters. For details, see Table 4-25.

    Table 4-25 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the start IP address of servers.

    IP address of the BMC. The IP address indicates only the IPv4 address.

    End IP

    Specifies the end IP address of servers.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the BMC administrator user name.

    -

    Password

    Specifies the BMC administrator password.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  4. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC IP address and the user name and password (for details, see Table 4-24), as shown in Figure 4-55.
        Figure 4-55 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-56.
        Figure 4-56 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  5. Click Next.

    The window for discovering a server is displayed, as shown in Figure 4-57.

    Figure 4-57 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-58.

    Figure 4-58 Discovering servers successfully

    After a server is discovered, the window for selecting the upgrade device type is displayed, as shown in Figure 4-59.

    Figure 4-59 Selecting the upgrade device type

  6. Select Upgrade by iBMC, and click Next.

    NOTE:

    You can use the BMC to upgrade the BMC, BIOS, and mainboard CPLD firmware of the rack/high-density server and E6000/E9000 blade server, and the PSU firmware of the rack server.

    The window for selecting firmware is displayed, as shown in Figure 4-60.

    Figure 4-60 Selecting firmware

  7. Select the upgrade file.

    • If the upgrade file is in .zip format (the file in this format is recommended), perform the following operations.
      1. Click Select to select the local upgrade software package (in .zip format).

        The system resolves the version.xml file in the software package and displays the resolution results in the upgrade file list and the list of supported servers, as shown in Figure 4-61.

        Figure 4-61 Upgrade file list
        NOTE:
        • Click Version Filter in the upper right corner to filter the servers whose firmware versions are the same as the target versions. The Version Filter check box is available only when the Product Filter check box is selected.
        • If multiple types of servers (rack and high-density) and firmware need to be upgraded at the same time, you can create a software package. For details about the supported server models, see Compatibility List. For details about how to create a software package, see step 1 in Upgrading Rack Server Firmware by Using a Package.
    • If the upgrade file is in .hpm format, perform the following operations.
      1. Click Select to select the local upgrade file (in .hpm format).

        The Config upgrade file attributes dialog box is displayed, as shown in Figure 4-62. Table 4-26 describes the parameters in this dialog box.

        Figure 4-62 Config upgrade file attributes
        Table 4-26 Upgrade file information

        Item

        Description

        Remarks

        FileName

        Specifies the upgrade file name.

        This parameter is read-only.

        Module

        Specifies the firmware to be upgraded. It can be iMana, iBMC, BIOS, or mainboard CPLD.

        Currently, the PSU type is not supported.

        Version

        Specifies the firmware version.

        If the firmware version of a server is the same as the value of Version, the server firmware is not upgraded.

        ActiveMode

        Specifies the mode for the upgrade to take effect. The options are as follows:

        • Immediately: The upgrade takes effect immediately.
        • ResetBMC: The upgrade takes effect only after the BMC is reset.
        • ResetOS: The upgrade takes effect only after the OS is reset.
        • ResetServer: The upgrade takes effect only after the server is powered off and then on.
        • Select ResetBMC for iMana/iBMC upgrade.
        • Select ResetOS for BIOS upgrade.
        • Select ResetServer for mainboard CPLD upgrade.
      2. Enter the upgrade file information according to Table 4-26, and click OK.

        The content of the upgrade file will be displayed in the upgrade file list, as shown in Figure 4-63.

        Figure 4-63 Upgrade file list
      3. Select the server supported by this upgrade file in the list of supported servers, and click Product Filter in the upper right corner.

        The software will filter the servers discovered by using IP addresses, as shown in Figure 4-64.

        Figure 4-64 Filtering servers
        NOTE:

        Click Version Filter in the upper right corner to filter the servers whose firmware versions are the same as the target versions. The Version Filter check box is available only when the Product Filter check box is selected.

  8. Click Next.

    The Warning dialog box is displayed, as shown in Figure 4-65.

    Figure 4-65 Warning dialog box

  9. Click OK.

    The dialog box for selecting a power control mode is displayed, as shown in Figure 4-66.

    Figure 4-66 Selecting a power control mode

  10. To implement automatic power control operations after the firmware upgrade is complete, enter YES and click OK.

    NOTE:

    To manually perform power control operations after the firmware upgrade is complete, enter NO and click OK. After the firmware upgrade is complete, perform power control operations according to 13 to 14 or Performing Server Power Control Operations.

    The dialog box shown in Figure 4-67 is displayed, indicating that the firmware upgrade will restart the iBMC if the iBMC version is earlier than 2.56 and interrupt services.
    Figure 4-67 Dialog box
    NOTE:

    This dialog box is displayed only when the BIOS, mainboard CPLD, or PSU is upgraded.

  11. If services are stopped on the server, enter yes in the text box and click Yes.

    The firmware upgrade starts, as shown in Figure 4-68.
    Figure 4-68 Firmware upgrade
    NOTE:

    You can click Stop to stop this task.

    The firmware upgrade is complete, as shown in Figure 4-69.

    Figure 4-69 Firmware upgrade completed
    NOTE:

    In this window:

    • You can select All Successful to view all servers whose firmware is upgraded successfully.
    • You can select All Failed to view all servers whose firmware fails to be upgraded.
    • You can select a server whose firmware needs to be upgraded again and click Upgrade Again to upgrade the firmware of the selected server again.

    If automatic power control operations fail on the server, you can manually perform power control operations according to 12 to 14 or Performing Server Power Control Operations.

  12. Click Back.

    The window for selecting firmware is displayed, as shown in Figure 4-70.

    Figure 4-70 Upgrade file list

  13. Select the required power control operation from the drop-down list in the lower left corner, for example, PowerOffThenOn, and click Next. For details, see Table 4-26 and Table 4-27.

    The Warning dialog box is displayed, as shown in Figure 4-71.

    Figure 4-71 Warning dialog box
    Table 4-27 Power control operation types

    Operation

    Description

    iBMCRestart

    Resets iBMC.

    PowerOff

    Powers off the system properly.

    PowerOn

    Powers on the system properly.

    PowerReset

    Resets the system forcibly.

    PowerOffThenOn

    Powers off and then on the system forcibly.

  14. Click OK.

    The power control operation starts, as shown in Figure 4-72.

    Figure 4-72 Performing a power control operation
    NOTE:

    You can click Stop to stop this task.

    The power control operation is complete, as shown in Figure 4-73.

    Figure 4-73 Power control operation completed

    After the power control operation is complete, the power control operation result window is displayed automatically, as shown in Figure 4-74.

    Figure 4-74 Power control operation result window
    NOTE:
    • You can click Export to save the power control operation results locally (the results are saved in .xlsx format by default).
    • You can click Log directory to go to the directory storing the result file powerOutput.xml, FusionServer Tools-uMate-Win-Vxxx\work\FWUpgrade\Date+Time+Number\Date+Time+Number, for example, FusionServer Tools-uMate-Win-Vxxx\work\FWUpgrade\20170606194838\20170606204350.

Upgrading Smart Provisioning
Scenarios

Use uMate to upgrade the V5 server Smart Provisioning in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • You are advised to upgrade the firmware on one server. If the upgrade is successful, perform batch firmware upgrades. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • If a server discovery failure or file upload failure occurs, reset the BMC and perform the upgrade again.
  • Before the upgrade is performed on Linux, an NFS server must be created. For details, see Creating an NFS Server on Linux.
  • Before the Smart Provisioning upgrade, check whether power capping is enabled. If power capping fails during the firmware upgrade, services may be interrupted.
  • Perform Smart Provisioning upgrade only when services are offline. Otherwise, services may be interrupted.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC IP address is pinged from the local PC.
  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC management network port
  • User name and password of the server BMC

Software

Download the Smart Provisioning software package at the Support-E website.

Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-75.

    Figure 4-75 uMate main window

  2. Click Firmware Upgrade.

    The dialog box shown in Figure 4-76 is displayed, indicating that this function will restart the server and interrupt services.

    Figure 4-76 Dialog box

  3. If services are stopped on the server, click Yes.

    The main window for upgrading firmware is displayed, as shown in Figure 4-77.

    Figure 4-77 Main window for upgrading firmware

    You can click Advanced... to view more parameters. For details, see Table 4-28.

    Table 4-28 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the start IP address of servers.

    IP address of the BMC. The IP address indicates only the IPv4 address.

    End IP

    Specifies the end IP address of servers.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the BMC administrator user name.

    -

    Password

    Specifies the BMC administrator password.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  4. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC IP address and the user name and password (for details, see Table 4-24), as shown in Figure 4-78.
        Figure 4-78 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-79.
        Figure 4-79 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  5. Click Next.

    The window for discovering a server is displayed, as shown in Figure 4-80.

    Figure 4-80 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-81.

    Figure 4-81 Discovering servers successfully

    After a server is discovered, the window for selecting the upgrade device type is displayed, as shown in Figure 4-82.

    Figure 4-82 Selecting the upgrade device type

  6. Select Upgrade SP, and click Next.

    NOTE:

    Only Smart Provisioning of V5 servers can be upgraded.

    The window for selecting firmware is displayed, as shown in Figure 4-83.

    Figure 4-83 Selecting firmware

    To perform the upgrade, you must place the Smart Provisioning file on the remote server.

  7. In the Upgrade File area, enter the path of the Smart Provisioning file. The path cannot contain spaces, Chinese characters, and special characters such as |;&$><.

    • On Windows, files can be transferred only by using the CIFS protocol. The format is: cifs://User name:Password@Remote server OS IP address/Directory/FusionServer-Tools-Smart Provisioning-Vxxx.iso. The folder where the upgrade file is located must be shared in advance.
    • On Linux, files can be transferred only by using the NFS protocol. The format is: nfs://Remote server OS IP address/Directory/FusionServer-Tools-Smart Provisioning-Vxxx.iso.

  8. In the UpgradeType drop-down list box, select a upgrade mode, as shown in Figure 4-84.

    Figure 4-84 Selecting a upgrade mode

    The upgrade modes are described as follows:

    Auto: If the current version of OS, APP, or Data is different from the target version, upgrade OS, APP, or Data of Smart Provisioning to the target version. The default mode is Auto.

    Full: Upgrade all OS, APP, and Data of Smart Provisioning to the target versions.

    Recover: Format the partition where Smart Provisioning is located, and then upgrade all OS, APP, and Data to the target versions.

    APP: Upgrade the Smart Provisioning applications to the target version.

    Data: Upgrade the Smart Provisioning data to the target version.

  9. In the Select Upgrade Devices area, select the server of which Smart Provisioning is to be upgraded, and click Next.

    The Warning dialog box is displayed, as shown in Figure 4-85.

    Figure 4-85 Warning dialog box

  10. Click OK.

    The Smart Provisioning upgrade starts, as shown in Figure 4-86.
    Figure 4-86 Smart Provisioning upgrade
    NOTE:

    You can click Stop to stop this task.

    The Smart Provisioning upgrade is complete, as shown in Figure 4-87.

    Figure 4-87 Smart Provisioning upgrade completed
    NOTE:
    • During the Smart Provisioning batch upgrade, you can select All Successful to view all servers where upgrades are performed successfully.
    • During the Smart Provisioning batch upgrade, you can select All Failed to view all servers where upgrades failed.

    The server restarts the OS automatically to complete the Smart Provisioning upgrade.

Upgrading Rack Server Firmware by Using a Package
Scenarios

Use uMate to upgrade the rack and high-density server BMC, BIOS, and mainboard CPLD as well as the rack server PSU by using a package in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • You are advised to upgrade the firmware on one server. If the upgrade is successful, perform batch firmware upgrades. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • If a server discovery failure or file upload failure occurs, reset the BMC and perform the upgrade again.
  • Before upgrading the rack server PSU firmware, ensure that the server has two PSUs and both of them are powered on.
  • For a 2-socket server, if the BIOS is rolled back from V087 to an earlier version, disconnect and then reconnect the AC power supply to make the target version take effect. For a 4-socket server, if the BIOS is rolled back from V099 to an earlier version, disconnect and then reconnect the AC power supply to make the target version take effect.
  • Before the upgrade, check whether power capping is enabled. If power capping fails during the firmware upgrade, services may be interrupted.
  • Perform firmware upgrade and power control operations only when services are offline. Otherwise, services may be interrupted.
  • During the server firmware upgrade process, do not power on or off or reset the system or reset the BMC.
  • If the BIOS or CPLD upgrade needs to take effect immediately, you are advised to shut down the system properly before the upgrade because the system will be forcibly powered off and then powered on for the upgrade to take effect.
  • System reset (PowerReset) and system power-off and power-on (PowerOffThenOn) are forcible system operations, which may damage OS files. Exercise caution when performing these operations.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC IP address is pinged from the local PC.
  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC management network port
  • User name and password of the server BMC

Software

Software packages of the server BMC, BIOS, mainboard CPLD as well as the rack server PSU

Procedure
  1. Create an upgrade package.

    1. Download the server BMC, BIOS, mainboard CPLD and PSU software packages (in .zip format) from the Support-E website.
      NOTE:

      To create the bundle, the BMC, BIOS, mainboard CPLD and PSU software packages of the server must contain version.xml.

    2. Obtain the version.xml file.
      • To obtain the version.xml file used for upgrading the BMC, BIOS, and mainboard CPLD: Go to the FusionServer Tools-uMate-Win-Vxxx\template\HWUpgrade directory, and obtain the version.xml file. Figure 4-88 shows the file example.
      • To obtain the version.xml file used for upgrading the PSU: Obtain the file directly from the downloaded PSU software package, as shown in Figure 4-89. Figure 4-90 shows the file example.

        Table 4-29 describes the parameters in the version.xml file.

        Figure 4-88 Example of version.xml used for upgrading the BMC, BIOS, and mainboard CPLD in package mode
        Figure 4-89 PSU software package
        Figure 4-90 Example of version.xml used for upgrading the PSU in package mode
        Table 4-29 version.xml

        Category

        Item

        Description

        Bundle

        FileName

        Specifies the file name of the upgrade package (the name must contain Bundle).

        ProductName

        • Specifies the name of the server where the firmware is to be upgraded when the software package is used to upgrade the BMC, BIOS and mainboard CPLD.
        • Use the value of SupportModelUID in version.xml in the PSU software package when the software package is used to upgrade the PSU.

        BundleType

        • Retain the default value iBMC when the software package is used to upgrade the BMC, BIOS and mainboard CPLD.
        • Use the value PSU when the software package is used to upgrade the PSU.

        SoftwareVersion

        Retain the default value.

        Version

        Retain the default value.

        Package

        FileName

        Specifies the name of the server BMC, BIOS and mainboard CPLD or PSU software package. The package name cannot contain the & character.

        NOTE:

        If the package name contains the & character, delete it and ensure that the value of FileName in version.xml is the same as the modified package name.

        Module

        BMC, BIOS, mainboard CPLD or PSU

        Vendor

        Retain the default value.

        SupportModel

        • Specifies the name of the server supported by the BMC, BIOS or mainboard CPLD software package when the software package is used to upgrade the BMC, BIOS and mainboard CPLD.
        • The value of this parameter must be the same as the value of SupportModel in the version.xml file in the PSU software package when the software package is used to upgrade the PSU.

        Version

        • Specifies the version of the BMC, BIOS or mainboard CPLD software package when the software package is used to upgrade the BMC, BIOS or mainboard CPLD.
        • The value of this parameter must be the same as the value of Version in the version.xml file in the PSU software package when the software package is used to upgrade the PSU.
    3. Go to the FusionServer Tools-uMate-Win-Vxxx\template\HWUpgrade directory.

      The version.xml file is obtained. Figure 4-91and Figure 4-92 show the file examples. Table 4-30 describes the parameters.

      Figure 4-91 Example of version.xml for upgrading the BMC, BIOS and mainboard CPLD by using a bundle
      Figure 4-92 Example of version.xml for upgrading the PSU by using a bundle
      Table 4-30 version.xml

      Category

      Item

      Description

      Bundle

      FileName

      Specifies the file name of the upgrade package (the name must contain Bundle).

      ProductName

      • Specifies the name of the server where the firmware is to be upgraded when the software package is used to upgrade the BMC, BIOS and mainboard CPLD.
      • Use the value of SupportModelUID in version.xml in the PSU software package when the software package is used to upgrade the PSU.

      BundleType

      • Retain the default value iBMC when the software package is used to upgrade the BMC, BIOS and mainboard CPLD.
      • Use the value PSU when the software package is used to upgrade the PSU.

      SoftwareVersion

      Retain the default value.

      Version

      Retain the default value.

      Package

      FileName

      Specifies the name of the server BMC, BIOS and mainboard CPLD or PSU software package. The package name cannot contain the & character.

      NOTE:

      If the package name contains the & character, delete it and ensure that the value of FileName in version.xml is the same as the modified package name.

      Module

      BMC, BIOS, mainboard CPLD or PSU

      Vendor

      Retain the default value.

      SupportModel

      • Specifies the name of the server supported by the BMC, BIOS or mainboard CPLD software package when the software package is used to upgrade the BMC, BIOS and mainboard CPLD.
      • The value of this parameter must be the same as the value of SupportModel in the version.xml file in the PSU software package when the software package is used to upgrade the PSU.

      Version

      • Specifies the version of the BMC, BIOS or mainboard CPLD software package when the software package is used to upgrade the BMC, BIOS or mainboard CPLD.
      • The value of this parameter must be the same as the value of Version in the version.xml file in the PSU software package when the software package is used to upgrade the PSU.
    4. Enter information in version.xml according to Table 4-30.
    5. Compress the downloaded BMC, BIOS, and mainboard CPLD or PSU software packages and the modified version.xml file into a .zip package. The package name is the value of FileName under Bundle, as shown in Figure 4-93.
      Figure 4-93 Compressed package
      NOTE:
      • If multiple models (rack and high-density) and various firmware need to be upgraded at the same time, separate the BMC, BIOS, mainboard CPLD or PSU firmware of each product model into a compressed package (in .zip format). Select multiple firmware packages in 8 to import them at the same time.
      • If multiple models (rack and high-density) and various firmware need to be upgraded at the same time, the value of SoftwareVersion in the version.xml file in each package must be the same, as shown in Figure 4-94.
        Figure 4-94 version.xml

  2. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-95.

    Figure 4-95 uMate main window

  3. Click Firmware Upgrade.

    The dialog box shown in Figure 4-96 is displayed, indicating that this function will restart the server and interrupt services.

    Figure 4-96 Dialog box

  4. If services are stopped on the server, click Yes.

    The main window for upgrading firmware is displayed, as shown in Figure 4-97.
    Figure 4-97 Main window for upgrading firmware

    You can click Advanced... to view more parameters. For details, see Table 4-31.

    Table 4-31 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the start IP address of servers.

    IP address of the BMC. The IP address indicates only the IPv4 address.

    End IP

    Specifies the end IP address of servers.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the BMC administrator user name.

    -

    Password

    Specifies the BMC administrator password.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  5. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC IP address and the user name and password (for details, see Table 4-24), as shown in Figure 4-98.
        Figure 4-98 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-99.
        Figure 4-99 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  6. Click Next.

    The window for discovering a server is displayed, as shown in Figure 4-100.

    Figure 4-100 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-101.

    Figure 4-101 Discovering servers successfully

    After a server is discovered, the window for selecting the upgrade device type is displayed, as shown in Figure 4-102.

    Figure 4-102 Selecting the upgrade device type

  7. Select Upgrade by bundle packages, and click Next.

    NOTE:

    You can upgrade the BMC, BIOS and mainboard CPLD firmware of a rack/high-density server and the PSU firmware of a rack server by using the package.

    The server selection window is displayed, as shown in Figure 4-103 or Figure 4-104.

    Figure 4-103 Selecting a server (single server model)
    Figure 4-104 Selecting servers (multiple server models)

  8. Click Select.

    The upgrade package import window is displayed, as shown in Figure 4-105.

    Figure 4-105 Importing the upgrade package

  9. Click Select to select the local upgrade package.

    The dialog box shown in Figure 4-106 is displayed.

    Figure 4-106 Message dialog box
    NOTE:

    When the message "Invalid upgraed package, please check it and then try again." is displayed, you need to upgrade the components of the servers of the same model one by one if the BMC, BIOS, mainboard CPLD, and PSU packages in the software package contain version.xml.

  10. Click OK.

    The upgrade package is imported, as shown in Figure 4-107 or Figure 4-108.

    Figure 4-107 Upgrade package imported (single server model)
    Figure 4-108 Upgrade package imported (multiple server models)

  11. Close the upgrade package import window.

    The server selection window is displayed, and the upgrade package information is displayed in the window, as shown in Figure 4-109or Figure 4-110.

    Figure 4-109 Selecting a server (single server model)
    Figure 4-110 Selecting servers (multiple server models)
    NOTE:
    • If Upgrade the standby iBMC and then the active iBMC is selected, the standby iBMC will be upgraded first and then the active iBMC will be upgraded. If this option is not selected, only the standby iBMC will be upgraded.
    • Filter Devices is used to filter server types in the Target Type column.
    • Filter Component is used to filter servers in the Component column.
    • Filter Sub Component is used to filter firmware types in the Sub Component column.
    • If Display Different Versions is selected, firmware whose versions are the same as the target versions will be filtered. If this option is not selected, all firmware will be displayed.

  12. Select the BMC, BIOS and CPLD or PSU firmware to be upgraded, and click Next.

    The dialog box shown in Figure 4-111 is displayed, indicating that the firmware upgrade will restart the iBMC if the iBMC version is earlier than 2.56 and interrupt services.
    Figure 4-111 Dialog box

  13. If services are stopped on the server, enter yes in the text box and click Yes.

    The BMC and BIOS upgrade starts, as shown in Figure 4-112.

    Figure 4-112 Upgrade started

    The firmware upgrade is complete, as shown in Figure 4-113.

    Figure 4-113 Firmware upgrade completed
    NOTE:

    You can click Export to export the upgrade results to a local PC.

Upgrading the PCIe Card and Hard Disk Firmware
Scenarios

Use uMate to upgrade the RAID controller card, NIC, and hard disk firmware in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • You are advised to upgrade the PCIe card and hard disk firmware on one server. If the upgrade is successful, perform batch upgrades. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • Use the BMC IP address of each compute node to perform the upgrade on an E9000 server.

During the configuration, do not reset or power off and on the servers.

Prerequisites

Conditions

  • The PC is properly communicating with the BMC of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC IP address is pinged from the local PC.

    For E9000 servers, if you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC
  • User name and password of the server BMC
Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-114.

    Figure 4-114 uMate main window

  2. Click Virtual Media Mount.

    The dialog box shown in Figure 4-115 is displayed, indicating that this function will restart the server and interrupt services.

    Figure 4-115 Dialog box

  3. If services are stopped on the server, click Yes.

    The main window for mounting virtual media is displayed, as shown in Figure 4-116.

    Figure 4-116 Main window for mounting virtual media

    You can click Advanced... to view more parameters. For details, see Table 4-32.

    Table 4-32 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the start IP address of servers.

    IP address of the BMC or OS or floating IP address of the HMM. The IP address indicates only the IPv4 address.

    End IP

    Specifies the end IP address of servers.

    • For a single server, the end IP address must be the same as the start IP address. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.2.2

    • For multiple servers with consecutive IP addresses, the first two fields of the start and end IP addresses must be the same. In addition, the user name and password must be the same for all the servers. For example:

      Start IP: 192.168.2.2

      End IP: 192.168.5.254

    • For multiple servers with inconsecutive IP addresses or different user names or passwords, enter the parameters the same way as you do for a single server.
    • IPv6 addresses are not supported.

    Username

    Specifies the BMC or HMM user name.

    -

    Password

    Specifies the user password.

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  4. Add devices.

    You can add devices in either of the following modes:

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server BMC IP address and the user name and password (for details, see Table 4-47), as shown in Figure 4-117.
        Figure 4-117 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-118.
        Figure 4-118 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  5. Click Next.

    The window for discovering servers is displayed, as shown in Figure 4-119.

    Figure 4-119 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-120.

    Figure 4-120 Server discovered successfully

    After a server is discovered, the server selection window is displayed, as shown in Figure 4-121.

    Figure 4-121 Selecting a server

  6. (Optional) Click the Filter Servers drop-down list box to filter the discovered servers and quickly select a type of servers to be operated, as shown in Figure 4-122.

    Figure 4-122 Filtering server types

  7. Select the server where the virtual media is to be mounted, and click Next.

    The window for selecting the virtual media is displayed, as shown in Figure 4-123.

    Figure 4-123 Selecting the virtual media

  8. Select the virtual media to be mounted and folder.

    Click Select in the ISO/IMG File row, and select the ISO file of the FwUpgrade tool of V101 or later. Click Select in the Directory row, and select the folder where the firmware upgrade package is located, as shown in Figure 4-124.
    Figure 4-124 Selecting the ISO file and folder of the FwUpgrade tool
    NOTE:
    • Reboot Server after Mount the Media, Set Boot Option from CD/DVD-ROM Drive, and Restart the system after all tasks are complete will be automatically selected.
    • You can manually deselect Restart the system after all tasks are complete. When this item is deselected, the system will not be restarted after all tasks are complete.
    • You can manually select Verify the digital signature. This item indicates that the digital certificate will be verified.
    • For details about how to obtain the firmware upgrade package, see "Application" in the FusionServer Tools 2.0 FwUpgrade User Guide.

  9. Click Next. A dialog box is displayed, indicating that the server services must be stopped before you mount virtual media, as shown in Figure 4-125.

    Figure 4-125 Dialog box

  10. If services are stopped on the server, enter yes in the text box and click Yes.

    The firmware upgrade starts, as shown in Figure 4-126.

    Figure 4-126 Upgrading firmware
    NOTE:

    You can click Stop to stop this task.

    When the progress reaches 100%, the upgrade is complete, as shown in Figure 4-127. You can view the detailed upgrade process on the remote virtual console of the BMC WebUI.

    Figure 4-127 Upgrade completed

Upgrading the E9000

Upgrading the E9000 Chassis Offline
Scenarios

Use uMate to upgrade the E9000 chassis offline in the following scenarios:

  • Deployment delivery
  • Routine maintenance
NOTE:
  • You are advised to upgrade one server. If the upgrade is successful, perform batch upgrades. It is recommended that the number of servers for batch operation be less than 200.
  • The switch module FC plane cannot be upgraded.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • If a server discovery failure or file upload failure occurs, reset the HMM and perform the upgrade again.
  • For a 2-socket server, if the BIOS is rolled back from V087 to an earlier version, disconnect and then reconnect the AC power supply to make the target version take effect. For a 4-socket server, if the BIOS is rolled back from V099 to an earlier version, disconnect and then reconnect the AC power supply to make the target version take effect.
  • The MM910 performs a self-check between 03:00 and 03:15 every day. During the self-check, do not upgrade the HMM, fan, BMC, BIOS, or mainboard CPLD. Otherwise, the upgrade will fail.
  • The offline upgrade of E9000 switch modules will interrupt services. Ensure that services are stopped before performing operations.
  • Before the upgrade, ensure that the device is exclusively used and the switch module SOL is available.
  • During the upgrade process, do not power on or off or reset the system or remove or install boards.
Prerequisites

Conditions

  • The PC is properly communicating with the HMM of the target server. The SNMP and SSH communication ports are enabled. Ensure that the server HMM IP address can be pinged.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

    • Ensure that uMate has been configured with the required protocols and ports. For details, see GUI.
    • Ensure that the HMM has been configured with the required protocols and ports. For details, see Viewing MM910 SNMP Protocols.
  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server HMM management network port
  • User name and password of the server HMM
  • User name and password of the Base plane on the switch module
  • User name and password of the Fabric plane on the switch module

Software

FusionServer Tools-uMate-V147 or later

Procedure
  1. Double-click uMate.exe.

    The uMate main window is displayed, as shown in Figure 4-128.

    Figure 4-128 uMate main window

  2. Click E9000 Upgrade.

    The dialog box shown in Figure 4-129 is displayed, indicating that this function will restart the server and interrupt services.

    Figure 4-129 Dialog box

  3. If services are stopped on the server, click Yes.

    The dialog box shown in Figure 4-130 is displayed, asking you whether to perform a pre-upgrade evaluation for switch modules. You are advised to perform a pre-upgrade evaluation for switch modules before the upgrade.

    Figure 4-130 Dialog box
    NOTE:
    • Click Yes, indicates to perform pre-upgrade evaluation, skip to the pre-upgrade evaluation main window. For details, see Performing a Pre-upgrade Evaluation for Switch Modules. The default policy of the pre-upgrade evaluation for switch modules is online evaluation.
    • Click No, indicates to enter firmware upgrade window directly, without pre-upgrade evaluation.

  4. If a pre-upgrade evaluation has been performed, click No.

    The main window for firmware upgrade is displayed, as shown in Figure 4-131.

    Figure 4-131 Main window for firmware upgrade

    You can click Advanced to view more parameters. Table 4-33 describes the parameters.

    Table 4-33 Parameter description

    Item

    Description

    Remarks

    Start IP

    Specifies the start IP address of servers.

    Floating IP address of the server HMM

    End IP

    Specifies the end IP address of servers.

    -

    Username

    HMM administrator user name

    -

    Password

    HMM administrator password

    -

    Write Community

    Specifies the read-write community name.

    This parameter needs to be set if the SNMP version is not v3.

    Information about the Fabric and Base planes on the switch module

    Fabric Username

    Fabric plane administrator user name

    -

    Fabric Password

    Fabric plane administrator password

    -

    Base Username

    Base plane administrator user name

    -

    Base Password

    Base plane administrator password

    -

    Use the same configuration for all switch modules

    Specifies that all switch modules use the same user name and password.

    This item is selected by default.

    Retain the default values for the following parameters.

    IPMI Port

    Specifies the IPMI port number.

    The default value is 623.

    SNMP Port

    Specifies the SNMP port number.

    The default value is 161.

    SSH/SFTP Port

    Specifies the SSH/SFTP port number.

    The default value is 22.

    VMM Port

    Specifies the VMM port number.

    The default value is 8208.

  5. Add devices.

    • Manual input mode. This mode applies to scenarios where a single device or multiple devices with the same parameter configuration are to be added.
      1. Enter the server HMM floating IP address, user name, and password as well as the user names and passwords of the Fabric/Base planes on the four switch modules (for details, see Table 4-31), as shown in Figure 4-132.
        Figure 4-132 Entering server information
      2. Click Add to add devices to the device list.
        NOTE:
        • To delete a server or an OS, right-click the row where the server or OS is located and choose Delete, or select the row where the server or OS is located and click Delete in the upper right area.
        • To modify the parameters of an added device, delete the device from the device list, set parameters again, and click Add.
    • Configuration file import mode. This mode applies to scenarios where multiple devices with different parameter configurations are to be added in batches.
      1. Edit the hwServers.xls configuration file in the FusionServer Tools-uMate-Win-Vxxx directory (for details, see Table 4-7), as shown in Figure 4-133.
        Figure 4-133 Editing hwServers.xls
        NOTE:

        You can specify configuration information for multiple servers or OSs at the same time.

        The configuration file contains user data. Delete it after use.

      2. Click Select and import the edited hwServers.xls configuration file.

  6. Click Next.

    The window for discovering servers is displayed, as shown in Figure 4-134.

    Figure 4-134 Discovering servers
    NOTE:

    You can click Stop to stop this task.

    A server is discovered, as shown in Figure 4-135.

    Figure 4-135 Discovering servers successfully

    After a server is discovered, the window for selecting the upgrade device type is displayed, as shown in Figure 4-136.

    Figure 4-136 Selecting the upgrade device type

  7. Select E9000 Upgrade, and click Next.

    The window for selecting firmware is displayed, as shown in Figure 4-137 to Figure 4-139.

    Figure 4-137 Selecting firmware 1
    Figure 4-138 Selecting firmware 2
    Figure 4-139 Selecting firmware 3

  8. Click Select to select the local upgrade package. If multiple pieces of firmware need to be upgraded, you can press Shift and select multiple upgrade packages to import them at a time.

    Figure 4-140 select multiple pieces of firmware
    NOTE:

    uMate automatically resolves the imported upgrade package and displays specific file information. If the upgrade package cannot be resolved or is incorrectly resolved, you can modify the information based on the actual situation.

    • Type: indicates the upgrade pack