The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. The l2cpd process with the indicated executable name and process ID (PID) terminated because the indicated test failed at the indicated line number in the indicated source file. The process created a diagnostic core file for analysis by technical support personnel.
The problem related to this syslog message is described in the following sections:
When an L2CPD_ASSERT event occurs, a message similar to the following is reported:
L2CPD_ASSERT: Assertion failed for <executable-name> (PID <pid>) at line <line-number> in file '<source-filename>': <message>
The cause is due to an internal error.
Messages that immediately follow this message in the system log might provide information about possible causes. Check the output of show log messages. Then carefully note any symptoms that seem to be associated with the message. 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 to 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 there is a core file, a case with your technical support representative will need to be opened and the core file will need to be uploaded to the Juniper FTP site under that case for analysis.