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

eSight V300R009C00 Operation Guide 10

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).
Connecting Servers to eSight

Connecting Servers to eSight

Methods and Protocols Used for Adding Server Devices

This topic describes the methods for adding servers to eSight.

Table 9-2 lists the server types and methods for adding servers to eSight.

Table 9-2 Methods to add servers and applications as well as used protocols

Server Type

Can Be Automatically Discovered by Network Segment? (Y/N)

Can Be Added in Batches? (Y/N)

Can Be Added One by One? (Y/N)

-

SNMP

Redfish

-

-

Rack server

Y

Y

Y

NOTE:

V5 servers are added to eSight through Redfish.

Y

NOTE:

V5 servers are added to eSight through Redfish.

Blade server

Y

N

Y

Y

High-density server

Y

Y

Y

NOTE:

V5 servers are added to eSight through Redfish.

Y

NOTE:

V5 servers are added to eSight through Redfish.

KunLun server

N

N

N

Y

Third-party server

Y

N

Y

Y

Heterogeneous Server

N

Y

Y

NOTE:

Heterogeneous servers are added to eSight through Redfish.

Y

NOTE:

Heterogeneous servers are added to eSight through Redfish.

The following tables list the default parameters for adding Huawei servers to eSight.

NOTE:
  • The parameters listed in the tables are for reference only. Their values may vary due to product upgrades or other reasons. The parameters are subject to the product documentation at http://support.huawei.com.
  • To ensure account security, it is recommended that you change your password upon first login. For details about how to change a password, see the product documentation at http://support.huawei.com.
  • For details about how to query or modify SNMP or Redfish parameters required for adding devices, see Setting SNMP Parameters or Setting Redfish Parameters.
  • For security purposes, SNMPv1 and SNMPv2c are disabled on the server by default. Exercise caution when enabling SNMPv1 or SNMPv2c.
Table 9-3 Rack server

Server Series

Default Access Parameter

Discovery Protocol

Default Value (SNMPv1/v2c)

  • RH2285 V2 (RH2265 V2)
  • RH2288 V2 (RH2268 V2)
  • RH5885 V2
  • RH2288H V2 (RH2268 V2)
  • RH2285H V2 (RH2265 V2)
  • RH2485 V2 V100R002C0
  • RH1288 V2
  • RH1288A V2
  • RH2288A V2
  • SNMP protocol type: SNMPv3
  • Username: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

  • Trap community:
    • For iMana earlier than V608: trappublic
    • For iMana V608 or later: TrapHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: trappublic
  • Read community:
    • For iMana earlier than V608: ropublic
    • For iMana V608 or later: roHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: ropublic
  • Write community
    • For iMana earlier than V608: rwpublic
    • For iMana V608 or later: rwHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: rwpublic
  • RH1288A V2
  • RH2288A V2
  • RH2288 V3
  • RH2288H V3
  • 5288 V3
  • RH5885 V3
  • RH5885H V3
  • RH8100 V3
  • SNMP protocol type: SNMPv3
  • Username: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

  • Trap community: TrapAdmin12#$
  • Read/Write community: rwAdmin12#$
  • 1288H V5
  • 2288H V5
  • 2488H V5
  • 5885H V5
  • 2488 V5
  • 8100 V5
  • 2288 V5
  • Username: Administrator
  • Password: Admin@9000

Redfish

-

  • TaiShan 2280
  • TaiShan 5280
  • SNMP protocol type: SNMPv3
  • Username: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

  • Trap community: TrapAdmin12#$
  • Read/Write community: rwAdmin12#$
Table 9-4 Blade server

Server Series

Default Access Parameter

Discovery Protocol

E6000/E9000

  • SNMP protocol type: SNMPv3
  • User name: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

Table 9-5 High-density server

Server Series

Default Access Parameter

Discovery Protocol

Default Value (SNMPv1/v2c)

  • XH621 V2
  • XH310 V2
  • XH311 V2
  • XH320 V2
  • XH321 V2
  • DH320 V2
  • DH321 V2
  • DH620 V2
  • XH620 V3
  • XH622 V3
  • XH628 V3
  • SNMP protocol type: SNMPv3
  • Username: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

  • Trap community:
    • For iMana earlier than V608: trappublic
    • For iMana V608 or later: TrapHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: trappublic
  • Read community:
    • For iMana earlier than V608: ropublic
    • For iMana V608 or later: roHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: ropublic
  • Write community
    • For iMana earlier than V608: rwpublic
    • For iMana V608 or later: rwHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: rwpublic
  • XH310 V3
  • XH321 V3
  • SNMP protocol type: SNMPv3
  • Username: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

  • Trap community: TrapAdmin12#$
  • Read/Write community: rwAdmin12#$

XH321 V5

  • Username: Administrator
  • Password: Admin@9000

Redfish

-

Table 9-6 KunLun server

Server Series

Default Access Parameter

Discovery Protocol

Default Value (SNMPv1/v2c)

  • 9008
  • 9016
  • 9032
  • 9032L
  • SNMP protocol type: SNMPv3
  • Username: root
  • Authentication protocol: HMACSHA
  • Authentication password: Huawei12#$
  • Data encryption protocol: AES
  • Data encryption password: Huawei12#$

SNMP

  • Trap community:
    • For iMana earlier than V608: trappublic
    • For iMana V608 or later: TrapHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: trappublic
  • Read community:
    • For iMana earlier than V608: ropublic
    • For iMana V608 or later: roHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: ropublic
  • Write community
    • For iMana earlier than V608: rwpublic
    • For iMana V608 or later: rwHuawei12#$
    • For upgrading a server earlier than iMana V608 to iMana V608 or later: rwpublic

9008 V5 (base version)

  • Username: Administrator
  • Password: Admin@9000

Redfish

-

Table 9-7 Heterogeneous server

Server Series

Default Access Parameter

Discovery Protocol

  • G530 V2
  • G560 V1
  • G2500
  • G560 V5
  • User name: Administrator
  • Password: Admin@9000

Redfish

Setting Server Protocol Parameters

This topic describes how to set protocol parameters on servers. After the setting, you can use the parameter settings to enable eSight to access and manage the servers.

Configuring Server Certificates

The server certificate authentication function can be used only when the V5 servers and blades in the E9000 chassis communicate with eSight.

NOTE:

The iBMC version of the E9000 blade must be 2.50 or later, and the HMM version must be 6.50 or later.

Prerequisites

The JDK is installed and correctly configured because the keytool command is a JRE command.

NOTE:

The JDK is installed and configured on the eSight server by default.

Procedure

  • Configure parameters.
    1. Open the eSight installation directory\data\CertificateVerify.xml file.
    2. Modify parameters in the CertificateVerify.xml file. The following table describes related parameters.

      Parameter

      Description

      Description

      isVerify

      Whether to enable the server certificate authentication function. The default value is false.

      • If this parameter is set to true, the server certificate authentication function is disabled. Servers can communicate with eSight only after their certificates are imported to the eSight trust store.
      • If this parameter is set to false, the server certificate authentication function is disabled. You do not need to import the certificates of servers. After disabling the function, you need to restart eSight to make the configuration take effect.

      true or false

    3. Save the modifications. The modifications take effect immediately.
  • View certificates.
    1. Log in to eSight.

      Log in to Windows as Administrator, and log in to Linux as ossuser.

      NOTE:

      If the Windows operating system has been hardened for security, log in the eSight server as user SWMaster.

    2. Go to the directory eSight installation directory\AppBase\jre\bin.
    3. Run the following command to view existing storage device certificates.
      • Windows:

        keytool -list -v -keystore ..\..\lib\resources\default_data\trustStore.jks

      • Linux:

        ./keytool -list -v -keystore ../../lib/resources/default_data/trustStore.jks

        NOTE:

        The initial password of the trust store is Huawei@123.

      The command output shows existing storage device certificates.

  • Change the trust store password(Optional).

To ensure the security of system data and user data, administrators must change the initial password immediately based on password rules. Otherwise, the customer shall be liable for all the losses incurred thereby.

  1. Log in to eSight.

    Log in to Windows as Administrator, and log in to Linux as ossuser.

    NOTE:

    If the Windows operating system has been hardened for security, log in the eSight server as user SWMaster.

  2. Go to the directory eSight installation directory\AppBase\jre\bin.
  3. Run the following command.
    • Windows:

      keytool -storepasswd -keystore ..\..\lib\resources\default_data\trustStore.jks

    • Linux:

      ./keytool -storepasswd -keystore ../../lib/resources/default_data/trustStore.jks

      The system prompts you to enter the keystore password.

  4. Enter the original password and enter the new password twice as promoted. Then press Enter.
  5. Go to the encrypt directory eSight installation directory/AppBase/tools/bmetool/encrypt.
    NOTE:

    On Windows, this operation is performed by the Administrator user. On Linux, this operation is performed by the ossuser user.

  6. Run the following command to generate the ciphertext for the new password of the trust store.
    • Windows: encrypt.bat 0
    • Linux: ./encrypt.sh 0
  7. Enter the new password and confirm the password.
  8. Copy the ciphertext and use it to replace the ciphertext in the eSight installation directory/AppBase/lib/resources/default_data/security.properties.
  • Import certificates.
    1. Obtain storage device certificates. For details about how to obtain the certificates, contact storage device vendors.
    2. Log in to eSight.

      Log in to Windows as Administrator, and log in to Linux as ossuser.

      NOTE:

      If the Windows operating system has been hardened for security, log in the eSight server as user SWMaster.

    3. Back up the trustStore.jks in eSight installation directory\AppBase\lib\resources\default_data.
    4. Go to the directory eSight installation directory\AppBase\jre\bin.
    5. Run the following command and import the obtained storage device certificates.
      • Windows:

        keytool -import -alias certificate alias -keystore ..\..\lib\resources\default_data\trustStore.jks -storepass trust store password -file Path and name of the certificate -trustcacerts

      • Linux:

        ./keytool -import -alias certificate alias -keystore ../../lib/resources/default_data/trustStore.jks -storepass trust store password -file Path and name of the certificate -trustcacerts

      • The alias of each certificate must be unique.
      • The path and name of a certificate is user-definable. You are advised not to save certificates to the eSight installation directory.

      Command example:

      • Windows:

        keytool -import -alias devicemanger_ca -keystore ..\..\lib\resources\default_data\trustStore.jks -storepass Huawei@123 -file D:\cert\ca.crt -trustcacerts

      • Linux:

        ./keytool -import -alias devicemanger_ca -keystore ../../lib/resources/default_data/trustStore.jks -storepass Huawei@123 -file /opt/cert/ca.crt -trustcacerts

        When a prompt is displayed, asking you whether to display the trust certificate, enter Y.

        If Certificates have been added to the trust store is displayed in the command output, certificates are added successfully.

    6. After all storage device certificates are imported, restart eSight.

      If the device's certificate update, please import the latest certificate into the trust. It is recommended that you update the certificates periodically to ensure communication security.

Setting SNMP Parameters

To add servers to eSight, you need to obtain or set SNMP parameters for normal communication between eSight and the servers. SNMP parameters need to be set for rack servers, blade servers, and high-density servers.

Context

The server management page and operation commands vary depending on server model. For example, the iMana 200 page is used for V1 and V2 servers, the iBMC page is used for V3 and V5 servers, and the HMM Web page is used for E9000 servers (management board: MM910). To view the specific page and commands, you can download the product documentation of Huawei servers from Huawei technical support website. For non-Huawei servers, contact the after-sales personnel of the servers. To download the product documentation from Huawei technical website, perform the following operations:

SNMP parameters required for adding servers to eSight are as follows:

  • SNMPv3: port, user name, authorization and authentication protocol, authorization and authentication password, data encryption protocol, and data encryption password
  • SNMPv1 and SNMPv2c: port, read community, and write community
NOTE:
  • Enabling SNMPv1 and SNMPv2c will reduce the system security. Therefore, SNMPv1 and SNMPv2c are disabled on servers by default. Exercise caution when enabling SNMPv1 or SNMPv2c. For blade servers such as E9000, eSight supports only the SNMPv3 protocol.
  • The MD5 algorithm is insecure. It is recommended that Authentication protocol be set to SHA.
  • The DES algorithm is insecure. It is recommended that Data encryption protocol be set to AES.

Procedure on the iMana 200 Page

