Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

SNMP Traps Supported by Junos OS

The QFX Series standalone switches, QFX Series Virtual Chassis, and QFabric systems support standard SNMP traps and Juniper Networks enterprise-specific traps.

SNMP Traps Support

SNMP Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis

QFX Series standalone switches and QFX Series Virtual Chassis support SNMPv1 and v2 traps. For more information, see:

SNMPv1 Traps

QFX Series standalone switches and QFX Series Virtual Chassis support both standard SNMPv1 traps and Juniper Networks enterprise-specific SNMPv1 traps. See:

  • Table 1 for standard SNMPv1 traps.

  • Table 2 for enterprise-specific SNMPv1 traps.

The traps are organized first by trap category and then by trap name. The system logging severity levels are listed for those traps that have them. Traps that do not have corresponding system logging severity levels are marked with an en dash (–).

Table 1: Standard SNMP Version 1 Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis

Defined in

Trap Name

Enterprise ID

Generic Trap Number

Specific Trap Number

System Logging Severity Level

Syslog Tag
Link Notifications

RFC 1215, Conventions for Defining Traps for Use with the SNMP

linkDown

1.3.6.1.4.1.2636

2

0

Warning

SNMP_ TRAP_ LINK_DOWN

linkUp

1.3.6.1.4.1.2636

3

0

Info

SNMP_TRAP_ LINK_UP
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

6

1

Info

SNMP_TRAP _PING_ PROBE_ FAILED

pingTestFailed

1.3.6.1.2.1.80.0

6

2

Info

SNMP_TRAP_ PING_TEST _FAILED

pingTestCompleted

1.3.6.1.2.1.80.0

6

3

Info

SNMP_TRAP_ PING_TEST_ COMPLETED

traceRoutePathChange

1.3.6.1.2.1.81.0

6

1

Info

SNMP_TRAP_ TRACE_ROUTE_ PATH_CHANGE

traceRouteTestFailed

1.3.6.1.2.1.81.0

6

2

Info

SNMP_TRAP_ TRACE_ROUTE_ TEST_FAILED

traceRouteTestCompleted

1.3.6.1.2.1.81.0

6

3

Info

SNMP_TRAP_ TRACE_ROUTE_ TEST_COMPLETED
RMON Alarms

RFC 2819a, RMON MIB

fallingAlarm

1.3.6.1.2.1.16

6

2

–

–

risingAlarm

1.3.6.1.2.1.16

6

1

–

–
Routing Notifications

BGP 4 MIB

bgpEstablished

1.3.6.1.2.1.15.7

6

1

–

–

bgpBackwardTransition

1.3.6.1.2.1.15.7

6

2

–

–

OSPF TRAP MIB

ospfVirtIfStateChange

1.3.6.1.2.1.14.16.2

6

1

–

–

ospfNbrStateChange

1.3.6.1.2.1.14.16.2

6

2

–

–

ospfVirtNbrStateChange

1.3.6.1.2.1.14.16.2

6

3

–

–

ospfIfConfigError

1.3.6.1.2.1.14.16.2

6

4

–

–

ospfVirtIfConfigError

1.3.6.1.2.1.14.16.2

6

5

–

–

ospfIfAuthFailure

1.3.6.1.2.1.14.16.2

6

6

–

–

ospfVirtIfAuthFailure

1.3.6.1.2.1.14.16.2

6

7

–

–

ospfIfRxBadPacket

1.3.6.1.2.1.14.16.2

6

8

–

–

ospfVirtIfRxBadPacket

1.3.6.1.2.1.14.16.2

6

9

–

–

ospfTxRetransmit

1.3.6.1.2.1.14.16.2

6

10

–

–

ospfVirtIfTxRetransmit

1.3.6.1.2.1.14.16.2

6

11

–

–

ospfMaxAgeLsa

1.3.6.1.2.1.14.16.2

6

13

–

–

ospfIfStateChange

1.3.6.1.2.1.14.16.2

6

16

–

–
Startup Notifications

RFC 1215, Conventions for Defining Traps for Use with the SNMP

authenticationFailure

1.3.6.1.4.1.2636

4

0

Notice

SNMPD_ TRAP_ GEN_FAILURE

coldStart

1.3.6.1.4.1.2636

0

0

Critical

SNMPD_TRAP_ COLD_START

warmStart

1.3.6.1.4.1.2636

1

0

Error

SNMPD_TRAP_ WARM_START
VRRP Notifications

RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol

vrrpTrapNewMaster

1.3.6.1.2.1.68

6

1

Warning

VRRPD_NEW MASTER_TRAP

vrrpTrapAuthFailure

1.3.6.1.2.1.68

6

2

Warning

VRRPD_AUTH_ FAILURE_TRAP
Table 2: Enterprise-Specific SNMPv1 Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis

Defined in

Trap Name

Enterprise ID

Generic Trap Number

Specific Trap Number

System Logging Severity Level

System Log Tag
Chassis Notifications (Alarm Conditions)

Chassis MIB (jnx-chassis. mib)

jnxPowerSupplyFailure

1.3.6.1.4.1.2636.4.1

6

1

Warning

CHASSISD_ SNMP_ TRAP

jnxFanFailure

1.3.6.1.4.1.26361

6

2

Critical

CHASSISD_ SNMP_ TRAP

jnxOverTemperature

11.4.1.2636.4.1

6

3

Alert

CHASSISD_ SNMP_ TRAP

jnxFruRemoval

1.3.6.1.4.1.2636.4.1

6

5

Notice

CHASSISD_ SNMP_ TRAP

jnxFruInsertion

1.3.6.1.4.1.2636.4.1

6

6

Notice

CHASSISD_ SNMP_ TRAP

jnxFruPowerOff

1.3.6.1.4.1.2636.4.1

6

7

Notice

CHASSISD_ SNMP_ TRAP

jnxFruPowerOn

1.3.6.1.4.1.2636.4.1

6

8

Notice

CHASSISD_ SNMP_ TRAP

jnxFruFailed

1.3.6.1.4.1.2636.4.1

6

9

Warning

CHASSISD_ SNMP_ TRAP

jnxFruOffline

1.3.6.1.4.1.2636.4.1

6

10

Notice

CHASSISD_ SNMP_ TRAP

jnxFruOnline

1.3.6.1.4.1.2636.4.1

6

11

Notice

CHASSISD_ SNMP_ TRAP

jnxFruCheck

1.3.6.1.4.1.2636.4.1

6

12

Warning

CHASSISD_ SNMP_ TRAP

jnxPowerSupplyOk

1.3.6.1.4.1.2636.4.2

6

1

Critical

CHASSISD_ SNMP_ TRAP

jnxFanOK

1.3.6.1.4.1.2636.4.2

6

2

Critical

CHASSISD_ SNMP_ TRAP

jnxTemperatureOK

1.3.6.1.4.1.2636.4.2

6

3

Alert

CHASSISD_ SNMP_ TRAP
Configuration Notifications

Configuration Management MIB (jnx- configmgmt. mib)

jnxCmCfgChange

1.3.6.1.4.1.2636.4.5

6

1

–

–

jnxCmRescueChange

1.3.6.1.4.1.2636.4.5

6

2

–

–
Remote Operations

Ping MIB (jnx-ping.mib)

jnxPingRttThresholdExceeded

1.3.6.1.4.1.2636.4.9

6

1

–

–

jnxPingRttStdDevThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

2

–

–

jnxPingRttJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

3

–

–

jnxPingEgressThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

4

–

–

jnxPingEgressStdDev ThresholdExceeded

1.3.6.1.4.1.2636.4.9

6

5

–

–

jnxPingEgressJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

6

–

–

jnxPingIngressThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

7

–

–

jnxPingIngressStddevThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

8

–

–

jnxPingIngressJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9

6

9

–

–
RMON Alarms

RMON MIB (jnx-rmon. mib)

jnxRmonAlarmGetFailure

1.3.6.1.4.1.2636.4.3

6

1

–

–

jnxRmonGetOk

1.3.6.1.4.1.2636.4.3

6

2

–

–

SNMPv2 Traps

  • Table 3 lists the standard SNMP traps

  • Table 4 lists the Juniper Networks enterprise-specific traps

Table 3: Standard SNMPv2 Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis

Defined in

Trap Name

SNMP Trap OID

System Logging Severity Level

Syslog Tag
Link Notifications

RFC 2863, The Interfaces Group MIB

linkDown

1.3.6.1.6.3.1.1.5.3

Warning

SNMP_TRAP_ LINK_DOWN

linkUp

1.3.6.1.6.3.1.1.5.4

Info

SNMP_TRAP_ LINK_UP
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

pingTestFailed

1.3.6.1.2.1.80.0.2

Info

SNMP_TRAP_PING_ TEST_FAILED

pingTestCompleted

1.3.6.1.2.1.80.0.3

Info

SNMP_TRAP_PING_ TEST_COMPLETED

traceRoutePathChange

1.3.6.1.2.1.81.0.1

Info

SNMP_TRAP_TRACE_ ROUTE_PATH_ CHANGE

traceRouteTestFailed

