ACCT_MALLOC_FAILURE

The accounting statistics process could not allocate memory from the heap.

ASP_L2TP_NO_MEM

The Layer 2 Tunneling Protocol (L2TP) could not allocate the memory it needed to create a flow for the indicated tunnel and session.

CFMD_RTSOCK_OPEN_FAILURE

The connectivity fault management process (cfmd) could not successfully open a routing socket to the kernel, for the indicated reason.

CHASSISD_BUS_DEVICE_OPEN_FAILURE

The chassis process (chassisd) could not open the indicated bus device for the indicated reason.

CHASSISD_CLOCK_FAILURE

The chassis process (chassisd) determined that the indicated clock source failed in the indicated way.

CHASSISD_CMB_READBACK_ERROR

The chassis process (chassisd) could not read back information from the Chassis Management Bus (CMB) about the indicated component (field-replaceable unit, or FRU).

CHASSISD_FAN_FAILURE

The indicated fan or impeller failed. The chassis process (chassisd) raised an alarm and increased the speed of the remaining fans (and impellers, if applicable) to full speed.

CHASSISD_FASIC_FTOKEN_ERROR

The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_HSL_LINK_ERROR

The chassis process (chassisd) detected an error for the indicated high-speed link (HSL) for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FASIC_INPUT_DROP

The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data that was received from the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC), it dropped the indicated number of cells per second.

CHASSISD_FASIC_OUTPUT_DROP

The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data before sending it to the indicated Packet Forwarding Engine on the indicated Flexible Port Concentrator (FPC) for outgoing transmission, it dropped the indicated number of cells per second.

CHASSISD_FASIC_PIO_READ_ERROR

The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB).

CHASSISD_FASIC_PIO_WRITE_ERROR

The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB).

CHASSISD_FASIC_SRAM_ERROR

The chassis process (chassisd) detected that SRAM failed to initialize for the indicated F chip on the indicated Control Board (CB).

CHASSISD_FCHIP_HSR_ERROR

The chassis process (chassisd) detected an error in the high-speed receiver (HSR) subsystem for the F chip with the indicated characteristics.

CHASSISD_FCHIP_HST_ERROR

The chassis process (chassisd) detected an error in the high-speed transmitter (HST) subsystem for the F chip with the indicated characteristics.

CHASSISD_FCHIP_LINK_ERROR

The chassis process (chassisd) detected an error for the indicated high-speed receiver (HSR) or high-speed transmitter (HST) link for an F chip on the indicated Switch Interface Board (SIB).

CHASSISD_FCHIP_PIO_READ_ERROR

The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link.

CHASSISD_FCHIP_PIO_WRITE_ERROR

The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link.

CHASSISD_FHSR_READ_REG_ERROR

The high-speed receiver (HSR) read routine failed at the indicated address on an F-chip register.

CHASSISD_FHSR_WRITE_REG_ERROR

The high-speed receiver (HSR) write routine could not record the indicated value at the indicated address on an F-chip register.

CHASSISD_FHST_READ_REG_ERROR

The high-speed transmitter (HST) read routine failed at the indicated address on an F-chip register.

CHASSISD_FHST_WRITE_REG_ERROR

The high-speed transmitter (HST) write routine could not record the indicated value at the indicated address on an F-chip register.

CHASSISD_FILE_OPEN

The chassis process (chassisd) could not open the indicated file for the indicated reason.

CHASSISD_FM_ERROR

During execution of the indicated fabric management routine, the indicated error occurred between the indicated Switch Interface Board (SIB) and the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC).

CHASSISD_FM_ERROR_SIB_L_FB_HSR

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the T640 routing nodes (called SIB-Ls) and the SIBs in the TX Matrix platform (called SIB-Ss). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected an error in the electrical path between the indicated ports on the SIB-L and the corresponding SIB-S.

CHASSISD_FM_ERROR_SIB_L_FB_SMF

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (the switch-card chassis, or SCC) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media.

CHASSISD_FM_ERROR_SIB_S_FB_HSR

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the TX Matrix platform detected an error in the electrical path between the indicated port on the indicated SIB-S and the indicated port on a SIB-L installed in the indicated routing node (line-card chassis, or LCC).

CHASSISD_FM_ERROR_SIB_S_FB_SMF

In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (line-card chassis, or LCCs). The chassis process (chassisd) on the TX Matrix platform detected the indicated error as packets that were traveling to or from the indicated LCC were translated between electrical and optical media.

CHASSISD_FM_SIB_ERROR

The chassis process (chassisd) detected the indicated type of error on the indicated Switch Interface Board (SIB) and performed the indicated action.

CHASSISD_HSR_FIFO_ERROR

A first-in, first-out (FIFO) read error occurred during execution of the indicated routine on the indicated high-speed receiver (HSR).

