All MIBs › SNMPv2-MIB-EXT-01
Category: Legacy and Compatibility MIBs, SNMP Infrastructure and Standards
Description:
Extends SNMPv2-MIB with additional system-level objects for enhanced agent management and monitoring.
Imported Objects
From SNMPv2-MIB
| system | OBJECT-IDENTITY |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DateAndTime |
What Is SNMPv2-MIB-EXT-01?
SNMPv2-MIB-EXT-01 is a vendor extension of the standard SNMPv2-MIB, adding a handful of additional system-level objects to the well-known system group most SNMP agents already implement. Per its module description, the notable addition is a locally-known date-and-time object, i.e. configuration/status data about the device's clock rather than traffic or hardware sensor data. Its monitoring value is straightforward but important for correlating events across a fleet: it lets an operator confirm a device's local clock is set, not still at the null unknown value, and implicitly whether it has learned time from NTP or requires a manual set, a common root cause of misaligned log timestamps and trap correlation problems. It directly extends and depends on the standard SNMPv2-MIB (RFC 3418) system group rather than defining an independent object tree. It is deployed on SNMP agents from the vendor that authored this extension, wherever operators need clock-status visibility alongside the standard sysUpTime/sysDescr system objects. Engineers can download the SNMPv2-MIB-EXT-01 file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in SNMPv2-MIB-EXT-01. 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.
What Can Be Monitored
- local system date and time
- clock synchronization status
Supported Devices
- vendor-neutral/vendor-extension of SNMPv2-MIB, not tied to a specific manufacturer
- any SNMP-managed device with a local clock
Monitoring Examples
No specific object or table names beyond the date-and-time object described in the module description were supplied, so further examples can't be grounded in real identifiers; in practice an operator would poll the local date-and-time object right after deployment to confirm it isn't still returning the all-zero unknown value, which would indicate the device hasn't yet synced its clock via NTP or manual configuration.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| DAT sysDateAndTime | 1.3.6.1.2.1.1.9 | DateAndTime | read-write | The locally known date and time. The value '0000000000000000'H is returned on systems without a local clock until the local date and time is learned, either from a network time protocol such as NTP or a management set operations on this object. |
RFC description
Extends SNMPv2 MIB with system date and time synchronization capabilities.
Start monitoring vendor-neutral/vendor-extension of SNMPv2-MIB, any SNMP-managed device with a local clock (clock-status extension) 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.