For V1 and V2 servers, perform the following operations on the iMana 200 page:

  1. In the navigation tree on the left, choose Configuration > Service. The Service page is displayed on the right.
  2. (Optional) Modify SNMPv1 or SNMPv2c parameters.

    1. Enable SNMPv1 or SNMPv2c.
      1. In the SNMP Configurations area, select the target SNMP version.
      2. Click OK.

        If the message "Operation performed successfully" is displayed, the setting is complete.

    2. In the SNMP Community area, set communities for the SNMP protocol.
      1. In the Read-Only Community text box, enter the read-only community of the SNMP protocol.
      2. In the Read-Write Community text box, enter the read-write community of the SNMP protocol.
      3. Click OK.

      If the message "Operation performed successfully" is displayed, the setting is complete.

    3. Modify the port number used by the SNMP protocol.
      1. In the Services Configuration area, select the check box next to the SNMP Agent service to enable the SNMP service.
      2. Enter a port number in the Port text box.
        NOTE:

        By default, the server provides port 161 for the SNMP service. You can select Default to set the port as the default port.

      3. Click OK.

        If the message "Operation performed successfully" is displayed, the setting is complete.

  3. Modify SNMPv3 parameters.

    1. Modify the port number used by the SNMP protocol.
      1. In the Services Configuration area, select the check box next to the SNMP Agent service to enable the SNMP service.
      2. Enter a port number in the Port text box.
        NOTE:

        By default, the server provides port 161 for the SNMP service. You can select Default to set the port as the default port.

      3. Click OK.

      If the message "Operation performed successfully" is displayed, the setting is complete.

    2. On the Local User page, modify user parameters.
      1. Choose Configuration > User in the navigation tree on the left.
      2. Click Local User on the right. The Local User page is displayed.
      3. On the user list page, select users to be modified and click .
      4. In the Modify User Information dialog box that is displayed, modify the basic attributes of users.
        • In Current User Password, enter the password of the current login user.
        • In User Name, enter the name of the target user.
        • Select the check box next to Change Password, and enter the password of the target user in the New Password text box.
        • In Confirm Password, enter the password of the target user again.
      5. Click OK. The Local User page is displayed, and the user information is modified successfully.
        NOTE:
        • You can also add a user for connecting to eSight.
        • The user password set here is used for both Authentication password and Data encryption password for adding servers to eSight.

Procedure on the iBMC Page

For V3 and V5 servers, perform the following operations on the iBMC page:

NOTE:

Operations on the iBMC page vary slightly depending on version. This section uses iBMC firmware version 2.60 (U2) as an example. You can obtain the iBMC firmware version on the iBMC overview page.

  1. Choose Configuration from the menu and choose Services in the navigation tree on the left.

    Ensure that the SNMP protocol is enabled, that is, is displayed for SNMP Agent.

    Enter a port number in the Port text box.
    NOTE:

    By default, the server provides port 161 for the SNMP service. You can select Restore Defaults to set the port as the default port.

  1. (Optional) Modify SNMPv1 or SNMPv2c parameters.

    1. Choose System in the navigation tree on the left, and select SNMPv1 or SNMPv2c to enable SNMPv1 or SNMPv2c.
    2. In the Read-Only Community text box, enter the read-only community of the SNMP protocol.
    3. In the Read-Write Community text box, enter the read-write community of the SNMP protocol.
    4. Click Save.

  1. Modify SNMPv3 parameters.

    1. Choose System in the navigation tree on the left.

      Set SNMPv3 AuthProtocol to SHA1 and SNMPv3 PrivProtocol to AES.

      Click Save.

    2. On the Local User page, modify user parameters.
      1. Choose Local User in the navigation tree on the left.
      2. On the user list page, select users to be modified and click .
      3. In the Modify User Information dialog box that is displayed, modify the basic attributes of users.
        • In Current User Password, enter the password of the current login user.
        • In User Name, enter the name of the target user.
        • Select the check box next to Change Password, and enter the password of the target user in the New Password text box.
        • In Confirm Password, enter the password of the target user again.
      4. Click Save. The Local User page is displayed, and the user information is modified successfully.
        NOTE:
        • You can also click Add to add a user for connecting to eSight.
        • The user password set here is used for both Authentication password and Data encryption password for adding servers to eSight.

Procedure on the HMM Web Page

For blade servers such as E9000 (management board: MM910), perform the following operations on the HMM Web page:

  1. Choose System Management from the menu and choose Security Policy in the navigation tree on the left.

    NOTE:

    The default port number of the SNMP service on the server is 161.

  1. Modify SNMPv3 parameters.

    1. Click Edit, and set the authentication type to SHA and encryption type to AES for SNMPv3 and SNMP Trap V3.

      Click Save.

    2. On the MM Users page, modify user parameters.
      1. Choose MM Users in the navigation tree on the left.
      2. On the user list page, select users to be modified and click .
      3. In the Modify User dialog box that is displayed, modify the basic attributes of users.
        • In Current User Password, enter the password of the current login user.
        • Select the check box next to Change Password, and enter the password of the target user in the New Password text box.
        • In Confirm Password, enter the password of the target user again.
      4. Click OK. The MM Users page is displayed, and the user information is modified successfully.
        NOTE:
        • You can also click Add to add a user for connecting to eSight.
        • The user password set here is used for both Authentication password and Data encryption password for adding servers to eSight.

Setting Redfish Parameters

V5 rack servers are added to eSight through Redfish and report alarms to eSight through SNMP.

Prerequisites

You have logged in to the iBMC WebUI. For details, see the HUAWEI Rack Server iBMC User Guide released with the server.

Context

Adding servers to eSight requires the Redfish parameters User Name, Password, and Port. You can set the Redfish parameters based on site requirements.

Procedure

  1. On the menu bar, choose Configuration.

    The Local Users page is displayed by default.

  2. Modify user parameters.

    1. In the user list, select the user to be modified and click.
    2. Configure basic user information.
      • Enter your password in the Current User Password text box.
      • Enter the name of the target user in the User Name text box.
      • Select the check box next to Change Password, and enter the new password for the target user in the Password text box.
      • Reenter the new password for the target user in the Confirm Password text box.
      • In the Login Interfaces text box, select all interfaces.
      NOTE:

      To use the Redfish protocol, select the Redfish interface.

    3. Click Save

  3. Change the port number.

    1. In the navigation tree, choose Change Password.
    2. Enable Web Server (HTTPS). Enter the port number in the Port text box.
    3. Click Save.

Configuring the Switch Module Encryption Algorithm

When the CX920 and CX320 switch modules are added to eSight, the AES256 encryption algorithm is used by default, and the AES128 encryption algorithm is disabled, which leads to SSH blocking. You need to manually delete the AES256 encryption algorithm for the CX920 and CX320 switch modules. Then the system automatically enables the AES128 encryption algorithm, and the SSH function of the switch modules becomes normal.

Prerequisites

IP addresses are configured for the CX920 and CX320 switch modules.

Procedure

  1. Use PuTTY to log in to the switch modules with the IP addresses and root user of the switch modules.
  2. Run the following command to display the system view:

    system-view

  3. Run the following command to delete the AES256 encryption algorithm for the switch modules:

    undo ssh server cipher

    undo ssh server hmac

    undo ssh server key-exchange

  4. Run the following command for the configuration to take effect:

    commit

Automatically Discovering Devices

You can apply the automatic device discovery function to discover devices in batches if all devices in an IP network segment need to be connected to and establish communication with eSight. This function can increase efficiency.

