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


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


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).
FAQ and Troubleshooting Typical Configuration Examples

FAQ and Troubleshooting Typical Configuration Examples

No Alarm Is Reported When a Blade Is Replaced


When a blade is added to the stateless computing domain, no alarm is reported after the blade is replaced. As a result, the stateless computing task cannot be triggered.

Possible Causes

The number of trap IP addresses in the list on the server web user interface (WebUI) reaches the threshold. As a result, the eSight IP address fails to register in the trap IP address list of the server.


  1. Delete unused IP addresses from the trap IP address list on the server WebUI.
  2. Add the eSight IP address to the trap IP address list.
  3. Confirm and save the modification.

Failed to Activate a Profile After a Compute Node Is Replaced or Configured Offline and Then Installed


A profile fails to be activated after a compute node is replaced or configured offline and then installed.

Possible Causes

  • The trap IP address fails to be registered.
  • The power-on policy is not set to automatic power-on on the iMana web user interface (WebUI). As a result, the device cannot send a power-on request.


  • Register the trap IP address by using the shelf management module (SMM) on the blade server.
  • On the iMana WebUI, set the power-on policy to automatic power-on.
    1. On the iMana WebUI, choose Configuration > System Configuration > Power Restore Policy.
    2. Select Turn On and click OK.
    3. Click OK.

eSight Failed to Receive Controlled Power-on Requests and eSight Stopped Responding to the Server Activating Operation When the Stateless Computing Feature Is Used


eSight fails to receive controlled power-on requests from a server.

If the stateless computing feature is used, eSight stops responding to the server activating operation and the Activation Status column displays Not Activate all the time.

Possible Causes

The stateless ID in eSight is inconsistent with that of the server.


The stateless ID identifies a device that supports stateless computing.


  1. Open the server list.

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

    The server type can be Rack Server, BladeServer, or High-density Server.

  2. In the server list in the right pane, click, corresponding to the server, in the Operation column to refresh the server.

    The stateless IDs in eSight are updated.

  3. Open the stateless computing page and add the server to the device collection again.

    1. On the menu bar, choose Resource > Server.
    2. In the navigation tree, choose Stateless Computing > Domain Management > Domain.
    3. Click Add.

      On the displayed page, add the server.

  4. Associate a device with a profile and activate the device.

    1. Click next to the server name.

      The Associate the Profile dialog box is displayed.


      If is unavailable in the Operation column, click Configuration in the Operation column first.

    2. In the Select Profile area, select the profile to be associated with the device.
    3. Select an option from the Activation mode drop-down list.
    4. Click OK.

      The confirmation dialog box is displayed.

    5. Click OK.

How Do I View the Configuration Information of the Stateless Computing Module


How to view the configuration information of the stateless computing module?


  1. Log in to the KVM.

    Log in to the server WebUI. Choose Remote Control in the navigation tree, and click Remote Virtual Console.

  2. Go to the in-band deployment directory (/home/ff/eSightCfg) and fully out-of-band deployment directory (/home/outband/eSightCfg) to view configuration information.

    • The result.XML file details the configuration results.
    • The profile.XML file details the profiles created by a user.
    • The MegaSAS.log file details RAID controller card loading results.
    • The cfg_and_export_run.log_CNA_X.log file details configuration results of all CNAs.

    The number of files varies depending on the server configurations.

    The following figure is for reference only.

How to Manually Synchronize the Files on a Two-Node Cluster


If the server runs on a two-node cluster, the file cannot be automatically updated. Instead, it requires manual modification.

To implement the server stateless computing function and automatic detection function, a device communicates with eSight, and eSight uses port 26957 to listen to the power-on request and automatic detection request on the device. The IP address matching this port is the default IP address bound during eSight installation. To change the bound IP address, change it in the configuration file.

If the server runs on a two-node cluster, and the IP address bound with port 26957 on one of the nodes has been changed, manually change the IP address in the configuration file of the other node accordingly and ensure that the new IP address is the one that eSight on the node uses to communicate with iBMC.


  1. Open the configuration file serverPortBinding.conf in eSight installation directory/AppBase/lib/resources/network/.
  2. Set monitorIP to the IP address of the network port for which the listening service needs to be enabled.

    Configuration example:


  3. Save and close the configuration file.
  4. Restart eSight.

How to Solve the Upload Failure, Configuration Export Failure, CNA Deployment Failure of the CH226 V3


During the stateless computing, the CH226 V3 fails to be uploaded, export configuration information, or deploy a CNA node, caused by the error information about the MXEF.


  1. Restart the board, press CTRL+P to enter the NIC BIOS screen to check whether the NIC configuration parameters are as follows:

    • MultiChannel Mode: Enabled
    • Advanced Mode Support: Disabled
    • Personality: NIC

  2. If yes, set Advanced Mode Support to Enabled and click Save to exit the BIOS screen.

    Advanced Mode Support is an advanced NIC interruption parameter for adding NIC queues and improving NIC performance. By default, Advanced Mode Support is enabled, but disabled in earlier NIC firmware versions.

    Figure 9-15 Configuration Diagram

    If the problems still exist, replace the NIC and contact Huawei engineers.

Failed to Download Configuration Tool Package During eSight In-Band Deployment


In in-band networking scenarios, a message indicating A configuration tool package download failure is displayed when eSight communicates with a small OS.

Possible Causes

The iBMC date and the date supported by the HostAgent certificate are inconsistent.


  1. Change the server system time.

    1. Log in to the server KVM.
    2. Restart the server. Press Delete during the restart.

      Go to the server BIOS.

    3. On the Main screen, change the values of the System Time and System Date parameters to the current time.
    4. Press F10 to save the settings and close the BIOS configuration screen.

  2. Perform the in-band configuration again after the server restart.

How to Resolve Configuration Deployment, Firmware Upgrade, or Stateless Computing Failures After Default VMM Port Change


After the default VMM port is changed, BIOS/RAID/HBA/CNA configuration deployment, firmware upgrade, or stateless computing fails.

Possible Causes

The default VMM port of the server must be used when eSight executes firmware upgrade, stateless computing, and BIOS/HBA/CNA deployment. If the default VMM port is changed, the connection to the virtual media fails, and the preceding tasks fail.


  • Log in to the server WebUI.
  • Go to the VMM port configuration page.
  • Restore the default configuration.
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 335579

Downloads: 671

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