[an error occurred while processing this directive][an error occurred while processing this directive]

Chassis Traps

The chassis-related traps are defined under the jnxTraps and jnxChassisOKtraps branches. For the system logging severity levels for these traps, see .Juniper Networks Enterprise-Specific SNMP Traps .

These traps are defined as follows:

  • Power failure (jnxPowerSupplyFailure)—Sent when the power supply, router circuit breaker, or power circuit fails, or when there is a power outage. When only one of the power supplies has failed, the service impact is minimal. One power supply can provide the necessary power for a fully loaded router. To determine the source of the failure, you must physically inspect the router. This trap is repeated every hour until the power supply is restored.
  • Fan failure (jnxFanFailure)—Sent when the fan fuse blows or when the fan wiring shorts out. When only one fan has failed, there is no service impact. The remaining fans increase speed to compensate. However, you must resolve the problem before another fan fails. This trap is repeated every hour until the fan failure is fixed. To determine the source of the failure, you must physically inspect the router, taking care to check the fuses. See the hardware installation guide for your router model for more information.
  • Overtemperature (jnxOverTemperature)—Sent when several fans fail or the room temperature increases significantly. The service impact of this trap depends on the temperature of the router. In general, the router increases the speed of the fans when any component exceeds a temperature of 55=° C. The fans remain at the higher speed until the temperature decreases below the threshold. In this case, there is no service impact. However, if the temperature exceeds 75° C, the router transmits a warning and automatically shuts down. This scenario creates a significant service impact because the shutdown affects additional routers and equipment. This trap is repeated every minute until the temperature is brought down to normal. To determine the source of the overtemperature problem, you must physically inspect the router to determine whether any fans have failed in the router.
  • Power Supply OK (jnxPowerSupplyOK)—Sent when a power supply recovers from failure.
  • Fan OK (jnxFanOK)—Sent when a fan recovers from failure.
  • Temperature OK (jnxTemperatureOK)—Sent when a chassis component recovers from an overtemperature condition.
  • Redundancy Switchover (jnxRedundancySwitchover)—For certain platforms, such as the M20 or M160, some subsystems, such as the Routing Engine, have a redundant backup unit that can be brought online, manually or automatically, if the main unit malfunctions. The redundancy switchover trap indicates such a change.
  • Field Replaceable Unit Removal (jnxFruRemoval)—Sent when the specified FRU has been removed from the chassis.
  • Field Replaceable Unit Insertion (jnxFruInsertion)—Sent when the specified FRU has been inserted into the chassis.
  • Field Replaceable Unit Power Off (jnxFruPowerOff)—Sent when the specified FRU has been powered off in the chassis.

    The jnxFruPowerOff trap is also sent in the following scenarios:

    • When an FRU that is controlled using inter-process communication (IPC) goes offline or is removed from the chassis. For example, a switch interface board (SIB).
    • When an FRU that does not have a backup unit goes offline or is removed from the chassis. For example, a Flexible PIC Concentrator (FPC).

    Note: When a SONET Clock Generator (SCG) is taken offline, the unit is not powered down. Therefore, jnxFruPowerOff or jnxFruPowerOn traps are not sent when the unit is taken online or offline.

  • Field Replaceable Unit Power On (jnxFruPowerOn)—Sent when the specified FRU has been powered on in the chassis.
  • Field Replaceable Unit Failed (jnxFruFailed)—Sent when the specified FRU has failed in the chassis. Typically, this is due to the FRU not powering up or being unable to load software. FRU replacement may be required.
  • Field Replaceable Unit Offline (jnxFruOffline)—Sent when the specified FRU goes offline. However, when an FRU that does not have a backup unit goes offline, JUNOS Software generates the jnxFruPowerOff trap instead of the jnxFruOffline trap. Typically, a jnxFruOffline trap is generated to inform the backup FRU about the status of the primary FRU so that the backup FRU can take over when the primary FRU goes offline.

    The following are some scenarios when jnxFruOffline traps are generated:

    • When a Packet Forwarding Engine Clock Generator (PCG) goes offline (M40e)
    • When a Sonnet Clock Generator goes offline (T Series)
    • When a Line Card Chassis goes offline (TX4 internet router)
    • When a Routing Engine goes offline.
  • Field Replaceable Unit Online (jnxFruOnline)—Sent when the specified FRU goes online.
  • Field Replaceable Unit Check (jnxFruCheck)—Sent when the specified FRU has encountered operational errors. On M120 and M320 routers, this trap is sent if the revision number for the ATM2 PIC FPGA is less than 8B44(4).
  • Forwarding Engine Board (FEB) Switch Over (jnxFEBSwitchover)—Sent when the specified FEB undergoes a switch over.
  • Hard disk Failure (jnxHardDiskFailed)—Sent when the hard disk in the specified Routing Engine is not operational.
  • Hard disk Missing (jnxHardDiskMissing)—Sent when the hard disk in the specified Routing Engine is missing from the boot device list.

This section contains the following topics:

SNMPv1 Trap Format

