Standard SNMP Version 2 Traps

[Contents] [Prev] [Next] [Index] [Report an Error]

Table 23 provides an overview of the standard SNMPv2 traps supported by the 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 23: Standard Supported SNMP Version 2 Traps

Trap Category	Trap Name	snmpTrapOID	System Logging Severity Level	Syslog Tag
Startup	authenticationFailure	1.3.6.1.6.3.1.1.5.5	Notice	SNMPD_TRAP _GEN_FAILURE
Link	linkDown	1.3.6.1.6.3.1.1.5.3	Warning	SNMP_TRAP_ LINK_DOWN
Link	linkUp	1.3.6.1.6.3.1.1.5.4	Info	SNMP_TRAP_ LINK_UP
Remote operations	pingProbeFailed	1.3.6.1.2.1.80.0.1	Info	SNMP_TRAP_ PING_PROBE_ FAILED
Remote operations	pingTestFailed	1.3.6.1.2.1.80.0.2	Info	SNMP_TRAP_PING_ TEST_FAILED
Remote operations	pingTestCompleted	1.3.6.1.2.1.80.0.3	Info	SNMP_TRAP_PING _TEST_COMPLETED
Remote operations	traceRoutePathChange	1.3.6.1.2.1.81.0.1	Info	SNMP_TRAP_TRACE_ ROUTE_PATH_ CHANGE
Remote operations	traceRouteTestFailed	1.3.6.1.2.1.81.0.2	Info	SNMP_TRAP_TRACE_ ROUTE_TEST_FAILED
Remote operations	traceRouteTestCompleted	1.3.6.1.2.1.81.0.3	Info	SNMP_TRAP_TRACE_ ROUTE_TEST_COMPLETED
RMON alarm	fallingAlarm	1.3.6.1.2.1.16.0.1	–	–
RMON alarm	risingAlarm	1.3.6.1.2.1.16.0.2	–	–
Routing	bgpEstablished	1.3.6.1.2.1.15.7.1	–	–
Routing	bgpBackwardTransition	1.3.6.1.2.1.15.7.2	–	–
Routing	ospfVirtIfStateChange	1.3.6.1.2.1.14.16.2.1	–	–
Routing	ospfNbrStateChange	1.3.6.1.2.1.14.16.2.2	–	–
Routing	ospfVirtNbrStateChange	1.3.6.1.2.1.14.16.2.3	–	–
Routing	ospfIfConfigError	1.3.6.1.2.1.14.16.2.4	–	–
Routing	ospfVirtIfConfigError	1.3.6.1.2.1.14.16.2.5	–	–
Routing	ospfIfAuthFailure	1.3.6.1.2.1.14.16.2.6	–	–
Routing	ospfVirtIfAuthFailure	1.3.6.1.2.1.14.16.2.7	–	–
Routing	ospfIfRxBadPacket	1.3.6.1.2.1.14.16.2.8	–	–
Routing	ospfVirtIfRxBadPacket	1.3.6.1.2.1.14.16.2.9	–	–
Routing	ospfTxRetransmit	1.3.6.1.2.1.14.16.2.10	–	–
Routing	ospfVirtIfTxRetransmit	1.3.6.1.2.1.14.16.2.11	–	–
Routing	ospfMaxAgeLsa	1.3.6.1.2.1.14.16.2.13	–	–
Routing	ospfIfStateChange	1.3.6.1.2.1.14.16.2.16	–	–
Startup	coldStart	1.3.6.1.6.3.1.1.5.1	Critical	SNMPD_TRAP_ COLD_START
Startup	warmStart	1.3.6.1.6.3.1.1.5.2	Error	SNMPD_TRAP_ WARM_START
VRRP	vrrpTrapNewMaster	1.3.6.1.2.1.68.0.1	Warning	VRRPD_NEWMASTER _TRAP
VRRP	vrrpTrapAuthFailure	1.3.6.1.2.1.68.0.2	Warning	VRRPD_AUTH_FAILURE_TRAP

The JUNOS software supports the following standard SNMP version 2 traps:

SNMP Version 2 Standard Traps

The JUNOS software supports the standard SNMP version traps, which are taken from RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2), and RFC 2863, The Interfaces Group MIB:



coldStartNOTIFICATION-TYPE
STATUScurrent
DESCRIPTION
"A coldStart trap signifies that the SNMPv2 entity, acting
in an agent role, is 
reinitializing itself and that its configuration may have
been altered."
::= { snmpTraps 1 }
warmStartNOTIFICATION-TYPE
STATUScurrent
DESCRIPTION
"A warmStart trap signifies that the SNMPv2 entity, acting
in an agent role, is 
reinitializing itself such that its configuration is unaltered."


::= { snmpTraps 2 }
linkDownNOTIFICATION-TYPE


OBJECTS {
ifIndex
ifAdminStatus
ifOperStatus 
ifName
}


STATUScurrent
DESCRIPTION
"A linkDown trap signifies that the SNMP entity, acting
in an agent role, has 
detected that the ifOperStatus object for one of its communication
links is about 
to enter the down state from some other state (but not
from the notPresent
state). This other state is indicated by the included value
of ifOperStatus."


::= { snmpTraps 3 }
linkUpNOTIFICATION-TYPE


OBJECTS {
ifIndex
ifAdminStatus
ifOperStatus 
ifName
}


STATUScurrent
DESCRIPTION
"A linkUp trap signifies that the SNMP entity, acting in
an agent role, has 
detected that the ifOperStatus object for one of its communication
links left the 
down state and transitioned into some other state (but
not into the notPresent 
state). This other state is indicated by the included value
of ifOperStatus."


::= { snmpTraps 4 }
authenticationFailureNOTIFICATION-TYPE
STATUScurrent
DESCRIPTION
"An authenticationFailure trap signifies that the SNMPv2
entity, acting in an
agent role, has received a protocol message that is not
properly authenticated. 
While all implementations of the SNMPv2 must be capable
of generating
this trap, the snmpEnableAuthenTraps object indicates whether
this trap will be
generated."


::= { snmpTraps 5 }
}


}


}


}


}

SNMP Version 2 MPLS Traps

The JUNOS software supports the Multiprotocol Label Switching (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 on disabling the generation of MPLS traps, see the JUNOS MPLS Applications Configuration Guide.

The 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 the 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 the JUNOS software releases earlier than 8.4, 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.

SNMP Version 2 OSPF Traps MIB

The JUNOS software supports the Open Shortest Path First (OSPF) SNMP version 2 traps. The following descriptions are taken from RFC 1850, OSPF Version 2 Management Information Base:



ospfIfStateChangeNOTIFICATION-TYPE
OBJECTS {
ospfRouterId, -- The originator of the trap
ospfIfIpAddress,
ospfAddressLessIf,
}
STATUS current
DESCRIPTION
"An ospfIfStateChange trap signifies that there has been
a change in the state of a 
non-virtual OSPF interface. This trap should be generated
when the interface state
regresses (e.g., goes from Dr to Down) or progresses to
a terminal state (i.e., 
Point-to-Point, DR Other, Dr, or Backup)."
::= { ospfTraps 16 }
ospfVirtIfStateChange NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfVirtIfAreaId,
ospfVirtIfNeighbor,
}


STATUScurrent
DESCRIPTION
"An ospfIfStateChange trap signifies that there has been
a change in the state of
an OSPF virtual interface. This trap should be generated
when the interface state
regresses (e.g., goes from Point-to-Point to Down) or progresses
to a terminal
state (i.e., Point)."


::= { ospfTraps 1 }
ospfNbrStateChange NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfNbrIpAddr,
ospfNbrAddressLessIndex,
ospfNbrRtrId,
ospfNbrState 
}


STATUScurrent
DESCRIPTION
"An ospfNbrStateChange trap signifies that there has been
a change in the state 
of a non-virtual OSPF neighbor. This trap should be generated
when the neighbor 
state regresses (e.g., goes from Attempt or Full to 1-Way
or Down) or progresses to a terminal state (e.g., 2-Way or Full).
When a neighbor transitions from or to 
Full on non-broadcast multi-access and broadcast networks,
the trap should be 
generated by the designated router. A designated router
transitioning to Down 
will be noted by ospfIfStateChange."


