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 V300R010C00 Maintenance Guide 07

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).
Device Addition Failure

Device Addition Failure

The reasons causing device addition failures vary depending on scenarios. This topic describes the reasons of device addition failures and troubleshooting methods based on error codes for device addition failures.

Common Causes

Error Code

Common Causes

Network is busy, the device is overloaded, or SNMP parameters are incorrect.

  • The network between the device and eSight is disconnected.
  • The SNMP parameters configured during device addition to eSight are inconsistent with those of the device.
  • The SNMP configuration on the device is incorrect.
  • The password for the SNMP read-write community name of the device does not meet complexity requirement.
  • The device adds the IP address of eSight server to its blacklist (USG firewall).
  • Third-party equipment's sysObjectID does not exist.
  • The device is working abnormally.

The device already exists.

The device to be added has a different IP address and the same MAC address with the device that already exists on eSight.

Database operation fails.

The database is abnormal.

Procedure

  • Network is busy, the device is overloaded, or SNMP parameters are incorrect.
    • Check the current network configuration.
      1. Check whether the device and eSight can ping each other. If the link between eSight and the device is reachable uni-directionally, configure the corresponding route.
      2. Check whether a firewall/NAT device exists between the device and eSight. If a firewall exists, disable the firewall. If a NAT device exists, ensure that NAT configuration is consistent with that planned in the communication matrix.
    • Check whether the SNMP parameters filled during device addition are inconsistent with those of the device.

      Read-write community name is encrypted both on the device and eSight. If you are uncertain of the SNMP parameters configured on the device, reconfigure the SNMP parameters on the device and then add the device again.

    • Check whether the SNMP configuration on the device is correct.
      1. Telnet to the device failing to be added.
      2. Run the display current-configuration | include snmp command to check the SNMP configuration of the device.
        Table 8-5 Checking the device's SNMP configuration

        Protocol

        Check Result

        Solution

        SNMP V2c

        The configured read-write community name does not carry the mib-view parameter or the mib-view parameter does not include the whole iso object.

        1. Run the system-view command in the Telnet window and enter the system view.
        2. Run the following command.

          snmp-agent mib-view include View_ALL iso

          snmp-agent community write {SNMP write community name} mib-view View_ALL

          snmp-agent community write {SNMP read community name} mib-view View_ALL

        SNMP V3

        The configured user group does not carry the mib-view parameter or the mib-view parameter does not include the whole iso node.

        1. Run the system-view command in the Telnet window and enter the system view.
        2. Run the following command.

          snmp-agent mib-view include View_ALL iso

          snmp-agent group v3 {SNMPv3 user group} privacy read-view View_ALL write-view View_ALL notify-view View_ALL

          snmp-agent usm-user v3 {user name} {SNMPv3 user group}

          snmp-agent usm-user v3 {user name} authentication-mode md5 {authentication password}

          snmp-agent usm-user v3 {user name} privacy-mode aes128 {encryption password}

  • Check whether the password for the SNMP read-write community name of the device meets complexity requirement.
    NOTE:

    If no, the following possible causes may exist: SNMP parameters may be configured when the community name password complexity check function is disabled and the configured community name is simple (for example, public or private). The check function is enabled after SNMP parameters have been configured.

    This operation is only applicable to devices supporting complexity check function. For those that do not support complexity check function, ignore this step.

    1. Telnet to the device failing to be added.
    2. Take S9700s as an example. Run the display current-configuration | include snmp command to check whether snmp-agent community-check displays disable. If it displays disable, run the undo snmp-agent community complexity-check disable command to enable community password complexity check function. If it does not display disable, go to the next step.
    3. Reconfigure the SNMP parameters to meet the complexity requirement.
    4. Add the device again.
  • Check whether the device adds the IP address of eSight server to its blacklist (USG firewall).
    1. Telnet to the device failing to be added and enter the system view.
    2. Run the display firewall blacklist item command to check whether the IP address of eSightserver is in the blacklist of the device. If so, run the undo firewall blacklist item allcommand to empty the device blacklist.
  • Check whether the third-party equipment's sysObjectID exists.
    NOTE:

    sysObjectID is the unique identifier of the device during device addition process. The missing of sysObjectID MIB object may cause device addition failures.

    1. Choose Configuration> Configuration Management > MIB Management.
    2. Connect to device failing to be added through the MIB management tool.
    3. In the filtering box of MIB navigation tree, enter 1.3.6.1.2.1.1.2 and check whether any data exists on sysObjectID object. If there is no data, the failure is caused by faulty device. Contact the supplier to locate the fault.
  • Check whether the device is abnormal.
    NOTE:

    If so, you can check logs and error message on eSight or check logs on the device to determine whether the device is abnormal.

    1. Telnet to the device failing to be added and enter the system view.
    2. Run the display logbuffer command to check log information.
    3. If the logbuffer is abnormal, for example, the following error message is displayed.
      Jan  2 2008 00:45:39-05:13 R6_U26_S2700 %%01SNMP/4/DECODE_ERR(l)[11]:Failed to login through SNMP, because of the decoded PDU error. (Ip=192.168.32.166, Times=1 

      The failure is caused by faulty device. Contact the supplier to locate the fault.

  • The device already exists.

    The device to be added has a different IP address and the same MAC address with the device that already exists on eSight.

    1. Choose Configuration> Configuration Management > MIB Management.
    2. Check whether conflicting devices have the same MAC address.

      Connect to the device through the MIB management tool. In the filtering box of the MIB navigation tree, enter 1.3.6.1.2.1.17.1.1, click the found object, click Walk on the toolbar, and check the MAC addresses.

    3. If the two devices have the same MAC address, the failure is caused by device hardware. Contact the supplier and confirm the problem.
  • Database operation fails.
    Check whether the database is abnormal (MySQL).
    1. Open the file stored in eSight directory eSight/MySQL/data/eSight.err. Check the database log information to determine whether the database is abnormal.
    2. If an error message, such as the following message, occurs, some of the database files are corrupted. Go to the next step, recover the corrupted files, and restart eSight.

      [ERROR] D:\eSight\MySQL\bin\mysqld.exe: Table '.\mysql\proc' is marked as crashed and should be repaired

    3. Stop the MySQL service and back up the files stored in MySQL directory on eSight server. (D:\eSight\MySQL)
      1. Log in to the eSight server as an Administrator.
      2. Choose Start> Run and enter cmd. The CMD window is displayed.
      3. Run the following commands to stop the MySQL service.

        > cd /d D:\eSight\MySQL\bin

        > uninstall.bat

      4. Back up the files stored in MySQL directory. (D:\eSight\MySQL)
    4. Run the following commands in the CMD window, start the MySQL service, and recover the corrupted database files.

      > install.bat

      > cd /d D:\eSight\MySQL\bin

      > myisamchk -c -r ../data/mysql/proc.MYI

    5. Restart eSight.
  • If the fault persists after the preceding operations, contact Huawei engineers.
Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 24878

Downloads: 74

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