1.3.6.1.2.1.81.0.2

Info

SNMP_TRAP_TRACE_ ROUTE_TEST_FAILED

traceRouteTestCompleted

1.3.6.1.2.1.81.0.3

Info

SNMP_TRAP_TRACE_ ROUTE_TEST_ COMPLETED
RMON Alarms

RFC 2819a, RMON MIB

fallingAlarm

1.3.6.1.2.1.16.0.1

–

–

risingAlarm

1.3.6.1.2.1.16.0.2

–

–
Routing Notifications

BGP 4 MIB

bgpEstablished

1.3.6.1.2.1.15.7.1

–

–

bgpBackwardTransition

1.3.6.1.2.1.15.7.2

–

–

OSPF Trap MIB

ospfVirtIfStateChange

1.3.6.1.2.1.14.16.2.1

–

–

ospfNbrStateChange

1.3.6.1.2.1.14.16.2.2

–

–

ospfVirtNbrStateChange

1.3.6.1.2.1.14.16.2.3

–

–

ospfIfConfigError

1.3.6.1.2.1.14.16.2.4

–

–

ospfVirtIfConfigError

1.3.6.1.2.1.14.16.2.5

–

–

ospfIfAuthFailure

1.3.6.1.2.1.14.16.2.6

–

–

ospfVirtIfAuthFailure

1.3.6.1.2.1.14.16.2.7

–

–

ospfIfRxBadPacket

1.3.6.1.2.1.14.16.2.8

–

–

ospfVirtIfRxBadPacket

1.3.6.1.2.1.14.16.2.9

–

–

ospfTxRetransmit

1.3.6.1.2.1.14.16.2.10

–

–

ospfVirtIfTxRetransmit

1.3.6.1.2.1.14.16.2.11

–

–

ospfMaxAgeLsa

1.3.6.1.2.1.14.16.2.13

–

–

ospfIfStateChange

1.3.6.1.2.1.14.16.2.16

–

–
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

warmStart

1.3.6.1.6.3.1.1.5.2

Error

SNMPD_TRAP_ WARM_START

authenticationFailure

1.3.6.1.6.3.1.1.5.5

Notice

SNMPD_TRAP_ GEN_FAILURE
VRRP Notifications

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

vrrpTrapAuthFailure

1.3.6.1.2.1.68.0.2

Warning

VRRPD_AUTH_ FAILURE_ TRAP
Table 4: Enterprise-Specific SNMPv2 Traps Supported on QFX Series Standalone Switches and QFX Series Virtual Chassis

Source MIB

Trap Name

SNMP Trap OID

System Logging Severity Level

System Log Tag
Chassis (Alarm Conditions) Notifications

Chassis MIB (mib-jnx-chassis)

jnxPowerSupplyFailure

1.3.6.1.4.1.2636.4.1.1

Alert

CHASSISD_ SNMP_ TRAP
 

jnxFanFailure

1.3.6.1.4.1.2636.4.1.2

Critical

CHASSISD_ SNMP_ TRAP
 

jnxOverTemperature

1.3.6.1.4.1.2636.4.1.3

Critical

CHASSISD_ SNMP_ TRAP
 

jnxFruRemoval

1.3.6.1.4.1.2636.4.1.5

Notice

CHASSISD_ SNMP_ TRAP
 

jnxFruInsertion

1.3.6.1.4.1.2636.4.1.6

Notice

CHASSISD_ SNMP_ TRAP
 

jnxFruPowerOff

1.3.6.1.4.1.2636.4.1.7

Notice

CHASSISD_ SNMP_ TRAP
 

jnxFruPowerOn

1.3.6.1.4.1.2636.4.1.8

Notice

CHASSISD_ SNMP_ TRAP
 

jnxFruFailed

1.3.6.1.4.1.2636.4.1.9

Warning

CHASSISD_ SNMP_ TRAP
 

jnxFruOffline

1.3.6.1.4.1.2636.4.1.10

Notice

CHASSISD_ SNMP_ TRAP
 

jnxFruOnline

1.3.6.1.4.1.2636.4.1.11

Notice

CHASSISD_ SNMP_ TRAP
 

jnxFruCheck

1.3.6.1.4.1.2636.4.1.12

Notice

CHASSISD_ SNMP_ TRAP
 

jnxPowerSupplyOK

1.3.6.1.4.1.2636.4.2.1

Critical

CHASSISD_ SNMP_ TRAP
 

jnxFanOK

1.3.6.1.4.1.2636.4.2.2

Critical

CHASSISD_ SNMP_ TRAP
 

jnxTemperatureOK

1.3.6.1.4.1.2636.4.2.3

