Nagios Support Forum

I had an issue with a monitored switch and when i was looking at nagios for some information i saw these errors. I have searched both Nagios and the switch and nothing is configured with this IP address.

Ideas fellas?

This means you have a switch (192.168.5.7) that is setup to send SNMP traps to your Nagios XI server.

Because you have not yet Run the Trap Wizard for this you are getting the errors listed because Nagios is receiving the traps but you have not configured it as a service yet.

Okay, i will have to search, i have not set up a switch with that ip address. and this just started happening at 11am EST, and i am not in the office today. I am the only Nagios admin.

benningtonr wrote:Okay, i will have to search, i have not set up a switch with that ip address. and this just started happening at 11am EST, and i am not in the office today. I am the only Nagios admin.

It's possible that it was setup in the past but there were changes today (on the switch) that triggered the traps to send.

Based on the traps you showed, something was plugged in to port 7,24,22,11, and 12 of this switch

I got some other wierd errors on another switch. This one has been up and running for years, so i know there is nothing new on it. I am the only admin here, so i make all the changes. these started yesterday, while i was working from home.

Looks like this 64.5.130.5 is set to send traps to Nagios XI as well.

I can't speak for the activity, all I can say is that someone had to configure these switches to send traps to your Nagios XI server, and didn't setup a service (run the SNMP Trap Wizard) or these logs would never exist.

I am upgrading Nagios to see if that helps. Last time i upgraded it was a very painful process, so it may have issues due to that, fingers crossed.

Upgrade went off without a hitch, i am going to unplug something on one of the switches to see if i get the same errors.

I agree, i probably did, years ago, but i just started getting these errors. I did a search through the event log, and you can see, for the last year it was only yesterday. you would think that in the last eight month, something else would have been disconnected and sent a trap, which would have produced an error like yesterday. I am hoping that by running the update, it fixed whatever might have been corrupt. because these switches have been in place and untouched for years.

Let me ask you this, is this a new feature? I could have had snmp traps set up for years, but nagios just ignored the traffic .