Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

QFX10008/QFX10016 may report false messages of "Power Supply Input failed"

0

1

Article ID: KB37515 KB Last Updated: 02 Dec 2021Version: 1.0
Summary:

Users may find that the QFX10008 and QFX10016 devices (running releases prior to Junos OS 19.1) are logging the "Power Supply Input failed" syslog message for all Power Supply modules every hour. This article clarifies that the message may be a false one and recommends confirming the message validity by checking the chassisd alarms.

The Junos OS versions in which this problem has been resolved are also given in this article.

Symptoms:

The following messages may be logged:

Jan 17 16:20:52.766  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 0, jnxOperatingState 2)
Jan 17 16:20:52.766  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 0, jnxOperatingState 2)
Jan 17 16:20:52.766  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 2, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 1, jnxOperatingState 2)
Jan 17 16:20:52.766  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 2, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 1, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 2, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 2, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 4, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 3, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 4, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 3, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 5, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 4, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 5, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 4, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 6, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 5, jnxOperatingState 2)
Jan 17 16:20:52.767  border1.sem chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 6, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 5, jnxOperatingState 2)

By the next hour, the same syslog messages of "Power Supply Input failed" may appear again for all PSU modules.

Jan 17 17:20:53.804  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 0, jnxOperatingState 2)
Jan 17 17:20:53.805  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 1, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 0, jnxOperatingState 2)
Jan 17 17:20:53.805  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 2, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 1, jnxOperatingState 2)
Jan 17 17:20:53.805  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 2, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 1, jnxOperatingState 2)
Jan 17 17:20:53.805  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 2, jnxOperatingState 2)
Jan 17 17:20:53.805  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 3, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 2, jnxOperatingState 2)
Jan 17 17:20:53.805  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 4, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 3, jnxOperatingState 2)
Jan 17 17:20:53.806  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 4, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 3, jnxOperatingState 2)
Jan 17 17:20:53.806  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 5, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 4, jnxOperatingState 2)
Jan 17 17:20:53.806  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 5, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 4, jnxOperatingState 2)
Jan 17 17:20:53.806  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 6, jnxContentsL2Index 1, jnxContentsL3Index 0, jnxContentsDescr Power Supply 5, jnxOperatingState 2)
Jan 17 17:20:53.806  jtac-QFX10008-r013 chassisd[5766]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Power Supply Input failed (jnxContentsContainerIndex 2, jnxContentsL1Index 6, jnxContentsL2Index 2, jnxContentsL3Index 0, jnxContentsDescr Power Supply 5, jnxOperatingState 2)
Cause:

This issue can be easily identified because chassisd will report all PSU modules that are having Power Supply Input failure while the entire system is still powered and functioning normally. It can be validated that the reported syslog messages are false alarms by checking the CLI output of show chassis alarms, show chassis power, and show chassis environment pem.

[edit]

root@jtac-QFX10008-r013# run show chassis alarms
No alarms currently active 

root@jtac-QFX10008-r013# run show chassis power    

PEM 0:
  State:     Online
  Capacity:  2700 W (maximum 2700 W)
  DC output: 468 W (zone 0, 39 A at 12 V, 17% of capacity)

PEM 1:
  State:     Online
  Capacity:  2700 W (maximum 2700 W)
  DC output: 456 W (zone 0, 38 A at 12 V, 16% of capacity)

PEM 2:
  State:     Online
  Capacity:  2700 W (maximum 2700 W)
  DC output: 468 W (zone 0, 39 A at 12 V, 17% of capacity)

PEM 3:
  State:     Online
  Capacity:  2700 W (maximum 2700 W)
  DC output: 444 W (zone 0, 37 A at 12 V, 16% of capacity)

PEM 4:
  State:     Online
  Capacity:  2700 W (maximum 2700 W)   
  DC output: 468 W (zone 0, 39 A at 12 V, 17% of capacity)

PEM 5:
 State:     Online
  Capacity:  2700 W (maximum 2700 W)
  DC output: 468 W (zone 0, 39 A at 12 V, 17% of capacity)

System:
  Zone 0:
      Capacity:          16200 W (maximum 16200 W)
      Allocated power:   6210 W (9990 W remaining)
      Actual usage:      2772 W
  Total system capacity: 16200 W (maximum 16200 W)
  Total remaining power: 9990 W

[edit]
root@jtac-QFX10008-r013# run show chassis environment pem
PEM 0 status:
  State                      Online
  Airflow                    Front to Back                          
  Temperature                OK   29 degrees C / 84 degrees F       
  Firmware version           0x36                                   
  Fan 0                      5700 RPM                               
  DC Output           Voltage(V) Current(A)  Power(W)  Load(%)
                        12.00       39            468      17    
PEM 1 status:
  State                      Online
  Airflow                    Front to Back                          
  Temperature                OK   39 degrees C / 102 degrees F      
  Firmware version           0x36                                   
  Fan 0                      5760 RPM                               
  DC Output           Voltage(V) Current(A)  Power(W)  Load(%)
                        12.00       38            456      16    
PEM 2 status:
  State                      Online
  Airflow                    Front to Back                          
  Temperature                OK   38 degrees C / 100 degrees F      
  Firmware version           0x36                                   
  Fan 0                      5700 RPM                               
  DC Output           Voltage(V) Current(A)  Power(W)  Load(%)
                        12.00       39            468      17    
PEM 3 status:
  State                      Online
  Airflow                    Front to Back                          
  Temperature                OK   34 degrees C / 93 degrees F       
  Firmware version           0x36                                   
  Fan 0                      5700 RPM                               
  DC Output           Voltage(V) Current(A)  Power(W)  Load(%)
                        12.00       37            444      16    
PEM 4 status:
  State                      Online
  Airflow                    Front to Back                          
  Temperature                OK   35 degrees C / 95 degrees F       
  Firmware version           0x36                                   
  Fan 0                      5760 RPM                               
  DC Output           Voltage(V) Current(A)  Power(W)  Load(%)
                        12.00       39            468      17    
PEM 5 status:
  State                      Online
  Airflow                    Front to Back                          
  Temperature                OK   32 degrees C / 89 degrees F       
  Firmware version           0x36                                   
  Fan 0                      5700 RPM                               
  DC Output           Voltage(V) Current(A)  Power(W)  Load(%)
                        12.00       39            468      17     
Solution:

This kind of syslog message about PSU INPUT failure for all PEMs does not necessarily indicate an actual problem with the Power Supply system.

On devices running releases prior to Junos OS Release 19.1, the message may be logged when the input feed status is not sent from lcmd to chassisd. The Simple Network Management Protocol (SNMP) checks for FRU failure on an hourly basis. Since chassisd does not have the status of input feeds in this case, it sends an SNMP trap for all PEMS. However, there is no actual hardware related issue with PEMs in this case.

This issue has been fixed in Junos OS Releases 19.1R3, 19.2R2, 19.3R3, 19.4R2, 20.1R1, and later. It is recommended that users upgrade to the Junos OS versions in which this problem has been resolved for a permanent solution. 

Meanwhile, as a workaround, users may refer to KB9382 - [Junos Platform] Example - How to prevent certain syslog messages from being written to the log file to prevent such syslog messages from being written to the log file. When any of the Power Supply modules have an actual issue, the chassisd process would raise chassis alarms for notification. 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search