Alert

CHASSISD_ SNMP_ TRAP
Configuration Notifications

Configuration Management MIB (mib-jnx-cfgmgmt)

jnxCmCfgChange

1.3.6.1.4.1.2636.4.5.0.1

–

–

jnxCmRescueChange

1.3.6.1.4.1.2636.4.5.0.2

–

–
Remote Operations Notifications

Ping MIB (mib-jnx-ping)

jnxPingRttThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.1

–

–

jnxPingRttStdDevThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.2

–

–

jnxPingRttJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.3

–

–

jnxPingEgressThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.4

–

–

jnxPingEgressStdDevThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.5

–

–

jnxPingEgressJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.6

–

–

jnxPingIngressThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.7

–

–

jnxPingIngressStddevThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.8

–

–

jnxPingIngressJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.9

–

–
RMON Alarms

RMON MIB (mib-jnx-rmon)

jnxRmonAlarmGetFailure

1.3.6.1.4.1.2636.4. 3.0.1

–

–

jnxRmonGetOk

1.3.6.1.4.1.2636.4. 3.0.2

–

–

SNMP Traps Supported on QFabric Systems

QFabric systems support standard SNMPv2 traps and Juniper Networks enterprise-specific SNMPv2 traps.

Note:

QFabric systems do not support SNMPv1 traps.

For more information, see:

  • Table 5 for standard SNMPv2 traps

  • Table 6 for Juniper Networks enterprise-specific SNMPv2 traps

Table 5: Standard SNMPv2 Traps Supported on QFabric Systems

Defined in

Trap Name

SNMP Trap OID

System Logging Severity Level

Syslog Tag
Link Notifications

RFC 2863, The Interfaces Group MIB

linkDown

1.3.6.1.6.3.1.1.5.3

Warning

SNMP_TRAP_ LINK_DOWN

linkUp

1.3.6.1.6.3.1.1.5.4

Info

SNMP_TRAP_ LINK_UP
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

warmStart

1.3.6.1.6.3.1.1.5.2

Error

SNMPD_TRAP_ WARM_START

authenticationFailure

1.3.6.1.6.3.1.1.5.5

Notice

SNMPD_TRAP_ GEN_FAILURE
Table 6: Enterprise-Specific SNMPv2 Traps Supported on QFabric Systems

Source MIB

Trap Name

SNMP Trap OID

System Logging Severity Level

System Log Tag

Fabric Chassis MIB (mib-jnx-fabric- chassis)

 Fabric Chassis (Alarm Conditions) Notifications

jnxFabricPowerSupplyFailure

1.3.6.1.4.1.2636.4.19.1

Warning

–

jnxFabricFanFailure

1.3.6.1.4.1.2636.4.19.2

Critical

–

jnxFabricOverTemperature

1.3.6.1.4.1.2636.4.19.3

Alert

–

jnxFabricRedundancySwitchover

1.3.6.1.4.1.2636.4.19.4

Notice

–

jnxFabricFruRemoval

1.3.6.1.4.1.2636.4.19.5

Notice

–

jnxFabricFruInsertion

1.3.6.1.4.1.2636.4.19.6

Notice

–

jnxFabricFruPowerOff

1.3.6.1.4.1.2636.4.19.7

Notice

–

jnxFabricFruPowerOn

1.3.6.1.4.1.2636.4.19.8

Notice

–

jnxFabricFruFailed

1.3.6.1.4.1.2636.4.19.9

Warning

–

jnxFabricFruOffline

1.3.6.1.4.1.2636.4.19.10

Notice

–

jnxFabricFruOnline

1.3.6.1.4.1.2636.4.19.11

Notice

–

jnxFabricFruCheck

1.3.6.1.4.1.2636.4.19.12

Warning

–

jnxFabricFEBSwitchover

1.3.6.1.4.1.2636.4.19.13

Warning

–

jnxFabricHardDiskFailed

1.3.6.1.4.1.2636.4.19.14

Warning

–

jnxFabricHardDiskMissing

1.3.6.1.4.1.2636.4.19.15

Warning

–

jnxFabricBootFromBackup

1.3.6.1.4.1.2636.4.19.16

Warning

–
Fabric Chassis (Alarm Cleared Conditions) Notifications

jnxFabricPowerSupplyOK

1.3.6.1.4.1.2636.4.20.1

Critical

–

jnxFabricFanOK

1.3.6.1.4.1.2636.4.20.2

Critical

–

jnxFabricTemperatureOK

1.3.6.1.4.1.2636.4.20.3

Alert

–

jnxFabricFruOK