The SNMPv1 trap format for the chassis-related traps is described in Table 1. To view the SNMPv1 chassis-related traps, see Juniper Networks Enterprise-Specific SNMP Version 1 Traps .

The column headings describe the SNMPv1 traps format:

  • Trap Name—The name of the trap.
  • Enterprise ID—The identification number of the enterprise-specific trap.
  • Generic Trap Number—The generic trap number field of the SNMP trap PDU. This field is enterpriseSpecific(6) for enterprise-specific traps, other predefined values for standard traps.
  • Specific Trap Number— The specific trap number field of the SNMP trap PDU. For standard traps, this field is zero; for enterprise-specific traps, this field is nonzero as defined in the enterprise-specific MIBs.

    Table 1: SNMP Version 1 Trap Format

    Trap Name

    Enterprise ID

    Generic Trap Number

    Specific Trap Number

    jnxFanFailure

    1.3.6.1.4.1.2636.4.1

    6

    2

    jnxFanOK

    1.3.6.1.4.1.2636.4.2

    6

    2

    jnxFruCheck

    1.3.6.1.4.1.2636.4.1

    6

    12

    jnxFruFailed

    1.3.6.1.4.1.2636.4.1

    6

    9

    jnxFruInsertion

    1.3.6.1.4.1.2636.4.1

    6

    6

    jnxFruOffline

    1.3.6.1.4.1.2636.4.1

    6

    10

    jnxFruOnline

    1.3.6.1.4.1.2636.4.1

    6

    11

    jnxFruPowerOff

    1.3.6.1.4.1.2636.4.1

    6

    7

    jnxFruPowerOn

    1.3.6.1.4.1.2636.4.1

    6

    8

    jnxFruRemoval

    1.3.6.1.4.1.2636.4.1

    6

    5

    jnxOverTemperature

    1.3.6.1.4.1.2636.4.1

    6

    3

    jnxPowerSupplyFailure

    1.3.6.1.4.1.2636.4.1

    6

    1

    jnxPowerSupplyOK

    1.3.6.1.4.1.2636.4.2

    6

    1

    jnxRedundancySwitchover

    1.3.6.1.4.1.2636.4.1

    6

    4

    jnxTemperatureOK

    1.3.6.1.4.1.2636.4.2

    6

    3

SNMPv2 Trap Format

The SNMPv2 trap format for the Chassis MIB traps is described in Table 2.

The column headings describe the SNMPv2 traps format:

  • Trap Name—The name of the trap.
  • snmpTrapOID—The authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2 trap PDU and InformRequest PDU.
  • Description—The JUNOS Software enterprise-specific name of the trap.

    Table 2: SNMP Version 2 Trap Format

    Trap Name

    snmpTrapOID

    Description

    jnxFanFailure

    1.3.6.1.4.1.2636.4.1.2

    The fan fuse has blown or the fan wiring has shorted out. This trap is generated every hour until the fan failure is fixed.

    jnxFanOK

    1.3.6.1.4.1.2636.4.2.2

    The fan has recovered from a failure state.

    jnxFruCheck

    1.3.6.1.4.1.2636.4.1.12

    The FRU has operational errors and has gone into a self-check diagnostic state. The revision number for the ATM2 PIC FPGA on an M120 or M320 router is less than 8B44(4).

    jnxFruInsertion

    1.3.6.1.4.1.2636.4.1.6

    The FRU has been inserted into the chassis.

    jnxFruFailed

    1.3.6.1.4.1.2636.4.1.9

    The FRU has failed in the chassis.

    jnxFruOffline

    1.3.6.1.4.1.2636.4.1.10

    The FRU has gone offline.

    jnxFruOnline

    1.3.6.1.4.1.2636.4.1.11

    The FRU has gone back online.

    jnxFruPowerOff

    1.3.6.1.4.1.2636.4.1.7

    The FRU has been powered off in the chassis.

    jnxFruPowerOn

    1.3.6.1.4.1.2636.4.1.8

    The FRU has been powered on in the chassis.

    jnxFruRemoval

    1.3.6.1.4.1.2636.4.1.5

    The FRU has been removed from the chassis.

    jnxOverTemperature

    1.3.6.1.4.1.2636.4.1.3

    Several fans have failed or the room temperature has increased significantly. This trap is repeated every minute until the temperature is brought down to normal.

    jnxPowerSupplyFailure

    1.3.6.1.4.1.2636.4.1.1

    The power supply, router circuit breaker, or power circuit failed, or there has been a power outage. This trap is generated every hour until the power supply is restored.

    jnxPowerSupplyOK

    1.3.6.1.4.1.2636.4.2.1

    The power supply has recovered from a failure.

    jnxRedundancySwitchover

    1.3.6.1.4.1.2636.4.1.4

    A redundant backup unit that can be brought online, manually or automatically, if the main unit malfunctions.

    jnxTemperatureOK

    1.3.6.1.4.1.2636.4.2.3

    The component sensor has detected an overtemperature condition.


Published: 2010-04-27

[an error occurred while processing this directive]