The alarm process (alarmd) was unable to connect to the chassis process (chassisd).
The problem related to this syslog message is described in the following sections:
The CONNECTION_CHASSISD_FAIL is logged every 30 failed attempts by the alarm process to connect to the chassis process.
When a CONNECTION_CHASSISD_FAIL event occurs, a syslog entry is created similar to the following:
CONNECTION_CHASSISD_FAIL: after 30 attempts chassisd connect returned error: Connection refused
The cause may be due to a software error or hardware failure. It might also be caused by faulty cabling between fabric ports on a multi-chassis platform , i.e. an SRX Chassis Cluster or TX Matrix (Plus).
Examine the following outputs to help determine the cause of this message:
show log messages
show log chassisd
Look for any related events that occurred with or just before the CONNECTION_CHASSISD_FAIL message.
The kind of conditions that cause this message often come with core-dumps. Also, review the output of show system core-dumps that were generated at or near the time of the message.