CHASSISD_IPC_MSG_DROPPED

The chassis process (chassisd) dropped an interprocess communication (IPC) message because the message queue had already reached maximum capacity.

CHASSISD_IPC_MSG_UNHANDLED

The chassis process (chassisd) received an interprocess communication (IPC) message about the indicated FRU. The message had the indicated characteristics. The chassisd process could not handle the message.

CHASSISD_MALLOC_FAILURE

The chassis process (chassisd) could not allocate memory. The chassisd process tried to continue functioning, but the lack of memory usually causes the process to fail. An administrator needs to restart it.

CHASSISD_MBE_DETECTED

A multi-bit ECC parity error was detected in Routing Engine DRAM.

CHASSISD_PEM_OVERLOAD

The indicated power entry module (PEM) reported an output voltage overload condition.

CHASSISD_PEM_VOLTAGE

The indicated power entry module (PEM) reported a problem with its output voltage.

CHASSISD_SBE_DETECTED

Too many single-bit correctable ECC parity errors were detected in Routing Engine DRAM.

CHASSISD_SMB_IOCTL_FAILURE

The indicated ioctl() operation failed at the indicated address on the system management bus (SMB).

CHASSISD_SMB_READ_FAILURE

A read() operation failed at the indicated address on the system management bus (SMB).

CHASSISD_TEMP_SENSOR_FAILURE

The temperature sensor for the indicated component (field-replaceable unit, or FRU) either did not respond to a request from the chassis process (chassisd) for a temperature reading or sent a value that is outside the normal operating range.

CHASSISD_UNEXPECTED_EXIT

The chassis process (chassisd) exited unexpectedly and reported the indicated error.

COSD_MALLOC_FAILED

The class-of-service (CoS) process (cosd) could not dynamically allocate memory, for the indicated reason.

COSD_UNEXPECTED_EXIT

COSD waits for the event notifications and processes the events that it is registered for. There was an error during event-handling initialization.

Daemon Crash

A JUNOS daemon crash occurred with a core dump.

DCD_PARSE_STATE_EMERGENCY

The interface process (dcd) encountered an unhandled internal state during interface parsing.

DCD_TRASHED_RED_ZONE

When DCD is allocating heap memory, it uses a private memory allocator that writes a special pattern at the end of each allocated segment of heap memory. Later, when de-allocating this memory, DCD checks for the pattern. If it does not find the previously written pattern, it means the memory was overwritten, which indicates an error in DCD.

DFWD_MALLOC_FAILED

DFWD must dynamically malloc memory for its needs. This allocation request failed. The specific data structure that was being allocated is listed in the message.

DFWD_PARSE_STATE_EMERGENCY

The firewall process (dfwd) encountered an unhandled internal state while parsing an interface.

DFWD_TRASHED_RED_ZONE

When DFWD is allocating heap memory, it uses a private memory allocator that writes a special pattern at the end of each allocated segment of heap memory. Later, when de-allocating this memory, DFWD checks for the pattern. If it does not find the previously written pattern, it means the memory was overwritten, which indicates an error in DFWD.

DH_SVC_RTSOCK_OPEN_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not successfully open a routing socket to the kernel. The error string accompanying this log entry indicates the specific error.

DH_SVC_RTSOCK_REGISTER_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not successfully register a callback function with a routing socket. The error string accompanying this log entry indicates the specific error.

DH_SVC_SETSOCKOPT_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not set the indicated socket option.

DH_SVC_SOCKET_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not create a socket.

EVENTD_EVENT_SEND_FAILED

JUNOS processes can request that the event processing process (eventd) notify them when a specific event occurs. The eventd process could not send an event notification for the indicated reason.

EVENTD_FORK_ERR

The event processing process (eventd) could not create a child process for executing policies.

EVENTD_PIPE_ERR

The event processing process (eventd) could not create a pipe for interprocess communication.

FSAD_ERROR

The File System Access process (fsad) internal error message.

FUD_MEMORY_ALLOCATION_FAILURE

The UDP forwarding process (fud) could not allocate the indicated amount of memory from the heap.

FUD_RTSOCK_WRITE_FAILURE

The UDP Forwarding process (fud) could not write to its routing socket for the indicated reason.

FUD_SENDMSG_FAILURE

The UDP Forwarding process (fud) could not send data to the indicated destination port and address using the indicated interface and routing instance, which it needs to do during normal operation.

FUD_SENDMSG_NOINT_FAILURE

The UDP Forwarding process (fud) could not send data to the indicated destination port and address using the indicated routing instance, which it needs to do during normal operation.

FUD_SETSOCKOPT_FAILURE

The UDP Forwarding process (fud) could not set the indicated socket option.

FUD_SOCKET_FAILURE

