Config Router

You are here: Home / Juniper / CHASSISD_VOLTAGE_READ_FAILED

CHASSISD_VOLTAGE_READ_FAILED

by

The CHASSISD_VOLTAGE_READ_FAILED message is reported into the system message file whenever the chassis control process (chassisd) is not able to read voltage data from a Field Replaceable Unit (FRU). This article documents an approach to troubleshoot this problem.

The problem related to this syslog message is described in the following sections:

The CHASSISD_VOLTAGE_READ_FAILED message is reported into the system message file whenever the chassis control process (chassisd) is not able to read voltage data from a Field Replaceable Unit (FRU).

When the chassis control process (chassisd) is not able to read voltage data from a FRU it generates these messages.
Below are examples of these messages. The FRU for which the process could not get the voltage information is listed in the message.

chassisd[7734]: CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from PEM 1 (group 10, address 40, channel 0)

chassisd[4657]: CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from PEM 0 (group 2, address 40, channel 0)

CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from PEM 0 (group 14, address 42, channel 7)

chassisd[5230]: %DAEMON-3-CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from FPC 0 (group 16, address 53, channel 3)

chassisd[3697]: CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from FPC 4 (group 20, address 53, channel 3)
craftd[3699]: Minor alarm set, FPC 4 Volt Sensor Fail

chassisd[1343]:CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from FPC 5 (group 23, address 53, channel 14)

chassisd[1011]: CHASSISD_VOLTAGE_READ_FAILED: Unable to read voltage from FPC 9 (group 27, address 53, channel 3)
alarmd[1012]: Alarm set: FPC color=YELLOW, class=CHASSIS, reason=FPC 9 Volt Sensor Fail

The failure to read the voltage information from an FRU can be due to hardware failure on the FRU, a faulty connection between the midplane and the FRU or a fault in the slot Rev.

  • Review the message to determine the FRU that may be faulty.
  • During a maintenance window, reseat the affected FRU.
  • If the messages no longer occur, then the messages were due to a faulty connection.
  • If the messages continue, swap the FRU with a similar FRU in a different slot.
  • If the messages follow the FRU, then the FRU has failed. If the messages stay with the slot, then the slot is faulty.

If the messages were due to a faulty connection, monitor the router for a reoccurrence of the issue.