The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd).
The problem related to this syslog message is described in the following sections:
When an L2CPD_PPM_WRITE_ERROR event occurs, a message similar to the following is reported:
shutting down chassisd connection: chassisd ipc pipe read error
L2CPD_PPM_WRITE_ERROR: ppm_send: write error on pipe to ppmd (Broken pipe)
The messages are triggered any time the L2CPD is abruptly shut down, such as a hardware reset, RDP crash, or restart of the L2CPD process.
Examine the following output to help determine the cause of this message:
show log messages
Look for any related events that occurred at or just before the L2CPD_PPM_WRITE_ERROR message. Then check to see if there are any current alarms in the show chassis alarms output. You also want to check to see if any core files were generated at the time of the L2CPD_ASSERT error message. This can be found in the output of “show system core-dumps”. It will look like this:
show system core-dumps
-rw-rw---- 1 root wheel 25960448 Oct 26 14:41 /var/tmp/l2cpd.core-tarball.0.tgz
/var/crash/kernel.*: No such file or directory
/tftpboot/corefiles/*core*: No such file or directory
If a core file was generated, a case will need to be opened with your technical support representative to investigate the issue, and the core file will need to be uploaded to the Juniper FTP site under that case for analysis.
Perform these steps:
- If the Layer 2 Control Protocol process daemon was not brought down as part of a restart or a planned event, open a case with your technical support representative to investigate this issue further.