Device discovered as unknown even through configured with SNMP credential in OpManager
Device discovered as unknown even after adding the SNMP read community.
The device may not be configured properly with SNMP or OpManager is not configured properly with device SNMP community.
You may check for the following:
1. SNMP Read community is case-sensitive. Verify if you have discovered the device with the correct SNMP community string.
2. Windows Firewall (Internet Connection & Sharing ) service [or any other software firewall] should be disabled. If the firewall is On, you may provide an exception to SNMP port 161.
3. Right Click and select Properties under Control Panel ->Administrative Tools -> Services -> SNMP. From the SNMP Properties dialog box, select the Security Tab. Click Add under Accepted Community names and provide a community string with Read-Only access. Make sure you have select the option "Accept SNMP packets from anyhost". In case you select the other option, Accept SNMP packets from these hosts, ensure that you have provided the IP address of OpManager Server. Apply the changes and restart the service.
Prerequisites to check if VLAN not discovered or status shows Unknown
Prerequisites to check if VLAN not discovered or status shows Unknown. Based on below OIDs result, we are showing VLANs information for Routers/Switches in OpManager. For Cisco category devices, load these two mib files CISCO-VTP-MIB and ...
Failed logon event generated even when OpManager monitors the device using correct credential
https://support.microsoft.com/en-us/kb/2816192 Symptoms Consider the following scenario: You have two or more computers running Windows. The computers are setup in a workgroup or domain environment. You run a remote WMI query using an application ...
SNMP WALK from OpManager MibBrowser
SNMPWalk allows you to detect a set of variables that are available for reading on a certain device. In this way full descriptions of variables and possible values are displayed. The SNMPWalk uses the SNMP GETNEXT request to query the agent on ...
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 ...
Device Availability in OpManager
Device Availability in OpManager is based on the ICMP Ping response of the respective devices from the OpManager server. The Availability, Packet loss and Response time would be calculated based on this response. The basic criteria is that the ...