::= { ospfTraps 2 }
ospfVirtNbrStateChange NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfVirtNbrArea,
ospfVirtNbrRtrId,
ospfVirtNbrState 
}


STATUS current
DESCRIPTION
  "An ospfIfStateChange trap signifies that there has been
a change in the state 
of an OSPF virtual neighbor. This trap should be generated
when the neighbor
state regresses (e.g., goes from Attempt or Full to 1-Way
or Down) or progresses to a terminal state (e.g., Full)."


::= { ospfTraps 3 }
ospfIfConfigError NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfIfIpAddress,
ospfAddressLessIf,
ospfPacketSrc, -- The source IP address
ospfConfigErrorType, -- Type of error
ospfPacketType
}


STATUScurrent
DESCRIPTION
"An ospfIfConfigError trap signifies that a packet has
been received on a 
non-virtual interface from a router whose configuration
parameters conflict with 
this router's configuration parameters. Note that the event
optionMismatch 
should cause a trap only if it prevents an adjacency from
forming."


::= { ospfTraps 4 }
ospfVirtIfConfigError NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfVirtIfAreaId,
ospfVirtIfNeighbor,
ospfConfigErrorType, -- Type of error
ospfPacketType
}


STATUScurrent
DESCRIPTION
"An ospfConfigError trap signifies that a packet has been
received on a virtual 
interface from a router whose configuration parameters
conflict with this router's 
configuration parameters. Note that the event optionMismatch
should cause a 
trap only if it prevents an adjacency from forming."


::= { ospfTraps 5 }
ospfIfAuthFailure NOTIFICATION-TYPE


OBJECTS {ospfRouterId, -- The originator of the trap
ospfIfIpAddress,
ospfAddressLessIf,
ospfPacketSrc, -- The source IP address
ospfConfigErrorType, -- authTypeMismatch or
 -- authFailure
ospfPacketType 
}


STATUScurrent
DESCRIPTION
"An ospfIfAuthFailure trap signifies that a packet has
been received on a 
non-virtual interface from a router whose authentication
key or authentication type 
conflicts with this router's authentication key or authentication
type."


::= { ospfTraps 6 }
ospfVirtIfAuthFailure NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfVirtIfAreaId,
ospfVirtIfNeighbor,
ospfConfigErrorType, -- authTypeMismatch or
-- authFailure
}


STATUScurrent
DESCRIPTION
"An ospfVirtIfAuthFailure trap signifies that a packet
has been received on a 
virtual interface from a router whose authentication key
or authentication type 
conflicts with this router's authentication key or authentication
type."


::= { ospfTraps 7 }
ospfIfRxBadPacket NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfIfIpAddress,
ospfAddressLessIf,
ospfPacketSrc, -- The source IP address
ospfPacketType
}


STATUScurrent
DESCRIPTION
"An ospfIfRxBadPacket trap signifies that an OSPF packet
has been received on
a nonvirtual interface that cannot be parsed."


::= { ospfTraps 8 }
ospfVirtIfRxBadPacket NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfVirtIfAreaId,
ospfVirtIfNeighbor,
ospfPacketType
}


STATUScurrent
DESCRIPTION
"An ospfRxBadPacket trap signifies that an OSPF packet
has been received on a 
virtual interface that cannot be parsed."


::= { ospfTraps 9 }
ospfTxRetransmit NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfIfIpAddress,
ospfAddressLessIf,
ospfNbrRtrId, -- Destination
ospfPacketType,
ospfLsdbType,
ospfLsdbLsid,
ospfLsdbRouterId
}


STATUScurrent
DESCRIPTION
"An ospfTxRetransmit trap signifies that an OSPF packet
has been retransmitted 
on a nonvirtual interface. All packets that may be retransmitted
are associated 
with an LSDB entry. The LS type, LS ID, and Router ID are
used to identify the 
LSDB entry."


::= { ospfTraps 10 }
ospfVirtIfTxRetransmit NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfVirtIfAreaId,
ospfVirtIfNeighbor,
  ospfPacketType,
ospfLsdbType,
ospfLsdbLsid,
ospfLsdbRouterId
}