1.3.6.1.4.1.2636.4.20.4

–

–

QFabric MIB (mib-jnx-qf-smi)

 QFabric MIB Notifications

jnxQFabricDownloadIssued

1.3.6.1.4.1.2636.3.42.1.0.1

–

–

jnxQFabricDownloadFailed

1.3.6.1.4.1.2636.3.42.1.0.2

–

–

jnxQFabricDownloadSucceeded

1.3.6.1.4.1.2636.3.42.1.0.3

–

–

jnxQFabricUpgradeIssued

1.3.6.1.4.1.2636.3.42.1.0.4

–

–

jnxQFabricUpgradeFailed

1.3.6.1.4.1.2636.3.42.1.0.5

–

–

jnxQFabricUpgradeSucceeded

1.3.6.1.4.1.2636.3.42.1.0.6

–

–
Configuration Notifications

Configuration Management MIB (mib-jnx-cfgmgmt)

jnxCmCfgChange

1.3.6.1.4.1.2636.4.5.0.1

–

–

jnxCmRescueChange

1.3.6.1.4.1.2636.4.5.0.2

–

–
Remote Operations Notifications

Ping MIB (mib-jnx-ping)

jnxPingRttThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.1

–

–

jnxPingRttStdDevThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.2

–

–

jnxPingRttJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.3

–

–

jnxPingEgressThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.4

–

–

jnxPingEgressStdDevThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.5

–

–

jnxPingEgressJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.6

–

–

jnxPingIngressThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.7

–

–

jnxPingIngressStddevThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.8

–

–

jnxPingIngressJitterThreshold Exceeded

1.3.6.1.4.1.2636.4.9.0.9

–

–

See Also

Standard SNMP Traps Supported by Junos OS

This topic provides the list of standard SNMPv1 and SNMPv2 traps supported by devices running Junos OS. For more information about traps see SNMP MIB Explorer.

Starting in Junos OS Release 20.1, after graceful routing engine switchover (GRES), the new primary Routing Engine sends a single warmStart notification. The primary Routing Engine sends a coldStart notification when the device comes up. The primary Routing Engine also sends warmStart notifications for subsequent restarts of the SNMP daemon. After GRES, the new primary Routing Engine sends a single warmStart notification and the backup Routing Engine does not send any notification.

Standard SNMP Version 1 Traps

Table 7 provides an overview of the standard traps for SNMPv1. The traps are organized first by trap category and then by trap name, and include their enterprise ID, generic trap number, and specific trap number. 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 System Log Explorer.

Table 7: Standard Supported SNMP Version 1 Traps

Defined in

Trap Name

Enterprise ID

Generic Trap Number

Specific Trap Number

System Logging Severity Level

Syslog Tag

Supported On
Startup Notifications

RFC 1215, Conventions for Defining Traps for Use with the SNMP

authenticationFailure

1.3.6.1.4.1.2636

4

0

Notice

SNMPD_ TRAP_ GEN_FAILURE

All devices running Junos OS.

coldStart

1.3.6.1.4.1.2636

0

0

Critical

SNMPD_TRAP_ COLD_START

All devices running Junos OS.

warmStart

1.3.6.1.4.1.2636

1

0

Error

SNMPD_TRAP_ WARM_START

All devices running Junos OS.
Link Notifications

RFC 1215, Conventions for Defining Traps for Use with the SNMP

linkDown

1.3.6.1.4.1.2636

2

0

Warning

SNMP_ TRAP_ LINK_DOWN

All devices running Junos OS.

linkUp

1.3.6.1.4.1.2636

3

0

Info

SNMP_TRAP_ LINK_UP

All devices running Junos OS.
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

6

1

Info

SNMP_TRAP _PING_ PROBE_ FAILED

All devices running Junos OS.

pingTestFailed

1.3.6.1.2.1.80.0

6

2

Info

SNMP_TRAP_ PING_TEST _FAILED

All devices running Junos OS.

pingTestCompleted

1.3.6.1.2.1.80.0

6

3

Info

SNMP_TRAP_ PING_TEST_ COMPLETED

All devices running Junos OS.
RMON Alarms

RFC 2819a, RMON MIB

fallingAlarm

1.3.6.1.2.1.16

6

2

–

–

All devices running Junos OS.

risingAlarm

1.3.6.1.2.1.16

6

1

–

–

All devices running Junos OS.
Routing Notifications

BGP 4 MIB

bgpEstablished

1.3.6.1.2.1.15.7

6

1

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

bgpBackwardTransition

1.3.6.1.2.1.15.7

6

2

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

OSPF TRAP MIB

ospfVirtIfStateChange

