This article explains the reason why " jnxPowerSupplyFailure " and " jnxPowerSupplyOK " SNMP traps are generated by the new primary RE in Junos OS 14.1 and 14.2 releases after a GRES switchover.
In Junos OS 14.1 and 14.2 releases, the " jnxPowerSupplyFailure( Power Supply failed) " and " jnxPowerSupplyOK( Power Supply OK) " SNMP traps with "FRU Online" and "FRU power on" traps are reported upon a GRES switchover.
--- JUNOS 14.1R9.1 built 2018-02-21 18:40:21 UTC {MASTER} User@mx-re0> show chassis hardware Hardware inventory: Item Version Part number Serial number Description Chassis JN11F437BAFC MX240 Midplane REV 07 760-021404 ACAB3861 MX240 Backplane FPM Board REV 05 760-021392 ZY9552 Front Panel Display PEM 0 Rev 05 740-027736 QCS1405T04V DC 2.4kW Power Entry Module PEM 2 Rev 05 740-027736 QCS1231T0ZD DC 2.4kW Power Entry Module Routing Engine 0 REV 13 740-031116 9016091055 RE-S-1800x4 Routing Engine 1 REV 05 740-051822 9016250327 RE-S-1800x4 CB 0 REV 07 750-062577 CAJK9554 Enhanced MX SCB CB 1 REV 05 750-062577 CAJL4793 Enhanced MX SCB FPC 1 REV 09 750-038492 CAAD8781 MPCE Type 2 3D EQ CPU REV 04 711-038484 CAAD8328 MPCE PMB 2G MIC 0 REV 30 750-028392 CACV7185 3D 20x 1GE(LAN) SFP PIC 0 BUILTIN BUILTIN 10x 1GE(LAN) SFP PIC 1 BUILTIN BUILTIN 10x 1GE(LAN) SFP QXM 0 REV 06 711-028408 CAAD8399 MPC QXM QXM 1 REV 06 711-028408 CAAD8439 MPC QXM FPC 2 REV 22 750-038491 CAGA9187 MPCE Type 2 3D CPU REV 07 711-038484 CAFT5955 MPCE PMB 2G MIC 0 REV 32 750-028392 CAES8724 3D 20x 1GE(LAN) SFP PIC 0 BUILTIN BUILTIN 10x 1GE(LAN) SFP PIC 1 BUILTIN BUILTIN 10x 1GE(LAN) SFP Fan Tray 0 REV 01 710-030216 CAAA8201 Enhanced Fan Tray
{MASTER} User@mx-re0> monitor start messages |match "SNMP trap generated" --- JUNOS 14.1R9.1 built 2018-02-21 18:40:21 UTC {BACKUP} User@mx-re1> monitor start messages |match "SNMP trap generated"
{MASTER} User@mx-re0> request chassis routing-engine master switch Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Complete. The other routing engine becomes the master. {BACKUP} User@mx-re0> Sep 6 11:16:28.936 mx-re0 chassisd[2884]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 1, jnxFruType 6, jnxFruSlot 1) {BACKUP} User@mx-re1> *** messages *** Sep 6 11:16:17.353 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP10: SNMP trap generated: redundancy switchover (jnxRedundancyContentsIndex 9, jnxRedundancyL1Index 2, jnxRedundancyL2Index 0, jnxRedundancyL3Index 0, jnxRedundancyDescr Routing Engine 1, jnxRedundancyConfig 3, jnxRedundancyState 2, jnxRedundancySwitchoverCount 1, jnxRedundancySwitchoverTime 15231, jnxRedundancySwitchoverReason 3) Sep 6 11:16:17.359 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 0, jnxFruType 6, jnxFruSlot 0) Sep 6 11:16:18.174 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D EQ @ 1/*/*, jnxFruType 3, jnxFruSlot 1) Sep 6 11:16:18.381 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 3, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D @ 2/*/*, jnxFruType 3, jnxFruSlot 2) Sep 6 11:16:19.321 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN) SFP @ 1/0/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0) Sep 6 11:16:19.367 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 3, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN) SFP @ 2/0/*, jnxFruType 11, jnxFruSlot 2, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0) Sep 6 11:16:48.804 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr PEM 0, jnxOperatingState/Temp 6) Sep 6 11:16:48.804 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply failed (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr PEM 2, jnxOperatingState/Temp 6) Sep 6 11:17:03.805 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply OK (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr PEM 0, jnxOperatingState/Temp 2) Sep 6 11:17:03.806 mx-re1 chassisd[1909]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply OK (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr PEM 2, jnxOperatingState/Temp 2)
However, Junos OS 15.1 and subsequent releases show a different behavior. In Junos OS 15.1R5.5 , both " Power Supply failed "/" Power Supply OK " SNMP traps are not generated on the new primary with GRES switchover.
--- JUNOS 15.1R5.5 Kernel 64-bit JNPR-10.3-20160927.337663_build {MASTER} User@mx-re0> request chassis routing-engine master switch Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Complete. The other routing engine becomes the master. {BACKUP} User@mx-re0> *** messages *** Sep 6 13:06:38.348 mx-re0 chassisd[10766]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 1, jnxFruType 6, jnxFruSlot 1) --- JUNOS 15.1R5.5 Kernel 64-bit JNPR-10.3-20160927.337663_build {BACKUP} User@mx-re1> *** messages *** Sep 6 13:06:38.353 mx-re1 chassisd[9781]: CHASSISD_SNMP_TRAP10: SNMP trap generated: redundancy switchover (jnxRedundancyContentsIndex 9, jnxRedundancyL1Index 2, jnxRedundancyL2Index 0, jnxRedundancyL3Index 0, jnxRedundancyDescr Routing Engine 1, jnxRedundancyConfig 3, jnxRedundancyState 2, jnxRedundancySwitchoverCount 1, jnxRedundancySwitchoverTime 32466, jnxRedundancySwitchoverReason 3) Sep 6 13:06:38.354 mx-re1 chassisd[9781]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 0, jnxFruType 6, jnxFruSlot 0) Sep 6 13:06:39.121 mx-re1 chassisd[9781]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 3, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D @ 2/*/*, jnxFruType 3, jnxFruSlot 2) Sep 6 13:06:39.303 mx-re1 chassisd[9781]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D EQ @ 1/*/*, jnxFruType 3, jnxFruSlot 1) Sep 6 13:06:39.678 mx-re1 chassisd[9781]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 3, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN) SFP @ 2/0/*, jnxFruType 11, jnxFruSlot 2, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0) Sep 6 13:06:39.706 mx-re1 chassisd[9781]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN) SFP @ 1/0/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0) {MASTER} user@mx-re1>
On the other hand, in Junos 15.1R6.7 with PR1232885 fix, the " Power Supply OK " SNMP trap is generated on the new primary with GRES switchover. " FRU power on " SNMP trap on CBs is also generated. " Power Supply failed " is no longer raised with GRES switchover in post 15.1 releases.
########## 15.1R6.7 ########## --- JUNOS 15.1R6.7 Kernel 64-bit JNPR-10.3-20170422.348838_build {MASTER} user@mx-re0> request chassis routing-engine master switch Toggle mastership between routing engines ? [yes,no] (no) yes Resolving mastership... Complete. The other routing engine becomes the master. {BACKUP} User@mx-re0> Sep 6 13:28:08.012 mx-re0 chassisd[14368]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 1, jnxFruType 6, jnxFruSlot 1) --- JUNOS 15.1R6.7 Kernel 64-bit JNPR-10.3-20170422.348838_build {BACKUP} User@mx-re1> *** messages *** Sep 6 13:27:53.220 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 12, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 0, jnxFruType 5, jnxFruSlot 0, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 15247) Sep 6 13:27:55.027 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 12, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName CB 1, jnxFruType 5, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 15428) Sep 6 13:28:07.988 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP10: SNMP trap generated: redundancy switchover (jnxRedundancyContentsIndex 9, jnxRedundancyL1Index 2, jnxRedundancyL2Index 0, jnxRedundancyL3Index 0, jnxRedundancyDescr Routing Engine 1, jnxRedundancyConfig 3, jnxRedundancyState 2, jnxRedundancySwitchoverCount 1, jnxRedundancySwitchoverTime 16725, jnxRedundancySwitchoverReason 3) Sep 6 13:28:07.989 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 9, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName Routing Engine 0, jnxFruType 6, jnxFruSlot 0) Sep 6 13:28:08.712 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 3, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D @ 2/*/*, jnxFruType 3, jnxFruSlot 2) Sep 6 13:28:08.929 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Online (jnxFruContentsIndex 7, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: MPCE Type 2 3D EQ @ 1/*/*, jnxFruType 3, jnxFruSlot 1) Sep 6 13:28:09.252 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 3, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN) SFP @ 2/0/*, jnxFruType 11, jnxFruSlot 2, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0) Sep 6 13:28:09.272 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on (jnxFruContentsIndex 20, jnxFruL1Index 2, jnxFruL2Index 1, jnxFruL3Index 0, jnxFruName MIC: 3D 20x 1GE(LAN) SFP @ 1/0/*, jnxFruType 11, jnxFruSlot 1, jnxFruOfflineReason 2, jnxFruLastPowerOff 0, jnxFruLastPowerOn 0) Sep 6 13:29:09.858 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply OK (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr PEM 0, jnxOperatingState/Temp 2) Sep 6 13:29:09.859 mx-re1 chassisd[13272]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply OK (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr PEM 2, jnxOperatingState/Temp 2)
{MASTER} User@mx-re1>
In Junos OS 14.1 and 14.2 releases, both " Power Supply failed " and " Power Supply OK " SNMP traps are generated with a GRES switchover. This behavior is per design. During mastership switchover, there is a 12-18 second gap during which the new primary RE will not be able to access the power device behind the mid-plane. Therefore, there are SNMP traps and alarms being generated, but the alarms get cleared after the GRES gap. Although, the " Power Supply failed " SNMP trap is reported in this transient period, it does not mean that the PSMs are faulty. " Power Supply OK " snmp trap will be generated immediately.
However, post Junos OS 15.1 shows a different behavior. Before PR1232885 , both " Power Supply failed " and " Power Supply OK " SNMP traps are not generated on the new master with a GRES switchover. Post PR1232885 , " Power Supply OK " and " FRU power on " SNMP traps on CBs are raised. The " Power Supply failed " SNMP trap is no longer generated with GRES switchover in post 15.1 releases.
2021-03-25: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives.