Unsolved

This post is more than 5 years old

12 Posts

14145

April 30th, 2012 11:00

Getting Alerts from machines not managed

I am getting authentication failure alerts from servers that I have not added to the include range. I even added them to the exclude range but still get the alerts. I do not want to turn off the authentication setting on this server. I cannot create a rule to ignore these alerts as the servers do not show in the devices list. I am getting hundreds of these a day.

12 Posts

April 30th, 2012 11:00

OK I'm still getting them. I removed my OME IP from all the SNMP settings on these servers and I selected ignore on all servers for the auth fail. I cannot restart SNMP right now so I'm hoping that that is the issue now.

4 Apprentice

 • 

2.8K Posts

April 30th, 2012 11:00

Hi there,

So you are getting traps in the OME alert console from systems that you are not intending to manage?

Are these MNs configured to point SNMP alerts at the OME server?  You should only be getting alerts from devices that have pointed the SNMP traps to the OME server.

If you right-click ignore on the alert does this help?

More info on these maybe in the FAQ #10.2.

thanks!

Rob

12 Posts

April 30th, 2012 11:00

Removed OME IP from traps on servers throwing alarms thanks

April 30th, 2012 11:00

any system that has Authentication traps enabled WILL send a trap to its "trap destination" when a community string that is not in its accapted community list is recieved by that system.  

see: technet.microsoft.com/.../cc959663.aspx

you have many choices to fix it.  

1) add the community name that is being queried on the target to the acceptable community list on that target.  

2) remove the trap destination for the essentials box on those targets you aren't managing

3) ignore the alert by right clicking on the alert itself and creating an ignore filter (right click -> ignore -> ignore on all devices

4) disable the authentication trap option on the target (not an option here)

12 Posts

April 30th, 2012 12:00

OK Rebooting the OME Server seems to have stopped the alerts. I guess I could have just restarted the network monitor service but what eva

No Events found!

Top