All MIBs › CISCOTRAP-MIB
Category: Cisco Devices, Vendor: Cisco Devices
Description:
Defines generic Cisco enterprise SNMP traps for common network events and fault notifications.
Imported Objects
From CISCO-SMI
| cisco | MODULE-IDENTITY |
| locIfReason | OBJECT-TYPE |
From OLD-CISCO-SYSTEM-MIB
| authAddr | OBJECT-TYPE |
| whyReload | OBJECT-TYPE |
From OLD-CISCO-TCP-MIB
| loctcpConnElapsed | OBJECT-TYPE |
| loctcpConnInBytes | OBJECT-TYPE |
| loctcpConnOutBytes | OBJECT-TYPE |
From OLD-CISCO-TS-MIB
| tsLineUser | OBJECT-TYPE |
| tslineSesType | OBJECT-TYPE |
From RFC-1215
| TRAP-TYPE |
From RFC1213-MIB
| egpNeighAddr | |
| ifDescr | |
| ifIndex | |
| ifType | |
| snmp | |
| sysUpTime | |
| tcpConnState |
What Is CISCOTRAP-MIB?
CISCOTRAP-MIB is a Cisco enterprise SNMP module that defines generic trap (notification) type OIDs used across Cisco routers, switches, and other network gear rather than a set of polled data objects. It exposes fault and event notification definitions -- the kind of asynchronous alerts a device sends when something changes or breaks -- as opposed to interface, environmental, or configuration tables. Its role in monitoring is squarely on the fault side: it lets a management station recognize incoming traps that signal restarts, link state changes, or other operational events that indicate a device's hardware or software status has changed, complementing uptime and health polling done via other MIBs. It builds on the standard SNMPv2 notification framework (SNMPv2-SMI/SNMPv2-CONF) and sits alongside Cisco's broader enterprise MIB tree for object identity. It is typically deployed in enterprise and service-provider Cisco networks where an NMS or trap receiver is configured to catch and correlate these Cisco-specific trap notifications for real-time fault alerting. Engineers can download the CISCOTRAP-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in CISCOTRAP-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
- Cisco routers
- Cisco switches
- Cisco network devices generally
Monitoring Examples
No sample objects were provided for this module (sample_objects is empty), and it appears to consist solely of trap/notification OID definitions rather than pollable tables, so no concrete object names can be honestly cited here. In practice, an admin would configure an SNMP trap receiver or NMS to recognize trap OIDs registered under this module and map them to alert rules, e.g., firing an alert whenever a Cisco device emits one of its generic fault traps. Because the module is trap-only, there is no periodic polling of counters or status tables associated with it directly.
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 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. | ||
| NTF reload | 1.3.6.1.4.1.9.0.0 | A reload 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 tcpConnectionClose | 1.3.6.1.4.1.9.0.1 | A tty trap signifies that a TCP connection, previously established with the sending protocol entity for the purposes of a tty session, has been terminated. |
RFC description
Cisco SNMP trap definitions for link events, authentication failures, EGP neighbor loss, and device reload notifications.
Start monitoring Cisco routers, switches, and network devices generally 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.