Discovery error "No response to snmp requests (check the community string?)"
search cancel

Discovery error "No response to snmp requests (check the community string?)"


Article ID: 36196


Updated On:


CA eHealth


Discovery error: “No response to snmp requests (check the community string?)”


When performing a discovery of a device, I get an error almost immediately.  Error message: “No response to snmp requests (check the community string?)”.  The message occurs even after confirming we are using the correct community string for the device.  Why is this happening?

eHealth 6.2.2 through 6.3.2.XX

This error occurs due to an invalid sysObjectId value from the device MIB.  Please contact the device vendor for a fix, or if the device is configurable, update the device with a valid sysObjectId.

Description "The vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree ( and provides an easy and unambiguous means for determining `what kind of box' is being managed. For example, if vendor `Flintstones, Inc.' was assigned the subtree, it could assign the identifier to its `Fred Router'."

1. Check if the device has a valid sysObjectId. Run the following command below.  Replace commStr with the community string of the device, and ipAddress with the IP address of the device. 

nhSnmpTool -c commStr -n -o ipAddress

nhSnmpTool -c public -n -o
SNMPv2-MIB::sysObjectID.0 =

2. Search the value of sysObjectId from your internet browser.  In the example above, sysObjectId value maps to a Cisco2811 device.  This is a valid sysObjectId value.

NOTE: The example below is of an invalid sysObjectId value, 0.1
nhSnmpTool -c public -n -o
SNMPv2-MIB::sysObjectID.0 = 0.1

Additional Information:
Here is a page listing many Cisco devices and their respective sysObjectId values.  Mibdepot page


Release: LHDEVC99000-6.3-eHealth-Live Health Upgrade Elements