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.

Knowledge Base

U2000 can not add S9300 successfully trough SNMP V3 because of the same local-engined

Publication Date:  2019-07-17  |   Views:  171  |   Downloads:  2  |   Author:  Jack Peng  |   Document ID:  EKB0000510561


Issue Description

U2000 can not add S9300 successfully trough SNMP V3, but if through SNMP V2 or V1, it will be OK.  The version of U2000 is V100R002C01SPC003, and S9300 is V100R003C00SPC200.

Alarm Information

If U2000 through automatically discover S9300, it will be the status of "to be created" and never become "created successfully". If through mannually adding the S9300 to U2000, it will immediately has the error. The error information is in the attachment.

Handling Process

1  Ping from U2000 to S9300 and the network is normal.
2  Because of SNMP V2 normal, there is no any problem for S9300 and U2000.
3  Double check the configuration in one switch and it's right. However when checking another switch and finding the local-engineid is the same. 
4  Change the local-engineid to the different one and try to add again, it's successful.

Root Cause

1  There are some problems between S9300 and U2000.
2  The configuration of S9300 is wrong.
3  There are some problems in U2000.
4  Other factors.


For SNMP V3, all the local-engineid must be different, else it will be failed to be added to the U2000. Because when added to the U2000, the U2000 will firstly search the U2000 database, and if  two switchs have the same local engineid, it will be failed.