The chassis process (chassisd) could not power up the indicated component (FRU for example FPC) because the Field Replaceable Unit (FRU) did not respond.
The chassisd could not power up the FRU component and the FRU would not respond, causing the CHASSISD_POWER_CHECK message.
Log messages below indicate that the FPC in slot 2 is not powering up, stating that the PEM in slot 1 is not allowing power to the FPC in slot 2. It was initially thought that the PEM was the problem, but with redundant PEMs, it is not likely going to be the PEM that is the problem. With further research, it was determined that the chassis backplane was the problem. When researching this error message, it is best to review the associated messages in the show log messages command output and the corresponding time frame in the show log chassisd command output to help determine the root cause of the issue. Below is an example of messages displayed in show log messages: Note the RED alarms and "Hard Errors" for FPC 2. chassisd[4616]: %DAEMON-3-CHASSISD_POWER_CHECK: FPC 2 not powering up alarmd[4617]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 2 Hard errors chassisd[4616]: %DAEMON-5-CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Failed (jnxFruContentsIndex 7, jnxFruL1Index 3, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: E-FPC Type 3 @ 2/*/*, jnxFruType 3, jnxFruSlot 3) craftd[4618]: %DAEMON-4: Major alarm set, FPC 2 Hard errors chassisd[4616]: %DAEMON-3-CHASSISD_I2C_IO_FAILURE: pem_read_status: PEM 1 i2c_write failed for group 15 at address 0x38 alarmd[4617]: %DAEMON-4: Alarm set: Pwr supply color=YELLOW, class=CHASSIS, reason=PEM 1 Temp Sensor Failed craftd[4618]: %DAEMON-4: Minor alarm set, PEM 1 Temp Sensor Failed Below is an example of messages displayed in show log chassisd: Note: Observe that CHASSISD_POWER_CHECK is showing FPC 2 not powering up. CHASSISD_PEM_INPUT_BAD: status failure for power supply 1 (status bits: 0x9d); check circuit breaker PEM 1 temp sensor not ok, status 0x8 failed 3 times CHASSISD_I2C_IO_FAILURE: pem_read_status: PEM 1 i2c_write failed for group 15 at address 0x38 PEM 1 temp sensor not ok, status 0x8 failed 4 times CHASSISD_POWER_CHECK: FPC 2 not powering up fpc_offline_now - slot 2, reason: Error, error Unresponsive hwdb: entry for fpc 405 at slot 2 deleted send: red alarm set, device FPC 2, reason FPC 2 Hard errors Below is an example of the output of show chassis fpc. Note that the FPC in slot 2 is showing offline: ---Unresponsive---. Slot State (C) Total Interrupt DRAM (MB) Heap Buffer 0 Empty 1 Empty 2 Offline ---Unresponsive--- 3 Online 30 1 0 128 5 54 4 Online 31 1 0 128 5 52 5 Empty
Log messages below indicate that the FPC in slot 2 is not powering up, stating that the PEM in slot 1 is not allowing power to the FPC in slot 2. It was initially thought that the PEM was the problem, but with redundant PEMs, it is not likely going to be the PEM that is the problem.
With further research, it was determined that the chassis backplane was the problem. When researching this error message, it is best to review the associated messages in the show log messages command output and the corresponding time frame in the show log chassisd command output to help determine the root cause of the issue.
show log messages
show log chassisd
Below is an example of messages displayed in show log messages: Note the RED alarms and "Hard Errors" for FPC 2.
chassisd[4616]: %DAEMON-3-CHASSISD_POWER_CHECK: FPC 2 not powering up alarmd[4617]: %DAEMON-4: Alarm set: FPC color=RED, class=CHASSIS, reason=FPC 2 Hard errors chassisd[4616]: %DAEMON-5-CHASSISD_SNMP_TRAP7: SNMP trap generated: Fru Failed (jnxFruContentsIndex 7, jnxFruL1Index 3, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC: E-FPC Type 3 @ 2/*/*, jnxFruType 3, jnxFruSlot 3) craftd[4618]: %DAEMON-4: Major alarm set, FPC 2 Hard errors chassisd[4616]: %DAEMON-3-CHASSISD_I2C_IO_FAILURE: pem_read_status: PEM 1 i2c_write failed for group 15 at address 0x38 alarmd[4617]: %DAEMON-4: Alarm set: Pwr supply color=YELLOW, class=CHASSIS, reason=PEM 1 Temp Sensor Failed craftd[4618]: %DAEMON-4: Minor alarm set, PEM 1 Temp Sensor Failed
Below is an example of messages displayed in show log chassisd: Note: Observe that CHASSISD_POWER_CHECK is showing FPC 2 not powering up.
CHASSISD_PEM_INPUT_BAD: status failure for power supply 1 (status bits: 0x9d); check circuit breaker PEM 1 temp sensor not ok, status 0x8 failed 3 times CHASSISD_I2C_IO_FAILURE: pem_read_status: PEM 1 i2c_write failed for group 15 at address 0x38 PEM 1 temp sensor not ok, status 0x8 failed 4 times CHASSISD_POWER_CHECK: FPC 2 not powering up fpc_offline_now - slot 2, reason: Error, error Unresponsive hwdb: entry for fpc 405 at slot 2 deleted send: red alarm set, device FPC 2, reason FPC 2 Hard errors
Below is an example of the output of show chassis fpc. Note that the FPC in slot 2 is showing offline: ---Unresponsive---.
show chassis fpc
Slot State (C) Total Interrupt DRAM (MB) Heap Buffer 0 Empty 1 Empty 2 Offline ---Unresponsive--- 3 Online 30 1 0 128 5 54 4 Online 31 1 0 128 5 52 5 Empty
CHASSISD_POWER_CHECK can be caused by a faulty chassis slot of the FRU, faulty FRU component, or faulty PEM (Power Entry Module).
CONFIRM CAUSES:
CHASSISD_POWER_CHECK is caused from the chassis not powering up the FRU (Field Replaceable Unit). When researching this error message, it is best to review the associated messages in the show log messages command output and the corresponding time frame in the show log chassisd command output to help determine the root cause of the issue. Check the Chassis FRU slots for bent pins or burn marks that could possibly show a problem with the component or chassis slot. Examine the show chassis environment command output for a "check or offline" status for the problem FRU component.
CHASSISD_POWER_CHECK is caused from the chassis not powering up the FRU (Field Replaceable Unit).
When researching this error message, it is best to review the associated messages in the show log messages command output and the corresponding time frame in the show log chassisd command output to help determine the root cause of the issue.
Check the Chassis FRU slots for bent pins or burn marks that could possibly show a problem with the component or chassis slot.
Examine the show chassis environment command output for a "check or offline" status for the problem FRU component.
If possible, swap the FRU component to another chassis slot to see if it will power up. If it powers up, the problem is with the chassis; else most likely it is with the FRU.Check the associated error messages in the show log messages command output and the corresponding time frame in the show log chassisd command output for a correct analysis.Check the FRU chassis slot for bent pins or burn marks where the FRU component connects with the pins. For further troubleshooting, contact Support.
2022-10-17: Article reviewed for accuracy; no changes required; article valid and relevant
2024-09-16: Article modified to reflect current information with regard to troubleshooting the syslog message
[KB36604- [MX] MPC 5E card does not power up [juniper.net]