1.3.6.1.2.1.14.16.2

6

1

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfNbrStateChange

1.3.6.1.2.1.14.16.2

6

2

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfVirtNbrStateChange

1.3.6.1.2.1.14.16.2

6

3

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfIfConfigError

1.3.6.1.2.1.14.16.2

6

4

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfVirtIfConfigError

1.3.6.1.2.1.14.16.2

6

5

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfIfAuthFailure

1.3.6.1.2.1.14.16.2

6

6

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfVirtIfAuthFailure

1.3.6.1.2.1.14.16.2

6

7

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfIfRxBadPacket

1.3.6.1.2.1.14.16.2

6

8

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfVirtIfRxBadPacket

1.3.6.1.2.1.14.16.2

6

9

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfTxRetransmit

1.3.6.1.2.1.14.16.2

6

10

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfVirtIfTxRetransmit

1.3.6.1.2.1.14.16.2

6

11

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfMaxAgeLsa

1.3.6.1.2.1.14.16.2

6

13

–

–

M, T, MX, J, EX, and SRX Series Firewalls.

ospfIfStateChange

1.3.6.1.2.1.14.16.2

6

16

–

–

M, T, MX, J, EX, and SRX Series Firewalls.
VRRP Notifications

RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol

vrrpTrapNewMaster

1.3.6.1.2.1.68

6

1

Warning

VRRPD_NEW MASTER_TRAP

All devices running Junos OS.

vrrpTrapAuthFailure

1.3.6.1.2.1.68

6

2

Warning

VRRPD_AUTH_ FAILURE_TRAP

All devices running Junos OS.

RFC 6527, Definitions of Managed Objects for the Virtual Router Redundancy Protocol Version 3 (VRRPv3)

vrrpv3NewMaster

1.3.6.1.2.1.207

6

1

Warning

VRRPD_NEW_MASTER

M and MX

vrrpv3ProtoError

1.3.6.1.2.1.207

6

2

Warning

VRRPD_V3_PROTO_ERROR

M and MX

Standard SNMP Version 2 Traps

Table 8 provides an overview of the standard SNMPv2 traps supported by the Junos OS. 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.

Table 8: 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 OS.

warmStart

1.3.6.1.6.3.1.1.5.2

Error

SNMPD_TRAP_ WARM_START

All devices running Junos OS.

authenticationFailure

1.3.6.1.6.3.1.1.5.5

Notice

SNMPD_TRAP_ GEN_FAILURE

All devices running Junos OS.
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 OS.

linkUp

1.3.6.1.6.3.1.1.5.4

Info

SNMP_TRAP_ LINK_UP

All devices running Junos OS.
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 OS.

pingTestFailed

1.3.6.1.2.1.80.0.2

Info

SNMP_TRAP_PING_ TEST_FAILED

All devices running Junos OS.

pingTestCompleted

1.3.6.1.2.1.80.0.3

Info

SNMP_TRAP_PING_ TEST_COMPLETED

All devices running Junos OS.
RMON Alarms

RFC 2819a, RMON MIB

fallingAlarm

1.3.6.1.2.1.16.0.1

–

–

All devices running Junos OS.

risingAlarm

1.3.6.1.2.1.16.0.2

–

–

All devices running Junos OS.
Routing Notifications

BGP 4 MIB

bgpEstablished

1.3.6.1.2.1.15.7.1

–

–

All devices running Junos OS.

bgpBackwardTransition

1.3.6.1.2.1.15.7.2

–

–

All devices running Junos OS.

OSPF Trap MIB

ospfVirtIfStateChange

1.3.6.1.2.1.14.16.2.1

–

–

All devices running Junos OS.

ospfNbrStateChange

1.3.6.1.2.1.14.16.2.2

–

–

All devices running Junos OS.

ospfVirtNbrStateChange

1.3.6.1.2.1.14.16.2.3

–

–

All devices running Junos OS.

ospfIfConfigError

1.3.6.1.2.1.14.16.2.4

–

–

All devices running Junos OS.

ospfVirtIfConfigError

1.3.6.1.2.1.14.16.2.5

–

–

All devices running Junos OS.

ospfIfAuthFailure

1.3.6.1.2.1.14.16.2.6

–

–

All devices running Junos OS.

ospfVirtIfAuthFailure

1.3.6.1.2.1.14.16.2.7

–

–

All devices running Junos OS.

ospfIfRxBadPacket

1.3.6.1.2.1.14.16.2.8

–

–

All devices running Junos OS.

ospfVirtIfRxBadPacket

1.3.6.1.2.1.14.16.2.9

–

–

