This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

In NetSight already cleared traps keep coming back.

In NetSight already cleared traps keep coming back.

Armin_Otten
New Contributor

‎11-05-2013 08:21 AM

After updating to Netsight 5.0.0.252 we have the problem that all traps keep coming back. If the traps are acknowleged today, tomorrow they are not acknowleged anymore. And each time this happens the alarms are ringing. I think we tried almost every setting, but nothing seems to help. What can we do to keep the traps acknowleged?
0 Kudos
13 REPLIES 13

Jason_Parker
Contributor

‎11-07-2013 02:30 PM

Armin, I am glad the issue has been resolved (from what I have read). I would test the traps again and let me know your results after the test has been run. Try "SET PORT TRAP X.X ENABLE) AND TRY A LINK UP OR DOWN ON THE PORT). The settings in the display of each of the fields (example:syslog or traps)you were looking at such as traps vs. syslogs would be different to report the path to which the event is directed. Please let me know if you have any further issues. Thanks Jason
0 Kudos

Armin_Otten
New Contributor

‎11-07-2013 07:42 AM

I am now in the Event View Manager, and there ist this list of available log managers. The parameters for the Traps Manager show: %logdir%traps. Is that OK? All other managers only have %logdir% without anything extra.
0 Kudos

Armin_Otten
New Contributor

‎11-07-2013 07:31 AM

Hi, here now something new. after we did the reboot, the traps did not come back. Even more, the are really gone from the trap log file.(console is OK) The logfile now only shows entries back up to 11/05/2013 17:00. That is about the time of the reboot. All entries before that are gone. (Yes, I did use the hide/unhide button) The first entry is, unable to find logfile. So I think we should fix this, and then we should test if the problem still exists.
0 Kudos

Armin_Otten
New Contributor

‎11-05-2013 02:39 PM

OK, I have not seen this before either. This problem started after the update. Just now we acknowledged all traps, and are now rebooting the Server. Let me know if you need logs or something else.
0 Kudos
GTM-P2G8KFN