Prerequisites

  • You have the operation permission on Access Resource.
  • You have obtained the IP network segment and protocol parameters of the target servers.
  • The HMMs and iBMCs of blade servers can communicate with eSight, and other servers can communicate with eSight.
  • The time zone of the servers is the same as that of eSight.

    If the time zone of the servers is different from that of eSight, the alarm time displayed on eSight is different from that on the iBMC.

Context

  • After adding the switch modules of a blade server, you need to set protocol parameters of the switch modules. For details, see Setting switch module protocol parameters in Managing Blade Servers.
    NOTE:

    eSight cannot obtain the IP address of the FC switch module of a blade server. You need to log in to the serial port of the blade server chassis to obtain the IP address of the FC switch module and reconfigure it on eSight.

  • If a V3 server is added to eSight using the default user root or admin, or a V5 server is added to eSight using the default user Administrator, the communication failure between eSight and the server may be caused by the lockout of the root, admin or Administrator user on the server. It is recommended that you create an administrator account dedicated for interworking with eSight on the server. For details about how to create the account, see How Do I Create an Interconnect Account on a Huawei Server.
  • If the network device management and server management components of eSight have been installed, when eSight automatically detects E9000 switch modules, the switch modules are automatically displayed in the network device list under Resource > Network > Equipment > Network Device. This will cause switch module management faults, and the switch module records need to be manually deleted from the network device list.
  • When the iBMC versions of blades on an E9000 are 2.50 or later, and the HMM versions are 6.50 or later, if no IP address is configured for the blades, you need to configure an IP address resource pool before the blades are connected to eSight through automatic discovery. By default, eSight automatically allocates IP addresses from the first IP address resource pool to blades. For details about configuring an IP address resource pool, see Configuring an IP Address Resource Pool.
  • For other restrictions imposed when servers are connected to eSight, see Application Restrictions.

Procedure

  1. Plan the automatic device discovery mode, discovery task type, and exclusion list.
  2. Add the network segments or IP addresses of the devices that do not need to be discovered to the exclusion list. The task will automatically skip the network segments or IP addresses.

    1. Choose Resource > Common from the main menu.

    2. In the navigation tree on the left, choose Add Resource > Automatic Task Management.

    3. On the Exclusion List tab page, add network segments or IP address to be excluded.

  3. Select an automatic device discovery method.

    1. In the navigation tree on the left, choose Add Resource > Automatic Discovery.

    2. On the Automatic Discovery page, click Change Discovery Mode in the upper right corner to select the required automatic discovery mode.

      Most servers use non-SNMP access protocols. For this reason, By network segment (advanced) is recommended.

      NOTE:

      The V5 devices of rack servers, V5 devices of high-density servers, and heterogeneous servers use the Redfish protocol for automatic discovery.

  4. Set the parameters of an automatic discovery task and create the task.

    You can configure frequently used protocol parameters as a template so that you can use a predefined parameter template for subsequently connected devices. This improves the efficiency. eSight offers the following default SNMP templates:

    • SNMPv1: DefaultSNMPV1
    • SNMPv2c: DefaultSNMPV2c
    • SNMPv3: DefaultSNMPV3

    • SNMPv1 and SNMPv2c protocols have security risks. SNMPv3 is recommended.
    • The authentication complexity of the default SNMP template is low. It is recommended that you create an SNMP template based on the site requirements instead of directly using the default SNMP template.
    • The default SNMP template cannot be modified or deleted.
    • For default SNMPv1 and SNMPv2c templates, the read community name is public, and the write community name is private. The authentication protocol and proprietary protocol for the default SNMPv3 template are both None.

  5. Confirm the discovery results.

    • You can immediately view the results of the task whose Frequency is One-off and the scheduled task that is immediately executed.
    • For the scheduled task that is not immediately executed, choose Add Resource > Automatic Task Management from the main menu and view the discovery results in Discovered Device List.

Adding a Single Server

If only a small number of servers need to be added to eSight, you can add them one by one.

Prerequisites

  • You have the operation permission on Access Resource.
  • You have obtained the IP addresses, types, and communications protocol parameters of the target servers.
  • If eSight is deployed on the Red Hat operating system and the servers need to be added to eSight through IPMI, ensure that the IPMI tool compilation is complete. For the compilation method, see section Preparing for Red Hat Installation in the Single-Node System Software Installation Guide (Red Hat).
  • The HMMs and iBMCs of blade servers can communicate with eSight, and other servers can communicate with eSight.
  • The time zone of the servers is the same as that of eSight.

    If the time zone of the servers is different from that of eSight, the alarm time displayed on eSight is different from that on the iBMC.

Context

  • When adding V1 servers, manually register the Trap IP addresses in the iBMCs of the servers. Otherwise, alarms of the servers cannot be reported to eSight. For details about how to register the Trap IP addresses in the iBMCs of the servers, see How to Manually Register eSight Trap IP Addresses with Switch Modules.
  • If a V3 server is added to eSight using the default user root or admin, or a V5 server is added to eSight using the default user Administrator, the communication failure between eSight and the server may be caused by the lockout of the root, admin or Administrator user on the server. It is recommended that you create an administrator account dedicated for interworking with eSight on the server. For details about how to create the account, see How Do I Create an Interconnect Account on a Huawei Server.
  • After adding the switch modules of a blade server, you need to set protocol parameters of the switch modules. For details, see Setting switch module protocol parameters in Managing Blade Servers.
    NOTE:

    eSight cannot obtain the IP address of the FC switch module of a blade server. You need to log in to the serial port of the blade server chassis to obtain the IP address of the FC switch module and reconfigure it on eSight.

  • For other restrictions imposed when servers are connected to eSight, see Application Restrictions.

