Standard SNMP Version 2 Traps
Table 7 provides an overview of the standard SNMPv2 traps supported by JUNOS Software. The traps are organized first by trap category and then by trap name and include their snmpTrapOID. The system logging severity levels are listed for those traps that have them with their corresponding system log tag. Traps that do not have corresponding system logging severity levels are marked with an en dash (–) in the table.
For more information about system log messages, see the Junos System Log Messages Reference. For more information about configuring system logging, see the Junos System Basics Configuration Guide.
Table 7: Standard Supported SNMP Version 2 Traps
Defined in | Trap Name | snmpTrapOID | System Logging Severity Level | Syslog Tag | Supported on |
|---|---|---|---|---|---|
| Startup Notifications | |||||
RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2), | coldStart | 1.3.6.1.6.3.1.1.5.1 | Critical | SNMPD_TRAP_ COLD_START | All devices running JUNOS Software. |
warmStart | 1.3.6.1.6.3.1.1.5.2 | Error | SNMPD_TRAP_ WARM_START | All devices running JUNOS Software. | |
authenticationFailure | 1.3.6.1.6.3.1.1.5.5 | Notice | SNMPD_TRAP_ GEN_FAILURE | All devices running JUNOS Software. | |
| Link Notifications | |||||
RFC 2863, The Interfaces Group MIB | linkDown | 1.3.6.1.6.3.1.1.5.3 | Warning | SNMP_TRAP_ LINK_DOWN | All devices running JUNOS Software. |
linkUp | 1.3.6.1.6.3.1.1.5.4 | Info | SNMP_TRAP_ LINK_UP | All devices running JUNOS Software. | |
| Remote Operations Notifications | |||||
RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations | pingProbeFailed | 1.3.6.1.2.1.80.0.1 | Info | SNMP_TRAP_ PING_PROBE_ FAILED | All devices running JUNOS Software. |
pingTestFailed | 1.3.6.1.2.1.80.0.2 | Info | SNMP_TRAP_PING_ TEST_FAILED | All devices running JUNOS Software. | |
pingTestCompleted | 1.3.6.1.2.1.80.0.3 | Info | SNMP_TRAP_PING_ TEST_COMPLETED | All devices running JUNOS Software. | |
traceRoutePathChange | 1.3.6.1.2.1.81.0.1 | Info | SNMP_TRAP_TRACE_ ROUTE_PATH_ CHANGE | All devices running JUNOS Software. | |
traceRouteTestFailed | 1.3.6.1.2.1.81.0.2 | Info | SNMP_TRAP_TRACE_ ROUTE_TEST_FAILED | All devices running JUNOS Software. | |
traceRouteTestCompleted | 1.3.6.1.2.1.81.0.3 | Info | SNMP_TRAP_TRACE_ ROUTE_TEST_ COMPLETED | All devices running JUNOS Software. | |
| RMON Alarms | |||||
RFC 2819a, RMON MIB | fallingAlarm | 1.3.6.1.2.1.16.0.1 | – | – | All devices running JUNOS Software. |
risingAlarm | 1.3.6.1.2.1.16.0.2 | – | – | All devices running JUNOS Software. | |
| Routing Notifications | |||||
BGP 4 MIB | bgpEstablished | 1.3.6.1.2.1.15.7.1 | – | – | M, MX, T, EX, J, and SRX for branch devices. |
bgpBackwardTransition | 1.3.6.1.2.1.15.7.2 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
OSPF Trap MIB | ospfVirtIfStateChange | 1.3.6.1.2.1.14.16.2.1 | – | – | M, MX, T, EX, J, and SRX for branch devices. |
ospfNbrStateChange | 1.3.6.1.2.1.14.16.2.2 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfVirtNbrStateChange | 1.3.6.1.2.1.14.16.2.3 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfIfConfigError | 1.3.6.1.2.1.14.16.2.4 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfVirtIfConfigError | 1.3.6.1.2.1.14.16.2.5 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfIfAuthFailure | 1.3.6.1.2.1.14.16.2.6 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfVirtIfAuthFailure | 1.3.6.1.2.1.14.16.2.7 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfIfRxBadPacket | 1.3.6.1.2.1.14.16.2.8 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfVirtIfRxBadPacket | 1.3.6.1.2.1.14.16.2.9 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfTxRetransmit | 1.3.6.1.2.1.14.16.2.10 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfVirtIfTxRetransmit | 1.3.6.1.2.1.14.16.2.11 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfMaxAgeLsa | 1.3.6.1.2.1.14.16.2.13 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
ospfIfStateChange | 1.3.6.1.2.1.14.16.2.16 | – | – | M, MX, T, EX, J, and SRX for branch devices. | |
RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol | vrrpTrapNewMaster | 1.3.6.1.2.1.68.0.1 | Warning | VRRPD_ NEWMASTER_ TRAP | All devices running JUNOS Software. |
vrrpTrapAuthFailure | 1.3.6.1.2.1.68.0.2 | Warning | VRRPD_AUTH_ FAILURE_ TRAP | All devices running JUNOS Software. | |
JUNOS Software also supports the following standard SNMP version 2 traps:
SNMP Version 2 MPLS Traps
JUNOS Software supports the MPLS SNMP version 2 traps defined in RFC 3812, Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base.
You can disable the MPLS traps by including the no-trap option at the [edit protocol mpls log-updown] hierarchy level. For information about disabling the generation of MPLS traps, see the JUNOS MPLS Applications Configuration Guide.
JUNOS Software supports the following MPLS traps:
- mplsTunnelUp—Generated when an mplsTunnelOperStatus object for one of the configured tunnels leaves the down state and transitions into another state, other than the notPresent state.
- mplsTunnelDown—Generated when an mplsTunnelOperStatus object for one of the configured tunnels enters the down state from a state other than the notPresent state.
Note: When an LSP flaps, only the ingress and egress routers of that LSP generate the mplsTunnelUp and mplsTunnelDown traps. Previously, all the routers associated with an LSP—that is, the ingress, egress, and transit routers—used to generate the traps when the LSP flaps.
- mplsTunnelRerouted—Generated when a tunnel is rerouted.
- mplsTunnelReoptimized—Generated when a
tunnel is reoptimized.
Note: In JUNOS Software Release 8.3 and earlier, mplsTunnelReoptimized was generated every time the optimization timer expired; that is, when the optimization timer exceeded the value set for the optimize-timer statement at the [edit protocols mpls label-switched-path path-name] hierarchy level. However, in Release 8.4 and later, this trap is generated only when the path is reoptimized, and not when the optimization timer expires.