All MIBs › RFC1215-TRAP
Category: IETF Standards
Description:
Defines standard SNMP trap objects and notification conventions per the RFC 1215 framework.
Imported Objects
From RFC-1215
| TRAP-TYPE |
From RFC1213-MIB
| egpNeighAddr | |
| ifIndex | |
| snmp |
What Is RFC1215-TRAP?
RFC1215-TRAP is the standard IETF MIB (RFC 1215) defining the classic SNMPv1 generic trap types — coldStart, warmStart, linkDown, linkUp, authenticationFailure, and egpNeighborLoss — and the conventions for defining enterprise-specific traps. Its coldStart trap, for example, signifies that the sending SNMP agent is reinitializing itself such that its configuration or protocol-entity implementation may have changed. As a notification-definition MIB it lets an NMS interpret the standard trap types every SNMPv1-capable agent is expected to emit. It underlies virtually all SNMPv1 agents implementing the standard generic traps defined by RFC 1215. Engineers implementing or auditing this functionality typically reference the RFC1215-TRAP RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1215-TRAP. 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
- standard SNMPv1 generic trap conditions
Supported Devices
- SNMPv1 agents implementing the RFC 1215 generic traps
Monitoring Examples
An NMS receives a coldStart trap defined by RFC1215-TRAP and flags the sending device as having just rebooted or reinitialized its SNMP agent.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| 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
Defines SNMP generic trap types for system state changes, link status, and authentication events.
Start monitoring SNMPv1 agents implementing the RFC 1215 generic traps (coldStart/warmStart/linkDown/linkUp) 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.