Procedure

  1. Choose Resource > Common from the main menu.

  2. In the navigation tree on the left, choose Add Resource > Add Resource.

  3. In the Server list, select the server type that you want to add.

    Available server types are rack, blade, high-density, KunLun, third-party, and heterogeneous servers.

  4. Configure the server basic information and access protocol.

    • SNMPv1 and SNMPv2c deliver low security. SNMPv3 is recommended.
    • MD5 and DES deliver low security. SHA and AES are recommended.
    • Use SNMP to add V2 and V3 servers. Use IPMI to add V1 servers. If a server supports both IPMI and SNMP, SNMP is preferred for adding the server. For details about how to query the access parameters required for adding servers, see How to Query Huawei Server Device Protocol Parameters
    The following table describes the server access parameters.

    Protocol

    Parameter

    Precautions

    SNMP

    Server IP address

    • When adding a blade server, use the floating IP address of the SMM.
    • When adding rack and high-density servers, use the iBMC to manage IP addresses.

    SNMP protocol type

    • SNMPv1 and SNMPv2c

      If you select SNMPv1 or SNMPv2c to add a server to eSight, the firmware upgrade, in-band configuration deployment, and stateless computing features of the server are unavailable.

      Before using SNMPv1 or SNMPv2c to discover devices, you must enable the SNMP service of the required version in the iBMCs of the devices.

    • SNMPv3

      If the server to be added to eSight supports KVM and VMM encryption, use SNMPv3 for device discovery.

      If the read-only community name and read/write community name of the server to be added to eSight are the same, use SNMPv3 for device discovery. Otherwise, the server cannot be added.

      If the trap version of the server to be added is set to V3 in the iBMC, use SNMPv3 for device discovery and ensure that the user name is the same as that specified in the iBMC. This ensures that alarms of the server can be reported to and displayed on eSight.

      Blade and KunLun servers support only SNMPv3.

    NOTE:
    • The SNMP configurations of the active and standby HMMs of the same server must be the same.
    • Rack, high-density, and third-party servers support SNMPv1, SNMPv2c, and SNMPv3.

    Community name

    The trap community name is used to report device alarms. The values of Trap community and Confirm trap community must be the same. The trap community name is automatically set by the system and cannot be manually changed. The default value is Huawei12#$.

    Timeout period

    You are advised to set Timeout period to 30 seconds or longer to avoid the situation where component information is in unknown state for a long time after a server is successfully discovered by using the SNMPv1 template.

    NOTE:

    If component information cannot be fully displayed due to SNMP synchronization timeout when RH2288H V3, RH5885 V2, RH5885 V3, and RH5885H V3 devices are connected to eSight, it is recommended that the timeout interval be prolonged to 40 seconds or longer.

    IPMI

    User information

    User name and password used when servers are added to eSight through IPMI.

    The following operations can only be performed through the IPMI protocol on third-party servers:

    • Querying server manufacturers
    • Querying server models
    • Querying management module versions
    • Querying server fans
    • Querying server mainboards
    • Querying and setting asset IDs
    • Remote power-on
    • Remote power-off
    • Remote reset
    • Setting server power cap values
    NOTE:

    When a third-party server is connected to eSight using the SNMP protocol, the preset server vendor can be displayed. If the IPMI protocol is configured, the detailed server vendor information can be displayed. For example, if you set only SNMP parameters, the displayed vendor is HP. If you enter the IPMI protocol parameters, the displayed vendor is HPE.

    Trap community name

    The trap community name is used to report device alarms. The trap community name entered in the eSight system must be the same as the trap community name of a server to avoid alarm reporting failures.

    The values of Trap community and Confirm trap community must be the same. The default value is public.

    Port number

    Port number used for a third-party server to execute the specified operation through the IPMI protocol. The port number must be the same as that on the third-party server.

    Timeout interval

    Timeout interval for a third-party server to execute the specified operation through the IPMI protocol. The default value is 60 seconds.

    Redfish

    -

    V5 servers and heterogeneous servers are added to eSight through Redfish and report alarms to eSight through SNMP.

    -

    IP Resource Pool

    When the iBMC versions of blades on an E9000 are 2.50 or later, and the HMM versions are 6.50 or later, if no IP address is configured for the blades, you need to configure an IP address resource pool before the E9000 is connected to eSight. When the E9000 is connected to eSight, a resource pool should be selected. After that, eSight automatically allocates IP addresses from this resource pool to blades. For details about configuring an IP address resource pool, see Configuring an IP Address Resource Pool.

  5. Click OK.
  6. Click OK.

    If the server is successfully added, the system automatically switches to the Server > Server Device > Server type page. On the page displayed, you can view the server adding result and manage the server.

  7. To enable the FC switch modules to report alarms and events to eSight, configure SNMP users and trap IP addresses on the switch modules.

    1. Use PuTTY to log in to the switch modules with the IP addresses as the root user.
      NOTE:

      The switch module IP addresses must be configured in advance.

    2. Run the following command to check whether SNMP users exist on the FC switch modules:

      snmpconfig --show snmpv3

      • If yes, no further action is required.
      • If no, go to 7.c.
    3. Run the following command to configure SNMP users:

      snmpconfig --set snmpv3

      The command output is as follows:

      SNMP Informs Enabled (true, t, false, f): [false]
    4. Use the default value false and press Enter.

      The command output is as follows:

      User (rw):
    5. Configure the SNMP users as required.

      Set the parameters as follows:

      • SNMP user name: root
      • Authentication protocol: SHA
      • Authentication password: Huawei12#$
      • Encryption protocol: AES256
      • Encryption password: Huawei12#$
      • Registered trap IP address: IP address of the eSight server
    NOTE:

    A maximum of six SNMP users can be configured each time.

Adding Servers in Batches

When eSight needs to manage a large number of servers, you can use an Excel file to import servers in batches to improve efficiency.

Prerequisites

  • You have the operation permission on Access Resource.
  • You have obtained the IP addresses, types, and communications protocol parameters of the target servers.
  • If eSight is deployed on the Red Hat operating system and the servers need to be added to eSight through IPMI, ensure that the IPMI tool compilation is complete. For the compilation method, see section Preparing for Red Hat Installation in the Single-Node System Software Installation Guide (Red Hat).
  • The HMMs and iBMCs of blade servers can communicate with eSight, and other servers can communicate with eSight.
  • The time zone of the servers is the same as that of eSight.

    If the time zone of the servers is different from that of eSight, the alarm time displayed on eSight is different from that on the iBMC.

Context

  • After adding the switch modules of a blade server, you need to set protocol parameters of the switch modules. For details, see Setting switch module protocol parameters in Managing Blade Servers.
    NOTE:

    eSight cannot obtain the IP address of the FC switch module of a blade server. You need to log in to the serial port of the blade server chassis to obtain the IP address of the FC switch module and reconfigure it on eSight.

  • If a V3 server is added to eSight using the default user root or admin, or a V5 server is added to eSight using the default user Administrator, the communication failure between eSight and the server may be caused by the lockout of the root, admin or Administrator user on the server. It is recommended that you create an administrator account dedicated for interworking with eSight on the server. For details about how to create the account, see How Do I Create an Interconnect Account on a Huawei Server.
  • When the iBMC versions of blades on an E9000 are 2.50 or later, and the HMM versions are 6.50 or later, if no IP address is configured for the blades, you need to configure an IP address resource pool before the blades are connected to eSight in batch import mode. By default, eSight automatically allocates IP addresses from the first IP address resource pool to blades. For details about configuring an IP address resource pool, see Configuring an IP Address Resource Pool.
  • For other restrictions imposed when servers are connected to eSight, see Application Restrictions.

