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>


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


Devices Fail to Be Added to eSight V200R005C00 Through SNMPv3

Publication Date:  2015-10-31 Views:  1761 Downloads:  0
Issue Description
Devices fail to be added to eSight V200R005C00 through SNMPv3.
Handling Process
 Check whether the device and eSight can successfully ping each other.

 Check whether the SNMPv3 parameters are correctly configured on the device and eSight.

 Check the SNMP connectivity between the device and eSight in the MIB tree on eSight.

 Obtain data packets sent to the device on the eSight server.

Analyze the obtained data packets. The result shows that the value of engineid is MISSING, indicating that eSight fails to obtain the correct engine ID.

 It is suspected that the snmp-agent local-engineid command is incorrectly configured. Run the undo snmp-agent local-engineid command to restore the default engine ID of the local SNMP entity and re-configure SNMP parameters. After that, the device can be added to eSight.
Root Cause
The snmp-agent local-engineid command configures an engine ID for a local SNMP entity, which uniquely identifies an SNMP entity.

As the unique identifier of the SNMP module, an SNMP engine ID identifies an SNMP entity in a management domain. SNMP engine ID is an important part of an SNMP entity and provides functions such as SNMP message scheduling, message processing, security verification, and access control.

When SNMPv3 is used, the SNMP agent needs to define a unique engine ID to respond to SNMPv3 requests.

If the default local engine ID of a device is modified, it may conflict with the local engine ID of another device on the local network. In this case, eSight receives information about two devices with the same local engine ID; therefore, eSight cannot respond to SNMPv3 requests. The local-engineid field in the data packet sent by eSight to the device is displayed as MISSING, causing a device addition failure on eSight.
Run the undo snmp-agent local-engineid command on the device to restore the default engine ID of the local SNMP entity and re-configure SNMP parameters.

If you want to set a local engine ID by yourself, comply with the following principles:

     The first four bytes in hexadecimal notation are the enterprise's private engine ID allocated by Internet Assigned Numbers Authority (IANA). The engine ID of Huawei devices is 2011 in decimal notation. The first binary digit has a fixed value 1. Therefore, the engine ID in hexadecimal format is 800007DB.
     The device information is configured manually. You are advised to use the IP address or MAC address of the device as device information to uniquely identify the device.
Do not modify specific default parameters of devices unless necessary.