All MIBs › SNMP-SMIv1-MIB
Category: Legacy and Compatibility MIBs, SNMP Infrastructure and Standards, Textual Conventions and SMI
Description:
Defines legacy SMIv1 structure of management information objects for backward compatibility with SNMPv1.
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-SMIv1-MIB?
SNMP-SMIv1-MIB is not a device-specific management MIB but a foundational IETF standards module defining the original SNMPv1 Structure of Management Information -- the base ASN.1 conventions (object types, network addresses, and standard traps like coldStart) that all SMIv1-era MIBs are built on. It does not expose device hardware or performance data itself; instead it establishes the common building blocks -- including the definitions behind traps such as coldStart, which signals that an agent has reinitialized -- that other MIBs reference. Its relevance to monitoring is indirect: any classic SMIv1 MIB implicitly depends on this module for its object and trap syntax, and the coldStart trap it defines is itself a basic software/agent-restart status signal used across virtually every SNMP-capable device. It is a core RFC-level dependency (RFC 1155-era SMIv1) underlying essentially the entire pre-SMIv2 SNMP MIB ecosystem. It is not deployed as a standalone monitored entity but is present, as defined by the SNMP-SMIv1-MIB RFC, as a structural/compatibility layer wherever legacy SNMPv1 agents and MIBs are still in use.
IPNetwork Monitor allows you to monitor SNMP objects defined in SNMP-SMIv1-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 legacy SNMPv1-capable network device
Monitoring Examples
There are no runtime data objects to poll in this module; it defines syntax and the standard coldStart trap rather than exposing monitorable device state. An administrator's practical interaction with it is indirect -- receiving a coldStart trap from a device tells them the SNMP agent (and likely the whole device) has just reinitialized, which is useful as a restart/reboot indicator even though the trap definition itself lives in this structural MIB.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| snmp | 1.3.6.1.2.1.11 | |||
| NTF coldStart | 1.3.6.1.2.1.11.0.0 | A coldStart trap signifies that the sending protocol entity is reinitializing itself such that the agent's configuration or the protocol entity implementation may be altered. | ||
| NTF warmStart | 1.3.6.1.2.1.11.0.1 | A warmStart trap signifies that the sending protocol entity is reinitializing itself such that neither the agent configuration nor the protocol entity implementation is altered. | ||
| NTF linkDown | 1.3.6.1.2.1.11.0.2 | A linkDown trap signifies that the sending protocol entity recognizes a failure in one of the communication links represented in the agent's configuration. | ||
| NTF linkUp | 1.3.6.1.2.1.11.0.3 | A linkUp trap signifies that the sending protocol entity recognizes that one of the communication links represented in the agent's configuration has come up. | ||
| NTF authenticationFailure | 1.3.6.1.2.1.11.0.4 | An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. While implementations of the SNMP must be capable of generating this trap, they must also be capable of suppressing the emission of such traps via an implementation- specific mechanism. | ||
| NTF egpNeighborLoss | 1.3.6.1.2.1.11.0.5 | 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
SNMP trap definitions for standard network events including cold start, warm start, link up/down, and authentication failures.
Start monitoring vendor-neutral, standards-based MIB, any legacy SNMPv1-capable network device (SMIv1 base types/coldStart trap) 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.