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 V300R010C00SPC200, 300, and 500 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).


eSight Backs Up the Configuration File of a Device Multiple Times, But Only One Configuration File Exists. Why


Only when the configuration file of a device is modified, eSight saves a copy of the modified configuration file additionally.

When Different VSs on the Same Physical Device Are Added to the Same Backup Group, eSight Fails to Periodically Back Up Configuration Files of Some VSs. How Can I Solve the Problem


When different virtual systems (VSs) on the same physical device are added to the same backup group, the VSs compete for resources when the physical device accesses eSight. As a result, eSight does not back up configuration files of the VSs that fail to occupy resources. It is recommended that different physical devices or VSs be added to one backup group.

Why Some Files Cannot Be Uploaded When eSight Functions as the SFTP Server


The SFTP service of eSight can upload files in specified formats. The formats are configured in the med_node_1_svc.xml file. The procedure is as follows:

  1. Open the med_node_1_svc.xml file in eSight installation directory\AppBase\sysagent\etc\sysconf\svcbase.
  2. Set permitFileType to a regular expression supported by Java. If this parameter is left empty, the file format is not limited. However, security risks exist if this parameter is left empty.
    <config name="sftp">
                    <param name="enable">true</param>
                    <param name="listenerPort">31922</param>
                    <param name="CAKeystoreFileName">etc/certificate/application/med/sftp/ca/sftpCATrustStore.jks</param>
                    <param name="CAPass">@010200000000f98fe2f6937545a06a9617e4927972c033611ad2111c21f4b0aeba68127a5c01</param>
                    <param name="keystoreFileName">etc/certificate/application/med/sftp/keys/sftpKeyStore.jks</param>
                    <param name="sslPassword">@010200000000f98fe2f6937545a06a9617e4927972c033611ad2111c21f4b0aeba68127a5c01</param>
                    <param name="permitFileSize">629145600</param>
                    <param name="permitFileType">([xX][mM][lL]|[cC][sS][vV]|[tT][xX][tT]|[zZ][iI][pP]|[cC][fF][gG]|[bB][iI][nN]|[cC][cC]|[tT][mM][pP]|[pP][aA][tT]|[bB][aA][kK]|[pP][tT][sS]|[pP][aA][tT][cC][hH]|[iI][nN][iI]|[bB][iI][oO][sS]|[pP][eE][mM]|[rR][oO][mM]|[tT][aA][rR]|[gG][zZ]|[jJ][kK][sS]|[kK][eE][yY][sS][tT][oO][rR][eE]|[mM][bB][fF]|[pP][aA][fF]|[dD][aA][tT]|[hH][wW][!])</param>
                    <param name="sftpMAC">hmac-sha2-256,hmac-sha1,hmac-md5,hmac-md5-96,hmac-sha1-96</param>
  3. Save the configuration file and restart eSight.

What Can I Do When I Fail to Back Up Cisco Configuration Files


What can I do when I fail to back up Cisco configuration files?


  • If a timeout error occurs when you back up Cisco configuration files by running commands, the Cisco device is faulty.
  • Check the FTP service password. When FTP is used to transfer Cisco configuration files, the FTP service password cannot be set to 0 to 7.

What Can I Do When Configuration File Backup Through SNMPv3 Fails


In SNMPv3, the default read mib view is ViewDefault and the mib-view that can be written and notified is empty. During the backup, the MIB node needs to be set but the MIB node that can be written is empty. As a result, the backup fails. How Do I do?


Run the following commands to set the SNMPv3 MIB view to ISO:

  • snmp-agent mib-view View_ALL include iso
  • snmp-agent group v3 snmpv3usergroup privacy read-view View_ALL write-view View_ALL notify-view View_ALL

When eSight Compares Configuration Files, a Message Is Displayed, Indicating that the File Has Been Deleted. How Can I Solve the Problem


When eSight backs up a configuration file, if the new configuration file is the same as the latest one, the latest configuration file will be deleted.

How Do I Solve the Problem that eSight Fails to Back Up Devices' Startup Configuration Files


This error may occur if the startup configuration files are unavailable. Ensure that startup configuration files exist.

How Do I Restore the Specified Configuration File for CE Switches Running V100R003C00 and Later Versions


Open the file in eSight installation directory/AppBase/etc/conffile and change the value of ce.rollback.enable to true to restore the specified configuration file of CE switches. After you perform the restoration operation for CE switches, they use the specified configuration file.

Compared with traditional restoration, this function restores all the addition, deletion, and modification made to CE switches' configuration files.

How Do I Configure the Configuration File Management Function of eSight to Generate a Device Configuration File Copy with a Fixed Name


When backing up the configuration file of a device, the configuration file management function of eSight generates a configuration file whose name contains the backup execution timestamp. Therefore, the backup configuration files cannot be accurately differentiated based on the file name.

In some scenarios (such as zero-touch deployment of a CE device), users need to obtain configuration files with fixed names. Therefore, eSight needs to be configured to copy the backup device configuration files and generate files with fixed names. In addition, a new configuration file backup task needs to be executed for eSight to replace the configuration files with fixed names, ensuring that the latest configuration files are stored.


  1. Enable the function of generating configuration files with fixed names in the file.

    By default, this function is disabled in eSight.

    1. Log in to the eSight server as the administrator.
    2. Modify the {eSight installation directory}\AppBase\etc\conffile\ configuration file.

      Set save.fixed.file.enable to enable to enable the function of generating configuration files with fixed names.

    3. Restart eSight for the configuration to take effect.
  2. Back up the device configuration file.

    Choose Resource > Network > Configuration > Configuration File Management from the main menu, choose Manage Config Files > Config Files, select related devices, and back up the configuration files of the devices.

  3. Check the device configuration file backup result.
    1. Log in to the eSight server as the administrator.
    2. Go to the {eSight installation directory}\AppBase\AppBase\var\iemp\data\ftp\configfile directory and verify that the configuration file with the fixed name exists.

Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 71903

Downloads: 378

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