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

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

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...

    • Compare our various methodologies for Website Monitoring

      Get to know Site24x7 monitors better and choose the one that best fits your monitoring needs. Compare the functionality of the following monitors: Website Monitoring Webpage Speed (Browser) Web Transaction Monitoring Web Transaction (Browser) SSL/TLS ...

    • Site24x7 Real User Monitoring (RUM) - Data Collection

      When you include Site24x7 RUM beacon script in your web pages, the following data is collected. All data that's being collected is in accordance with GDPR compliance. Performance details of web page load time - Metrics like response time of web page ...

    • Exclude Site24x7 monitoring traffic from Google Analytics

      You can exclude traffic from the Site24x7 Web Transaction (Browser) monitor and Webpage Speed (Browser) traffic from Google Analytics in two ways. To exclude traffic for the Web Defacement monitor, you can follow the first method. 1. Creating a ...