topic NetSight Traps: unable to find events in log file in ExtremeCloud IQ- Site Engine Management Center

NetSight Traps: unable to find events in log file

Mike_Ladach — Thu, 19 Dec 2013 03:14:00 GMT

Since upgrading to NetSight 4.4.0.113 we have lost the ability to log our trap events. Prior to the upgrade, the traps were working very well. After the upgrade the only event information shown in the traps window shows "Unable to find events in log file". I have added the users to the snmpd.conf file and restarted the trap service without any change.

When I view the snmptrapd logs, all that is present is the message "Warning: no access control information configured. This receiver will *NOT* accept any incoming notifications." The syslog logs are working fine, but not the traps.

The server is running Windows Server 2008 with SP2, and Java was updated from 6 to 7.

Is there an additional configuration that needs to be applied to get the traps working again?

RE: NetSight Traps: unable to find events in log file

Bob_Maheu — Thu, 19 Dec 2013 21:29:00 GMT

Hello,

The following tech note should address this issue:

15029: NetSight - Traps not Being Received After Upgrade to version 4.4
Title:NetSight - Traps not Being Received After Upgrade to version 4.4
Article ID:15029

Products
NetSight Console

Changes
Upgrade to version 4.4 was performed.

Symptoms
Traps are no longer being received in NetSight Traps view.

Cause
Code missing to make sure the trap file and the SNMP mode is correct after restoring files on an upgrade.

Solution/Workaround
Upgrade to NetSight Suite version 5.0 or higher.
Release notes state, in the 'Console Issues Addressed' section:
Resolved an upgrade problem that caused the trap service to not process traps in some cases. 920482

Pre-upgrade workaround:
1. Start NetSight Console.
2. Select Tools -> Options -> Suite Options -> Advanced SNMP settings.
3. Check the option to use NetSNMP.
4. Save and restart the server when asked.

Edit the file /NetSight_Install_Path/NetSight/appdata/snmptrapd.conf.

Make sure that the first uncommented line is:

disableAuthorization yes

If it is not please add it and then start the SNMP trap service.

RE: NetSight Traps: unable to find events in log file

Tamera_Rousseau — Fri, 20 Dec 2013 00:51:00 GMT

Hi Mike, please let us know if this solves this problem. Thank you!

RE: NetSight Traps: unable to find events in log file

Mike_Ladach — Fri, 20 Dec 2013 01:10:00 GMT

Thanks for the reply, Bob. I went through this procedure for the "pre-upgrade workaround", and it did not have any affect. I am still not able to capture the trap events.

RE: NetSight Traps: unable to find events in log file

Bob_Maheu — Fri, 20 Dec 2013 02:00:00 GMT

Hi Mike,

Try changing to the newer SNMP stack. You can do this from any NetSight client by selecting Tools -> options -> Suite Options -> Advanced SNMP. If the option for Use NetSNMP is not check then please check it. The NetSight server services will need to be restarted after this change. I would also suggest restarting the client(s) as well. See if this helps.

Let me know if it does not.

RE: NetSight Traps: unable to find events in log file

Mike_Ladach — Fri, 20 Dec 2013 03:09:00 GMT

This was already checked from the initial work-around, so I unchecked it, and restarted NetSight. I then checked it again, restarted NetSight, and there is no difference.

RE: NetSight Traps: unable to find events in log file

Rey_Juan_Carlos — Fri, 20 Dec 2013 14:42:00 GMT

We had the same problem, and we clear it with:
Edit the file /NetSight_Install_Path/NetSight/appdata/snmptrapd.conf.

Add "disableAuthorization yes" in the first line of snmptrapd.conf

Save and restart the process.

RE: NetSight Traps: unable to find events in log file

Tamera_Rousseau — Fri, 20 Dec 2013 14:42:00 GMT

Thanks for the suggestion! Mike, please let the community know if this fixes the problem. Thank you for your continued patience with this issue. 

RE: NetSight Traps: unable to find events in log file

Mike_Ladach — Fri, 20 Dec 2013 21:27:00 GMT

No, this did not correct the issue. This is now the fourth time I have performed this, without any affect. Is there anything else I can explore?