This KB provides details of the error log "CHASSISD_FM_ERROR".

Below log messages were observed:
 

Mar  4 02:52:57.155  <hostname> chassisd[8482]: CHASSISD_FM_ERROR: fm_qfx10_ev_sib_state_handler: SIB got link errors (SIB#1, Packet Forwarding Engine 0 on FPC 2)
Mar  4 02:52:57.155  <hostname> chassisd[8482]: CHASSISD_FM_ERROR: fm_qfx10_ev_sib_state_handler: SIB got link errors (SIB#5, Packet Forwarding Engine 0 on FPC 2)
Mar  4 02:52:58.155  <hostname> chassisd[8482]: CHASSISD_FM_ERROR: fm_qfx10_ev_sib_state_handler: SIB got link errors (SIB#2, Packet Forwarding Engine 0 on FPC 2)
Mar  4 02:53:08.166  <hostname> chassisd[8482]: CHASSISD_FM_ERROR: fm_qfx10_ev_sib_state_handler: SIB got link errors (SIB#3, Packet Forwarding Engine 0 on FPC 2)
Mar  4 02:53:13.170  <hostname> chassisd[8482]: CHASSISD_FM_ERROR: fm_qfx10_ev_sib_state_handler: SIB got link errors (SIB#4, Packet Forwarding Engine 0 on FPC 2)

Under chassisd logs:

Mar 4 02:53:39 rcv: ch_ipc_dispatch() ETIMEDOUT TCP/IP pipe ipc read for args 0xa6f11a0 pipe 0x9cb3a60, fru FPC 2 errno 60

Mar 4 02:53:39 rcv: ch_ipc_dispatch() ipc pipe read error for args 0xa6f11a0 pipe 0x9cb3a60, fru FPC 2 errno 0

Mar 4 02:53:39 ch_ipc_dispatch: fru FPC offline_reason = Bad Voltage

Mar 4 02:53:39 ch_connection_shutdown: Destroying the IPC pipe

Mar 4 02:53:39 FPC2 fpc_tvp_chassis_disconnect.

Mar 4 02:53:39 pic detach portinfo, pic 0 fpc 2 

Mar 4 02:53:39 fpc_disconnect_generic: fpc 2 state Offline cargs 0xa6f11a0 clean_shutdown 0, offline_reason=Bad Voltage

Mar 4 02:53:39 -- FPC 2, last request 132, state Offline

Mar 4 02:53:39 CHASSISD_IPC_CONNECTION_DROPPED: Dropped IPC connection for FPC 2

Logs from RSI:

Slot 2 information:
 State                Offline
 Reason               Bad Voltage

These errors were due to bad FPC. In this case it was FPC2.

It is hardware problem with FPC and faulty FPC needs to be RMAed.