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

Failed to Upload Software Due to the Automatic Logout of the Client During an Attempt to Add a Software Source on eSight


When a user attempts to add a software source on eSight, software uploading fails because the client logs out automatically.

Possible Causes

The function for logout upon timeout is enabled on eSight and the value of Idle time (min) is less than the time required for uploading software.


  1. On the menu bar, choose System > User Management > My Settings.
  2. Configure the function for logout upon timeout.

    • Select Enable auto logout and increase the value of Idle Time. It is recommended that you set the idle duration to 1 hour.
    • Deselect Enable auto logout to disable the function.

  3. Click Apply.

Failed to Install the SLES OS Due to Error Partitioning Format


The SLES OS installation fails and the system displays "Error while configuring partitions. Try again".

Possible Causes

The SLES OS to be installed does not support the partitioning format.

Fault Diagnosis

  1. When the message in the following figure is displayed, press Ctrl+Alt+F2 to enter the CLI.

  2. Enter fdisk –l and press Enter. The following alarm information is displayed.

    The SLES OS does not support the GUID partition table (GPT) format. Convert the disk format to the master boot record (MBR) format.


  1. Press Ctrl+Alt+F2 to switch to a terminal screen.
  2. Run the fdisk –l command to view disk information. Perform boot partition on the disk where the OS is installed, that is, convert the GPT format to the MBR format.
  3. Run the parted –s /dev/sda mklabel msdos command to install the OS in the disk partition.
  4. Reinstall the SLES OS.

What Do I Do If eSight Fails to Deploy Windows


Copying file fails.

Possible Causes

The server where eSight is installed and the managed server are not in the same work group.

Fault Diagnosis

The attempt to access the shared directory of the server where eSight is installed fails.

You may not have the permission to use the network resource. Contact the server administrator to check whether you have the permission.

Multiple connections between the server or shared resource and one user using more than one user name are not allowed. Disconnect these connections and access the shared resource or the server again.


  1. Log in to the server where eSight is installed.
  2. On the Start menu, right-click Computer and choose Properties from the shortcut menu.
  3. In the Computer name, domain, and workgroup settings area, check whether the server where eSight is installed and the managed server are in the same work group.

    Method for changing the work group as follows:

    1. Click Change settings.
    2. In the System Properties window, click Computer Name.
    3. Click Change.
    4. In the Computer Name/Domain Changes window, select Workgroup and enter the new work group name in the Workgroup text box.
    5. Click OK.

  4. Remotely access the shared directory of the server where eSight is installed.

    If the access is successful, you can deploy Windows.

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 to Resolve the ServiceCD Inexistence or File Name Error During Operating System Deployment


During operating system deployment, the system displays a message to indicate that the ServiceCD software does not exist or its file name is incorrect.

Possible Causes

  • The ServiceCD software does not exist in the eSight installation directory.
  • The directory name of the ServiceCD software in the eSight installation directory does not comply with the required format.


  1. Log in to and download the SoftwareCD software.
  2. Decompress the downloaded software package.
  3. Change the name of the .iso file to FusionServer Tools-ServiceCD2.0-V110.iso.
  4. Copy FusionServer Tools-ServiceCD2.0-V110.iso to eSight installation directory\AppBase\var\iemp\data\ftp\.

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 View the Configuration Information of the Configuration and Deployment Module


How to view the configuration information of the configuration and deployment 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.

What Can I Do If the BIOS/CNA/RAID of E9000 Blades Fails to Be Configured or the CNA/RAID of E9000 Blades Fails to Be Upgraded on eSight


  • When the BIOS, CNA, or RAID configuration is delivered to E9000 blades, the virtual media connection failed.
  • When the CNA or RAID of E9000 blades is upgraded, the virtual media connection failed.

Possible Causes

  • The HMM user does not have the KVM permission.
  • The communication between eSight and the managed server is abnormal.


  1. Access the HMM web page of the blade server.
  2. Check whether the HMM users (including the root user) have permission on the KVM interface.

    • If yes, no further action is required.
    • If no, perform 3~5.

  3. Connect the HMM910 serial port and the PC using a serial cable.
  4. Use PuTTY and the IP address of the HMM910 serial port to log in to the port as an HMM user from the PC.
  5. Run the following command to add the KVM interface permission:

    smmset [ -l smm ] -d userintfauth -v root privilege

    • This command can be run only through the HMM910 serial port.
    • In the preceding command, privilege indicates the interface permission. You can set it as required. For details, see the MM910 Management Module Command Reference.

What Can I Do If the Hard Disk Slots Do Not Match During RAID Configuration


When configurations are delivered to servers through a RAID template, the system displays a message indicating that the hard disk slots do not match.

Possible Causes

The iBMC page of a server displays the physical slot numbers of the hard disks. When multiple RAID controller cards are inserted, if you select hard disk slots based on the physical slots, eSight may fail to identify the hard disks.


If the hard disk backplane of the server has no expander, select the slot numbers as follows: For a RAID controller card with two ports, the hard disk numbers of each RAID controller card should range from 0 to 7. The RAID controller card types include LSI SAS2308, LSI SAS2208, LSI SAS3008, LSI SAS3108, Avago SAS3408iMR, and Avago SAS3508.

When creating a RAID template, select slots based on the hard disk slot numbers of the RAID controller card.

For example, as shown in Figure 9-7, during the RAID controller card configuration for the PCIe Card 4, PCIe Card 6, or PCIe Card 8 slot, the hard disk slots selected for the Avago SAS3508 RAID controller card are physical slots. During the configuration on eSight, the slots selected should start from slot 0 of the RAID controller card, as shown in Figure Figure 9-8.

Figure 9-7 Storage information about a server
Figure 9-8 RAID controller card slot configuration on eSight
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 309970

Downloads: 633

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