How to find the Device Identifier (sysOID) using MIB browser?

How to find the Device Identifier (sysOID) using MIB browser?

The managed objects in an MIB are called object identifiers (object IDs or OIDs). OIDs are identifiable by strings of numbers separated by dots.
You can find the sysOID using the MIB browser.
  1. Open the Command Prompt as an administrator
  2. Go to the directory where the On-Premise Poller is installed
  3. Then navigate to Network Plus\bin folder
  4. Start the MibBrowser.sh/MibBrowser.bat file in the Network Plus\bin folder
  5. As the MibBrowser opens up, set the SNMP credentials with respect to the version.
    • For SNMP v1, set the host, port, and the SNMP community
    • For SNMP v2, click Edit > Settings > Change the SNMP version to v2 > Click Ok. Set the host, port, and the SNMP community
    • For SNMP v3, click Edit > Settings > Change the SNMP version to v3 > Click Add. Set the host, port, user name, authentication credentials and click ok

  6. In the MibBrowser screen, look out for RFC 1213-MIB in the left end
  7. Navigate to org > dod > internet > mgmt > mib-2 > system by clicking on it
  8. Select sysOID from the list
  9. Now click on the "Get SNMP variable" icon (located 7th from the left, below the menu bar)
The sysOID displayed on the screen is .iso.org.dod.internet.private.enterprises.9.1.283 and this can also be written
as .1.3.6.1.4.1.9.1.283 
If the MIB browser throws an error, refer here to identify the issue.
Alternative steps:
If the MIB browser is inaccessible or fails to work, SNMP command line tools can be used to find the sysOID.

Install the required packages:
Fedora/Centos: yum install net-snmp-utils
Ubuntu: apt-get install snmp

> snmpget -v [1/2c/3] -c Read_Community IP_Address .1.3.6.1.2.1.1.2.0
Ex: snmpget -v 2c -c public 10.10.10.1 .1.3.6.1.2.1.1.2.0

Note: If the SNMP port is not default, use it like IP_Address:Port
Ex: 10.10.10.1:601


Related article:

    • Related Articles

    • How to set up alerts for network device data collection issues

      When your network monitoring interfaces are not collecting data due to issues in the Network Module, you'll want to be alerted. To set up alerts, you need to add or edit the threshold and availability profile of the On-Premise Poller, which is used ...

    • Monitors that require On-Premise Pollers in Site24x7

      Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...

    • Resolving huge disk space issues with the On-Premise Poller and Network Module

      Often huge disk space results from the heap dump files in the NetworkPlus/bin directory of the On-Premise Poller.  What are HPROF files? HPROF files are used to store Java virtual machine (JVM) memory dumps. When a JVM runs out of memory (OOM), it ...

    • Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring

      By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...

    • Device/Licence Key

      Device Key is a unique and secure alphanumeric key that can be accessed by logging in and navigating to Admin > Developer > Device Key. It is an authentication mechanism where the Site24x7 agent pushes the performance metrics to site24x7.com to ...