This article will explain the LCMD message "Power failure recorded for FPC <>, sending notification to CHASD".

Power failure recorded for FPC <>: This explicitly states that the system has detected a loss of power to the FPC. This could be due to various reasons, such as:

• Power supply failure: Issues with the chassis's power supply units (PSUs).
• Faulty power cables or connectors: Problems with the connections between the PSUs and the FPC.
• Transient/hardware failure on FPC.

Sending notification to CHASD: This indicates that the system is generating a notification about the power failure event. CHASD (Chassis Daemon) is a system process responsible for managing chassis-level events, such as FPC insertions, removals, and power failures.

In most situations, FPC will reboot and the Last Reboot Reason will show as Power On Reset.

vmhost# cat /var/log/lcmd.log

<time> <date> local-node lcmd[8208]: fru_periodics:1299 Initializing resiliency FRU FPC <>
<time> <date> local-node lcmd[8208]: FRU State Change Detected (Name = FRU FPC Id = 14, Slot = <>, OState = 2)
<time> <date> local-node lcmd[8208]: Power failure recorded for FPC <>, sending notification to CHASD
<time> <date> local-node lcmd[8208]: Releasing fru mutex lock before calling Plugin
<time> <date> local-node lcmd[8208]: pvi_opus_ipc_plugin_fru_event_done: Acquiring global lock

Syslog Message:

<time> <date>  user@RE chassisd[22454]: CHASSISD_SNMP_TRAP7: SNMP trap generated: FRU insertion (jnxFruContentsIndex 7, jnxFruL1Index 7, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName FPC @ <>/*/*, jnxFruType 3, jnxFruSlot 6)
<time> <date>  user@RE mosquitto[22511]: Allocated node for mosq : 0x849a00, Client : client-2-re0-NA_event_subscriber-re0, topic : /1000/0/0, max bytes in queue : 10485760, hash_size is 500, hashIndex is 0x961000
<time> <date> user@RE fpc<> logger: Last Reboot Reason:  Power On Reset
<time> <date> user@RE fpc<> logger: Integrity check passed for hash-data-plane.md5.
<time> <date> user@RE fpc<>: Line card linux booted.

1. Verify all PSMs are in good health and the chassis is getting sufficient power.

                            user@re> show chassis power details

1. If the incident occurred only once, suggest physically examining FPC <> for any bending pins and reseating it under a maintenance window.
2. After performing the reseat, please monitor FPC <> for the next 48 hours to ensure stability.