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 09

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

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

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 Do I Customize a Big Package for Firmware Upgrade


How do I customize a big package for firmware upgrade?

  1. In the address box of the browser, enter and press Enter.

    The Huawei Server Online Software Package Download Tool page is displayed.

  2. Click Add.

  3. Set Device Type, Device Model, Device Version, and Firmware Type. Then click Add to List.


    One device model in a customized big package corresponds to only one device version. Otherwise, the system displays a message indicating that the verification fails when the package is uploaded to eSight.

  4. Repeat 2 to 3 to add the latest software packages of all device models of the specified device type to the software package list. Then enter a file name for saving these software packages and click Download.

  5. Click Progress to check the packaging progress.

  6. In the lower right or left corner of the page, obtain the customized big package.

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.

How Do I View the Configuration Information of the Firmware Upgrade Module


How to view the configuration information of the firmware upgrade 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 firmware upgrade results.
    • The profile.XML file details the firmware upgrade information.

How Do I Obtain the IP Addresses of Servers from a Subnet Specified by eSight


How do I obtain the IP addresses of servers from a subnet specified by eSight?

  1. Log in to the eSight server.


    If eSight is deployed in active/standby mode, perform the following operations on both the active and standby nodes.

    • Windows operating system

      Log in to the eSight server as the administrator user.

    • Linux operating system

      Log in to the eSight server as the ossuser user.

  2. Open the vlan.conf file in eSight installation directory\AppBase\lib\resources\network.
  3. Modify the VlanId and cfgVlanId parameters based on the site requirements.

    • The VlanId parameter is used for stateless computing.
    • The cfgVlanId parameter is used for configuration deployment and firmware upgrade.
    • The values of VlanId and cfgVlanId range from 2 to 4094.
    • Set the VlanId and cfgVlanId parameters to obtain IP addresses in a specified VLAN through the DHCP protocol. The VlanId parameter is mandatory. If the cfgVlanId parameter is not set, IP addresses are obtained from the default network segment through the DHCP protocol.

How Do I Query the Physical Server Where the eSight VM Is Located


How do I query the physical server where the eSight VM is located when eSight is deployed on a VM?

  • Scenario when virtual resources are managed by eSight
    This section assumes that the eSight VM and its physical server are managed by the FusionSphere.
    1. Choose Resource > Server from the main menu.
    2. In the navigation tree on the left, choose FusionSphere.
    3. In the virtual resource list, click the name of a virtual resource.
    4. In the navigation tree on the left, choose Computing Resources > Virtual Machines.
    5. In the VM list, click the eSight VM name.

      In the Basic Information area, view the name of the host that the eSight VM belongs to.

    6. Click the host name.

      In the Basic Information area, view the host name, IP address, and associated physical server.

  • Scenario when virtual resources are not managed by eSight
    1. Query the host BMC IP address and server serial number on the virtualization management platform.
    2. Query the physical server where the eSight VM is located based on the host BMC IP address and server serial number.

What Can I Do If the Firmware Upgrade Duration Is Incorrect Due to the DST Transition


The firmware upgrade duration is incorrect, as shown in the following figure.

Possible Causes

Due to the DST transition, the end time of the firmware upgrade task is earlier than the start time. As a result, the firmware upgrade duration is incorrectly calculated.

  1. Confirm the DST skipped time in the current time zone.
  2. Calculate the value of Upgrade Period based on the end time of the firmware upgrade task and DST skipped time.

    Firmware upgrade duration = End time + DST skipped time - Start time

    For example:

    • Year: 2018
    • Time zone: UTC+00:00
    • DST skipped time: 60 minutes
    • Start time: 2018-10-28 02:33:32
    • End time: 2018-10-28 02:02:32
    • Firmware upgrade duration: 02:02:32 + 60 minutes – 02:33:32 = 00:29:00

Updated: 2019-05-17

Document ID: EDOC1100011877

Views: 285047

Downloads: 550

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