The UDP Forwarding process (fud) could not create a socket.

GRAPH_NO_MEMORY

The graphing process could not allocate memory while trying to create a graph.

L2CPD_ABORT

The Layer 2 Control Protocol process (l2cpd) terminated because of an internal error.

L2CPD_ASSERT

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.

L2CPD_ASSERT_SOFT

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.

L2TPD_EVLIB_CREATE_FAILED

The Layer 2 Tunneling Protocol process (l2tpd) could not create a context for handling asynchronous events.

L2TPD_SERVER_START_FAILED

The Layer 2 Tunneling Protocol (L2TP) server did not start.

LACPD_DAEMONIZE_FAILED

The Link Aggregation Control Protocol process (lacpd) could not create a version of itself to run in the background as a daemon.

LIBJNX_DEFAULT_IP_ADDR_NOT_SET

A JUNOS process could not retrieve the system default IP address from the kernel, because the address is not defined there.

PFE Crash

Any PFE board crash that occurs in conjunction with a system exception message.

PPMD_ASSERT_SOFT

The source code for the periodic package management process (ppmd) includes internal self-consistency checks. As the ppmd process with the indicated process ID (PID) executed the binary compiled from the indicated source file, a check failed at the indicated line number in the file. The ppmd process created a diagnostic core file for analysis by technical support personnel and continued to run.

RDD_EVLIB_CREATE_FAILURE

The redundant interfaces process (rdd) could not create a context used for handling all asynchronous events (such as timers and message availability).

RPD_ABORT

The routing protocol process (rpd) terminated because of an internal error.

RPD_ACTIVE_TERMINATE

After receiving multiple termination requests, the routing protocol process (rpd) exited without performing the indicated cleanup tasks.

RPD_ASSERT

The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, causing the instance of rpd that was using the indicated binary and had the indicated process ID (PID) to terminate. The process created a diagnostic core dump for analysis by technical support personnel.

RPD_ASSERT_SOFT

The source code for the routing protocol process (rpd) includes internal self-consistency checks. A check failed at the indicated line number in the indicated source file, but the instance of rpd that was using the indicated binary and had the indicated process ID (PID) continued running. The process created a diagnostic core dump for analysis by technical support personnel.

RPD_DYN_CFG_BAD_REQ_OPCODE

The routing protocol process (rpd) received a dynamic configuration request with an unexpected operation code.

RPD_DYN_CFG_GET_PROFILE_FAILED

The routing protocol process (rpd) tried to load a profile from the database and failed.

RPD_DYN_CFG_GET_SNAPSHOT_FAILED

The routing protocol process (rpd) tried to load client session data from the database and failed.

RPD_DYN_CFG_PDB_CLOSE_FAILED

The routing protocol process (rpd) tried to close the profile database and failed.

RPD_DYN_CFG_PROCESSING_FAILED

The routing protocol process (rpd) tried to process dynamic configuration and failed.

RPD_DYN_CFG_REGISTER_FAILED

The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed.

RPD_DYN_CFG_SDB_OPEN_FAILED

The routing protocol process (rpd) tried to open the session database and failed.

RPD_ISIS_LSPCKSUM

The indicated IS-IS informational link-state PDU (LSP) failed an internal checksum validity test, implying that it was corrupted.

RPD_ISIS_OVERLOAD

The IS-IS link-state database is full and no additional memory can be allocated for it.

RPD_LMP_UNEXPECTED_OPCODE

The routing protocol process (rpd) received the indicated type of message, which had the indicated invalid operation code.

RPD_RT_ERROR

A route in the routing table was found to be in an unrecoverable error state.

RPD_TASK_FORK

The routing protocol process failed to create the indicated child process.

SERVICED_CONNECTION_ERROR

The remote client closed the connection when data was expected.

SERVICED_EVENT_FAILED

The Services PICs process (serviced) could not continue processing a task because a call to a function in the event library failed.

SERVICED_INTERNAL_INCONSISTENCY

An internal consistency check failed due to a mismatch between expected and received values for the specified object.

SERVICED_MALLOC_FAILURE

The Services PICs process (serviced) could not allocate the number of bytes needed to hold the indicated object.

SERVICED_NETWORK_FAILURE

An attempt to use the indicated network library call failed with an error.

SERVICED_RTSOCK_SEQUENCE

The Services PICs process (serviced) encountered a sequence error while receiving messages from the routing socket library.

SERVICED_STDLIB_FAILURE

The value returned by a call to a library function indicated that an error occurred.

SPD_DAEMONIZE_FAILED

The adaptive services process (spd) could not create a version of itself to run in the background as a daemon.

SPD_EVLIB_CREATE_FAILURE

The adaptive services process (spd) could not create a context used for handling all asynchronous events (such as timers and message availability).