All MIBs › SNMP-SMIv2-MIB
Organization: IETF SNMPv3 Working Group
Last Updated: 2002-10-16
Category: SNMP Infrastructure and Standards, Textual Conventions and SMI
Description:
Specifies the SMIv2 structure of management information, as defined by the IETF SNMPv3 working group, for organizing MIB modules.
Imported Objects
From IF-MIB
| ifAdminStatus | OBJECT-TYPE |
| ifIndex | OBJECT-TYPE |
| ifOperStatus | OBJECT-TYPE |
From RFC1213-MIB
| egpNeighAddr |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| TimeTicks | |
| mib-2 | |
| snmpModules |
From SNMPv2-TC
| DisplayString | |
| TestAndIncr | |
| TimeStamp |
What Is SNMP-SMIv2-MIB?
SNMP-SMIv2-MIB is a vendor-neutral, IETF standards-based module associated with the SNMPv3 working group's Structure of Management Information Version 2 (SMIv2), the foundational framework that defines how all other MIB modules are structured and organized. Rather than exposing device-specific operational data, it provides the meta-level conventions (data types, module identity, notification structure) that other MIBs build upon. As a foundational/definitional module it has no direct role in monitoring hardware or software status such as uptime, temperature, or CPU load -- it exists purely to standardize how such data is described elsewhere. Every SNMP MIB module in existence is implicitly dependent on the SMIv2 conventions this module represents, making it one of the most foundational building blocks in the SNMP ecosystem. It is present on essentially every SNMP-capable device purely as part of the underlying management framework, not as an operator-facing monitoring MIB. Engineers implementing or auditing this functionality typically reference the SNMP-SMIv2-MIB RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in SNMP-SMIv2-MIB. 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, not tied to a specific manufacturer
- any SNMP-capable network device (as underlying framework)
Monitoring Examples
No sample objects were provided, and as a foundational structure-of-management-information module it has no device-specific runtime data of its own to monitor; it defines the conventions other MIBs use rather than exposing operational counters or statuses itself.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| snmpMIB | 1.3.6.1.6.3.1 | The MIB module for SNMP entities. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3418; see the RFC itself for full legal notices. | ||
| snmpMIBObjects | 1.3.6.1.6.3.1.1 | |||
| snmpTraps | 1.3.6.1.6.3.1.1.5 | |||
| NTF coldStart | 1.3.6.1.6.3.1.1.5.1 | A coldStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered. | ||
| NTF warmStart | 1.3.6.1.6.3.1.1.5.2 | A warmStart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself such that its configuration is unaltered. | ||
| NTF linkDown | 1.3.6.1.6.3.1.1.5.3 | A linkDown trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links is about to transition into the down state. | ||
| NTF linkUp | 1.3.6.1.6.3.1.1.5.4 | A linkUp trap signifies that the SNMPv2 entity, acting in an agent role, has detected that the ifOperStatus object for one of its communication links has transitioned out of the down state. | ||
| NTF authenticationFailure | 1.3.6.1.6.3.1.1.5.5 | An authenticationFailure trap signifies that the SNMP entity has received a protocol message that is not properly authenticated. While all implementations of SNMP entities MAY be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated. | ||
| NTF egpNeighborLoss | 1.3.6.1.6.3.1.1.5.6 | An egpNeighborLoss trap signifies that an EGP neighbor for whom the sending protocol entity was an EGP peer has been marked down and the peer relationship no longer obtains. |
RFC description
Defines IETF SNMPv3 working group SMIv2 structure of management information for MIB module organization.
Start monitoring vendor-neutral, standards-based MIB, any SNMP-capable network device (SMIv2 foundational framework) 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.