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 .
Timeout: No Response from

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:

• --> system.sysDescr
• --> system.sysObjectID
• --> system.sysContact
• --> system.sysName
• --> system.sysLocation

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

  • Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer.
    – Ron Maupin
    Commented Aug 14, 2017 at 2:41

2 Answers 2


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.)

  • Thank you so much @Marat. I will try this out and see the result.
    – Fokwa Best
    Commented May 12, 2016 at 13:25
  • Hello, I have contacted the network admin, he said SNMP is enabled on the device, port 161 is ok, firewall isn't an issue, community string is ok, etc. What else can be the problem?
    – Fokwa Best
    Commented May 12, 2016 at 15:19
  • Ok, I've just installed virtual debian with access to the network with a lot of switches. I tried 4 variations. 1. snmpget -v 1 -c 12345 . (Correct IP, wrong SNMP version, wrong community, wrong OID) - Timeout. No response from 2. snmpget -v 2c -c 12345 . (Correct IP, wrong community, wrong OID) - Timeout. No response from Commented May 12, 2016 at 17:08
  • 3. snmpget -v 1 -c *** . (Correct IP, correct community, wrong SNMP version, wrong OID) Error in packet. Reason: (noSuchName) there is no such variable name in this MIB. Failed object: iso. 4. snmpget -v 2c -c *** . (Correct IP, correct community, correct SNMP version, wrong OID) iso. = No Such Instance currently exists at this OID 5. snmpget -v 2c -c *** (Correct IP, correct community, correct SNMP version, correct OID) iso. = 106 days, 14:15:50.00 Commented May 12, 2016 at 17:15
  • According to this - you have 2 variations. 1. You can't see device via network (no "echo reply" so device in "unreachable"). 2. You type community wrong. It should be exactly match with community settings on the device. Commented May 12, 2016 at 17:17

You probarly need to enable SNMP on your devices, with the correct community, unless you do that, no response could be received by your SCOM. If you already done this, then you can check on the logs of your devices to see if SNMP request are received, and some kind of error, if happens. It is not, you need to check if the SNMP default port, 161, are been filtered in some place. Remember, this is only a global answer, every equipment have it owns steps to configure SNMP. If yow can't resolve, you can edit your question and put devices model.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.