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

CH222 Compute Node V100R001 User Guide 18

This document describes the appearance, functions, structure, and installation, removal, and configuration methods of the CH222 compute node.
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).
Checking the CH222

Checking the CH222

Log in to the MM910 command line interface (CLI) to check the health status of the CH222.

Scenarios

Log in to the MM910 CLI to check the health status of the CH222. Ensure that it meets the environmental requirements for software installation.

Prerequisites

Conditions

The CH222 has been powered on.

Data

The following data is available:

  • User name for logging in to the MM910 to be connected.
  • Password for logging in to the MM910 to be connected.

Procedure

  1. Log in to the MM910 CLI.

    1. Connect the local PC to the MM910.
      • Connect the network port of the local PC to the MGMT port of the active or standby MM910.

        Figure 4-2 shows the network connections.

        Figure 4-2 Network connections

        If the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption.

        NOTE:

        The MM910 management port is provided by either of the following modes:

        • An Ethernet port on the switch module in slot 2X or 3X.

          However, if a CX910/CX911/CX912/CX913 is in slot 2X or 3X, only a GE port can be used; if a CX920 is in slot 2X or 3X, only a 10GE port can be used. The CX910/CX911/CX912/CX913 are not recommended for providing the management port of the management module.

        • MGMT port on the MM910 panel
        • For the MM910 (U54)2.25 or earlier, the management port is provided by the switch module by default. For the MM910 (U54)2.26 or later, the management port is provided by the MM910 by default. For details about how to query the MM910 version, see MM910 Management Module V100R001 User Guide.
        • You can run the outportmode command to change the mode in which the MM910 management port is provided. If the switch module in slot 2X or 3X is used to provide the management port, do not connect the MM910 MGMT port and the switch module ports to the same network. Otherwise, a network storm will occur and the network will be interrupted. For details, see MM910 Management Module V100R001 Command Reference.
      • Connect the network port of the local PC to the MGMT or STACK port of the active MM910.
        • If the MGMT port of the active MM910 is available, use this port. Figure 4-3 shows the connection.
          Figure 4-3 Connection between the local PC and the active MM910 (in slot MM2 in this example)
        • If the MGMT port of the active MM910 is unavailable, connect the PC to the STACK port of the active MM910. If the STACK port is used to stack the MGMT port in another chassis, connect the PC to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis. Figure 4-4 shows the connection.

          If the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption.

          Figure 4-4 Connection between the local PC and an idle STACK port on an MM910 stacked
    2. Open an SSH connection tool and enter the floating IP address of the MM910 to visit the MM910 CLI.

      In this document, PuTTY is used as an example during login over SSH. For details, see Logging In to the Server Over a Network Port by Using the PuTTY.

  2. Check the version and health status of the CH222.

    1. Run the following command to query the CH222 version information:

      smmget -l bladeN -d version

      In the command, N indicates the slot number of the CH222 to be queried. The value ranges from 9 to 16.

      For example, to query the version information about the CH222 in slot 9, run the following command:

      smmget -l blade9 -d version

      The command output similar to the following is displayed if the command is run successfully:

      Blade9 version information: 
      IPMC               CPU:           SPEAr310 
      IPMI           Version:           2.0 
      FPGA           Version:           (U4008)012 
      CPLD           Version:           (U38)008 
      BIOS           Version:           (U41)V010 
      Active iMana Version:           (U4005)3.07 
      Active iMana     Built:           15:47:39 Oct 16 2012 
      Backup iMana Version:           3.07 
      Driver         Version:           1.00 
      Driver           Built:           15:47:48 Oct 16 2012 
      Uboot          Version:           U-Boot 1.3.1 (Jun 14 2012 - 17:45:15) 
      SESA           BoardID:           0x0130 
      SESA               PCB:           .A 
      RAID CARD      BoardID:           0x0021 
      RAID CARD          PCB:           .A 
      IPMB           Address:           0x90
      • CPLD Version: indicates the CPLD version of the compute node.
      • BIOS Version: indicates the BIOS version of the compute node.
      • Active iMana Version: indicates the main iMana version of the compute node.
      • Backup iMana Version: indicates the standby iMana version of the compute node.
      • SESA BoardID: indicates the version of the compute node.
    2. Check whether the CH222 software versions are consistent with the data plan.
      • If yes, go to 2.d.
      • If no, go to 2.c.
    3. Upgrade the integrated management module (iMana 200), basic input/output system (BIOS), or complex programmable logical device (CPLD). For details, see the E9000 Server V100R001 Upgrade Guide.
    4. Run the following command to check whether alarms are generated for the CH222:

      smmget -l bladeN -d healthevents

      In the command, N indicates the slot number of the CH222 to be queried.

      For example, to query alarms about the CH222 in slot 9, run the following command:

      smmget -l blade9 -d healthevents

      • No alarm is generated for the CH222 if the following information is displayed:
        blade9 has no problem.     
      • The information similar to the following indicates an alarm:
        Wed Oct 17 11:51:02 2012 RTC Battery: Battery low.  Assertion [Major]     
    5. Check whether alarms are generated.
      • If yes, go to 2.f.
      • If no, no further action is required.
    6. Handle the alarms. For details, see E9000 Server V100R001 Alarm Handling.

Translation
Download
Updated: 2019-08-16

Document ID: EDOC1000018075

Views: 8315

Downloads: 321

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next