Procedure

  1. Choose Resource > Common from the main menu.

  2. In the navigation tree on the left, choose Add Resource > Import Resource.

    The batch import page is displayed.

  3. Choose Server > Server.
  4. In the Download template area, click the Excel template.
  5. Configure the information about the servers to be imported in batches in the template and save the Excel file.

    NOTE:

    Carefully read the configuration requirements and restrictions on the Notes sheet of the template and configure the template based on the requirements and restrictions.

  6. On the server import page, click corresponding to Upload file and select the Excel file you have saved.
  7. Click Upload.

    The server information in the batch import template is displayed in the lower part of the page.

  8. Select the servers to be added and click Add Device.

    If Status of a server is Failed, determine the failure cause based on the value of Detail.

    If the protocol passwords for importing servers in batches change, import the template again, select the specified servers, click Password Change, and enter the new passwords on eSight.

Adding FC Switch Modules in Batches

IP addresses of FC switch modules connected to eSight through blade servers cannot be obtained. Therefore, you are advised to import FC switch modules in batches using an Excel file.

Prerequisites

  • You have the operation permission on Access Resource.
  • You have obtained the blade server IP address, switch module IP addresses, and protocol parameters.
  • The HMMs and iBMCs of blade servers can communicate with eSight, and other servers can communicate with eSight.
  • The time zone of the servers is the same as that of eSight.

    If the time zone of the servers is different from that of eSight, the alarm time displayed on eSight is different from that on the iBMC.

  • You have created a user with the SNMP permission on the switch modules.
NOTE:

If the user does not have the SNMP permission, run the following command to assign the SNMP permission to the user:

snmpconfig –set snmpv3 admin

In the command, snmpv3 indicates the protocol type used to add switch modules, and admin indicates the user used to add switch modules.

Context

  • After adding the switch modules of a blade server, you need to set protocol parameters of the switch modules. For details, see Setting switch module protocol parameters in Managing Blade Servers.
    NOTE:

    eSight cannot obtain the IP address of the FC switch module of a blade server. You need to log in to the serial port of the blade server chassis to obtain the IP address of the FC switch module and reconfigure it on eSight.

  • If a V3 server is added to eSight using the default user root or admin, or a V5 server is added to eSight using the default user Administrator, the communication failure between eSight and the server may be caused by the lockout of the root, admin or Administrator user on the server. It is recommended that you create an administrator account dedicated for interworking with eSight on the server. For details about how to create the account, see How Do I Create an Interconnect Account on a Huawei Server.

Procedure

  1. Choose Resource > Common from the main menu.

  2. In the navigation tree on the left, choose Add Resource > Import Resource.

  3. On the Import Resource page, select Server > FC switch module.
  4. In the Download template area, click the Excel template.
  5. Configure the information about the switch modules to be added in batches in the Excel template and save the Excel file.

    NOTE:

    Carefully read the configuration requirements and restrictions on the Notes sheet of the template and configure the template based on the requirements and restrictions.

  6. On the FC switch module import page, click corresponding to Upload file and select the Excel file you have saved.
  7. Click Upload.

    The FC switch module information in the batch import template is displayed in the lower part of the page.

  8. Select the FC switch modules to be added and click Add Device.

    If Status of an FC switch module is Failed, determine the failure cause based on the value of Detail.

  9. To enable the FC switch modules to report alarms and events to eSight, configure SNMP users and trap IP addresses on the switch modules.

    1. Use PuTTY to log in to the switch modules with the IP addresses as the root user.
      NOTE:

      The switch module IP addresses must be configured in advance.

    2. Run the following command to check whether SNMP users exist on the FC switch modules:

      snmpconfig --show snmpv3

      • If yes, no further action is required.
      • If no, go to 9.c.
    3. Run the following command to configure SNMP users:

      snmpconfig --set snmpv3

      The command output is as follows:

      SNMP Informs Enabled (true, t, false, f): [false]
    4. Use the default value false and press Enter.

      The command output is as follows:

      User (rw):
    5. Configure the SNMP users as required.

      Set the parameters as follows:

      • SNMP user name: root
      • Authentication protocol: SHA
      • Authentication password: Huawei12#$
      • Encryption protocol: AES256
      • Encryption password: Huawei12#$
      • Registered trap IP address: IP address of the eSight server
    NOTE:

    A maximum of six SNMP users can be configured each time.

FAQ and Troubleshooting Typical Configuration Examples

This topic describes how to resolve issues that may occur during server management by using eSight.

Failed to Add a Server on eSight After the Server IP Address Is Changed

Symptom

A server is failed to add on eSight after the server IP address is changed.

Possible Causes

The existing server is not deleted.

Procedure

  1. Delete the existing server on eSight.

    NOTE:

    This topic uses a rack server as an example to describe how to delete the existing rack server on eSight as required.

    1. On the menu bar, choose Resource > Server.
    2. In the navigation tree, choose Server > Rack Server.
    3. In the function pane, select the existing server.
    4. Click Delete.
    5. Click OK.

  2. Go to The Add Resource page.

    1. On the menu bar, choose Resource > Common.
    2. In the navigation tree, choose Add Resource > Add Resource.

      The Add Resource page is displayed, add a server as required.

What Can I Do If the System Displays a Message Indicating that Basic Information Failed to Be Queried When a Server Is Added to eSight

Symptom

eSight fails to add a server.

Possible Causes

The product name or serial number of the server is missing. As a result, eSight fails to add the server.

Fault Diagnosis

Check whether the product name and product serial number lack.

  1. Log in to the server WebUI.
  2. In the navigation tree, choose Information > Overview.
  3. Check the product name and product serial number.

Procedure

  1. If server faults cause the lack of the product name or product serial number, contact Huawei technical support.

Failed to Add a Server to eSight, and a Message Is Displayed, Indicating that Data Failed to Be Stored in the Database

Symptom

A message indicating "Failed to store data to the database" is displayed when eSight fails to add the server.

Possible Causes

An eSight IT database is abnormal.

Fault Diagnosis

NOTE:

The possible cause for database writing failures is database or table abnormality.

  1. Restart eSight and the database. This problem persists.
  2. Query the eSight IT database information in the database, and a message indicating "It has been marked SUSPECT by recovery" is displayed.