STATUScurrent
DESCRIPTION
"An ospfTxRetransmit trap signifies that an OSPF packet
has been retransmitted 
on a virtual interface. All packets that may be retransmitted
are associated with 
an LSDB entry. The LS type, LS ID, and Router ID are used
to identify the LSDB 
entry."


::= { ospfTraps 11 }


ospfMaxAgeLsa NOTIFICATION-TYPE


OBJECTS {
ospfRouterId, -- The originator of the trap
ospfLsdbAreaId, -- 0.0.0.0 for AS Externals
ospfLsdbType,
ospfLsdbLsid,
ospfLsdbRouterId
}


STATUScurrent
DESCRIPTION
"An ospfMaxAgeLsa trap signifies that one of the LSAs in
the router's link-state 
database has aged to MaxAge."


::= { ospfTraps 13 }
}


}


}


}


}


}


}


}


}


}


}


}


}


}

SNMP Version 2 Ping Traps MIB

The following descriptions for the SNMPv2 ping traps are from RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations:



pingProbeFailedNOTIFICATION-TYPE
OBJECTS {
pingCtlTargetAddressType,
 pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}
STATUScurrent
DESCRIPTION
"Generated when a probe failure is detected when the corresponding 
pingCtlTrapGeneration object is set to probeFailure(0)
subject to the value of
pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter
can be 
used to specify the number of successive probe failures
that are required
before this notification can be generated."
::= { pingNotifications 1 }
pingTestFailedNOTIFICATION-TYPE


OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}


STATUScurrent
DESCRIPTION
"Generated when a ping test is determined to have failed
when the 
corresponding pingCtlTrapGeneration object is set to testFailure(1).
In this 
instance pingCtlTrapTestFailureFilter should specify the
number of probes in a 
test required to have failed in order to consider the test
as failed."


::= { pingNotifications 2 }
pingTestCompletedNOTIFICATION-TYPE


OBJECTS {
pingCtlTargetAddressType,
pingCtlTargetAddress,
pingResultsOperStatus,
pingResultsIpTargetAddressType,
pingResultsIpTargetAddress,
pingResultsMinRtt,
pingResultsMaxRtt,
pingResultsAverageRtt,
pingResultsProbeResponses,
pingResultsSentProbes,
pingResultsRttSumOfSquares,
pingResultsLastGoodProbe
}


STATUScurrent
DESCRIPTION
"Generated at the completion of a ping test when the corresponding 
pingCtlTrapGeneration object is set to testCompletion(4)."


::= { pingNotifications 3 }
}


}


}

SNMP Version 2 Traceroute Traps MIB

The following descriptions for the SNMPv2 traceroute traps are from RFC 2925, Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations:



traceRoutePathChangeNOTIFICATION-TYPE
OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}
STATUScurrent
DESCRIPTION
"The path to a target has changed."
::= { traceRouteNotifications 1 }
traceRouteTestFailedNOTIFICATION-TYPE


OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}


STATUScurrent
DESCRIPTION
"Could not determine the path to a target."


::= { traceRouteNotifications 2 }
traceRouteTestCompletedNOTIFICATION-TYPE


OBJECTS {
traceRouteCtlTargetAddressType,
traceRouteCtlTargetAddress,
traceRouteResultsIpTgtAddrType,
traceRouteResultsIpTgtAddr
}


STATUScurrent
DESCRIPTION
"The path to a target has just been determined."


::= { traceRouteNotifications 3 }
}


}


}

SNMP Version 2 VRRP Traps MIB

The following descriptions for the SNMPv2 Virtual Router Redundancy Protocol (VRRP) traps are from RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol:



--- vrrp trap definitions
vrrpTrapPacketSrcOBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESSaccessible-for-notify
STATUScurrent
DESCRIPTION
"The IP address of an inbound VRRP packet. Used by
vrrpTrapAuthFailure trap."
::= { vrrpOperations 5 }
 vrrpTrapAuthErrorTypeOBJECT-TYPE


SYNTAXINTEGER {
invalidAuthType (1),
authTypeMismatch (2),
authFailure (3)
}


MAX-ACCESSaccessible-for-notify
STATUScurrent
DESCRIPTION
"Potential types of configuration conflicts. Used by vrrpAuthFailure
trap."
}

[Contents] [Prev] [Next] [Index] [Report an Error]