This means that some SNMP manager is polling this device with the wrong community string. There are patches available for more recent versions of DFM to show the actual polling manager in the event, but for your version, you would need to either have the device send traps to a general purpose trap receiver, or use a sniffer trace to inspect the raw trap.
If you remove SNMP from the switch, then it will not be manageable. While you may have applied an ACL to the community string, a manager could be polling this switch with a community string which is not configured (which would generate the authFail trap). You need to find out which management station is polling this device. You can see that with a sniffer, or with "debug snmp packet" if you don't have another trap receiver.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...