Troubleshooting SNMPv3 issues

Users with OpManager versions below 12.4.151 had some issues with discovering devices associated with SNMPv3 credential. This also caused data collection failure in the associated monitors. Listed below are the most common issues and their troubleshooting tips.

SNMP data collection stopped for all devices

Description: Data collection was not carried out for any devices configured with SNMPv2 and SNMPv3. This also lead to the failure of associated test monitors.

Troubleshooting tips:

1. Try to find the below trace in the stderr after restarting the OpManager service.
   com.adventnet.snmp.snmp2.SnmpException: Error in open : java.net. SocketException: No buffer space available (maximum connections reached?): Cannot bind
2. Check for the availability of ports in OpManager.
   SNMP uses ports 50000- 65535. These ports should be available for polling to initiate data collection.

SNMP data collection stopped for some devices

Description: This issue was due to duplicate engineIDs for OpManager versions below 12.4.151 . For versions above 12.4.151, the problem was with the frequent changes in the device IP and EngineID

Troubleshooting steps:

1. Stop the OpManager service and enable debugging by logging in.
2. Rename the existing 'logs' folder and create a new one.
3. Start the OpManager service and it run for a day.
4. Send the new 'logs' folder and problematic device IPs to support-opmanager@manageengine.com for further assistance.

SNMPv3 test credential and SNMPv3 'Add Device' failure

Description: The SNMPv3 configured devices were categorized as unknown upon discovery and the previously categorized devices failed while testing the SNMPv3 credentials.

Troubleshooting tips:

1. Go to Settings --> Tools --> MIB Browser.
2. Select the RFC1213-MIB file and select sysObjectID.
3. Select the IP Address/Host name if the device is already added or click on the '+' icon and enter the IP Address/DNS of the problematic device.
4. Select the preferred credential. If not found, create a new one from Settings -> Discovery -> Credential -> Add Credential.
5. Once the credentials are selected, click on "Get" and take the screenshot of the output/error shown and send it to support-opmanager@manageengine.com for further assistance.

SNMP Load issue

Description: Intermittent data collection issue affected some of the SNMP performance monitors associated with the discovered devices.

Troubleshooting tips:

1. Look for duplicate EngineIDs. SNMP engines are uniquely identified using their engine IDs. Find and remove duplicate EngineIDs if found.
2. Check the 'Memory Utilization' monitor count: Check the total count of memory utilization monitors associated with the respected device.
3. Check the SNMP and interface polled data count: Find the SNMP polled data count and interface polled data count by clicking on the Support and navigating through System Performance -> System Info -> Polled Data.
4. Check the data collection rate:
   Access the Polling Statistics page and check the data collection rate by clicking on the Support and navigating through System Performance -> Polling Statistics.
5. Check the data collection log:
   Get a complete view of the data collection log from the Monitor Health Reports page by clicking on the Support and navigating through System Performance -> Monitor Health Reports.

For further assistance, please contact our support team at opmanager-support@manageengine.com with the necessary log files.