Receiving Authentication Failure Trap alarms in Opmanager
Issue: Authentication Failure error messages in OpManager
Reason:
Authentication failure alarm is due to some monitoring system trying to access the device with wrong community string including OpManager , It may be opmanager or some other monitoring system installed in your network sending snmp queries with wrong community strings.
Resolution:
Please use our bulk "Test Credential" option under admin tab and make sure your devices are configured with correct SNMP read community and are getting passed, if all the devices are passing SNMP credential test then it may be due to some other devices on the network contacting the device with wrong SNMP read community.
As a final step we can install any packet sniffer software Ethereal(www.ethereal.com) or Wireshark capture packets to see which device is sending request with wrong SNMP community.
New to ADSelfService Plus?
Related Articles
Escalating alarms in OpManager
Discover devcies in OpManager via Trap
Discovery via Trap SNMP traps are cryptic messages or alerts sent from a SNMP device. Traps are sent by the SNMP agent when there is a change in its environment such as hardware changes, login failure, patch upgrade, new client connectivity, etc. If ...
How to add a SNMP trap processor?
1. Navigate to Settings--> Monitoring --> SNMP Trap Processors. Hover the cursor over the Actions tab and click on Add. 2. Choose the SNMP version - SNMP v1/ SNMP v2c/v3 and enter the Name and Description. Note: When you use SNMP v3 to monitor a ...
Adding SNMP Trap monitoring by loading vendor Trap Mibs in OpManager
Question : How do I add Trap processors by loading vendor Trap Mibs in OpManager? Solution: Following are the steps to load the traps from various MIBs: Go to Settings → Monitoring → SNMP Trap Processors. All the configured processors are listed ...
Traps not received in OpManager
Please check below for the possible reasons for not receiving the traps and its corresponding resolution. 1. Trap port might be occupied in opmanager server. ---> Make sure the that trap port of OpManager is not occupied by trap service of Operating ...