No Response SNMP

snmp

I am trying to monitor network devices in our company using SCOM. So far the devices are not responding to SNMP request. These devices support SNMP. Firewall is not an issue since the monitoring server is already in the company's network. Trying the command below gave the following result for one device:

~$ snmpget -v 1 -c ro345iu5672 11.248.154.10 .1.3.6.1.2.1.1.1.0
Timeout: No Response from 11.248.154.10.

Additional research suggested that the target SNMP device needs to enable the whole system MIB/OID-tree to be discoverable in SCOM. If any of the following OIDs are missing, you will not be able to discover the device:

• 1.3.6.1.2.1.1.1.0 --> system.sysDescr
• 1.3.6.1.2.1.1.2.0 --> system.sysObjectID
• 1.3.6.1.2.1.1.4.0 --> system.sysContact
• 1.3.6.1.2.1.1.5.0 --> system.sysName
• 1.3.6.1.2.1.1.6.0 --> system.sysLocation

How can I enable these OID's for a network device?

Best Answer

There is pretty simple scenario to access device via SNMP and get information you want.

  1. Enable SNMP on the device, select SNMP version (v1, v2c, v3), set read/write community (it's like "password" in SNMP)

  2. Find out MIB file for that device vendor/product(usually developers include .mib files with firmware versions/updates)

  3. Check exactly what that device can "tell" you via SNMP (check MIB file), it's usually easier to do with some software like Castle Rock SNMPc Network Manager or some else products, that can "scan" device using IP address, mib file, and communities you wrote in. (yeah, this is for win* systems, but I'm pretty sure there is *nix alternatives).

After you have found what exactly you need to know - you will know OID, and should use the command you wrote above to get info you need.

Now, responding for your situation. I guess you should do steps in this order:

  1. Check network connection to this device (if we are assuming that ping is working - than you should use check 161 port as mentioned above by Orlando.)

  2. Check that your device have SNMP=enabled in configuration. Check SNMP version and communities.

  3. Check that your device know something about OID you are writing there (but I guess it's not the case cause there should be some respond at all, even with wrong OID. imo.)

Related Topic