Procedure

  • Method 1: Recreate an eSight IT database.

  • Once the new eSight IT database is created, the data in the original eSight IT database will be lost. Exercise caution when performing this operation.
  • eSight needs to add and configure servers again after the eSight IT database is created.
  1. In the eSight Console window, click Stop to stop eSight.

  2. On the PC, in the Run text box, enter cmd to open the command window.
  3. Enter the following command to create the eSight IT database.
    NOTE:
    • The command varies depending on the database type.

      This topic uses the SQL Server database as an example. Enter the command based on the actual database type.

    • Before creating the eSight IT database, delete all tables in the original eSight IT database.
    • Tables are automatically generated when new eSight IT database is created.
    osql -UDatabase user name -PPassword of the database user name 
    drop database esightit 
    go     
    NOTE:

    This command is used to delete the tables in the original eSight IT database.

    create database [ESIGHTIT] on 
    ( name = [ESIGHTIT_dat], 
      filename = 'D:\data\ESIGHTIT_DB.mdf', 
      size = 100, 
      maxsize = 500, 
      filegrowth = 10 
    ) 
    log on 
    ( name = [ESIGHTIT_log], 
      filename = 'D:\data\ESIGHTIT_LOG.LDF', 
      size = 100, 
      maxsize = 500, 
      filegrowth = 10 
    ) 
    go
    NOTE:

    This command is used to create the new eSight IT database.

  4. In the eSight Console window, click Start to start eSight.

    After the eSight IT database is created, add and configure the servers again.

  • Method 2: Go to eSight\uninstall and uninstall eSight.

    Reinstall the eSight for the eSight IT database to recover.

After eSight is uninstalled, all data is lost. Exercise caution when performing this operation.

How to Query Huawei Server Device Protocol Parameters

Symptom

The access protocol parameters of the eSight server must be consistent with the corresponding device protocol parameters. How to query the Huawei server protocol parameters?

Possible Causes

None

Procedure

  1. Obtain the WebUI initial account information of the Huawei server device.

    Find the server information label on the server and find the default server account information on the label.

  2. Log in to the device WebUI.
  3. Query the device protocol parameters.

    • E9000

      Querying SNMP parameters

      Access Protocol Parameter

      How to Query on the WebUI

      Username and Password

      User name and password for logging in to the E9000 WebUI.

      NOTE:

      The initial login user name and password are root and Huawei12#$ respectively.

      Authentication protocol and Data encryption protocol

      Choose System Management > System Settings > Security Policy. The Security Policy page is displayed.

      In the function pane, click Edit and set SNMP V3 and SNMP Trap V3 Authentication protocol and SNMP V3 and SNMP Trap V3 Privacy protocol.

    • Rack, high-density, and KunLun servers
      • IPMI

      Access Protocol Parameter

      How to Query on the WebUI

      Username and Password

      WebUI login user name and password of the server device.

      NOTE:

      The initial login user name and password are root and Huawei12#$ respectively.

      Trap community

      Choose Common Tasks > SNMP Trap Configuration. The SNMP Trap Configuration page is displayed.

      SNMP Trap Community indicates the required trap community name.

      • SNMP

        Access Protocol Parameter

        How to Query on the WebUI

        Retry times

        -

        Timeout period

        -

        Username

        WebUI login user name of the server device.

        NOTE:

        The initial login user name are root.

        Authentication protocol and Data encryption protocol

        Choose Configuration > System.

        The SNMPv3 area displays the authentication protocol and data encryption protocol.

        Authentication password and Data encryption password

        WebUI login password of the server device.

        NOTE:

        The initial login password is Huawei12#$.

        Port

        Choose Configuration > Services.

        SNMP Agent indicates the port number required.

        Read community and Write community

        Choose Configuration > System.

        SNMPv1 or SNMPv1 indicates the required read and write community names.

        Trap community

        Choose Alarm & SEL > Alarm Settings.

        Community Name indicates the required trap community name.

What Do I Do if eSight Fails to Discover Servers Automatically

Symptom

eSight fails to detect servers automatically.

Possible Causes

  • eSight does not add SNMP and IPMI at the same time.
  • LAN channels for servers to be added are not enabled.

Procedure

  • eSight does not add SNMP and IPMI at the same time.

    eSight can detect the servers automatically only when SNMP and IPMI are added at the same time.

    • IPMI is used to add rack servers, and high-density servers.
    • SNMP is used to add rack servers, blade servers, high-density servers, and third-party servers.
  • The LAN channels for servers to be added are not enabled.

    eSight can detect the servers automatically only when the LAN channels for servers to be added are enabled.

    NOTE:

    When eSight add a single server, the LAN Plus channel for the server needs to be enabled.

    1. Log in to the server WebUI.
    2. In the navigation tree, choose Configuration > Service.
    3. In the Services Configuration list, select IPMI LAN(RMCP) to enable the LAN channel.
      NOTE:
      • Select IPMI LAN(RMCP+) to enable the LAN channel.
      • Select IPMI LAN(RMCP+) to enable the LAN Plus channel.

How to Manually Register eSight Trap IP Addresses with Switch Modules

Symptom

After a switch module is added to eSight, the eSight trap IP address cannot be automatically registered with the switch module, and therefore alarms of the switch module cannot be reported to eSight.

Possible Causes

  • More than 20 trap IP addresses have been registered with the switch module.
  • The switch module has incorrect settings of parameters such as IP addresses, user names, passwords, and protocol types.

Procedure

  1. Use PuTTY to log in to the switch modules with the IP addresses and root user of the switch modules.

    NOTE:

    IP addresses are configured for the switch modules.

  2. Run the following command to display the system view:

    system-view

  3. Run the following command to check whether the eSight trap IP address is registered with the switch module:

    display this

    NOTE:

    If southbound and northbound services are separated for eSight , the eSight IPv4 address here refers to the southbound IP address. Please refer to the How to Obtain the IP Address of eSight to obtain the IP address.

    • If yes, no further action is required.
    • If no, perform either of the following operations:
      • If the number of trap IP addresses registered with the switch module reaches the upper limit, go to Step 5.
      • If the number of trap IP addresses registered with the switch module does not reach the upper limit, go to Step 4.
    NOTE:

    A maximum of 20 trap IP addresses can be registered with each switch module.

  4. Delete an unwanted trap IP address from the switch module.

    1. Run the following command to delete an unwanted trap IP address from the switch module:

      undo snmp-agent target-host trap address udp-domain eSight IPv4 address source MEth0/0/0 params securityname eSightSwitch

    2. Run the following command for the configuration to take effect:

      commit

  5. Register the eSight trap IP addresses with the switch module.

    1. Run the following command to register the eSight trap IP addresses with the switch module:

      snmp-agent target-host trap address udp-domain eSight IP address source MEth0/0/0 params securityname eSightSwitch v3 privacy

    2. Run the following command for the configuration to take effect:

      commit

How Do I Create an Interconnect Account on a Huawei Server

Symptom

  • A server cannot access eSight.
  • After a server is added to eSight, the server's monitoring information cannot be refreshed.

