Currently Running:

CentOS 5.6 (Linux)

OpManager 8.8 (8811)

RAM: 2 GB

Sometimes when adding a new SNMPv3 device in OpManager you will notice that it seems to take a very long time to added it, but when you search for the newly added device you will be unable to locate it.  The reason is because for some reason in the mysql database the EngineID will report as nothing.  The only way I have found to successfully correct this issue issue is to edit OpManager’s MySQL database and restart the service.  Once you have the service restarted, I find that you will not see the issue occur again when adding new SNMPv3 devices for another 24 hours.  This issue does not effect any currently added SNMPv3 devices in the system only ones that show up with nothing in the EngineID field.

Disclaimer:

*These steps have only been tested on the Linux CentOS operating system.  Backup your information before preforming these steps on the MySQL database.  I am not responsible for any corrupted databases.

Step 1:

/opt/ManageEngine/OpManager/mysql/bin/mysql --socket=../mysql.socket 

Step 2:

mysql> use OpManagerDB;

Step 3:

mysql> select * from ENGINETABLE;

If the “ENGINEID” shows up blank on a device that was just added, you will need to proceed to step 4 - 8.

DBKEY                | HOST            | PORT | ENGINENAME | ENGINEID             | ENGINETIME | ENGINEBOOTS

172.22.1.78##161     | 172.22.1.78     | 161  | null       | 80001f88809890ac0b9c571b4e00000000             | 1822       | 1

172.16.1.225##161   | 172.16.1.255   | 161  | null       |                                                                               | 0             | 0

Step 4:

mysql> select * from USMTABLE;

You should see a bunch of tables that have all kinds of information populated about your newly added device.

Step 5:

mysql> delete from  ENGINETABLE where HOST='172.16.1.225';

Step 6:

mysql> delete from USMTABLE where HOST='T#172.16.1.225';

Step 7:

Shutdown OpManager (admin admin) is the (username password) for the services.

/opt/ManageEngine/OpManager/bin/ShutDownOpManager.sh admin admin

Step 8:

Start OpManager back up after being shutdown.

/opt/ManageEngine/OpManager/bin/StartOpManagerServer.sh &

After the OpManager service started, you should be able to log back into your web interface and re-add the devices that were failing to add.  You should notice that the device will add a lot quicker and you should have no issue with adding other SNMPv3 devices that day.