All devices running Junos OS.

ospfTxRetransmit

1.3.6.1.2.1.14.16.2.10

–

–

All devices running Junos OS.

ospfVirtIfTxRetransmit

1.3.6.1.2.1.14.16.2.11

–

–

All devices running Junos OS.

ospfMaxAgeLsa

1.3.6.1.2.1.14.16.2.13

–

–

All devices running Junos OS.

ospfIfStateChange

1.3.6.1.2.1.14.16.2.16

–

–

All devices running Junos OS.
MPLS Notifications

RFC 3812, Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base

mplsTunnelUp

mplsTunnelDown

mplsTunnelRerouted

mplsTunnelReoptimized

Entity State MIB Notifications

RFC 4268, Entity State MIB

entStateOperEnabled

1.3.6.1.2.1.131.0.1

Notice

CHASSISD_SNMP_TRAP3

MX240, MX480, and MX960

entStateOperDisabled

1.3.6.1.2.1.131.0.2

Notice

CHASSISD_SNMP_TRAP3

MX240, MX480, and MX960
L3VPN Notifications

RFC 4382, MPLS/BGP Layer 3 Virtual Private Network (VPN)

mplsL3VpnVrfUp

mplsL3VpnVrfDown

mplsL3VpnVrf RouteMidThresh Exceeded

mplsL3VpnVrf NumVrfRouteMax ThreshExceeded

mplsL3VpnNum VrfRouteMax ThreshCleared

VRRP Notifications

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 OS.

vrrpTrapAuthFailure

1.3.6.1.2.1.68.0.2

Warning

VRRPD_AUTH_ FAILURE_ TRAP

All devices running Junos OS.

RFC 6527, Definitions of Managed Objects for the Virtual Router Redundancy Protocol Version 3 (VRRPv3)

vrrpv3NewMaster

1.3.6.1.2.1.207.0.1

Warning

VRRPD_NEW_MASTER

M and MX

vrrpv3ProtoError

1.3.6.1.2.1.207.0.2

Warning

VRRPD_V3_PROTO_ERROR

M and MX

See Also

Customized SNMP MIBs for Syslog Traps

SNMP syslog traps are alert messages sent from a remote SNMP-enabled device to a central collector notifying you of a component failure or when critical resources are out of configurable limits. This information is captured in a Management Information Base (MIB). The Juniper Networks enterprise-specific System Log MIB enables notification of an SNMP trap-based application when an important system log message occurs. The MIB is defined to map the syslog entry to the generic jnxSyslogTrap OID.

The jnxSyslogTrap OID is a trap based on the logs generated in the syslog. The Event process (eventd) monitors syslog and, based on the event policy raise-trap configuration statement for syslog events, sends all syslog events into one generic syslog-defined trap MIB, which is jnxSyslogTrap.

Using one generic MIB OID is inconvenient for customers who want to process syslog trap OID values to discover specific events because it is impossible to distinguish alarms having the same OID. But as of Junos OS Release 18.3R1, you can map a custom OID to a particular log and load it on the device dynamically.

The benefit of this feature is that because there is a way to assign specific OIDs to different types of syslog events, you can now effectively monitor for each different type of syslog event.

Overview of Custom SNMP MIBs

To create a custom SNMP MIB for a syslog trap, you must complete the following tasks:

  • Write the custom MIB.

  • Convert the MIB file to YANG format and copy the YANG file to the device.

  • Load the YANG file onto the device.

The following sections overview these steps.

Write the MIB File

Before you can map a particular log with a custom OID, you must write a custom MIB. To avoid collisions, you must define your MIB objects and traps only under the reserved roots shown in Table 9.

Table 9: MIB Roots for Custom MIB Modules

Root

Description

OID

.iso.org.dod.internet.private.enterprises.juniperMIB.jnxMibs.jnxCustomMibRoot

Custom MIB module

.1.3.6.1.4.1.2636.3.86

.iso.org.dod.internet.private.enterprises.juniperMIB.jnxTraps.jnxCustomSyslogNotifications

Custom trap notification

.1.3.6.1.4.1.2636.4.30

Convert to a YANG File

