RFC1065-SMI

MIB Reference — IPNetwork Monitor

All MIBsRFC1065-SMI

Category: IETF Standards

Description:

Defines the original SMI structure-of-management-information base types from RFC 1065.

What Is RFC1065-SMI?

RFC1065-SMI defines the original Structure of Management Information (SMI) from RFC 1065, one of the foundational documents of SNMP, establishing the base ASN.1 data types, naming tree conventions, and object-definition macros that all later SNMP MIB modules build upon. It is a purely foundational, type-defining module with no runtime scalars or tables of its own -- it introduced base types like Counter, Gauge, TimeTicks, and IpAddress and the object identifier (OID) tree structure used to name every management object in every subsequent MIB. Its relevance to hardware/software status monitoring is entirely foundational rather than direct: virtually every counter, gauge, and uptime value used across the SNMP ecosystem (interface counters, system uptime, CPU/memory gauges elsewhere) ultimately derives its base type from conventions first defined here. It has no dependency on other MIBs since it is the historical root of the whole SMI framework, later superseded by RFC 1155/RFC 1212 and then the SNMPv2-SMI. It is not deployed on any specific device today in its original form but is referenced historically as the ancestor of the modern SMI used by every SNMP-capable device, and consulting an RFC1065-SMI OID list today serves mainly historical or academic interest since virtually all modern agents implement the successor SNMPv2-SMI instead.

IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1065-SMI. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • vendor-neutral, standards-based MIB, foundational to all SNMP-capable devices historically

Monitoring Examples

The single sample object entry is a placeholder ('--') rather than a real object name, consistent with this being a historical, superseded type-definition document rather than a module with live data; no monitoring scenario applies. There is nothing an admin would poll on a live device under this exact historical module, since virtually all modern agents implement the successor SNMPv2-SMI instead. Its significance is purely as the origin of base types (Counter, Gauge, TimeTicks) that every later, currently-deployed MIB (and its monitorable objects) relies on.

RFC description

Original SMIv1 Structure of Management Information from RFC 1065, defining fundamental object types and root OID tree for internet, directory, mgmt, experimental, and private branches.

Start monitoring vendor-neutral, standards-based MIB, foundational to all SNMP-capable devices historically with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download RFC1065-SMI