Device discovered as unknown even through configured with SNMP credential in OpManager
Issue:
Device discovered as unknown even after adding the SNMP read community.
Reason:
The device may not be configured properly with SNMP or OpManager is not configured properly with device SNMP community.
Resolution:
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.
Device discovered as unknown even after adding the SNMP read community.
Reason:
The device may not be configured properly with SNMP or OpManager is not configured properly with device SNMP community.
Resolution:
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.
New to ADSelfService Plus?
Related Articles
Why is the discovered device categorized as unknown?
A device may be categorized as Unknown due to the following reasons. 1. Discovery credentials may be incorrect. Cause: Configuring your device with the wrong credentials will affect the discovery process. The configured credential may be incorrect or ...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 ...How to add a new credential in OpManager?
OpManager accesses the remote devices using the protocols SNMP, CLI, WMI or VMWare API. Credentials such as password/snmp community, port etc., may differ for different device types. Pre-configuring a set of credentials in OpManager helps applying ...How to change device availability monitoring from ICMP to TCP or SNMP?
Monitoring via TCP Here, the availability of the configured device is calculated based on the successful socket connection between the OpManager server and the TCP port of the monitored device. TCP based availability monitoring is most suitable for ...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 ...