Before loading your MIB definition onto the device, you must convert the MIB file to YANG format. The recommended way to covert the MIB file to YANG is to use the smidump v0.5.0 tool. The smidump tool is an open source application which can be installed on your laptop (see https://www.ibr.cs.tu-bs.de/projects/libsmi/smidump.html).

Once the file is in YANG format, you must copy it to the device. Then, using a CLI command, you load the into the SNMP process (snmpd). A corresponding JSON file is then generated, which snmpd parses and from it builds the database of the OID hierarchy. If some unknown tag is found, snmpd returns the appropriate error message.

CLI Commands to Use for Managing YANG Files

To load the YANG module into snmpd, use the snmp option with the request system yang add command:

The yang-filename includes the absolute path.

Note:

In order to run the request system yang add command, you must have super-user access.

There are two other commands for managing YANG files on devices: show system yang package and request system yang delete.

See Also

Define a Custom MIB for a Syslog Trap

In this procedure, we use the following example files:

  • MIB file to convert

  • output

Note:

Although YANG can be written manually by referring to the example YANG provided in this documentation, we recommend you convert the MIB to YANG format using the smidump tool v0.5.0.

To define a custom MIB for a syslog trap:

  1. Load your MIB onto the network management system (NMS) and check if there are any errors.
  2. Invoke the smidump tool using the following command, where dependency-mib, input-custom-mib-file, and YANG-MODULE-NAME are variables for specific filenames:

    For example:

    As output, you will get the converted YANG file JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang.

    Notice that the input custom MIB file mib-jnx-example-custom-syslog.txt is dependent on SNMPv2-SMI, JUNIPER-SMI, and IF-MIB. But since SNMPv2-SMI and IF-MIB are standard MIBs, their definitions are already present in smidump. So, the only dependent MIB file required is mib-jnx-smi.txt, which has module JUNIPER-SMI definitions.

  3. Copy the file JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang to any path on the device, and copy all the dependent YANG files to the device at the following path: /opt/lib/python2.7/site-packages/pyang/modules.
    Note:

    You must convert all the dependent MIBs to YANG files and copy to these to the device.

    Following are some of the standard MIBs that have been converted to YANG modules and are present in the above path: IANAifType-MIB.yang, ietf-yang-types.yang, ietf-inet-types.yang, IF-MIB.yang, JUNIPER-SMI.yang, SNMPv2-TC.yang.

  4. Using the CLI, load the YANG modules into snmpd using this command:

    For example:

    The YANG module is converted to JSON format and goes to snmpd for parsing and creating the internal database.

  5. To verify the trap based on the syslog with the newly added trap definitions is working, spoof (mimic) the trap. You can do this either using the CLI or an event policy. The following is an example of spoofing the trap using the CLI.

mib-jnx-example-custom-syslog.txt

JUNIPER-EXAMPLE-CUSTOM-SYSLOG-MIB.yang

Limitations of Using Custom SNMP Traps

Be careful to write the event scripts in such a way that they won’t trigger traps for frequently occurring syslogs. This practice avoids introducing more load on the device.

If you add an object whose access type is readonly or readwrite, that object will not be available for polling in snmp polling operations such as snmpget or snmpwalk; it will be treated as access type notifyonly. This is because this feature is for adding dynamic TRAP OID definitions to the device so that customer can write scripts to send custom traps for each syslog. Access types readonly and readwrite are for snmp polling, whereas notifyonly is for traps.

For custom MIBs, the definition of a custom table is not supported. If you want to send a trap that has a table object as a varbind, use the already defined table in Junos MIBs rather than defining a custom table in your custom MIB.

The YANG file needs to be loaded on all the chassis nodes and Routing Engines separately. The request system yang add command does not automatically copy it to backup Routing Engine.

Example Custom Syslog Trap

This example custom syslog trap illustrates a use case in which the operator wants to receive traps when either of the following occur:

  • A user enters the configuration mode in the CLI (event defined as ui_dbase_login_event)

  • A user does a commit (event defined as ui_commit)

Before the custom syslog trap feature was supported, the only way to do this was to use jnxSyslogTrap, which has a fixed OID, for both events. With the custom syslog trap feature, you can now generate traps that have custom defined OIDs.

To define a custom syslog trap:

  1. Use the sample file provided and convert it to JUNIPER-EXAMPLE-CUSTOM-SYSLOIG-MIB.yang .
  2. Copy the YANG file onto your device.
  3. Load the SNMP YANG file.
  4. Copy the slax script to /var/db/scripts/event to spoof the trap .

    For ui_dbase_login_event, you will configure the enteredConfigMode trap which has the username varbind.

    For ui_commit, you will configure the configCommitted trap which has the username command an comment as three varbinds.

  5. Configure the trap:
  6. Enable snmpd traceoptions and trap target to verify the traps that are sent.
  7. Verify trap is working.

Sample MIB file

Sample YANG Converted File

slax Script cutom_trap.slax (in /var/db/scripts/event)

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
20.1R1
Starting in Junos OS Release 20.1, after graceful routing engine switchover (GRES), the new primary Routing Engine sends a single warmStart notification.