The Layer 2 Control Protocol process (l2cpd) terminated because of an internal error.
The problem related to this syslog message is described in the following sections:
When a L2CPD_ABORT event occurs, a message similar to the following is reported:
l2cp: L2CPD_ABORT: abort l2cpd version 8.1I0.1 [builder] built by builder on 2006-06-2010:31:21 UTC: Device busy
/kernel: pid 3213 (l2cpd), uid 0: exited on signal 6 (core dumped)
init: layer2-control (PID 3213) terminated by signal number 6. Core dumped!
dumpd: Core and context for l2cpd saved in /var/tmp/l2cpd.core-tarball.0.tgz
This error will likely proceed a core dump file with the layer 2 control protocol daemon (l2cpd).
Check the output of show log messages and 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_ABORT error message. This can be found in 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. Instructions for doing so can be found here: www.juniper.net/customers/csc/help/upload_files.jsp