Possible Causes

If a server is added to eSight using the default user root or admin, the communication failure between eSight and the server may be caused by the lockout of the root or admin user on the server.

Procedure

  • iBMC
    1. Log in to the server iBMC as an administrator.
    2. On the menu bar, choose Configure.

      The Local Users page is displayed by default.

    3. Click Add.
    4. Configure the new account.
      • Set New User Name to eSightUser01.
      • In the Login Interface text box, select all interfaces.
      • Set Role to Administrator.
    5. Click Save.
  • iMana 200
    1. Log in to the server iMana 200 as an administrator.
    2. On the menu bar, choose Configuration > User.

      The Local User page is displayed by default.

    3. Click corresponding to User ID.
    4. Configure the new account.
      • Set User Name to eSightUser01.
      • Set User Group to Administrator.
    5. Click OK.
  • HMM WebUI
    1. Log in to the HMM WebUI as an administrator.
    2. On the menu bar, choose System Management.
    3. In the navigation tree, choose Account Management > MM User Management.
    4. Click New User.
    5. Configure the new account.
      • Set User name to eSightUser01.
      • Set Belong to to superdomain.
      • Set User Group to Administrator.
      • In the User Interface text box, select all interfaces.
    6. Click OK.

Failed to Add a Server to eSight

Symptom

Adding a rack or E9000 server to eSight failed.

Possible Causes

  • The communication between eSight and the server is abnormal.
  • Firewall is enabled or port 161 is disabled for the servers.
  • The access information configured in eSight is different from that on the server.

Procedure

  • Rack server
    1. Check that the communication between eSight and the rack server iBMC is normal.
    2. Check that firewall is disabled and port 161 is enabled for the rack server.
    3. Check that the SNMPv3 encryption protocol and encryption password configured in eSight are the same as those on the rack server.
    4. Check whether the eSight server has multiple IP addresses. If the IP address specified during eSight installation cannot communicate with the IP address of the server management port, the function for managing devices in several subnets must be enabled.

      The procedure for enabling the multi-subnet function on eSight is as follows:

      • Windows

        See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Single-Node System Software Installation Guide (Windows).

      • SUSE Linux
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Single-Node System Software Installation Guide (SUSE Linux).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Local High Availability System Software Installation Guide (SUSE Linux + Oracle + Veritas).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Remote High Availability System Software Installation Guide (SUSE Linux + Oracle + Veritas).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Local High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Remote High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA).
    5. If the server still cannot be added to eSight after 1 to 4, perform the following:
      1. Create an administrator on the rack server and use the administrator to add the server to eSight.

        For the administrator creation method, see How Do I Create an Interconnect Account on a Huawei Server.

      2. Change the encryption protocol on the rack server and use the new protocol to add the server to eSight.
      NOTE:
      • The default subnet of eSight is recommended for adding a rack server to eSight.
      • Incorrect product name or SN of the rack server will lead to the failure to add the server to eSight.
  • E9000 server
    1. Check that the E9000 is added to eSight through the floating IP address of the SMM and that the communication between eSight and the floating IP address is normal.
    2. Check that firewall is disabled and port 161 is enabled for the E9000.
    3. Check that the SNMPv3 encryption protocol and encryption password configured in eSight are the same as those on the E9000.
    4. Check whether the eSight server has multiple IP addresses. If the IP address specified during eSight installation cannot communicate with the IP address of the server management port, the function for managing devices in several subnets must be enabled.

      The procedure for enabling the multi-subnet function on eSight is as follows:

      • Windows

        See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Single-Node System Software Installation Guide (Windows).

      • SUSE Linux
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Single-Node System Software Installation Guide (SUSE Linux).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Local High Availability System Software Installation Guide (SUSE Linux + Oracle + Veritas).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Remote High Availability System Software Installation Guide (SUSE Linux + Oracle + Veritas).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Local High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA).
        • See Commissioning the eSight > Configuring System Services > (Optional) Configuring Multi-Subnet Management in the Remote High Availability System Software Installation Guide (SUSE Linux + MySQL + OMMHA).
    5. Check that no static IP address is configured for the E9000 SMM and that the Shelf Type value under Manufacturing Information of Chassis Information contains E9000. See the following figure.

    6. If the server still cannot be added to eSight after 1 to 5, perform the following:
      1. Create an administrator on the E9000 SMM and use the administrator to add the server to eSight.

        For the administrator creation method, see How Do I Create an Interconnect Account on a Huawei Server.

      2. Change the encryption protocol on the E9000 and use the new protocol to add the server to eSight.
      NOTE:
      • The default subnet of eSight is recommended for adding an E9000 to eSight.
      • Incorrect product name or SN of the E9000 will lead to the failure to add the server to eSight.

How Do I Handle the Failure in Synchronizing Blade Alarms Using an SMM Board of Version 6.81 to 6.88 in Non-Flat Scenarios

Symptom

If an SMM board of version 6.81 to 6.88 is used on the E9000 server in non-flat scenarios, blade alarms fail to be synchronized using the SMM board.

Possible Causes

When the SNMP interface is used to query blade alarms of the E9000 server through the SMM board, some alarms are lost because the format of the returned event code is different with that queried on the E9000 server.

Procedure

  1. Log in to the E9000 chassis as the root user.
  2. Run the following command to view E9000 precise alarms:

    smmget -d precisealarmswitch

  3. Run the following command to disable the precise alarm function of the E9000 server:

    smmset -d precisealarmswitch -v OFF

What Can I Do If the Server Power Status Is Incorrectly Displayed on the eSight Home Page

Symptom

On the eSight Home page, the power status is incorrectly displayed.

Possible Causes

After the eSight service is restarted, the server power status is incorrectly displayed.

Procedure

  1. On the menu bar, choose Resource > Server.
  2. In the navigation tree, choose Server Device > Server type.

    Available server types are rack, blade, high-density, KunLun, third-party, and heterogeneous servers.

  3. Select the server to be refreshed and click Refresh.
  4. Repeat 2 and 3 to refresh all servers.

How Do I Check Whether Alarms Are Properly Reported from Servers to eSight

Question

eSight cannot receive alarms reported by servers. How do I check whether alarms are properly reported from servers to eSight?

Answer

  1. Log in to the iBMC UI of the server as the Administrator user.
  2. Choose Alarm & SEL > Alarm Settings from the main menu.
  3. In the Trap Notification Settings area, click Test corresponding to the specified Trap server.

    The server sends a test alarm to eSight to check whether the SNMP Trap function is normal.
    NOTE:

    After a server is connected to eSight, the Trap IP address of eSight is automatically registered with the server.

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 333779

Downloads: 667

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