cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2992
Views
5
Helpful
21
Replies

SNMP-3-AuthFail

dionjiles
Level 1
Level 1

I am getting this error on my Cisco Catalyst 6509 Switches. I verified that the AniServer.properties values for 0, but for some reason it looks like they keep getting reverted back to 1 (UTGetSuspendedVlans and UTGetVlansOnDownPorts). Has anyone else faced this issue I am an admin on the CiscoWorks Server.

21 Replies 21

I have the same problem with LMS 2.6.Catalyst 6509 generates this trap when it receives SNMP-request from LMS Data Collection with community string @mst-0. File

ANIServer.properties:

UTGetSuspendedVlans=1

UTGetVlansOnDownPorts=1

File UT.properties does not exist. What I have to do for eliminating this trap?

Hi JClarke,

I did exactly what you told me to do to troubleshoot this matter with no luck. No errors were found I have asked my engineer to take a look at the other two Cisco Catalyst 6509 devices which I don't see any errors in the show logging statements to see if he can see what's going on.

What do you mean, no errors were found? Did the authFail messages stop? The steps I gave you weren't designed to produce errors. The sniffer trace will show SNMP packets. The packets that correspond to authFail messages will be of interest, as those are polling with an invalid SNMP community.

So for not providing enough info. I verified the trace with the authfail messages from the logs and verified that the right SNMP community was being polled.

But what about the indexes? The community string itself will be correct. It's a matter of the "@X" indexes that is causing the authFails. Figuring out what objects are being polled will tell us what component has the wrong indexes, and what needs to be troubleshot.

Is this close to somewhat you are looking for. If not I will have my engineer take another look at it.

No, this would not cause authFail events. An authFail would be triggered by an SNMP packet with a community string that the device does not recognize. This could be an obviously incorrect string, or a VLAN index which does not exist or is suspended on the device (e.g. public@6 when vlan 6 is not valid for that device). Such a request would not have a corresponding SNMP response.