 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the L2CPD prefix. They are generated by the Layer 2 Control Protocol process (l2cpd), which supports the transmission of control messages for Layer 2 spanning tree protocols in a Layer 2 bridge environment.
Assertion failed for executable-name (PID pid) at line line-number in file 'source-filename': message
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.
Error: An error occurred
error
Messages that immediately follow this message in the system log might provide information about possible causes.
Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core file, if requested.
Assertion failed for executable-name (PID pid) at line line-number in file 'source-filename' (message); process continued running
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 type of check failed at the indicated line number in the indicated source file. The process continued to run, but created a diagnostic core file for analysis by technical support personnel.
Error: An error occurred
error
Messages that immediately follow this message in the system log might provide information about possible causes.
Contact a technical support representative, and be ready to provide the list of messages and the diagnostic core file, if requested.
l2cpd process with PID pid exited (was using executable executable-name, version version built by builder on date); caller was address
The Layer 2 Control Protocol process (l2cpd) exited. The process had the indicated process ID (PID) and was using an executable with the indicated name, version, and other characteristics.
Event: This message reports an event, not an error
notice
Either a system resource was unavailable, the l2cpd process could not interpret an error, or the indicated user (referred to as a 'caller') terminated the process.
Kernel version (kernel-version) of routing sockets was not required version (l2cpd-version)
The Layer 2 Control Protocol process (l2cpd) determined that the indicated version of routing sockets, which the kernel supports, is not the version that it requires.
Error: An error occurred
error
Upgrade the kernel package.
Kernel version (kernel-version) of routing socket message type message-type is older than the required version (l2cpd-version)
The Layer 2 Control Protocol process (l2cpd) determined that the kernel supports an indicated older version of the indicated routing socket message type than it requires.
Error: An error occurred
error
Upgrade the kernel package.
Kernel version of routing socket message type 'message-type' was not required version (l2cpd-version)
The Layer 2 Control Protocol process (l2cpd) determined that the kernel does not support the version of the indicated routing socket message type that it requires.
Error: An error occurred
error
Upgrade the kernel package.
Using size KB of memory, percentage-value percent of available
The Layer 2 Control Protocol process (l2cpd) was using the indicated amount and percentage of Routing Engine memory, which is considered excessive.
Error: An error occurred
error
Either the l2cpd process is leaking memory or the use of system resources is excessive. Possible causes include misconfigured routing filters or a very complex configured network topology.
Increase the amount of RAM in the Routing Engine.
Peer peer-name timed out
The Layer 2 Control Protocol process (l2cpd) did not receive input from the indicated management peer within the timeout period.
Error: An error occurred
warning
Messages that immediately follow this message in the system log might provide information about possible causes.
Unable to establish mirror connection between Routing Engines: error-message
The Layer 2 Control Protocol process (l2cpd) could not establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines.
Error: An error occurred
warning
The master and backup Routing Engines are running incompatible versions of the JUNOS software.
Update the JUNOS software to compatible versions on the master and backup Routing Engines.
Mirror version (master-version) on master Routing Enginemaster-is-local is not compatible with version (standby-version) on backupstandby-is-local
While trying to establish the mirror connection (which supports nonstop routing) between the master and backup Routing Engines, the Layer 2 Control Protocol process (l2cpd) determined that the versions of JUNOS software on the Routing Engines were incompatible.
Error: An error occurred
warning
Update the JUNOS software to compatible versions on the master and backup Routing Engines.
Read error on pipe from ppmd: reason (error-message)
The Layer 2 Control Protocol process (l2cpd) could not read a message available on the read pipe from the periodic packet management process (ppmd).
Error: An error occurred
error
Contact your technical support representative.
function-name: write error on pipe to ppmd (error-message)
The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd).
Error: An error occurred
error
Contact your technical support representative.
function-name: runtime was excessive (time) during action of module
The indicated operation on the indicated submodule of the Layer 2 Control Protocol process (l2cpd) ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The message was logged because task accounting is enabled. The function might be implemented inefficiently.
function-name: runtime was excessive (time) during action of module
The indicated operation on the indicated submodule of the Layer 2 Control Protocol process (l2cpd) ran uninterrupted for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The message was logged because task accounting is enabled. The function might be implemented inefficiently.
function-name: runtime was excessive (total-time [user-time user, system-time system]) doing action
While performing the indicated operation, the indicated function in the Layer 2 Control Protocol process (l2cpd) ran uninterrupted for the indicated period of time (the sum of the indicated user and system times), which is considered excessive.
Event: This message reports an event, not an error
warning
The message was logged because task accounting is enabled. The function might be implemented inefficiently.
function-name: runtime was excessive (total of time in count callbacks) after action of module
After the indicated operation on the indicated submodule of the Layer 2 Control Protocol process (l2cpd), several functions ran uninterrupted in the indicated number of callbacks for the indicated period of time, which is considered excessive.
Event: This message reports an event, not an error
warning
The message was logged because task accounting is enabled. The function might be implemented inefficiently.
l2cpd process started (version l2cpd-version built on date by builder)
The Layer 2 Control Protocol process (l2cpd) started. It was assigned the indicated process ID (PID) and was using an executable with the indicated name, version, and build date.
Event: This message reports an event, not an error
notice
Child process 'task-name' terminated by SIGsignal-name core-dump-status
While a child process of the Layer 2 Control Protocol process (l2cpd) was performing the indicated operation, it terminated in response to the indicated signal.
Event: This message reports an event, not an error
error
Child process 'task-name' stopped by SIGsignal-name
While a child process of the Layer 2 Control Protocol process (l2cpd) was performing the indicated operation, it stopped in response to the indicated signal.
Event: This message reports an event, not an error
error
Unable to fork task-name: error-message
The Layer 2 Control Protocol process (l2cpd) could not create the indicated child process.
Error: An error occurred
error
getwd() failed for error-message
The Layer 2 Control Protocol process (l2cpd) invoked the getwd() system call, which failed.
Error: An error occurred
error
It is possible that the kernel lacked the resources needed to fulfill the request. The l2cpd process continued operating.
Assumed mastership
The Layer 2 Control Protocol process (l2cpd) became active when the Routing Engine on which it was running assumed mastership.
Event: This message reports an event, not an error
info
Unable to reinitialize
The Layer 2 Control Protocol process (l2cpd) did not reinitialize as requested, because it was running in a state that did not allow reconfiguration.
Error: An error occurred
error
Unable to close and remove PID file filename: error-message
The Layer 2 Control Protocol process (l2cpd) could not close and remove the file that records its process ID (PID), which serves to prevent multiple instances of the l2cpd process from running simultaneously.
Error: An error occurred
error
flock(filename, LOCK_EX): error-message
The Layer 2 Control Protocol process (l2cpd) could not lock the file that records its process ID (PID), which serves to prevent multiple instances of the l2cpd process from running simultaneously.
Error: An error occurred
error
Unable to write to PID file filename: error-message
The Layer 2 Control Protocol process (l2cpd) could not write to the file that records its process ID (PID), which serves to prevent multiple instances of the l2cpd process from running simultaneously.
Error: An error occurred
error
Reinitialized
The Layer 2 Control Protocol process (l2cpd) reinitialized.
Event: This message reports an event, not an error
info
Unable to register SIGsignal-name to be ignored: error-message
The Layer 2 Control Protocol process (l2cpd) informed the kernel that it wished to ignore the indicated signal, but the kernel did not process the request.
Error: An error occurred
error
Exited with active tasks: task-name
After receiving multiple termination requests, the Layer 2 Control Protocol process (l2cpd) exited without performing the indicated cleanup tasks.
Event: This message reports an event, not an error
notice
Exited after receiving termination signal signal-name
In response to the indicated termination request, the Layer 2 Control Protocol process (l2cpd) terminated adjacencies with neighbors and shut down.
Event: This message reports an event, not an error
notice
Unable to write to trace file filename
The Layer 2 Control Protocol process (l2cpd) could not write to the indicated trace file, and stopped attempting to do so. The next commit of the configuration database will reenable tracing.
Event: This message reports an event, not an error
error
Unable to shut down error-message module
The Layer 2 Control Protocol process (l2cpd) could not shut down the indicated Rapid Spanning Tree Protocol (RSTP) or Multiple Spanning Tree Protocol (MSTP) module.
Error: An error occurred
error
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |