SNMP OID: Full Insight

 SNMP uses OIDs to uniquely identify pieces of data (like CPU usage, interface status, etc.).

  • Standard OIDs (defined by IETF) are common across all devices, e.g.:

    • 1.3.6.1.2.1.1.1.0sysDescr (system description)

    • 1.3.6.1.2.1.2.2.1.10ifInOctets (interface input bytes)

  • Vendor-specific OIDs:

For example:

VendorEnterprise OID BaseExample
Cisco1.3.6.1.4.1.91.3.6.1.4.1.9.1.516 (Cisco 2960 model)
Juniper1.3.6.1.4.1.2636Juniper-specific OIDs
HP1.3.6.1.4.1.11HP printer/router OIDs
Fortinet1.3.6.1.4.1.12356FortiGate device OIDs

Part 1: Standard SNMP OID.1.3.6.1.2.1.1.1.0

This is used for system description, and it works on all SNMP-supported devices (routers, switches, servers, etc.).

Let’s break this path:

🔹 .1iso

International Organization for Standardization
This is the root of the SNMP OID tree. Every OID begins from here.


🔹 .3org

Organization
This level is used for organizations that are registered under ISO.


🔹 .6dod

Department of Defense (USA)
Historically, internet protocols like SNMP, TCP/IP were developed under DoD — that’s why this is here.


🔹 .1internet

This node refers to Internet protocols like SNMP, TCP/IP, etc.


🔹 .2mgmt

Management
This branch contains standard SNMP management objects.


🔹 .1mib-2

Management Information Base version 2
This is a standard set of objects used across all SNMP devices. It includes system info, interfaces, network protocols, etc.


🔹 .1system

This group contains general system-level information.


🔹 .1sysDescr

System Description
This OID returns info like OS name, version, hardware model, firmware, etc.


🔹 .0 → Instance

This indicates a scalar value (single result) — not a table.


🔸 Visual Breakdown:

markdown
.1.3.6.1.2.1.1.1.0 | | | | | | | | |____ Instance (0) | | | | | | | |______ sysDescr | | | | | | |________ system | | | | | |__________ mib-2 | | | | |____________ mgmt | | | |______________ internet | | |________________ dod | |__________________ org |____________________ iso

✅ Part 2: Vendor-Specific SNMP OID.1.3.6.1.4.1.9

This is used by vendors (Cisco, HP, Juniper, Fortinet, etc.) to define their custom/private OIDs.

Let’s explain each part:

🔹 .1iso

(Same as above)


🔹 .3org

(Same as above)


🔹 .6dod

(Same as above)


🔹 .1internet

(Same as above)


🔹 .4private

This branch is used for non-standard, vendor-specific objects. Not globally standardized.


🔹 .1enterprises

This subtree contains registered vendors — each one has a unique number.


🔹 .9Cisco

Cisco’s enterprise number is 9. So .1.3.6.1.4.1.9 points to Cisco's private SNMP space.

Cisco will have further sub-paths here, like:

  • .1.3.6.1.4.1.9.9.43.1.1.1.0 → config last changed

  • .1.3.6.1.4.1.9.2.1.56.0 → CPU load

  • etc.


🔸 Visual Breakdown:

markdown
.1.3.6.1.4.1.9 | | | | | | |____ Cisco's Enterprise ID (9) | | | | | |______ enterprises | | | | |________ private | | | |__________ internet | | |____________ dod | |______________ org |________________ iso

💡 Summary:

NodeMeaningUsed For
.1isoRoot of the SNMP tree
.3orgRegistered organizations
.6dodOrigin of Internet protocol
.1internetInternet-related protocols
.2mgmtStandard management data
.1mib-2Common SNMP groups
.1systemGeneral system info
.1sysDescrSystem description text
.4privateVendor-defined MIBs
.1enterprisesVendors list
.9CiscoCisco's private SNMP objects




Core MIB‑II System Objects (.1.3.6.1.2.1.1)

These objects provide basic device/system information:

OIDNameDescription
.1.3.6.1.2.1.1.1.0sysDescrSystem description (OS, firmware, etc.)
.1.3.6.1.2.1.1.2.0sysObjectIDDevice’s vendor-specific OID
.1.3.6.1.2.1.1.3.0sysUpTimeTime since last reboot (TimeTicks)
.1.3.6.1.2.1.1.4.0sysContactAdministrator contact info reference
.1.3.6.1.2.1.1.5.0sysNameHostname or device name
.1.3.6.1.2.1.1.6.0sysLocationDevice’s physical location
.1.3.6.1.2.1.1.7.0sysServicesServices supported by the device
Cisco Community+12Dell+12Sysadmin MD+12Fortinet Community+5Observium+5Alvestrand+5

🌐 Interfaces Group (.1.3.6.1.2.1.2)

Standard interface statistics and status:

OIDNameDescription
.1.3.6.1.2.1.2.1.0ifNumberNumber of network interfaces
.1.3.6.1.2.1.2.2.1.ifIndexifIndexInterface index (row identifier)
.1.3.6.1.2.1.2.2.1.2.ifIndexifDescrInterface description (e.g. GigabitEthernet1/0/1)
.1.3.6.1.2.1.2.2.1.10.ifIndexifInOctetsBytes received
.1.3.6.1.2.1.2.2.1.16.ifIndexifOutOctetsBytes transmitted
.1.3.6.1.2.1.2.2.1.14.ifIndexifInErrorsInput packet errors
.1.3.6.1.2.1.2.2.1.20.ifIndexifOutErrorsOutput packet errors
Wikipedia+3Observium+3Sysadmin MD+3

📊 Protocol and Management Groups

Additional useful standard MIB‑II subtrees:

  • SNMP group (.1.3.6.1.2.1.11) — handles SNMP-specific stats, such as number of get/set requests, errors, traps generated/received Sysadmin MD+1Alvestrand+1

  • IP group (.1.3.6.1.2.1.4) — IP statistics, routing table entries Server Fault+11Observium+11Alvestrand+11

  • TCP/UDP groups (.1.3.6.1.2.1.6, .1.3.6.1.2.1.7) — connection state, retransmissions, datagram counts Observium


✅ Summary: Most Useful SNMP Standard OIDs

  • System info: sysDescr, sysName, sysUpTime, sysContact, sysLocation, sysServices

  • Interface metrics: ifDescr, ifInOctets, ifOutOctets, ifInErrors, ifOutErrors

  • Protocol-level statistics: SNMP counters, IP, TCP, UDP stats

Comments

Popular posts from this blog

How to enable the syslog monitoring-Zabbix

Zabbix installation: Distribution setup

API & API in Zabbix