Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Event Policies

 

This section lists the event policies present in an AI-Scripts package. The event policies monitor occurrence of events (abnormal conditions) in a device. The event policies have .slax extension and are stored in the /var/db/scripts/event folder when AI-Scripts are installed on a device.

Structured Event Policies

Note
  • Starting in Release 7.0R1.0, AI-Scripts monitors the new events for MPC cards in MX Series devices. For the list of regular expressions of the new events, refer to the AI-Scripts 7.0R1.0 release notes  .

  • Starting in Release 6.0R1.0, AI-Scripts monitors the following events—SMQ Chip:SMQCHIP( 0) Fabric RED drops message is logg ed on , CMALARM: Error (code: 1219, type:Major, MQCHIP( 0): Possibl e Remot e PFE fault detected, err_c ell total/rate, XMCHIP(1): FI: Cell underfl ow at the state stage, LUCHIP(1) RMC 0 Unc orrectable ECC syslog messages, CHIP_S TREAM_BL OCKED: ICHIP (0) one or mor e stream block ed detected, and CHA SSISD_IFDEV_GET_B Y_NAME_F AIL: Unable to retrieve informa tion for interface device : Cannot allocate memory.

  • Starting in Release 5.0R6.0, AI-Scripts monitors unstructured Major Alarm messages from alarmd on MX960 devices.

  • Starting in Release 5.0R4.0, AI-Scripts monitors RED drop profiles.

  • Starting in Release 5.0R3.0, AI-Scripts monitors when the chassis process is unable to obtain information about an indicated device and the MQCHIP(0): Possible Remote PFE fault detected, err_cell total/rate event.

Table 1 lists the event policies for structured Junos OS log messages. The event policies have *.slax extension.

Table 1: Structured Events Detected by AI-Scripts

Event Policy File Name

Event Matching Pattern Used for the Service Now Event Synopsis

Description of the Event

ACCT_MALLOC_FAILURE.slax

ACCT_MALLOC_FAILURE

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

ACCT_XFER_POPEN_FAIL.slax

ACCT_XFER_POPEN_FAIL

The popen() function fails when the accounting statistics process invokes the indicated command to transfer the indicated file.

ASP_PGCP_IPC_MSG_WRITE_FAILED.slax

ASP_PGCP_IPC_MSG_WRITE_FAILED

The Packet Gateway Control Protocol (PGCP) client on the Services Port Interface Card failed to write an interprocess communication (IPC) message to the end of its pipe.

ASP_PGCP_IPC_PIPE_WRITE_FAILED.slax

ASP_PGCP_IPC_PIPE_WRITE_FAILED

The Packet Gateway Control Protocol (PGCP) client on the Services Port Interface Card failed to write the contents of its interprocess communication (IPC) pipe to the socket layer.

AUDITD_RADIUS_OPEN_FAILED.slax

AUDITD_RADIUS_OPEN_FAILED

The audit process (auditd) could not create a RADIUS object handle used for various RADIUS operations.

AUDITD_RADIUS_REQ_CREATE_FAILED.slax

AUDITD_RADIUS_REQ_CREATE_FAILED

The audit process (auditd) could not create a RADIUS accounting request for the indicated reason.

AUDITD_SOCKET_FAILURE.slax

AUDITD_SOCKET_FAILURE

The audit process (auditd) listens on a Transmission Control Protocol (TCP) socket for system accounting events reported by other processes on the device. The indicated socket operation failed with the indicated error.

AUTHD_AUTH_CREATE_FAILED.slax

AUTHD_AUTH_CREATE_FAILED

The generic authentication service process (authd) could not allocate an authentication object for the indicated reason.

AUTHD_SERVER_INIT_BIND_FAIL.slax

AUTHD_SERVER_INIT_BIND_FAIL

The generic authentication service process (authd) could not bind the server to the address specified.

AUTHD_SERVER_INIT_LISTEN_FAIL.slax

AUTHD_SERVER_INIT_LISTEN_FAIL

The generic authentication service process (authd) could not initialize listening on the server for the indicated socket.

AUTHD_SETSOCKOPT_FAILED.slax

AUTHD_SETSOCKOPT_FAILED

The generic authentication service process (authd) could not set socket options during the indicated operation.

AUTHD_SOCKET_FAILED.slax

AUTHD_SOCKET_FAILED

The generic authentication service process (authd) could not open a socket during the indicated operation.

AUTOCONFD_AUTH_NO_MEM.slax

AUTOCONFD_AUTH_NO_MEM

Memory allocation (malloc) for username authentication failed.

AUTOD_RECV_FAILURE.slax

AUTOD_RECV_FAILURE

The autoinstallation process (autod) receives the indicated error when it tries to receive data on a socket.

AUTOD_SEND_FAILURE.slax

AUTOD_SEND_FAILURE

The autoinstallation process (autod) receives the indicated error when it sends data on a socket.

AUTOD_SOCKET_CREATE_FAILURE.slax

AUTOD_SOCKET_CREATE_FAILURE

The autoinstallation process (autod) receives the indicated error when it creates a socket.

AV_PATTERN_KL_CHECK_FAILED.slax

AV_PATTERN_KL_CHECK_FAILED

The device is unable to use the Kaspersky pattern file. The error message provides information to give to Juniper Networks technical support.

AV_PATTERN_TOO_BIG.slax

AV_PATTERN_TOO_BIG

The pattern file size specified in the server initialization file (server.ini) exceeds the maximum prescribed limit.

AV_PATTERN_WRITE_FS_FAILED.slax

AV_PATTERN_WRITE_FS_FAILED

The device is unable to save the contents of an antivirus pattern file to the file system.

BFDD_READ_ERROR.slax

BFDD_READ_ERROR

The bidirectional forwarding detection process (bfdd) could not read a message available on the indicated type of pipe.

BFDD_WRITE_ERROR.slax

BFDD_WRITE_ERROR

The bidirectional forwarding detection process (bfdd) could not write a message to the indicated type of pipe.

BOOTPD_HWDB_ERROR.slax

BOOTPD_HWDB_ERROR

The boot parameter process (tnp.bootpd) could not complete an operation in the hardware database maintained by the chassis process (chassisd), for the indicated reason.

CFMD_RTSOCK_OPEN_FAILURE.slax

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.slax

CHASSISD_BUS_DEVICE_OPEN_FAILURE

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

CHASSISD_CFEB_POWER_FAILURE.slax

CHASSISD_CFEB_POWER_FAILURE

The chassis process (chassisd) could not turn on or turn off the power to the indicated Compact Forwarding Engine Board (CFEB).

CHASSISD_CLOCK_FAILURE.slax

CHASSISD_CLOCK_FAILURE

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

CHASSISD_CMB_READBACK_ERROR.slax

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_COMMAND_ACK_ERROR.slax

CHASSISD_COMMAND_ACK_ERROR

The chassis process requested that the indicated component (field-replaceable unit, or FRU) confirm that it was online. The indicated error occurred when the FRU sent its response. In the normal case, the chassis process performs any additional action necessary to guarantee that the FRU comes online.

CHASSISD_COMMAND_ACK_SFM_ERROR.slax

CHASSISD_COMMAND_ACK_SFM_ERROR

The chassis process (chassisd) requires an acknowledgment from each Switching and Forwarding Module (SFM) before it registers a Flexible PIC Controller (FPC) as online. The acknowledgment message from the indicated SFM failed for the indicated FPC.

CHASSISD_FAN_FAILURE.slax

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.slax

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_FTOKEN_INIT_ERROR.slax

CHASSISD_FASIC_FTOKEN_INIT_ERROR

The chassis process (chassisd) encountered an error while initializing memory at the indicated address for the indicated F-chip on the indicated Control Board (CB).

CHASSISD_FASIC_HSL_CONFIG_ERROR.slax

CHASSISD_FASIC_HSL_CONFIG_ERROR

The chassis process (chassisd) could not configure high-speed links for the indicated F-chip on the indicated Control Board (CB).

CHASSISD_FASIC_HSL_LINK_ERROR.slax

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_INIT_ERROR.slax

CHASSISD_FASIC_INIT_ERROR

The chassis process (chassisd) detected that F-chips were not yet initialized on the Control Board (CB).

CHASSISD_FASIC_INPUT_DROP.slax

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.slax

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.slax

CHASSISD_FASIC_PIO_READ_ERROR

The chassis process (chassisd) has detected a read error on a fabric link

CHASSISD_FASIC_PIO_WRITE_ERROR.slax

CHASSISD_FASIC_PIO_WRITE_ERROR

The chassis process (chassisd) has detected a write error on a fabric link

CHASSISD_FASIC_PLL_ERROR.slax

CHASSISD_FASIC_PLL_ERROR

The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated F-chip on the indicated Control Board (CB).

CHASSISD_FASIC_RESET_ERROR.slax

CHASSISD_FASIC_RESET_ERROR

The chassis process (chassisd) could not reset the indicated F-chip on the indicated Control Board (CB).

CHASSISD_FASIC_SRAM_ERROR.slax

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_CONFIG_MD_ERROR.slax

CHASSISD_FCHIP_CONFIG_MD_ERROR

The chassis process (chassisd) detected an invalid number of MD-chips for the indicated F-chip, Packet Forwarding Engine, and Flexible PIC Concentrator (FPC).

CHASSISD_FCHIP_HSR_ERROR.slax

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.slax

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.slax

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_MONITOR_ERROR.slax

CHASSISD_FCHIP_MONITOR_ERROR

The chassis process (chassisd) detected an invalid F-chip module while enabling or disabling the monitoring of F-chip functional blocks.

CHASSISD_FCHIP_PIO_READ_ERROR.slax

CHASSISD_FCHIP_PIO_READ_ERROR

A routine encountered an error while reading an F-chip register

CHASSISD_FCHIP_PIO_WRITE_ERROR.slax

CHASSISD_FCHIP_PIO_WRITE_ERROR

A routine encountered an error while writing to an F-chip

CHASSISD_FEB_SWITCHOVER.slax

CHASSISD_FEB_SWITCHOVER

The chassis daemon (chassisd) switched to the indicated FEB from the specified FEB.

CHASSISD_FHSR_READ_REG_ERROR.slax

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.slax

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.slax

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.slax

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.slax

CHASSISD_FILE_OPEN

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

CHASSISD_FM_ERROR.slax

CHASSISD_FM_ERROR

During the 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_F13_FB_TX_VC.slax

CHASSISD_FM_ERROR_F13_FB_TX_VC

In a TX Matrix Plus router, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the T1600 routing nodes (called ST-SIB-Ls) and the SIBs in the TX Matrix Plus platform (called F13SIBs and F2S-SIBs). The chassis process (chassisd) on the routing node that houses the indicated F13SIB detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media.

CHASSISD_FM_ERROR_SIB_L_FB_HSR.slax

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 router (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.slax

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 (the switch-card chassis, or SCC) and the SIBs in the T640 routers (called SIB-Ls). The chassis process (chassisd) on the T640 router 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.slax

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 routers (called SIB-Ls). The chassis process (chassisd) on the TX Matrix router has 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 T640 router (line-card chassis, or LCC).

CHASSISD_FM_SIB_ERROR.slax

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_FPC_PIC_DETECT_TIMEOUT.slax

CHASSISD_FPC_PIC_DETECT_TIMEOUT

The chassis process (chassisd) expects to receive notification within a timeout period that each Flexible PIC Concentrator (FPC) has attached the PIC that it houses. It did not receive notification from the indicated FPC.

CHASSISD_FRU_INVALID_SLOT.slax

CHASSISD_FRU_INVALID_SLOT

The chassis process (chassisd) detected that the indicated hardware component (field-replaceable unit, or FRU) was inserted in a slot that is not valid for that component type.

CHASSISD_FRU_IO_ERROR.slax

CHASSISD_FRU_IO_ERROR

The chassis process (chassisd) could not perform the indicated I/O operation on the indicated component (field-replaceable unit, or FRU).

CHASSISD_FRU_OFFLINE_NOTICE.slax

CHASSISD_FRU_OFFLINE_NOTICE

The chassis process (chassisd) took the indicated component (field-replaceable unit, or FRU) offline for the indicated reason.

CHASSISD_GBUS_READBACK_ERROR.slax

CHASSISD_GBUS_READBACK_ERROR

There was an error when the chassis process (chassisd) tried to read back information from the GBUS on the indicated component (field-replaceable unit, or FRU).

CHASSISD_HWDB_ERROR.slax

CHASSISD_HWDB_ERROR

The operation performed on the hardware database was unsuccessful.

CHASSISD_I2C_BAD_IDEEPROM_FORMAT.slax

CHASSISD_I2C_BAD_IDEEPROM_FORMAT

The chassis process (chassisd) determined that the ID EEPROM format specified for the indicated type of hardware component (field-replaceable unit, or FRU) is not valid for it.

CHASSISD_I2C_READ_ERROR.slax

CHASSISD_I2C_READ_ERROR

The chassis process (chassisd) cannot read I2C data from the indicated device.

CHASSISD_I2CS_READBACK_ERROR.slax

CHASSISD_I2CS_READBACK_ERROR

The chassis process (chassisd) cannot read back information from the I2C slave (I2CS) about the indicated component (field-replaceable unit, or FRU).

CHASSISD_IFDEV_DETACH_FPC.slax

CHASSISD_IFDEV_DETACH_FPC

The chassis process (chassisd) detached the interface devices for all PICs on the indicated Flexible PIC Concentrator (FPC).

CHASSISD_IFDEV_DETACH_PIC.slax

CHASSISD_IFDEV_DETACH_PIC

The chassis process (chassisd) detached the interface devices for the indicated PIC.

CHASSISD_IFDEV_GET_BY_NAME_FAIL.slax

CHASSISD_IFDEV_GET_BY_NAME_FAIL

The chassis process (chassisd) could not obtain information about the indicated interface.

CHASSISD_IPC_CONNECTION_DROPPED.slax

CHASSISD_IPC_CONNECTION_DROPPED

The chassis process (chassisd) dropped the interprocess communication (IPC) connection to the indicated component (field-replaceable unit, or FRU).

CHASSISD_IPC_DAEMON_WRITE_ERROR.slax

CHASSISD_IPC_DAEMON_WRITE_ERROR

The chassis process (chassisd) could not write to a socket because of the indicated error. The socket is for a connection to another process that runs on the Routing Engine and helps manage the chassis.

CHASSISD_IPC_MSG_DROPPED.slax

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.slax

CHASSISD_IPC_MSG_UNHANDLED

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

CHASSISD_IPC_WRITE_ERR_NULL_ARGS.slax

CHASSISD_IPC_WRITE_ERR_NULL_ARGS

The chassis process (chassisd) could not send a message to the indicated component (field-replaceable unit, or FRU) because one or more required parameters had a null value.

CHASSISD_ISSU_ERROR.slax

CHASSISD_ISSU_ERROR

The chassis process (chassisd) encountered an error during the In Service Software Upgrade Process.

CHASSISD_MAC_ADDRESS_ERROR.slax

CHASSISD_MAC_ADDRESS_ERROR

The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated interface because of an internal error.

CHASSISD_MAC_ADDRESS_FABRIC_ERROR.slax

CHASSISD_MAC_ADDRESS_FABRIC_ERROR

The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated fabric interface because of an internal error.

CHASSISD_MALLOC_FAILURE.slax

CHASSISD_MALLOC_FAILURE

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

CHASSISD_MBE_DETECTED.slax

CHASSISD_MBE_DETECTED

A multibit ECC parity error was detected in the Routing Engine DRAM.

CHASSISD_OVER_TEMP_CONDITION.slax

CHASSISD_OVER_TEMP_CONDITION

The temperature of one or more components (field-replaceable units, or FRUs) exceeded the indicated temperature, which is the upper of two thresholds. The fans (and impellers, if applicable) were in the indicated state. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, chassisd shuts down the device. When this message was logged, the indicated number of seconds remained before shutdown.

CHASSISD_OVER_TEMP_SHUTDOWN_TIME.slax

CHASSISD_OVER_TEMP_SHUTDOWN_TIME

The chassis process (chassisd) shut down the device because the temperature of one or more components exceeded the indicated threshold temperature for the indicated amount of time. Continued operation at the excessive temperature could damage the device.

CHASSISD_PEM_INPUT_BAD.slax

CHASSISD_PEM_INPUT_BAD

The chassis process (chassisd) detected the indicated error condition for the indicated power entry module (PEM).

CHASSISD_PEM_OVERLOAD.slax

CHASSISD_PEM_OVERLOAD

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

CHASSISD_PEM_TEMPERATURE.slax

CHASSISD_PEM_TEMPERATURE

The chassis process (chassisd) detected that the 'temperature check bit' was set in the status bit mask for the indicated power entry module (PEM).

CHASSISD_PEM_VOLTAGE.slax

CHASSISD_PEM_VOLTAGE

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

CHASSISD_PIC_HWERROR.slax

CHASSISD_PIC_HWERROR

The indicated PIC experienced a hardware error. The chassis process (chassisd) did not bring the PIC online.

CHASSISD_POWER_CHECK.slax

CHASSISD_POWER_CHECK

The chassis process (chassisd) could not power up the indicated component (field-replaceable unit, or FRU), because the FRU did not respond.

CHASSISD_PSU_ERROR.slax

CHASSISD_PSU_ERROR

The chassis process (chassisd) detected the indicated error condition for the indicated power supply unit (PSU).

CHASSISD_PSU_FAN_FAIL.slax

CHASSISD_PSU_FAN_FAIL

The PSU fan-fail bit is set in the status for the indicated power supply unit (PSU).

CHASSISD_PSU_INPUT_BAD.slax

CHASSISD_PSU_INPUT_BAD

The chassis process (chassisd) detected the input voltage/warning fault condition for the indicated power supply unit (PSU).

CHASSISD_PSU_OVERLOAD.slax

CHASSISD_PSU_OVERLOAD

The indicated power supply unit (PSU) reported an output voltage overload condition.

CHASSISD_PSU_TEMPERATURE.slax

CHASSISD_PSU_TEMPERATURE

The chassis process (chassisd) detected that the temperature check bit was set in the status bit mask for the indicated power supply unit (PSU).

CHASSISD_PSU_VOLTAGE.slax

CHASSISD_PSU_VOLTAGE

The indicated power supply unit (PSU) reported a problem with its output voltage.

CHASSISD_RE_OVER_TEMP_CONDITION.slax

CHASSISD_RE_OVER_TEMP_CONDITION

The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds.

CHASSISD_RE_OVER_TEMP_SHUTDOWN.slax

CHASSISD_RE_OVER_TEMP_SHUTDOWN

The chassis process (chassisd) performed the indicated action because the temperature of the indicated Routing Engine exceeded the maximum threshold for more than four minutes. Continued operation at the excessive temperature could damage device components.

CHASSISD_RE_OVER_TEMP_WARNING.slax

CHASSISD_RE_OVER_TEMP_WARNING

The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, chassisd shuts down the indicated component. When this message was logged, the indicated number of seconds remained before shutdown.

CHASSISD_SHUTDOWN_NOTICE.slax

CHASSISD_SHUTDOWN_NOTICE

Although the chassis process (chassisd) normally does not exit or shut down except when the Routing Engine reboots, it shut down for the indicated reason.

CHASSISD_SIGPIPE.slax

CHASSISD_SIGPIPE

The chassis process (chassisd) received a signal indicating that its attempt to write to a pipe failed because the reader (which could be another process or thread) did not exist.

CHASSISD_SMB_INVALID_PS.slax

CHASSISD_SMB_INVALID_PS

The chassis process (chassisd) could not set the status (enabled or disabled) for a power supply because it received the indicated power supply status code, which is invalid.

CHASSISD_SMB_IOCTL_FAILURE.slax

CHASSISD_SMB_IOCTL_FAILURE

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

CHASSISD_SMB_READ_FAILURE.slax

CHASSISD_SMB_READ_FAILURE

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

CHASSISD_SNMP_TRAP6.slax

CHASSISD_SNMP_TRAP6

The device sent a CHASSISD_SNMP_TRAP6 trap for a Power Supply Failed event.

CHASSISD_TEMP_SENSOR_FAILURE.slax

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_TIMER_VAL_ERR.slax

CHASSISD_TIMER_VAL_ERR

The chassis process (chassisd) started a timer to track the timeout period for an event. The timer returned a null identifier, so chassisd could not clear the timer.

CHASSISD_UNEXPECTED_EXIT.slax

CHASSISD_UNEXPECTED_EXIT

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

CHASSISD_VOLTAGE_READ_FAILED.slax

CHASSISD_VOLTAGE_READ_FAILED

The chassis process (chassisd) could not read the voltage data from the indicated component (field-replaceable unit, or FRU).

CHASSISD_VOLTAGE_SENSOR_INIT.slax

CHASSISD_VOLTAGE_SENSOR_INIT

The chassis process (chassisd) could not initialize the voltage sensor for the indicated component (field-replaceable unit, for FRU).

CONNECTION_CHASSISD_FAIL.slax

CONNECTION_CHASSISD_FAIL

The alarm process (alarmd) was unable to connect to the chassis process (chassisd).

CONNECTION_CRAFTD_FAIL.slax

CONNECTION_CRAFTD_FAIL

The alarm process (alarmd) was unable to connect to the craft process (craftd).

CONNECTION_RTLOGD_FAIL.slax

CONNECTION_RTLOGD_FAIL

The alarm process (alarmd) was unable to connect to the Juniper Networks J Series Services Router (JSR) log process (rtlogd).

CONNECTION_SEND_ERROR.slax

CONNECTION_SEND_ERROR

The alarm process (alarmd) received an error while it was trying to send a message.

COSD_GENCFG_WRITE_FAILED.slax

COSD_GENCFG_WRITE_FAILED

The class-of-service (CoS) process (cosd) uses GENCFG to read and write data from the kernel. If the write fails, the kernel returns an error.

COSD_MALLOC_FAILED.slax

COSD_MALLOC_FAILED

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

COSD_RTSOCK_LIB_ERR.slax

COSD_RTSOCK_LIB_ERR

The class-of-service (CoS) process (cosd) uses rtsock library for reading and writing data from and to kernel. The specified error occurred while using rtsock library to read or write data.

COSD_RTSOCK_WRITE_FAILED.slax

COSD_RTSOCK_WRITE_FAILED

The class-of-service (CoS) process (cosd) uses rtsock to read or write data from kernel. If the write fails kernel returns an error.

COSD_UNEXPECTED_EXIT.slax

COSD_UNEXPECTED_EXIT

The class-of-service (CoS) process (cosd) waits for the event notifications and processes the events that it is registered for. There was an error during event-handling initialization.

COSD_UNKNOWN_TRANSLATION_TABLE.slax

COSD_UNKNOWN_TRANSLATION_TABLE

The class-of-service (CoS) process (cosd) did not recognize the indicated translation table type from the rtsock library.

DCD_CONFIG_WRITE_FAILED.slax

DCD_CONFIG_WRITE_FAILED

The interface process (dcd) encountered an error while trying to send an interface configuration to the kernel over the routing socket.

DCD_GET_ERROR.slax

DCD_GET_ERROR

The interface process (dcd) encountered an error while trying to load the kernel interface configuration over the routing socket.

DCD_PARSE_STATE_EMERGENCY.slax

DCD_PARSE_STATE_EMERGENCY

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

DCD_RTSOCK_READ_SYNC_NOBUF.slax

DCD_RTSOCK_READ_SYNC_NOBUF

The interface process (dcd) communicates with the kernel by writing messages to and reading messages from routing sockets. The dcd could not allocate memory to use to read messages from the kernel.

DCD_RTSOCK_SEND_NOBUF.slax

DCD_RTSOCK_SEND_NOBUF

If the Routing Engine is busy or operating under a heavy load, messages between the interface process (dcd) and the kernel may be dropped. To detect whether messages have been dropped, dcd and the kernel place sequence numbers in messages. dcd detected that a message was dropped. In an attempt to recover the message, dcd retries the operation.

DCD_TRASHED_RED_ZONE.slax

DCD_TRASHED_RED_ZONE

When the interface process (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 deallocating this memory, dcd checks for the pattern. Not finding the previously written pattern means the memory was overwritten, which indicates an error in dcd.

DFCD_GENCFG_MALLOC_FAILED.slax

DFCD_GENCFG_MALLOC_FAILED

The dynamic flow capture process (dfcd) could not allocate memory for the GENCFG message.

DFCD_GENCFG_WRITE_FAILED.slax

DFCD_GENCFG_WRITE_FAILED

The dynamic flow capture process (dfcd) could not send the GENCFG message for the indicated reason.

DFCD_LINH_MALLOC_FAILED.slax

DFCD_LINH_MALLOC_FAILED

The dynamic flow capture process (dfcd) could not allocate memory for the LINH message.

DFWD_CONFIG_WRITE_FAILED.slax

DFWD_CONFIG_WRITE_FAILED

The firewall process (dfwd) encountered an error while trying to send an interface configuration to the kernel over the routing socket.

DFWD_MALLOC_FAILED.slax

DFWD_MALLOC_FAILED

The firewall process (dfwd) must dynamically allocate 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.slax

DFWD_PARSE_STATE_EMERGENCY

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

DFWD_TRASHED_RED_ZONE.slax

DFWD_TRASHED_RED_ZONE

When the firewall process (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 deallocating this memory, dfwd checks for the pattern. Not finding the previously written pattern means the memory was overwritten, which indicates an error in dfwd.

DH_SVC_LOGIN_FAILURE.slax

DH_SVC_LOGIN_FAILURE

The Dynamic Host Configuration Protocol (DHCP) services process (dhcp-service) could not log the client in with the indicated application and the indicated session ID on the indicated interface (interface name) due to the indicated failure (preauthentication or postauthentication failure).

DH_SVC_RTSOCK_OPEN_FAILURE.slax

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.slax

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.slax

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.slax

DH_SVC_SOCKET_FAILURE

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

ESWD_DAI_FAILED.slax

ESWD_DAI_FAILED

The ARP request/response received on this port cannot be linked to any of the IPs assigned by DHCP.

ESWD_DHCP_UNTRUSTED.slax

ESWD_DHCP_UNTRUSTED

DHCP server packets are being received on a port that was not meant to receive server traffic.

ESWD_PPM_READ_ERROR.slax

ESWD_PPM_READ_ERROR

The Ethernet bridging process (eswd) could not read a message available on the read pipe from the periodic packet management process (ppmd).

ESWD_PPM_WRITE_ERROR.slax

ESWD_PPM_WRITE_ERROR

The Ethernet bridging process (eswd) could not write a message on the pipe to the periodic packet management process (ppmd).

ESWD_ST_CTL_ERROR_IN_EFFECT.slax

ESWD_ST_CTL_ERROR_IN_EFFECT

This condition occurs when storm control error condition is detected.

EVENTD_EVENT_SEND_FAILED.slax

EVENTD_EVENT_SEND_FAILED

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

EVENTD_FORK_ERR.slax

EVENTD_FORK_ERR

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

EVENTD_PIPE_ERR.slax

EVENTD_PIPE_ERR

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

EVENTD_VERSION_MISMATCH.slax

EVENTD_VERSION_MISMATCH

The event processing process (eventd) received an event with the indicated version indicator, which does not match the indicated version expected by eventd.

FPCLOGIN_IP_ADDRESS_GET_FAILURE.slax

FPCLOGIN_IP_ADDRESS_GET_FAILURE

The fpclogin module attempted to get the IP address of the physical interface module. The attempt failed.

FSAD_ERROR.slax

FSAD_ERROR

Internal error message of the file system access process (fsad)

FUD_MEMORY_ALLOCATION_FAILURE.slax

FUD_MEMORY_ALLOCATION_FAILURE

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

FUD_RTSOCK_WRITE_FAILURE.slax

FUD_RTSOCK_WRITE_FAILURE

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

FUD_SENDMSG_FAILURE.slax

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.slax

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.slax

FUD_SETSOCKOPT_FAILURE

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

FUD_SOCKET_FAILURE.slax

FUD_SOCKET_FAILURE

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

GGSN_ALARM_TRAP_SEND.slax

GGSN_ALARM_TRAP_SEND

An alarm trap to be relayed by the services PICs process (serviced) failed to initialize.

GGSN_TRAP_SEND.slax

GGSN_TRAP_SEND

The system sent a GGSN trap of an unrecognized type.

GRAPH_NO_MEMORY.slax

GRAPH_NO_MEMORY

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

HNCACHED_PATRICIA_ERROR.slax

HNCACHED_PATRICIA_ERROR

This event is generated when a call to a Patricia tree library function returns an error.

ICCPD_ASSERT_SOFT.slax

ICCPD_ASSERT_SOFT

The source code for the interchassis communication process (iccpd) includes internal self-consistency checks. As iccpd 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. iccpd created a diagnostic core file for analysis by technical support personnel and continued to run.

ICCPD_OPEN_ERROR.slax

ICCPD_OPEN_ERROR

The interchassis communication process (iccpd) could not initialize.

IDP_DAEMON_INIT_FAILED.slax

IDP_DAEMON_INIT_FAILED

An attempt to start the IDP policy daemon failed because an error was encountered during initialization.

IDP_INTERNAL_ERROR.slax

IDP_INTERNAL_ERROR

This event is generated when the IDP daemon encounters an internal error.

IKED_CFG_PATRICIA_ERROR.slax

IKED_CFG_PATRICIA_ERROR

This event is generated when a call to a Patricia tree library function returns an error.

JCS_MM_COMMUNICATION_ERROR.slax

JCS_MM_COMMUNICATION_ERROR

The JCS process (jcsd) could not send an SNMP request to the Management Module because of the indicated error.

JCS_READ_BANDWIDTH_ERROR.slax

JCS_READ_BANDWIDTH_ERROR

The indicated error occurred when attempting to read the current switch bandwidth.

JCS_READ_BBD_ERROR.slax

JCS_READ_BBD_ERROR

The indicated error occurred when attempting to read the current blade bay data by using a sysctl call.

JCS_SWITCH_COMMUNICATION_ERROR.slax

JCS_SWITCH_COMMUNICATION_ERROR

The JCS process (jcsd) could not send an SNMP request to the indicated Switch Module because of the indicated error.

JSRPD_DAEMONIZE_FAILED.slax

JSRPD_DAEMONIZE_FAILED

The Juniper Services Redundancy Protocol process (jsrpd) could not create a version of itself to run in the background as a daemon.

JSRPD_EVLIB_EXIT_FAILURE.slax

JSRPD_EVLIB_EXIT_FAILURE

The Juniper Services Redundancy Protocol process (jsrpd) returned from an event loop, which it should never do.

JSRPD_RG_STATE_CHANGE.slax

JSRPD_RG_STATE_CHANGE

The Juniper Services Redundancy Protocol process (JSRPD) detected an event that caused the state of the chassis cluster redundancy group to change due to the reason indicated in the log.

JSRPD_SET_SPU_MON_FAILURE.slax

JSRPD_SET_SPU_MON_FAILURE

The Juniper Services Redundancy Protocol process (JSRPD) detected Services Processing Unit (SPU) monitoring failure for a redundancy group.

JSRPD_SOCKET_CREATION_FAILURE.slax

JSRPD_SOCKET_CREATION_FAILURE

The Juniper Services Redundancy Protocol process (jsrpd) could not successfully create a socket.

JSRPD_SOCKET_LISTEN_FAILURE.slax

JSRPD_SOCKET_LISTEN_FAILURE

The Juniper Services Redundancy Protocol process (jsrpd) could not successfully listen on a socket.

JSRPD_SOCKET_RECV_HB_FAILURE.slax

JSRPD_SOCKET_RECV_HB_FAILURE

The Juniper Services Redundancy Protocol process (jsrpd) was not successfully received on a socket.

KMD_SNMP_PIC_NO_RESPONSE.slax

KMD_SNMP_PIC_NO_RESPONSE

The indicated PIC did not respond to a request from the key management process (kmd) for SNMP statistics about IP Security (IPsec) associations.

L2ALD_IPC_PIPE_WRITE_ERROR.slax

L2ALD_IPC_PIPE_WRITE_ERROR

The Layer 2 address learning process (l2ald) could not write to an interprocess communication (IPC) pipe for the indicated reason.

L2ALD_PIP_IFD_READ_RETRY.slax

L2ALD_PIP_IFD_READ_RETRY

The Layer 2 address learning process (l2ald) could not read the provide-in-provider interface (pip0) from the kernel.

L2CPD_ABORT.slax

L2CPD_ABORT

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

L2CPD_ASSERT.slax

L2CPD_ASSERT

The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. l2cpd 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.slax

L2CPD_ASSERT_SOFT

The source code for the Layer 2 Control Protocol process (l2cpd) includes internal self-consistency tests. l2cpd 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.

L2CPD_PPM_WRITE_ERROR.slax

L2CPD_PPM_WRITE_ERROR

The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd).

L2CPD_SCHED_SLIP.slax

L2CPD_SCHED_SLIP

The Layer 2 Control Protocol process (l2cpd) delayed an event, such as issuing an adjacency establishment message that was supposed to occur at a particular time. The event did not occur at the right time.

L2CPD_SYSTEM_CALL_FAILED.slax

L2CPD_SYSTEM_CALL_FAILED

A system call made by the Layer 2 Control Protocol process (l2cpd) failed.

L2TPD_EVLIB_CREATE_FAILED.slax

L2TPD_EVLIB_CREATE_FAILED

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

L2TPD_SERVER_START_FAILED.slax

L2TPD_SERVER_START_FAILED

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

LACPD_DAEMONIZE_FAILED.slax

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.

LIBESPTASK_SNMP_CONN_PROG.slax

LIBESPTASK_SNMP_CONN_PROG

The indicated error occurred while the process using libesptask was connecting to the SNMP master agent.

LIBESPTASK_SNMP_SOCKOPT_RECVBUF.slax

LIBESPTASK_SNMP_SOCKOPT_RECVBUF

The process using libesptask could not set the size of the kernel receive buffer, which allows it to accept the largest possible packet from the SNMP primary agent.

LIBESPTASK_SNMP_SOCKOPT_SENDBUF.slax

LIBESPTASK_SNMP_SOCKOPT_SENDBUF

The process using libesptask could not set the size of the kernel send buffer, which allows it to send the largest possible packet to the SNMP primary agent.

LIBJNX_DEFAULT_IP_ADDR_NOT_SET.slax

LIBJNX_DEFAULT_IP_ADDR_NOT_SET

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

LIBJNX_EVLIB_FAILURE.slax

LIBJNX_EVLIB_FAILURE

A Junos OS process called the indicated function in the event library. The function failed for the indicated reason.

LIBJNX_EXEC_SIGNALED.slax

LIBJNX_EXEC_SIGNALED

A Junos OS process created a child process to execute the indicated command. The child process received the indicated signal and exited.

LIBJNX_REPLICATE_RCP_ERROR.slax

LIBJNX_REPLICATE_RCP_ERROR

This event is generated when the rcp command fails during replication.

LIBJNX_SNMP_ENGINE_FILE_FAILURE.slax

LIBJNX_SNMP_ENGINE_FILE_FAILURE

A Junos OS process could not perform the indicated operation on the indicated SNMP engine data file.

LIBJNX_SNMP_ENGINE_SCAN_FAILURE.slax

LIBJNX_SNMP_ENGINE_SCAN_FAILURE

A Junos OS process could not perform the scan operation on the indicated SNMP engine data file.

LIBJNX_SOCKET_FAILURE.slax

LIBJNX_SOCKET_FAILURE

Various system processes use TCP, UDP, and Reliable Data Protocol (RDP) sockets. The indicated socket operation failed for the indicated reason.

LIBJSNMP_NS_LOG_EMERG.slax

LIBJSNMP_NS_LOG_EMERG

This event is generated when there are SNMP errors with LOG_EMERG as severity.

LIBJSNMP_NS_LOG_ERR.slax

LIBJSNMP_NS_LOG_ERR

This event is generated when there are SNMP errors with LOG_ERR as severity.

LIBMSPRPC_CLIENT_INIT_FAILED.slax

LIBMSPRPC_CLIENT_INIT_FAILED

A Junos OS process (mspinfo) could not establish initialization of the RPC client.

LIBMSPRPC_CLIENT_KCOM_FAILED.slax

LIBMSPRPC_CLIENT_KCOM_FAILED

A Junos OS process (mspinfo) could not establish initialization of the KCOM subsystem.

LIBMSPRPC_CLIENT_KCOM_NO_IF.slax

LIBMSPRPC_CLIENT_KCOM_NO_IF

A Junos OS process (mspinfo) could not find any configured and active extension-provider interfaces.

LIBMSPRPC_CLIENT_NO_CONNECTION.slax

LIBMSPRPC_CLIENT_NO_CONNECTION

Remote execution of the command given from the Routing Engine to the PIC failed. The Routing Engine cannot connect to the PIC.

LIBMSPRPC_CLIENT_NO_REPLY.slax

LIBMSPRPC_CLIENT_NO_REPLY

Remote execution of the command given from the Routing Engine to the PIC failed. There was no reply from the PIC.

LIBMSPRPC_CLIENT_PIC_DOWN.slax

LIBMSPRPC_CLIENT_PIC_DOWN

Remote execution of the command given from the Routing Engine to the PIC failed. The PIC is down.

LIBMSPRPC_CLIENT_WRONG_OUTPUT.slax

LIBMSPRPC_CLIENT_WRONG_OUTPUT

Remote execution of the command given from the Routing Engine to the PIC failed. The PIC returned unexpected output.

LIBSERVICED_CLIENT_CONNECTION.slax

LIBSERVICED_CLIENT_CONNECTION

An attempt to establish a client connection failed.

LIBSERVICED_SOCKET_BIND.slax

LIBSERVICED_SOCKET_BIND

This event is generated when an attempt to bind a server socket for receiving client requests failed.

LIBSERVICED_SOCKET_PRIVATIZE.slax

LIBSERVICED_SOCKET_PRIVATIZE

An attempt to attach a socket to the management routing instance for communication between the Routing Engine and GGSN-C PICs failed.

LICENSE_EXPIRED.slax

LICENSE_EXPIRED

A time-based license for a feature has expired. The feature will remain inactive until a new license is installed.

LICENSE_GRACE_PERIOD_APPROACHING.slax

LICENSE_GRACE_PERIOD_APPROACHING

The grace period for a licensable feature is about to expire. Unless a new license is installed, the feature will become inactive after the grace period expires.

LICENSE_GRACE_PERIOD_EXCEEDED.slax

LICENSE_GRACE_PERIOD_EXCEEDED

The grace period for a scale license is about to expire. Unless the scale license is upgraded, the license will scale back to the licensed limit after the grace period expires.

LICENSE_GRACE_PERIOD_EXPIRED.slax

LICENSE_GRACE_PERIOD_EXPIRED

The grace period for a licensable feature has expired. Strict license enforcement will remain active until a new license is installed.

LICENSE_NEARING_EXPIRY.slax

LICENSE_NEARING_EXPIRY

A time-based license for a feature is about to expire. Unless a new license is installed, the feature will become inactive after the license expires.

LICENSE_SOCKET_FAILURE.slax

LICENSE_SOCKET_FAILURE

This event is generated when the indicated process encounters a system error while manipulating a socket.

LPDFD_DYN_PDB_OPEN_FAILED.slax

LPDFD_DYN_PDB_OPEN_FAILED

The local policy decision function process (lpdfd) fails to open the profile database.

LPDFD_DYN_REGISTER_FAILED.slax

LPDFD_DYN_REGISTER_FAILED

The local policy decision function process (lpdfd) fails to register with the dynamic configuration subsystem.

LPDFD_DYN_SDB_OPEN_FAILED.slax

LPDFD_DYN_SDB_OPEN_FAILED

The local policy decision function process (lpdfd) fails to open the session database.

LPDFD_PCONN_SERVER.slax

LPDFD_PCONN_SERVER

The local policy decision function process (lpdfd) pconn server fails to initialize.

LPDFD_RTSOCK_OPEN_FAILURE.slax

LPDFD_RTSOCK_OPEN_FAILURE

The local policy decision function (LPDF) services process could not successfully open a routing socket to the kernel. The error string accompanying this log entry indicates the specific error.

MIB2D_REALPATH_FAILURE.slax

MIB2D_REALPATH_FAILURE

When MIB2D is copying the /var/db/dcd.snmp_ix file, it could not resolve its real path.

MIB2D_SNMP_INDEX_DUPLICATE.slax

MIB2D_SNMP_INDEX_DUPLICATE

This event is generated when the first interface name was assigned the same SNMP index as the second interface name.

MIB2D_SNMP_INDEX_UPDATE_STAT.slax

MIB2D_SNMP_INDEX_UPDATE_STAT

This event is generated when MIB2D cannot get the status of the SNMP index file.

MIB2D_SNMP_INDEX_WRITE.slax

MIB2D_SNMP_INDEX_WRITE

This event is generated when MIB2D cannot write to a file containing all the indices.

NSD_MEMORY_ALLOC_FAILED.slax

NSD_MEMORY_ALLOC_FAILED

This event is generated when the network security process (nsd) could not allocate the indicated number of bytes of memory.

NSD_SEC_NODE_COMP_SYNC_FAILED.slax

NSD_SEC_NODE_COMP_SYNC_FAILED

One or more subcomponents of the network security process (nsd) failed to synchronize their state when the nsd restarted on secondary mode.

NSTRACED_MEMORY_ALLOC_FAILED.slax

NSTRACED_MEMORY_ALLOC_FAILED

The USP trace process (nstraced) could not allocate the indicated number of bytes of memory.

NSTRACED_SSAMLIB_CALL_FAILED.slax

NSTRACED_SSAMLIB_CALL_FAILED

The indicated error occurred when the usp trace daemon process (nstraced) called a function in the ssamlib library or tried to process a callback from the library.

PFE_NH_RESOLVE_THROTTLED.slax

PFE_NH_RESOLVE_THROTTLED

The Packet Forwarding Engine throttled next-hop resolution requests from the indicated interface because the high number of requests might constitute an attempted denial-of-service (DoS) attack. Examples of events that generate next-hop resolution requests include an attempt to forward a packet without an Address Resolution Protocol (ARP) entry and receiving a multicast data packet with no matching route. Normally, the Packet Forwarding Engine forwards the requests to the Routing Engine.

PPMD_ASSERT_SOFT.slax

PPMD_ASSERT_SOFT

The source code for the periodic package management process (ppmd) includes internal self-consistency checks. As ppmd 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. ppmd created a diagnostic core file for analysis by technical support personnel and continued to run.

PPMD_READ_ERROR.slax

PPMD_READ_ERROR

The source code for the periodic package management process (ppmd) includes internal self-consistency checks. As ppmd 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. ppmd created a diagnostic core file for analysis by technical support personnel and continued to run.

RDD_EVLIB_CREATE_FAILURE.slax

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.slax

RPD_ABORT

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

RPD_ACTIVE_TERMINATE.slax

RPD_ACTIVE_TERMINATE

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

RPD_ASSERT.slax

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 file for analysis by technical support personnel.

RPD_ASSERT_SOFT.slax

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 file for analysis by technical support personnel.

RPD_DYN_CFG_BAD_REQ_OPCODE.slax

RPD_DYN_CFG_BAD_REQ_OPCODE

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

RPD_DYN_CFG_BUSY_SIGNAL_FAILED.slax

RPD_DYN_CFG_BUSY_SIGNAL_FAILED

The routing protocol process (rpd) failed to notify dynamic configuration clients about its availability to process dynamic configuration requests.

RPD_DYN_CFG_GET_PROF_NAME_FAILED.slax

RPD_DYN_CFG_GET_PROF_NAME_FAILED

The routing protocol process (rpd) tried to get the profile name from the session snapshot and failed.

RPD_DYN_CFG_GET_PROFILE_FAILED.slax

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_SES_STATE_FAILED.slax

RPD_DYN_CFG_GET_SES_STATE_FAILED

The routing protocol process (rpd) failed to get the session state from the session snapshot.

RPD_DYN_CFG_GET_SNAPSHOT_FAILED.slax

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.slax

RPD_DYN_CFG_PDB_CLOSE_FAILED

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

RPD_DYN_CFG_PDB_OPEN_FAILED.slax

RPD_DYN_CFG_PDB_OPEN_FAILED

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

RPD_DYN_CFG_PROCESSING_FAILED.slax

RPD_DYN_CFG_PROCESSING_FAILED

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

RPD_DYN_CFG_REGISTER_FAILED.slax

RPD_DYN_CFG_REGISTER_FAILED

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

RPD_DYN_CFG_REQUEST_ACK_FAILED.slax

RPD_DYN_CFG_REQUEST_ACK_FAILED

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

RPD_DYN_CFG_SCHEMA_OPEN_FAILED.slax

RPD_DYN_CFG_SCHEMA_OPEN_FAILED

The routing protocol process (rpd) tried to open the configuration schema and failed.

RPD_DYN_CFG_SDB_CLOSE_FAILED.slax

RPD_DYN_CFG_SDB_CLOSE_FAILED

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

RPD_DYN_CFG_SDB_OPEN_FAILED.slax

RPD_DYN_CFG_SDB_OPEN_FAILED

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

RPD_DYN_CFG_SES_RECOVERY_FAILED.slax

RPD_DYN_CFG_SES_RECOVERY_FAILED

The routing protocol process (rpd) tried to recover a session and failed.

RPD_ISIS_LSPCKSUM.slax

RPD_ISIS_LSPCKSUM

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

RPD_ISIS_OVERLOAD.slax

RPD_ISIS_OVERLOAD

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

RPD_KRT_KERNEL_BAD_ROUTE.slax

RPD_KRT_KERNEL_BAD_ROUTE

As it restarted, the routing protocol process (rpd) could not process a route obtained from the kernel because the route contained references to objects that are no longer valid.

RPD_LMP_UNEXPECTED_OPCODE.slax

RPD_LMP_UNEXPECTED_OPCODE

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

RPD_OS_MEMHIGH.slax

RPD_OS_MEMHIGH

The routing protocol process (rpd) is using the indicated amount and percentage of Routing Engine memory, which is considered excessive.

RPD_RT_ERROR.slax

RPD_RT_ERROR

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

RPD_TASK_FORK.slax

RPD_TASK_FORK

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

RT_SCREEN_TCP.slax

RT_SCREEN_TCP

A TCP attack category.

RT_SCREEN_UDP.slax

RT_SCREEN_UDP

A UDP attack category.

RTLOGD_DAEMONIZE_FAILED.slax

RTLOGD_DAEMONIZE_FAILED

The JSR log daemon could not create a version of itself to run in the background as a daemon.

RTLOGD_EVLIB_FAILURE.slax

RTLOGD_EVLIB_FAILURE

The JSR log daemon called the indicated event library function. The function failed with the indicated error.

RTLOGD_GET_TNP_ADDRESS_FAILED.slax

RTLOGD_GET_TNP_ADDRESS_FAILED

The JSR log daemon failed to determine the local TNP address used to receive JSR log.

RTLOGD_LOG_BIND_ERROR.slax

RTLOGD_LOG_BIND_ERROR

The JSR log daemon received the JSR log from a JSR log forwarder. The JSR log daemon failed to connect to the forwarder.

RTLOGD_LOG_READ_ENABLE_ERROR.slax

RTLOGD_LOG_READ_ENABLE_ERROR

The JSR log daemon received the JSR log from a JSR log forwarder. The JSR log daemon failed to enable the reading of the JSR log from the forwarder.

RTLOGD_LOG_READ_ERROR.slax

RTLOGD_LOG_READ_ERROR

The JSR log daemon relayed the JSR logs from the dataplane to the system event daemon for logging. The JSR log daemon failed to read JSR logs for the indicated reason.

RTPERF_CPU_THRESHOLD_EXCEEDED.slax

RTPERF_CPU_THRESHOLD_EXCEEDED

The Packet Forwarding Engine CPU threshold has been exceeded.

SAVAL_RTSOCK_FAILURE.slax

SAVAL_RTSOCK_FAILURE

The MAC SA Validate system process (jsavald) experienced the indicated error with a routing socket.

SDXD_DAEMONIZE_FAIL.slax

SDXD_DAEMONIZE_FAIL

The service deployment system process (sdxd) could not create a version of itself to run in the background as a daemon.

SERVICED_CLIENT_DISCONNECTED.slax

SERVICED_CLIENT_DISCONNECTED

The remote client closed the connection or stopped responding.

SERVICED_CLIENT_ERROR.slax

SERVICED_CLIENT_ERROR

An I/O error caused the termination of a connection with an interface client.

SERVICED_COMMAND_FAILED.slax

SERVICED_COMMAND_FAILED

An error caused a command being executed on an interface client to be canceled.

SERVICED_CONNECTION_ERROR.slax

SERVICED_CONNECTION_ERROR

The remote client closed the connection when data was expected.

SERVICED_EVENT_FAILED.slax

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_INIT_FAILED.slax

SERVICED_INIT_FAILED

One of the steps in the initialization sequence for the Services PICs process (serviced) failed.

SERVICED_INTERNAL_INCONSISTENCY.slax

SERVICED_INTERNAL_INCONSISTENCY

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

SERVICED_MALLOC_FAILURE.slax

SERVICED_MALLOC_FAILURE

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

SERVICED_NETWORK_FAILURE.slax

SERVICED_NETWORK_FAILURE

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

SERVICED_PID_FILE_LOCK.slax

SERVICED_PID_FILE_LOCK

As part of normal startup, the services PICs process (serviced) locks a file and writes its process ID (PID) into it. It could not lock the file.

SERVICED_PID_FILE_UPDATE.slax

SERVICED_PID_FILE_UPDATE

As part of normal startup, the services PICs process (serviced) locks a file and writes its process ID (PID) into it. It could not write to the file.

SERVICED_RTSOCK_SEQUENCE.slax

SERVICED_RTSOCK_SEQUENCE

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

SERVICED_SIGNAL_HANDLER.slax

SERVICED_SIGNAL_HANDLER

As a part of normal functioning, the services PICs process (serviced) attempted to initialize a signal-handling function. Part of the initialization failed with an error.

SERVICED_SOCKET_CREATE.slax

SERVICED_SOCKET_CREATE

An attempt by the services PICs process (serviced) to create a new socket for communication with an interface client failed with an error.

SERVICED_SOCKET_IO.slax

SERVICED_SOCKET_IO

A call to a socket library function indicated that an error occurred while attempting to perform I/O.

SERVICED_SOCKET_OPTION.slax

SERVICED_SOCKET_OPTION

An attempt to set an option on a socket failed

SERVICED_STDLIB_FAILURE.slax

SERVICED_STDLIB_FAILURE

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

SIB_CHECK.slax

SIB_CHECK

SNMP_PATRICIA_ERROR.slax

SNMP_PATRICIA_ERROR

A call to a Patricia tree library function returns an error.

SNMP_RTSLIB_FAILURE.slax

SNMP_RTSLIB_FAILURE

A call to the indicated function in the routing socket library failed with the indicated error.

SNMPD_FILE_FAILURE.slax

SNMPD_FILE_FAILURE

The SNMP agent process (snmpd) could not access the indicated file.

SNMPD_RMONFILE_FAILURE.slax

SNMPD_RMONFILE_FAILURE

The indicated operation failed on the indicated remote monitoring (RMON) data file.

SNMPD_SOCKET_FATAL_FAILURE.slax

SNMPD_SOCKET_FATAL_FAILURE

The SNMP agent process (snmpd) uses sockets for communication with subagents. The process exited after a socket operation, such as creation or removal, failed.

SNMPD_SUBAGENT_NO_RESOURCES.slax

SNMPD_SUBAGENT_NO_RESOURCES

The SNMP agent process (snmpd) uses certain resources for communication with subagents. However, the resources were not available for communication with the indicated subagent.

SPD_DAEMONIZE_FAILED.slax

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.slax

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).

SPD_GEN_NUM_FAIL.slax

SPD_GEN_NUM_FAIL

The adaptive services process (spd) attempted to initialize the generation-number for the service sets. However, the memory allocation failed.

TASK_OS_MEMHIGH.slax

TASK_OS_MEMHIGH

The process is using the indicated amount and percentage of Routing Engine memory, which is considered excessive.

TASK_SYSTEM.slax

TASK_SYSTEM

A system call made by this process failed.

TFTPD_RECVCOMPLETE_INFO.slax

TFTPD_RECVCOMPLETE_INFO

The TFTP process (tnp.tftpd) received the last portion of a transmitted file. This message records the number of blocks received, the block size used, and the name of the file to which the data was written.

UI_CHILD_SIGNALED.slax

UI_CHILD_SIGNALED

The child process (PID) created by the management process (mgd) to execute a command for it exited with the following core dump message: “Child received signal: PID 17332, signal Abort trap: 6, core dumped, command='/proc/1533/file”

UI_CMDLINE_READ_LINE.slax

UI_CMDLINE_READ_LINE

This message indicates that the management process (mgd) has received a command from the user.

UI_DBASE_REBUILD_FAILED.slax

UI_DBASE_REBUILD_FAILED

The management process (mgd) could not rebuild the configuration database file.

UI_DBASE_REBUILD_SCHEMA_FAILED.slax

UI_DBASE_REBUILD_SCHEMA_FAILED

The management process (mgd) could not rebuild the schema for the configuration database.

UI_DBASE_REOPEN_FAILED.slax

UI_DBASE_REOPEN_FAILED

After rebuilding the schema file for the configuration database, the management process (mgd) closes the file and reopens it in read-only mode to prevent corruption. It could not reopen the file.

UI_NETCONF_CMD.slax

UI_NETCONF_CMD

This message indicates that the user executed a command by using the NETCONF application programming interface (API).

UI_SCHEMA_SEQUENCE_ERROR.slax

UI_SCHEMA_SEQUENCE_ERROR

The Junos OS user interface schema file records all CLI commands and configuration statements available in the Junos operating system. The management process (mgd) rebuilds the schema as necessary to be compatible with the Junos OS software installed on the device. A sequence number in the schema acts as a checksum that represents its content and format. A Junos OS process attempted to access the schema but determined that the schema's sequence number means that it is incompatible with the process.

UTMD_MALLOC_FAILURE.slax

UTMD_MALLOC_FAILURE

The example process (utmd) could not allocate memory for a resource, possibly due to lack of memory.

UTMD_SSAMLIB_FAILURE.slax

UTMD_SSAMLIB_FAILURE

The example process (utmd) encountered an error while calling a function or from a callback of ssamlib.

VCCPD_PROTOCOL_LSPCKSUM.slax

VCCPD_PROTOCOL_LSPCKSUM

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

VRRPD_MISSING_VIP.slax

VRRPD_MISSING_VIP

The indicated interface received a Virtual Router Redundancy Protocol (VRRP) packet for the indicated VRRP group in which the indicated virtual IP address was missing.

WEB_ALLOCATE.slax

WEB_ALLOCATE

The Web management process (httpd) could not allocate the indicated amount of memory, for the indicated reason.

WEB_MEMORY_ALLOC.slax

WEB_MEMORY_ALLOC

The Web management process (httpd) could not allocate the indicated number of bytes of memory, for the indicated reason.

WEB_MGD_LISTEN_ERROR.slax

WEB_MGD_LISTEN_ERROR

The Web management process (httpd) could not open the mgd listening socket.

WEB_SOCKET.slax

WEB_SOCKET

The Web management process (httpd) could not create a socket, for the indicated reason.

WEBFILTER_CACHE_NOT_ENABLED.slax

WEBFILTER_CACHE_NOT_ENABLED

This event occurs whenever the webfilter (integrated web filtering) process failed to enable the web-filtering category cache.

WEBFILTER_REQUEST_NOT_CHECKED.slax

WEBFILTER_REQUEST_NOT_CHECKED

The Web filtering failed to check a Web request.

Unstructured Events

Table 2 lists the event policies for unstructured Junos OS log messages.

Table 2: Unstructured Events Detected by AI-Scripts

Event Policy File Name

Event Matching Pattern Used for the Service Now Event Synopsis

Description

problem-event-acb_storm_active.slax

SYSTEM:fpm_atlas_acb_storm_state_change: acb storm active

The "acb storm active" message is logged when a Control Board has received too many interrupts to process in a second.

problem-event-ASICiniterror.slax

PFE: ASIC Initialization Error

Any Packet Forwarding Engine ASIC initialization error that occurs in conjunction with a system exception message, such as: router-name fpc5 CMG: Fatal ASIC initialization error, Offlining FPC

problem-event-cannotperformaddandget.slax

SYSTEM:cannot perform nh operation ADDANDGET

When exporting local OSPF P2P LAN prefixes using rib groups, an error message can be logged containing the ADDANDGET keyword.

problem-event-CB_alarm.slax

SYSTEM:Alarm set: CB color=RED, class=CHASSIS, reason=CB

The CB Failure message reports a hardware issue. Usually, this is with the referenced Control Board, although sometimes it may be with an FPC.

problem-event-cellunderflow.slax

PFE: XMCHIP[(].[)]: (%PFE-.*: )?FI: Cell underflow at the state stage

The fabric cells are arriving late on the egress PFE.

problem-event-cmalarm_major.slax

CMALARM: Error (code: 1219, type:Major)

There are some hardware errors in the PFE memory component

problem-event-cmid_vsc8248_fw_unexpect.slax

PFE: cmic_vsc8248_ready_for_dfe.*CMIC.* - VSC8248 EDC FW unexpectedly in state.*toggling mode to reset FW

The "VSC8248 EDC FW unexpectedly in state" message reports a transient hardware issue.

problem-event-cmrfebhsl2error.slax

PFE: CMRFEB: Fatal HSL2 errors for FPC

A switching board (for example, FEB) is reporting a bad fabric connection to an FPC.

problem-event-COSMAN-FPC.slax

PFE:COSMAN-FPC PFE:COSMAN-FPC allocation of scheduler failed for stream type

The COSMAN-FPC allocation failure event message is generated when a scheduler has to be allocated, but the action results in failure.

problem-event-CRClinkerrordetected.slax

PFE:.*CRC link error detected for FPC

The high-speed link (HSL) messages show a cyclic redundancy check (CRC) error when sent between the switch fabric (SF) and Multi-Services Dense Port Concentrator (DPC).

problem-event-cxge_spi42_update_errors.slax

PFE:CXGE_SPI42: cxge_spi42_update_errors: snk: pkt end with eop abort

2HX FPGA error The S2HX FPGA is reporting it received an invalid cell. This does not mean the chip caused the error, only that it is reporting it.

problem-event-dcrash.slax

Daemon crash

A Junos OS daemon crash occurred with a core file.

problem-event-DFPGA_errors.slax

PFE:DFPGA got error events on non-zero link in last one second

The "DFPGA got .* error events on non-zero link in last one second" message reports that the associated PIC has sent the stated number of spurious interrupts

problem-event-dfwLogFirewallRows.slax

PFE: mrvl_dfw_log_effuse_status:Firewall rows

The TCAM error messages listed indicate a permanent nonfixable error with TCAM, if they persist after rebooting the EX Series switch or Virtual Chassis (VC). These errors are TCAM hardware issues on this FPC and are harmful. ACLs will be unreliable on this FPC.

problem-event-ea_celljmpdrp.slax

MQSS.*FI.*Cell jump drop error

The "Cell jump drop error" message reports a cell arrived with a sequence number which is ahead of the allocated reorder queue.

problem-event-ea_cellpackintrfc.slax

MQSS.*Cell packing interface error

The "Cell packing interface error" message reports a corrupted cell received from the HMC (Hybrid Memory Cube) interfaces.

problem-event-ea_chlddrperr.slax

MQSS.*FI.*Child drop error

The "Child drop error" message reports a cell is dropped during allocation in the fabric input reorder engine.

problem-event-ea_cksmerrdet.slax

EA.*Checksumerror detected on FO response

The "Checksum error detected on" message reports a corrupted cell received from the HMC (Hybrid Memory Cube) interfaces failing ECC Checksum.

problem-event-ea_cmdfsmstate.slax

MQSS.*DRD.*CMDFSMstate error

The "MQSS.*DRD.*CMD FSM state error" message reports that the Forwarding State Machine of the reorder queue received an unexpected value.

problem-event-ea_cpqw_fast_req_empty.slax

EACHIP CPQW Fast request is asserted for empty Queue

The "CPQW Fast request is asserted for empty Queue" message reports a transient software issue.

problem-event-ea_cpqw_freelist_man_runout.slax

EACHIP CPQW Freelist Manager run out of available fl pointers

The "CPQW Freelist Manager run out of available fl pointers" message reports a transient software issue.

problem-event-ea_fatalhmc.slax

EACHIP response packet with a FATAL state is received from HMC

The "response packet with a FATAL state is received from HMC" message reports a fatal error condition in Hybrid Memory Cube.

problem-event-ea_hmcif_chunkix_woread.slax

EACHIP EA.*HMCIF.*HMCIF has no chunk index available for incoming WO read

The "HMCIF has no chunk index available" message reports a transient hardware issue.

problem-event-ea_hmcif_rxlink_respfifo.slax

EACHIP EA.*HMCIF Rx.*Link.*Response FIFO . overflow

The "HMCIF Rx Link Response FIFO overflow" message reports a transient hardware issue.

problem-event-ea_hmcif_rxretry_failed.slax

EACHIP EA.*HMCIF Rx.*Link.*HMCIF Rx retry attempts failed

The "HMCIF Rx retry attempts failed" message reports a transient hardware issue.

problem-event-ea_hmcif_rxhmc_tokenov.slax

EACHIP EA.*HMCIF Rx.*Link.*HMC token overflow

The "Rx Link HMC token overflow" message reports a transient hardware issue.

problem-event-ea_hmcif_snglbiterr.slax

EACHIP total number of corrected single-bit errors from HMC

The "number of corrected single-bit errors from HMC" message reports a transient hardware issue.

problem-event-ea_hmcio_rx_sfifo.slax

EA.*HMCIO RX: SFIFO overflow detected in Channel:

The "sFIFO overflow event detected in Channel" message reports a transient FIFO overflow condition.

problem-event-ea_hmcio_tx_afifo.slax

EA.*HMCIO TX: AFIFO overflow event detected in Channel:

The "AFIFO overflow event detected in Channel" message reports a transient FIFO overflow condition.

problem-event-ea_li_recv_parcel.slax

MQSS.*LI.*Received a parcel with more than 512B accompanying data

The "LI Received a parcel with more than 512B accompanying data" message reports a transient hardware error or EACHIP software ucode issue.

problem-event-ea_mqss_bcmf_cbuf_sramprotpar.slax

EACHIP MQSS.*BCMF CBUF.*SRAM Protect.*Parity error

The "SRAM Protect Parity error detected for Bank" message reports a transient hardware issue.

problem-event-ea_mqss_drd_protpar_alloc.slax

EACHIP MQSS.*DRD.*Protect.*Parity error corrected for alloc state memory

The "Protect Parity error corrected" message reports a software issue.

problem-event-ea_mqss_li_unroll_taillen.slax

EACHIP MQSS.*LI.*Unroll TAIL length overflow

The "LI Unroll TAIL length overflow" message reports a software issue.

problem-event-ea_qdepth_underrun_err.slax

PFE: XQSS.*Qdepth underrun error in Drop engine 0

The "Qdepth underrun error" message reports a transient software issue.

problem-event-ea_reqtimouterr.slax

EACHIP MQSS FO: Request timeout error

The "F0 Request timeout error" message reports a transient hardware issue.

problem-event-ea_rspnsfatalHMC.slax

EA.*HMCIF Rx: Link.: A response packet with a FATAL state is received from HMC - State: 0x1f

The "FATAL state is received from HMC" message reports a multi-bit uncorrectable error condition in the Hybrid Memory Cube.

problem-event-ea_underflowstate.slax

EACHIP MQSS FI: Cell underflow at the state stage

The "MQSS FI: Cell underflow at the state stage" message reports a transient software issue

problem-event-eaxl_dbug_prot_corr.slax

XL.*cass_xr.*dbuf_protect Corrected XR DBUF

The "dbuf_protect Corrected XR DBUF" message reports a transient hardware issue.

problem-event-eaxlchip_filteralphaprot.slax

filter.pf0_1.alpha[0].protect

The "filter.pf0_1.alpha[0].protect" message reports a transient memory hardware issue in EACHIP or XLCHIP.

problem-event-eaxlluchip_asyncxtxn.slax

Errors async xtxn

The "Errors async xtxn error" message reports a software-related error condition in EACHIP, XLCHIP, and LUCHIP when accessing illegal memory space.

problem-event-eaxlluchip_syncxtxn.slax

Errors sync xtxn error

The "Errors sync xtxn error" message reports a hardware-related error condition in EACHIP, XLCHIP, and LUCHIP when synchronous transaction to external device is not possible.

problem-event-eaxlchip_prisectimeout.slax

SECONDARY_TIMEOUT or PRIMARY_TIMEOUT

The "SECONDARY_TIMEOUT or PRIMARY_TIMEOUT" message indicates a transient hardware or software defect in EACHIP or XLCHIP.

problem-event-eaxlchip_prbevenodd.slax

PRB_EVENERR or PRB_ODDERR

The "PRB_EVENERR or PRB_ODDERR" message indicates a transient hardware issue in the unload block of EACHIP or XLCHIP.

problem-event-eaxlchip_dblbitecc.slax

Double-bit ECC error

The "Double-bit ECC error" message indicates a transient Hardware error in EACHIP and LUCHIP.

problem-event-eaxlluchip_lmemaddr.slax

lmem addr error

The "lmem addr error" message indicates a transient hardware or software defect in EACHIP, XLCHIP, and LUCHIP.

problem-event-ECCsinglebit.slax

SYSTEM: Alarm set: .* color=RED, class=CHASSIS, reason=Host . ECC single bit parity error

The Packet Forwarding Engine component is reporting that L2 Cache Single-bit ECC errors were detected in the last 30 seconds. If problem persists, this is likely to result in a component crash or failure.

The "ECC single bit parity error" message reports that a correctable single bit error was detected once on the designated platform.

problem-event-exceededRLIMITDATA.slax

KERNEL:Process .* has exceeded 85% of RLIMIT_DATA

This message indicates that the virtual memory size of a process’s data-segment area (RLIMIT_DATA) has exceeded its current soft limit.

problem-event-EZsrhStruct_StatEntry_DoesExist.slax

PFE:EZsrhStruct_StatEntry_DoesExist failed

The message is emitted by the interface statistics module. The module is expecting a particular interface to be present and did not find the data structure for that interface.

problem-event-Fabric_request_time_out.slax

PFE:sntl_f_check_dest_errors: Fabric request time out for plane

The "sntl_f_check_dest_errors: Fabric request time out for plane" message is logged when an issue with a fabric connection is detected. The message reports the hardware that detected the issue, not the hardware that produced it.

problem-event-fast_failover_disabled.slax

SYSTEM:cm_ff_ifd_disable: fast failover disabled

The chassism process could not forward traffic as expected.

problem-event-fatalerr.slax

PFE:Fatal Error Encountered by .*

The "Fatal Error Encountered by" message reports that the specified hardware is not able to handle some transit traffic internally.

problem-event-Flow_table_full.slax

SYSTEM: Alarm set: SESSION TABLE reason=CP/Flow session table full

The "CP/Flow session table full" message indicates that the device has reached its maximum session capacity, causing the firewall to drop traffic.

problem-event-FPC_alarm.slax

Alarm set: FPC color=RED, class=CHASSIS, reason=FPC

The FPC alarm error message reports that there is a hardware issue in the FPC

problem-event-gen_auth_svc.slax

KERNEL:general-authentication-service terminated by signal number 11

The "general-authentication-service terminated" message reports that the authentication daemon has crashed and is being restarted. An associated core file has also been created on the device.

problem-event-GenCfgBloberror.slax

KERNEL:GENCFG: op 2 (Gencfg Blob) failed.*

The kernel error message is generated because no handler exists for a certain GENCFG blob message.

problem-event-harddiskerr.slax

SYSTEM:Alarm set RE Host hard-disk drive error

The hard-disk drive error message reports that a hard drive on the specified Routing Engine is no longer available to the kernel. Usually, either the message is reported from the backup Routing Engine or the master Routing Engine.

If the message is reported to the master Routing Engine, the master Routing Engine gets the corrupted boot list, reboots to fix the error, and in the process Routing Engine mastership switches.

If there is only one Routing Engine, the Routing Engine reboots on occurrence of this message. At that point the Routing Engine runs out of its alternate media, usually Compact Flash.

problem-event-hsl2hsl2error.slax

• PFE: HSL2: (%PFE-.*: )?HSL2 detected fatal error on

FPC detected fatal HSL2 error.

problem-event-HSR-crc-errors.slax

PFE:HSR.Too many crc errors

The "HSR: Too many crc errors" message reports that the indicated part in the message has gone into link error and may require reseating or replacement, or both. It may also indicate a false alarm thrown by the SIB orFPC.

problem-event-i2c_fan_error.slax

KERNEL.*i2c_s1.*group.*device

Fan tray response error. This error due to the fan tray processing a different task.

problem-event-ichipfcheck.slax

PFE: .*ichip_f_check_dest_errors.*

The FPC is reporting a bad fabric connection to one or more destinations. Another FPC is likely to be causing packet corruption.

problem-event-ichipregerr.slax

PFE:ICHIP(.*)_REG_ERR:.*

An ICHIP(.*)_REG_ERR message occurs when an I-chip reports an issue detected on an incoming fabric stream. The I-chip is only reporting the event, and is not the source of the fabric issue.

problem-event-ichipstreamblk.slax

CHIP_STREAM_BLOCKED: ICHIP (0) one or more stream blocked detected

The message indicates an I-chip wedge condition in MX Series devices.

problem-event-igmprelayfailed.slax

SYSTEM:.*snp_igmp_io_flood: relay failed.*

This message indicates that the device is flooding the IGMP unknown packet back on the same port that it was received on.

problem-event-IMQ_error_sid.slax

PFE:ICHIP IMQ: error sid detected

The "error sid .* detected" message is reporting that the Packet Forwarding Engine is receiving instructions from the IMQ (Inbound Message Queuing) to forward data to a system identifier(SID) that is either a duplicate or that does not exist. The I-chip is only reporting the condition. It is not the cause of the issue.

problem-event-ipv4_input_set_proto_and_ports.slax

PFE: PPE PPE HW Fault Trap: (%PFE-.*: )? Count .*, PC .*, 0x.*: ipv4_input_set_proto_and_ports

The ipv4_input_set_proto_and_ports message indicates that a trap occurred when the microcode attempted to interpret data past the end of the packet.

problem-event-kernel_cksum.slax

KERNEL:.*cksum.*out of data.*

This event is generated when "/kernel: cksum: out of data" is logged in the system log.

problem-event-kernelcrash.slax

SYSTEM: writing kernel to

A kernel crash event. A writing kernel message is captured after the router reboots.

problem-event-kmem_devbuf.slax

KERNEL:kmem type devbuf using .*, exceeding limit .*

The "kmem type devbuf" message reports that the kernel device buffer is allocating more memory than what is available to the kernel.

problem-event-l2cacheerror.slax

PFE: L2 Cache Single-bit ECC errors

The Packet Forwarding Engine component is reporting that Layer 2 Cache Single-bit ECC errors were detected in the last 30 seconds. If the problem persists, this situation is likely to result in a component crash or failure.

problem-event-lchipcrc.slax

PFE: LCHIP[(].[)]: (%PFE-.*: )?.* new crcerror errors in NLIF

The outbound FPC is reporting a corrupt packet received on the Nchip-to-Lchip interface. Another FPC is likely to be causing the packet corruption.

problem-event-linkerror-iwo_desrd_poll_stream_stats.slax

PFE: ICHIP[(][0-9][)]: (%PFE-.*: )?New illegal link errors in WO DESRD .* stream_id .*, iwo_desrd_poll_stream_stats

Potential I-chip stream problem due to logical interface flooding. Refer to [PR 289104]—device may need software upgrade.

The ICHIP: New illegal link errors system log message indicates a potential I-chip stream problem, possibly due to IFL flooding.

problem-event-Loss_of_communication.slax

SYSTEM: Loss of communication with Backup RE

The “Loss of communication with Backup RE” message is logged each time the master Routing Engine detects loss of keepalive messages being sent from the backup Routing Engine.

problem-event-luchip_bist_rldram.slax

PFE: LUCHIP.*Bist RLDRAM .* failed

The "LUCHIP Bist RLDRAM failed" message reports a transient hardware issue due to an ASIC initialization error.

problem-event-luchip_ddr_verfpass.slax

PFE: Starting luchip.*TOE

The "luchip.*TOE" message reports a hardware error detected in memory.

PFE: LUCHIP.*no TCAM installed, intr state not changed

The "no TCAM installed, intr state not changed" message reports a hardware error detected in memory.

PFE: LUCHIP.* DDR.*VERIFY_PASSED at retry

The "DDR VERIFY_PASSED at retry" message reports a hardware error detected in memory.

problem-event-luchip_disp_trapinfo_logic.slax

PFE: LUCHIP.*Display trap-info logic not initialized

The "trap-info logic not initialized" message reports a transient software initialization issue.

problem-event-luchip_err_thread_timeout_lmem.slax

PFE: LMEM errors require LUCHIP.* PPE .* Zone .* disable

The "LMEM errors require LUCHIP.* PPE .* Zone .* disable" event message reports a transient hardware issue.

PFE: LUCHIP.*PPE.* Errors thread timeout error lmem data error

The "thread timeout error lmem data error" message reports a transient hardware issue.

PFE: LUCHIP. PPE Thread Timeout Trap: Count .*PC .*handle_ppe_hw_fault

The "Thread Timeout Trap" message reports a transient hardware issue.

problem-event-luchip_hash_intstat.slax

PFE: LUCHIP.*HASH FPM ERROR: Alloc OMI Ram IF Error, TID.*FP_ID

The "HASH FPM Error" message reports a transient software issue.

PFE: LUCHIP.*HASH INT Status FPM Error

The "HASH INT Status FPM Error" message reports a transient software issue.

problem-event-luchip_idmem_readerr.slax

PFE: LUCHIP.* IDMEM.*read error

The "IDMEM read error" message reports a transient hardware issue.

problem-event-luchip_pio_handle_read.slax

PFE: LUCHIP.*GUMEM.*.ucode.instr.*read error

The "GUMEM.*.ucode.instr. read error" message reports a transient hardware issue.

PFE: LUCHIP.*pio_handle.*pio_read_u64.*failed.*IDMEM

The "pio_handle pio_read_u64 failed" message reports a transient hardware issue.

PFE: LUCHIP.*pio_handle.*jspec_pio_read_u256 failed.*gumem

The "pio_handle.*jspec_pio_read_u256 failed.*gumem" message reports a transient hardware issue.

PFE: trinity_pio.*PIO errors occurred

The "PIO errors occurred" message reports a transient hardware issue.

problem-event-luchip_ppe_cbo_mis_rdexp.slax

PFE: LUCHIP.*PPE.*CBO.*mismatch.*rd.*exp

The "PPE CBO mismatch" message reports a transient hardware issue.

problem-event-luchip_ppe_zone.slax

PFE: LUCHIP.* PPE.*Zone.* is not bound to a context

The "PPE Zone is not bound to a context" message reports a transient hardware issue.

PFE: LUCHIP.* PPE.*Zone_.* Context_.* PC .* State .* Traps

The "PPE.*Zone_.* Context_.* PC .* State .* Traps" message reports a transient hardware issue.

problem-event-luchip_ppe_err_sync_xtxn.slax

PFE: PPE.*Errors sync xtxn error

The "PPE Errors sync xtxn error" message reports a software issue.

problem-event-luchip_ppe_hwfault_trap.slax

PFE: PPE HW Fault Trap: Count .*PC .*init_xtxn_fields

The "PPE HW Fault Trap" message reports a transient hardware issue.

PFE: PPE Thread Timeout Trap: Count .*PC .*handle_trap_write_pc

The "PPE HW Fault Trap" message reports a transient hardware issue.

PFE: LUCHIP.*PPE.* Errors.*KMA.*parity error

The "PPE KMA.*parity error" message reports a transient hardware issue.

problem-event-luchip_ppe_kmberr.slax

PFE: LUCHIP.* PPE.* Errors thread timeout error

The "Errors thread timeout erro" message reports a transient hardware or software issue

PFE: LUCHIP.* PPE_.* Errors KMB.* parity error

The "KMB parity error" message reports a transient hardware or software issue.

PFE: PPE HW Fault Trap: Count .*PC .*init_xtxn_fields_drop_or_clip

The "PPE HW Fault Trap: Count" message reports a transient hardware or software issue.

problem-event-luchip_ppeerr_lmem_data.slax

The "PPE Errors lmem data error"

The "PPE Errors lmem data error" message reports a transient hardware issue.

problem-event-luchip_rambist_ddr.slax

PFE: CMT: Failed to init LU chip

The "Failed to init LU chip” event message reports a hardware issue.

PFE: CMT.*LU.*init failed.*generic failure

The "LU.*init failed.*generic failurer" event message reports a hardware issue.

PFE: LUCHIP.*Bist .* failed

The "BIST: failed" message reports a hardware issue.

PFE: RamBIST:LU-CHIP .* BIST: Memory Error

The "BIST: Memory Error" message reports a hardware issue.

PFE: RamBIST:LU-CHIP.* BIST: Test Name:Unique Address

The "BIST: Test Name:Unique Address" message reports a hardware issue.

problem-event-luchip_rambist_rld.slax

PFE: RamBIST:LU-CHIP.* RLDRAM .* BIST: Actual Data:

The "RLDRAM BIST Actual Data" message reports a transient hardware issue.

PFE: RamBIST:LU-CHIP.* RLDRAM .* BIST: Error Address

The "RLDRAM BIST Error Address" message reports a transient hardware issue.

PFE: RamBIST:LU-CHIP.* RLDRAM .* BIST: Error Count:

The "RLDRAM BIST Error Count" message reports a transient hardware issue.

PFE: RamBIST:LU-CHIP.* RLDRAM .* BIST: Expected Data

The "RLDRAM BIST Expected Data" message reports a transient hardware issue.

PFE: RamBIST:LU-CHIP.*RLDRAM.*BIST: Memory Error

The "RLDRAM BIST Memory Error" message reports a transient hardware issue.

PFE: RamBIST:LU-CHIP.* RLDRAM .* BIST: Vector Data

The "RLDRAM BIST Vector Data" message reports a transient hardware issue.

problem-event-luchip_reorder_intr.slax

PFE: SHARED LMEM errors require LUCHIP.*PPE.*disable

The "SHARED LMEM errors" message reports a hardware issue.

problem-event-luchip_rmc_correct_ecc_cnt.slax

PFE: LUCHIP.*RMC.*Correctable ECC .* cnt .* syn .* EDMEM

The "LUCHIP RMC Correctable ECC" message reports a transient hardware issue.

problem-event-luchip_rmc_uninit_edmem_read.slax

PFE: RMC.*Uninitialized EDMEM.*Read

The "RMC Uninitialized EDMEM Read" message reports a software issue.

problem-event-luchip_secondary_ppe_zone.slax

PFE: Secondary PPE.*zone.*timeout

The "Secondary PPE zone timeout" message reports a software or hardware issue.

problem-event-luchip_toe_memerr.slax

PFE: toe_coredump_read_regs.*failed.*read

The "toe_coredump_read_regs. failed read" message reports a transient hardware issue.

PFE: TOE ERROR.*DETECTED IN PFE.*TOE LU Stats

The "TOE ERROR DETECTED IN PFE.*TOE LU Stats" message reports a transient hardware issue.

PFE: toe_interrupt_errors.*LU TOE chip.*Memory Error Thread.*INSTR Addr

The "toe_interrupt_errors" message reports a transient hardware issue.

TOE:TOE LU.*SetErr - LU TOE chip.*Memory Error Thread.*INSTR Addr

The ”TOE chip.*Memory Error Thread” message reports a transient hardware issue.

problem-event-luchip_toeread_uncor_ecc_edmem.slax

PFE: LUCHIP.*TOE Read

The "LUCHIP TOE Read" message reports a transient hardware issue.

problem-event-LUCHIPuncorrectECC.slax

LUCHIP[(].[)] .*RMC .*Uncorrectable ECC .* EDMEM

The "LUCHIP Uncorrectable ECC" message reports a transient hardware issue.

problem-event-luchip_Uncorr_ecc_edmem.slax

PFE: Uncorrectable ECC.*EDMEM

The "Uncorrectable ECC EDMEM" message reports a software issue.

problem-event-LUCHIPuncorrectECC.slax

LUCHIP(1) RMC 0 Uncorrectable ECC syslog messages

ECC has detected uncorrectable errors in the LU-chip of an FPC

problem-event-LUchipWedge.slax

PFE: LUCHIP Wedge Detected, Active Zones

The "Wedge Detected, Active Zones" message reports transit traffic congestion on the associated LU-chip on the FPC listed in the system log message.

problem-event-mbufHighUtil.slax

kernel: Mbuf: High Utililization Level

The system log message Mbuf: High Utilization Level reports high memory utilization on the Routing Engine buffers. This message seeks a response to this condition.

problem-event-mq_fi_linksan.slax

PFE:MQCHIP(.) FI Link Sanity

The "FI Link sanity checks" message reports that there are corrupted packets identified by the FPC/MPC during the internal sanity checks at each block in the FPC/MPC.

problem-event-mqchip_chan_rx_read.slax

PFE: MQCHIP.*chan-rx.*read errors.crc_error.*failed

The "read crc_error" message reports a transient hardware error as a result of a PCI error.

problem-event-mqchip_cpq_rldram_dblecc.slax

PFE: MQCHIP.*CPQ RLDRAM double bit ECC error.*bank.*addr

CPQ RLDRAM double bit ECC error" message reports a transient hardware issue.

problem-event-mqchip_cpq_rldram_sglecc.slax

PFE: MQCHIP.*CPQ RLDRAM single bit ECC error.*bank.*addr

The "CPQ RLDRAM single bit ECC error" message reports a transient hardware issue.

problem-event-mqchip_cpq_sram_parity.slax

PFE: MQCHIP.*CPQ Sram parity error, errlog

The "CPQ Sram parity error" message reports a transient hardware error.

problem-event-mqchip_ddrif_fo_cksum.slax`

PFE: MQCHIP.*DDRIF FO.*Checksum Error

The "MQCHIP DDRIF FO Checksum Error" message reports detected cell checksum errors on the FPC

problem-event-mqchip_ddrif_wo_cksum.slax

PFE: MQCHIP.*DDRIF WO Checksum Error

The "DDRIF WO Checksum Error" message reports that there is checksum error in the DDRIF memory.

problem-event-mqchip_fi_cell_underflow.slax

PFE: MQCHIP.*FI Cell underflow at the state stage

The "FI Cell underflow at the state stage" message reports that Fabric Cells arrived too late.

problem-event-mqchip_fi_enque.slax

PFE:MQCHIP(.) FI Reorder Enqueuing error

The "FI Enqueuing error" message reports that the ASIC chip has an internal queue error in the packet stream traversing the chip.

problem-event-mqchip_fi_engueuing.slax

PFE: MQCHIP.*FI Enqueuing error.*type.*seq.*stream

The "FI Enqueuing error" message reports a transient hardware error. This means that the Fabric cells arrived too late in the MQ-chip.

problem-event-mqchip_fi_errcell_sent.slax

PFE: MQCHIP.*FI Error-cell sent to reorder engine

The "FI Error-cell sent to reorder engine" message reports a transient hardware issue.

problem-event-mqchip_fo_req_timeout.slax

PFE: MQCHIP.*FO Request time-out error

The "F0 Request time-out error" message reports a transient software error which means the fabric grant was not received.

problem-event-mqchip_freepool_empty.slax

PFE:MQCHIP(.*) FI Link cp freepool becomes empty

The "FI Link cp freepool becomes empty" message reports that the MQ-chip is experiencing a hardware issue on the associated FPC when handling transit cell traffic.

problem-event-mqchip_malloc_msgs.slax

PFE: MQCHIP.*MALLOC Q Reference Count Memory parity error

The “MALLOC Q Reference Count Memory parity error” message reports a software error.

PFE: MQCHIP.*MALLOC Pre-Q Reference Count underflow.*decrement below zero

The "MALLOC Pre-Q Reference Count underflow" message reports a software error.

PFE: MQCHIP.*MALLOC Two or more Q Ref-Count Memory parity errors

The "MALLOC Two or more Q Ref-Count Memory parity errors" message reports a software error.

problem-event-mqchip_ocm_fo_ddrif_par.slax

PFE: MQCHIP.*OCM Fo.*Ddrif Parity Error

The "Ddrif Parity Error" message reports a transient hardware error caused by on-chip memory parity errors.

PFE: MQCHIP.*OCM Parity Error Log.*rddst.*bnk_vec.*addr.*bank.*data

The "Parity Error Log.*rddst.*bnk_vec.*addr.*bank.*data" message reports a transient hardware error caused by on-chip memory parity errors.

problem-event-mqchip_ptcpt_parerr.slax

PFE: MQCHIP.*PT CPT parity error detected

The "PT CPT parity error detected" message reports a transient hardware issue.

problem-event-mqchip_timedout.slax

PFE: MQCHIP[(].[)] timed out waiting for phy_stream

The "timed out waiting for phy_stream" system log message reports an error found by the MQ-chip in the traffic stream. Most likely the error occurred elsewhere, as the MQ-chip is only detecting the issue.

problem-event-mqchip_wi_parerr_ibuf.slax

PFE: MQCHIP.*WI parity error detected when read from ibuf

The "WI parity error detected" message reports a transient hardware issue.

problem-event-mqchipCPQ_ECCerror.slax

PFE:MQCHIP(.) CPQ RLDRAM .* bit ECC error

The “MQCHIP(.) CPQ RLDRAM .* bit ECC error” message reports that a single or double-bit memory error was detected.

problem-event-mqchipremPFEfaultdet.slax

MQCHIP(0): Possible Remote PFE fault detected, err_cell total/rate

An error is found by the MQ-chip in the traffic stream.

Note: Most likely, the error occurred elsewhere; the MQ-chip is only detecting the issue.

problem-event-mqchip-throttle.slax

PFE:MQchip.*XE.*Throttle: Last.*seconds have seen interrupt throttling at

The MQ-chip has limited the number of interrupts being triggered on the Packet Forwarding Engine.

problem-event-mqDDRIFckerr.slax

PFE:MQCHIP(.) DDRIF FO0 Checksum Error

The “MQCHIP(.) DDRIF FO0 Checksum Error” reports an error in the checksum of the transit traffic stream through the chip.

problem-event-mqreordercell.slax

PFE:MQCHIP(.) FI Reorder cell timeout

The "FI Reorder cell timeout" message reports a packet drop in fabric traffic.

problem-event-mrvl_brg_port_cist_init.slax

PFE:.*mrvl_brg_port_stg_cist_init.*

Initialization warning message pertaining to MSTP, STP, and RSTP configured ports for any spanning tree groups shared common IST(CIST).

problem-event-multicorrectECCDMC.slax

PFE: Multiple Correctable ECC

The Packet Forwarding Engine board is reporting multiple correctable ECC memory errors.

problem-event-multiuncorrectECCDMC.slax

PFE: Multiple UnCorrectable ECC

The Packet Forwarding Engine board is reporting multiple uncorrectable ECC memory errors

problem-event-nfabcrcerror.slax

PFE: NFAB[(][0-9]/[0-9][)]: (%PFE-.*: )?.*new CRC errors detected

The fabric connection to the ingress FPC is reporting a bad connection.

problem-event-nhipcfailed.slax

KERNEL:RT_PFE: NH IPC failed, err 6 (No Memory)

The kernel is reporting that the Packet Forwarding Engine cannot install or change routing table entries because it is running out of memory.

problem-event-oam_lfm_adjacencyloss.slax

SYSTEM:Adjacency Lost

The message "Action Syslog on .* [adjacency-loss]: :Adjacency Lost" is reported into the system log message to indicate the occurrence of a link-fault event—that is, Link Adjacency Lost.

problem-event-oam_lfm_frameerror.slax

SYSTEM:Frame Error crossed threshold

The message "Action Syslog on .* [frame-error-event]: :Frame Error crossed threshold .* " is reported in the system log message to indicate the occurrence of a link-fault event—that is, Errored Frame Event.

problem-event-pfecrash.slax

PFE Crash

Any Packet Forwarding Engine board crash that occurs in conjunction with a system exception message.

problem-event-pfesendfailed.slax

Kernel:/kernel: pfe_send_failed, err=32

This is an internal message generated by the kernel. There is a keepalive message sent to the Packet Forwarding Engine (PFE) to check the status. The kernel missed the keepalive message for the CFEB because of hardware failure.

problem-event-phy_eeprom_read_failed.slax

PFE:phy_BCM8726_read_i2c: pumaj phy eeprom read failed

When the "phy_BCM8747_read_i2c: phy eeprom read failed" log message is seen on EX 8200 switches, the system missed a read from the EEPROM.

problem-event-piccrash.slax

PIC Crash

Any PIC crash that occurs in conjunction with a system exception message

problem-event-PIC-PIO-error-indicated.slax

PFE: PIC.*PIO error indicated

The "PIC <number> PIO error indicated " message may report that the indicated PIC had connectivity issues or has experienced a hardware failure.

problem-event-pio_read_error.slax

PFE: (CMFPC|CMG|CMS): (%PFE-.*: )?PIC ([0-9]*[/]?[0-9]*) PIO Read error, address

The PIO read error could indicate a hardware issue with the PIC.

problem-event-pio_write_error.slax

PFE: CMS: (%PFE-.*: )?PIC .* PIO Write error, address

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).

problem-event-pkterror-iwo_hdrf_poll_stats.slax

PFE: I-CHIP New packet errors in WO HDRF, iwo_hdrf_poll_stats

Potential I-chip stream problem due to logical interface flooding. Refer to [PR 289104]—device may need software upgrade.

problem-event-portcommandhandlerfailed.slax

PFE:port command handler failed processing cmd

This message is observed, when an error with the incorrect polling status for SFP on copper interfaces occurs.

problem-event-que_traffic.slax

PFE:ICHIP(.) Queued traffic in physical queue .* not transmitted

This message reports that I-chip Queued traffic in a physical queue is not being transmitted. When this condition is seen, the router will automatically changes the CoS configuration for the queue to force the queue to empty. The CoS parameters are then restored after one second.

problem-event-que_wedge.slax

PFE:ICHIP(.) Queue Wedge detected in physical queue

The "Queue Wedge detected in physical queue" message indicates that there was traffic queued on a specific interface queue that was being dropped.

problem-event-RCHIPSRAMparityerror.slax

PFE: RCHIP: SRAM parity error

SRAM parity error detected on FPC R-chip

problem-event-rdpretransmit.slax

KERNEL:rdp retransmit error

The kernel is indicating that no system buffer space is available.

problem-event-reflective_relay.slax

PFE:Reflective Relay set Failed

Reflective relay failed to be enabled on the specified interface.

problem-event-REmasterswitch.slax

SYSTEM: Keepalive timeout of *. Assuming RE mastership

The backup Routing Engine became the master Routing Engine due to a Routing Engine keepalive timeout.

problem-event-REwatchdog.slax

Reboot reason(s): 0x2: watchdog

Routing Engine watchdog timeout event. Related to PSN-2008-07-017 and PR/297313. Event is triggered by string: Reboot reason(s): 0x2: watchdog.

problem-event-RKME_int_status1.slax

PFE:SRCHIP(.): RKME int_status 10x100

RKME is a key match engine located in the FPC SR-chip or R-chip hardware. The RKME engine received the error interrupt shown.

problem-event-rnhlistdeletedpatnode.slax

KERNEL:unilist found on the rnhlist_deleted_root patnode

When graceful Routing Engine Switchover (GRES) is enabled, this message may be logged by the kernel of the master Routing Engine, as it is trying to add a unilist next-hop route; however, there is already a delete request pending acknowledgment from the kernel of the backup Routing Engine. So, the add request is deferred until the delete request is acknowledged. The number printed is the Next Hop Index in the Packet Forwarding Engine.

problem-event-RTfailedprefixchange.slax

PFE: RT: Failed prefix change

These messages indicate that the Routing Engine is trying to delete routes from the Packet Forwarding Engine, but it cannot because the routes do not exist. This usually means the Packet Forwarding Engine has run out of memory. For example, if you bring up many BGP peers, the number of routes the Routing Engine can hold may surpass the number the Packet Forwarding Engine can hold. In this case, the Packet Forwarding Engine runs out of memory and cannot add the routes. Later, when the Routing Engine tries to remove the routes, the prefix looks for is unknown.

problem-event-rtprefixadd.slax

KERNEL:RT_PFE: RT msg op 1 (PREFIX ADD) failed

When the Routing Protocol Process (rpd) is running out of all available memory, the kernel may fail to allocate memory for new prefixes. In this case a message of the following form may appear in the System log message file: kernel: RT_PFE: RT msg op 1 (PREFIX ADD) failed, err 6 (No Memory).

problem-event-scheduler_oinker.slax

SYSTEM: SCHED: Thread.*ran for.*without yielding

"Scheduler Oinker" messages seen on the console when a single thread of execution does not release itself from memory and CPU resources.

problem-event-SDRAMECCerror.slax

PFE: SDRAM ECC Error

Any Packet Forwarding Engine SDRAM ECC error that occurs in conjunction with a system exception message, for example: router-name fpc0 ADPC: detected 1 DDR SDRAM Single-bit ECC errors in the last 30 seconds

problem-event-SHEAFleakerror.slax

PFE: SHEAF: possible leak

Possible FPC SHEAF memory leak.

problem-event-SIB_STATE_OFFLINE_ACK_WAIT.slax

PFE:SIB_STATE_ONLINE-> SIB_STATE_OFFLINE_ACK_WAIT

When a "state transition SIB_STATE_ONLINE -> SIB_STATE_OFFLINE_ACK_WAIT" event occurs, a message similar to one of the following is reported:

sfc0-spmb0 CMGSIB: SIB #14 state transition SIB_STATE_ONLINE -> SIB_STATE_OFFLINE_ACK_WAIT sfc0-spmb0 CMGSIB: %PFE-6: SIB #1 state transition SIB_STATE_ONLINE -> SIB_STATE_OFFLINE_ACK_WAIT

This message may be associated with one or more of the following messages in the system log output:

CMGSIB: SIB #0 state transition SIB_STATE_OFFLINE_ACK_WAIT -> SIB_STATE_OFFLINE CMGSIB: cmg_sib_button_action(): 0 CMGSIB: Offline button request for SIB 0 CMGSIB: %PFE-3: SIB#1 voltage outside tolerance! spmb0 CMGSIB: SIB#0 voltage outside tolerance for channel: 10! sfc0-spmb0 CMGSIB: %PFE-3: Taking SIB#1 offline! chassisd[3247]: CHASSISD_FRU_OFFLINE_NOTICE: Taking SIB 1 offline: Offlined by cli command chassisd[2906]: CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power off (jnxFruContentsIndex 15, jnxFruL1Index 22, jnxFruL2Index 0, jnxFruL3Index 0, jnxFruName SFC0 SIB F2S 1/2, jnxFruType 9, jnxFruSlot 21, jnxFruOfflineReason 7, jnxFruLastPowerOff 423594357, jnxFruLastPowerOn 159058) When a SIB goes offline, this can trigger an alarm on the system."

problem-event-smqchipreddrops.slax

SMQCHIP(0) Fabric RED drops

The SMQ-chip has reported fabric RED drops

problem-event-sonn_errors.slax

PFE:SONN errors

The "SONN errors" message is logged periodically when the FPC loses track of notification cell traffic and reports the number of frames dropped.

problem-event-SRCHIPSRAMparityerror.slax

• PFE: SRCHIP[(].[)]: (%PFE-.*: )?SRAM parity error at loc

SRAM parity error detected on FPC RCHIP

problem-event-TCAMERROR.slax

PFE: Route TCAM rows could not be redirected on device

The TCAM error messages listed indicate a permanent nonfixable error with TCAM, if they persist after rebooting the EX Series switch or Virtual Chassis (VC). These errors are TCAM hardware issues on this FPC and are harmful. ACLs will be unreliable on this FPC.

problem-event-tempwarm.slax

SYSTEM: Alarm set: Temp Too Warm

The system is indicating that the sensor on an EX Series FPC is exceeding the temperature threshold.

problem-event-toxicsfp.slax

PFE: TOXIC SFP

Junos OS marks an SFP as toxic and logs the TOXIC SFP message when communication through the I2C (the bus through which the router monitors the SFP and updates diagnostic data) bus fails.

problem-event-ucode_data_error.slax

PFE:Errors ucode data error

The "Errors ucode data error" message is logged each time an ASIC fails its periodic code check.

problem-event-uncorrectECCerror.slax

• PFE: BCHIP .*: (%PFE-.*: )?multiple uncorrectable ECC error

The Packet Forwarding Engine board is reporting multiple uncorrectable ECC memory errors.

problem-event-unknownencapsohead.slax

SYSTEM:.*dcd.* unknown encaps_ohead; dev vlan, encaps .* flags.*

Informational message generated by the dcd deamon in system log when certain protocols and VLANs are configured (for example, MSTI, VRRP).

problem-event-vsc8248_firm_var_rdwr.slax

PFE: vsc8248_firmware_variable_rd_wr.*cmic-vsc8248.*channel.*vsc8248 firmware control register.*is not ready to accept new command

The "vsc8248 firmware control register is not ready" message reports a transient hardware issue.

problem-event-wanqwedge.slax

PFE: imq_stream_disable_stream

The imq_stream_disable_stream message is logged when an internal part of the I-chip is unable to clear data to make room for new data streams. The message indicates that the queue was not drained within 200ms; so, the software stopped trying to disable the queue.

problem-event-WRITE_DMAerror.slax

KERNEL:.*WRITE_DMA UDMA ICRC error.*

This message is seen when there is hardware fault on the hard drive or communication between the hard drive and kernel or Routing Engine and the motherboard.

problem-event-xfchipCRCerrors.slax

SYSTEM:New CRC errors found on xfchip

The "New CRC errors found on xfchip" message indicates that there are errors on the high-speed link between an FPC or DPC card and the associated SCB.

problem-event-xmchip_cellpackintrfc.slax

Cell packing interface error

The "Cell packing interface error" message reports a transient hardware issue with permanent operational impact in XMCHIP.

problem-event-xmchip_ddrif_cksum_fowo.slax

PFE: XMCHIP.*OCM.*Parity Error Counter

The "Parity error counter message reports a transient hardware issue.

PFE: XMCHIP.*DDRIF.*Checksum error for FO/WO.*Channel.*Address.*Checksum Errors

The “DDRIF Checksum error" message reports a transient hardware issue.

XMCHIP.*OCM.*DDR0 parity error.*Parity Error Address.*Bank

The “DDR0 parity error” message reports a transient hardware issue.

PFE: XMCHIP.*FO.*Packet error.*Error Packets

The "Packet error" message reports a transient hardware issue.

problem-event-xmchip_ddrif_wrrdprot.slax

PFE: XMCHIP.*DDRIF.*WR.*RD Protect: Parity error for RUNN checksum SRAM

The "RD Protect: Parity error" message reports a transient hardware issue.

PFE: XMCHIP.*DDRIF.*WR.*RD Protect: Multiple Errors

The "RD Protect: Multiple Errors" message reports a transient hardware issue.

problem-event-xmchip_drd_fabric_parcel_timout.slax

PFE: XMCHIP.*DRD.*Fabric parcel timeout error

The "Fabric parcel timeout error" message reports a software or transient hardware error.

problem-event-xmchip_drd_protect_parerr_mem.slax

PFE: XMCHIP.*DRD.*Protect.*Parity error for DRD memory

The "Parity error for DRD memory" message reports a transient hardware error.

problem-event-xmchip_drd_wanparcel.slax

PFE: XMCHIP.*DRD.*Wan parcel timeout error

The "Wan parcel timeout error" message reports a hardware or software issue.

problem-event-xmchip_drdo_cmdseqerr.slax

PFE:XMCHIP.*DRD.*Command sequence error

The "Command sequence error" message reports a problem in the DRD state machine.

problem-event-xmchip_drdo_refcntmemdec.slax

PFE: XMCHIP.*DRD0.*Reference count memory decrement error

The "Reference count memory decrement error" message reports flow export packets are being sent out at high rates.

problem-event-xmchip_epm_enq_freepool.slax

PFE: XMCHIP.*EPM.*Dequeue upon free pool full or eQ empty

The “EPM.*Dequeue upon free pool full or eQ empty” message reports a transient hardware issue.

PFE: XMCHIP.*EPM.*Enqueue upon free pool empty

The “EPM.*Enqueue upon free pool empty” message reports a transient hardware issue.

problem-event-xmchip_fo_req_timout.slax

PFE: XMCHIP.*FO.*Request timeout error.*Number of timeouts

The "FO Request timeout error" message reports a transient hardware issue.

problem-event-xmchip_fi_aliasing.slax

PFE: XMCHIP.*FI.*Aliasing on allocates error.*Pipe count

The "Aliasing on allocates error" message reports a transient hardware issue.

PFE: XMCHIP.*FI.*Reorder cell timeout

The “Reorder cell timeout” message reports a transient hardware issue.

problem-event-xmchip_fi_packet_crc.slax

PFE: XMCHIP.*FI.*Packet CRC error

The "FI Packet CRC error" message reports a transient hardware issue.

problem-event-xmchip_fi_prot_parerr_cpfree.slax

PFE: XMCHIP.*FI.*Protect.*Log Error

The "FI Protect Log Error" message reports a transient hardware memory error.

PFE: XMCHIP.*FI.*Protect.*Parity error for CP freepool SRAM

The "FI Protect Parity error for CP freepool SRAM" message reports a transient hardware memory error.

PFE: XMCHIP.*FI.*Protect.*Parity error for L2 freepool SRAM

The "FI Protect Parity error for L2 freepool SRAM" message reports a transient hardware memory error.

problem-event-xmchip_filink_sanity.slax

PFE: XMCHIP.*FI.*Link sanity checks.*Type

The "FI Link sanity checks" message reports a transient hardware issue.

problem-event-xmchip_li_recparc_hsl2.slax

PFE: XMCHIP.*LI.*Received a parcel from the HSL2 interface with EOPE

The "LI Received a parcel from the HSL2 interface" message reports a transient hardware or LU/XL software issue.

problem-event-xmchip_li_recv_parcel.slax

PFE: XMCHIP.*LI.*Received parcel with more than 512B accompanying data

The "LI Received parcel with more than 512B" message reports a transient hardware or LU/XL software issue.

problem-event-xmchip_malloc_dmem_parerr.slax

PFE: XMCHIP.*MALLOC.*Two or more DMEM allocation memory parity error

PFE: XMCHIP.*MALLOC.*Two or more DMEM allocation memory parity error.

PFE: XMCHIP.*MALLOC.*DMEM allocation memory parity error

The “DMEM allocation memory parity error" message reports a transient hardware issue.

problem-event-xmchip_malloc_drefmempar.slax

PFE: XMCHIP.*MALLOC.*SRef.*SChunk Reference Count.*memory parity error

The "SChunk Reference Count.* memory parity error" message reports a transient hardware issue.

PFE: XMCHIP.*MALLOC.*DREF memory parity error

The "DREF memory parity error" message reports a transient hardware issue.

problem-event-xmchip_malloc_schunk_parerr.slax

PFE: XMCHIP.*MALLOC: SChunk allocation memory parity error

The "SChunk allocation memory parity error" message reports a transient hardware error.

problem-event-xmchip_pt_missingsop_eop.slax

PFE: XMCHIP.*PT.*Missing SOP.*EOP errors from input blocks

The "EOP errors from input blocks" message reports a transient hardware issue.

problem-event-xmchip_ocmlo_parerr.slax

XMCHIP.*OCM: .*parity error - Parity Error Address

The "OCM parity error" message reports a transient hardware issue.

problem-event-xmchip_preclxmpar.slax

XMCHIP PRECL XM_engine instmem parity error detected

The "PRECL instmem parity error detected" message reports memory parity error in the XMCHIP preclassifier

problem-event-xmchip_ptprot_log.slax

PFE: XMCHIP.*PT.*Protect.*Parity error for CPT freelist memory

The "Parity error for CPT freelist memory" message reports a transient hardware issue.

PFE: XMCHIP.*PT.*Protect.*Log Error.*Log Address.*Multiple Errors

The "PT Protect Log Error" message reports a transient hardware issue.

problem-event-xmchip_pt_protpar_cpfifo.slax

PFE: XMCHIP.*PT.*Protect.*Parity error for CPFIFO data memory

The "Parity error for CPFIFO data memory" message reports a transient hardware issue.

problem-event-xmchip_pt_stream_emptywait.slax

PFE: xmchip_pt_stream_empty_wait.*Timeout occurred while waiting for the PT stream.*to become empty

The "Timeout occurred while waiting for the PT stream" message reports a transient hardware issue.

problem-event-xmchip_queunderrun.slax

XMCHIP CPQ1: Queue un[r]*derrun indication

The "CPQ1: Queue underrun indication" message reports a transient hardware error.

problem-event-xmchip_sched_prot_parerr.slax

PFE: XMCHIP.*Scheduler.*Protect.*Parity error for TDM table single port SRAM

The "Parity error for TDM table single port SRAM" message reports a transient hardware error.

problem-event-xmchip_sched_prot_parerr_tick.slax

PFE: XMCHIP.*Scheduler: Protect: Parity error for tick table single port SRAM

The "Scheduler: Protect: Parity error for tick table single port SRAM" message reports a transient hardware memory error.

problem-event-xmchip_wo_packet_protect.slax

PFE: XMCHIP.*WO.*Packet error - Error Packets

The "WO Packet error" message reports a transient hardware issue.

PFE: XMCHIP.*WO.*Protect.*Parity error for Output buffer data

The "Parity error for Output buffer " message reports a transient hardware issue.

problem-event-xmchip_wi_cpq_freeptrsram.slax

PFE: XMCHIP.*WI CPQ Free Pointer SRAM Protect: Parity error

The "WI CPQ Free Pointer SRAM Protect: Parity error" message reports a transient hardware memory parity error.

problem-event-xmchip_wi_inpaus_bufexcd.slax

PFE: XMCHIP.*WI.*Input pause buffer exceeded.*Check if the transmitter respects pause frames

The "Input pause buffer exceeded" message reports a configuration, wedge, or chip resource issue.

problem-event-xmchip_xxlce_portint.slax

PFE:XMCHIP.*XXLCE.*Port Interrupts.*Ethernet Rx Stats Parity Error

The “Port Interrupts.” Ethernet Rx Stats Parity Error” message reports a transient hardware issue.

PFE: xmchip_xxlce_mtip_cge_read.*Reading MTIP register failed

The "Reading MTIP register failed" message reports a transient hardware issue.

PFE: xmchip_pio_read_u32.*Reading 32-bit register failed

The "Reading 32-bit register failed message reports a transient hardware issue.

problem-event-xmreordercell.slax

PFE:XMCHIP(.): FI: Reorder cell timeout

The "XMCHIP(.): FI: Reorder cell timeout" message indicates that no further traffic is sent to the fabric due to packet drops.

problem-interval-vpls_drops.slax

INTERVAL: ICHIP non-RED vpls tail drops

The script associated with this event checks for non-red packets (tails drops) on all FPCs with tunnel-services enabled.

problem-interval-vpls_traffic.slax

INTERVAL: VPLS tunnel usage exceeded threshold

The event script checks periodically to see if any tunnel interface (vt-*/*/*) is experiencing usage of 65% or greater.

Events Deactivated in AI-Scripts Release 7.0R1.0

Starting Release 7.0R1.0, AI-Scripts has deactivated events listed in Table 3.

Table 3: Events Deactivated in AI-Scripts Release 7.0R1.0

Event Policy File Name

Event Matching Pattern Used for the Service Now Event Synopsis

Description of the Event

ASP_IDS_INV_CLEAR_QUERY.slax

ASP_IDS_INV_CLEAR_QUERY

The intrusion detection services (IDS) receives a request to clear information from the IDS tables. The request includes the indicated type of query, which the IDS cannot interpret.

ASP_IDS_INV_CLEAR_QUERY_VER.slax

ASP_IDS_INV_CLEAR_QUERY_VER

The intrusion detection services (IDS) receives a request to clear information from the IDS tables. The request version number did not match the version number of requests that the IDS can service.

ASP_L2TP_NO_MEM.slax

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.

ASP_L2TP_OBJ_CAC_FAIL.slax

ASP_L2TP_OBJ_CAC_FAIL

The Layer 2 Tunneling Protocol (L2TP) could not allocate memory from an object cache for the flow defined by the indicated unit, tunnel, and session.

CHASSISD_FM_ERROR_SIB_S_FB_SMF.slax

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 routers (called SIB-Ss) and the SIBs in the T640 routers (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_GBUS_NOT_READY.slax

CHASSISD_GBUS_NOT_READY

The GBUS was not ready when the chassis process (chassisd) first tried to power it on, and the power-up operation timed out.

CHASSISD_HSR_FIFO_ERROR.slax

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_SBE_DETECTED.slax

CHASSISD_SBE_DETECTED

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

CHASSISD_SIB_INVALID_SLOT.slax

CHASSISD_SIB_INVALID_SLOT

The chassis process (chassisd) detected the presence of a Switch Interface Board (SIB) in an invalid slot. The SIB remains offline.

ESPTASK_PARSE_BAD_SWITCH.slax

ESPTASK_PARSE_BAD_SWITCH

This process terminated because of an invalid option.

ESPTASK_PARSE_CMD_ARG.slax

ESPTASK_PARSE_CMD_ARG

This process terminated because of an internal error.

ESPTASK_PARSE_CMD_EXTRA.slax

ESPTASK_PARSE_CMD_EXTRA

This process terminated because of an invalid option.

ESWD_STP_BASE_MAC_ERROR.slax

ESWD_STP_BASE_MAC_ERROR

This condition occurs when the STP cannot derive the base MAC address of the system.

JCS_BBD_LOAD_FAILURE.slax

JCS_BBD_LOAD_FAILURE

The JCS process (jcsd) could not load blade bay data for the specified blade.

JCS_BBD_LOCAL_MISMATCH.slax

JCS_BBD_LOCAL_MISMATCH

The blade bay data retrieved for the specified blade does not match the data loaded during the reboot process. This error usually indicates that blade bay data in the JCS Management Module was changed since the last reboot.

JCS_BBD_NOT_FOUND.slax

JCS_BBD_NOT_FOUND

This event is generated when the blade bay data is not found for the specified blade.

JCS_BBD_NOT_VALID.slax

JCS_BBD_NOT_VALID

This event is generated when the blade bay data for the specified blade is invalid.

JCS_BBD_PARSE_ERROR.slax

JCS_BBD_PARSE_ERROR

This event is generated when the blade bay data for the specified blade did not parse correctly.

JCS_BBD_PEER_MISMATCH.slax

JCS_BBD_PEER_MISMATCH

The blade bay data retrieved for the specified peer blade does not match the data retrieved for the local blade. This error indicates that blade bay data in the JCS Management Module was not configured properly.

JCS_KERNEL_RSD_LINK_DOWN.slax

JCS_KERNEL_RSD_LINK_DOWN

The JCS process (jcsd) has disabled kernel RSD communication for the specified reason.

LLDPD_SYSTEM.slax

LLDPD_SYSTEM

This event is generated when a system call made by the Link Layer Discovery Protocol process (LLDPD) fails.

MIB2D_RTSLIB_READ_FAILURE.slax

MIB2D_RTSLIB_READ_FAILURE

A call to the indicated function in the routing socket library failed during the indicated operation on the indicated object.

MIB2D_SNMP_INDEX_ASSIGN.slax

MIB2D_SNMP_INDEX_ASSIGN

This event is generated when MIB2D cannot assign an SNMP index for each interface.

RPD_KRT_Q_RETRIES.slax

RPD_KRT_Q_RETRIES

The routing protocol process (rpd) attempted to update the kernel for the indicated times and failed. It will continue retrying.

SNMPD_SEND_FAILURE.slax

SNMPD_SEND_FAILURE

The SNMP agent process (snmpd) could not send either a protocol data unit (PDU) to the (UDP or a message to a subagent.

VCCPD_PROTOCOL_OVERLOAD.slax

VCCPD_PROTOCOL_OVERLOAD

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

problem-event-CCHIPabnormaldiscard.slax

PFE:.*CCHIP: .*abnormal discard seen.*

Packet Forwarding Engine board is reporting CCHIP abnormal discard errors.

problem-event-CCHIPSRAMparityerror.slax

CCHIP: (%PFE-.*: )?SRAM parity error .* bank

Any Packet Forwarding Engine SDRAM ECC error that occurs in conjunction with a system exception message; for example; router-name ssb CCHIP: %PFE-3: SRAM parity error 0x80000 bank 0x1

problem-event-clockerror.slax

PFE:.*clock error.*

Clock error reported on the Packet Forwarding Engine board.

problem-event-cm_read_i2c.slax

SYSTEM:.*cm_read_i2c errno is 5.*

The chassis manager event message results from an error in calculating the DC power budget for Packet Ordering Engine (POE) interfaces.

problem-event-DFWjtreecutoverfailed.slax

PFE: DFW: jtree cutover failed

The firewall filter configuration cannot be applied due to insufficient amount of contiguous memory on the SRAM.

problem-event-ichippktdrop.slax

PFE: Packet drop in Ichip

The I chip packet writer drop counter is incrementing, possibly indicating packet drops which may, but not necessarily, be due to a faulty switching board.

problem-event-jbuserror.slax

PFE: JBUS error

An error occurred on the FPC control bus used for packet memory allocation.

problem-event-jtreeLWMlimit.slax

PFE:.*RSMON: Resource Category:jtree Instance.*less than LWM limit.*

RSMON is reporting critical JTree memory resource shortage.

problem-event-LchipLSIFerrors.slax

PFE: LCHIP new errors in LSIF

The FPC is reporting LCHIP interface errors.

problem-event-multicasttraffic.slax

PFE: Failed to find MC RT_NH entry:.*

Informational message logged when multicast next-hop traffic ages from the switch routing tables.

problem-event-parityerrordetectedmpfe.slax

KERNEL:parity error detected, fll reinit: mpfe.*

The message indicates that the Packet Forwarding Engine was reset when detecting a parity error in the ASIC.

problem-event-PFEPacketDiscard.slax

PFE_PACKET_DISCARD_ERROR

The counter for the /pfe-hardware-statistics/fabric-discard tag from the junoscript call get-pfe-statistics (show pfe statistics) incremented.

problem-event-pfestat_req_receive.slax

KERNEL:pfestat_req_receive: request.*

This is a kernel message regarding a Packet Forwarding Engine statistics counter request.

problem-event-SDRAMECCmultibiterror.slax

PFE: Multi-bit ECC error

The Packet Forwarding Engine detected a multibit error correcting code (ECC) error in one of its boards.

problem-event-SFPlowpower.slax

PFE:.SFP receive power low warning

This event indicates that the SFP has received power low warning.

problem-event-vlanMACfilter.slax

KERNEL:vlan MAC filter: .* from port .* rejected

If a protocol is not configured on an EX Series device but receives Virtual Router Redundancy Protocol (VRRP) packets, all VRRP packets are dropped in the kernel with the /kernel: vlan MAC filter: 01:00:5e:00:05: reject message in /var/log/ messages.

This message is seen when packets arrive for all those protocol packets for which the EX Series device is not configured or enabled. When routed VLAN interface (RVI) is configured on a VLAN, a copy of all L3 multicast control packets (Institute of Electrical and Electronics Engineers (IEEE) well known multicast MACs, such as OSPF, (VRRP), and Protocol Independent Multicast (PIM)) is sent to the kernel.

problem-event-voltage_fail_shutdown.slax

KERNEL:.*Voltage Fail Shutdown.*device.*

The Voltage Fail Shutdown message is reported in the system message file if the indicated device in the system log message has or is about to be reset or due to improper grounding of the FRU causing it to go offline.

Events Deactivated in AI-Scripts Release 7.0R2.0

Starting Release 7.0R2.0, AI-Scripts has deactivated events listed in Table 4.

Table 4: Events Deactivated in AI-Scripts Release 7.0R2.0

Event Policy File Name

Event Matching Pattern Used for the Service Now Event Synopsis

Description of the Event

problem-event-xmchip_ddrif_cksum_fowo.slax

PFE: XMCHIP.*DDRIF.*Checksum error for FO/WO.*Channel.*Address.*Checksum Errors

PFE: XMCHIP.*DDRIF.*Checksum error for FO/WO.*Channel.*Address.*Checksum Errors

problem-event-xmchip_ddrif_cksum_fowo.slax

PFE: XMCHIP.*DDRIF.*Checksum error for WO.*Channel.*Address

DDRIF Checksum error" message reports a transient hardware issue

problem-event-luchip_Uncorr_ecc_edmem.slax

PFE: Uncorrectable ECC.*EDMEM

The "Uncorrectable ECC EDMEM" message reports a software issue.

problem-event-xmchip_fi_aliasing.slax

PFE: XMCHIP.*FI.*Aliasing on allocates error.*Pipe count

The "Aliasing on allocates error" message reports a transient hardware issue.

problem-event-xmchip_fi_aliasing.slax

PFE:XMCHIP(.): FI: Reorder cell timeout

The "XMCHIP(.): FI: Reorder cell timeout" message indicates that no further traffic is sent to the fabric due to packet drops.

problem-event-xmchip_pt_stream_emptywait.slax

PFE: xmchip_pt_stream_empty_wait.*Timeout occurred while waiting for the PT stream.*to become empty

The "Timeout occurred while waiting for the PT stream" message reports a transient hardware issue.

problem-event-luchip_ppe_zone.slax

PFE: LUCHIP.* PPE.*Zone.* is not bound to a context

The "PPE Zone is not bound to a context" message reports a transient hardware issue.

problem-event-luchip_ppe_zone.slax

PFE: LUCHIP.* PPE.*Zone_.* Context_.* PC .* State .* Traps

The "PPE Zone is not bound to a context" message reports a transient hardware issue.

Release History Table
Release
Description
Starting Release 7.0R2.0, AI-Scripts has deactivated events listed in Table 4
Starting in Release 7.0R1.0, AI-Scripts monitors the new events for MPC cards in MX Series devices. For the list of regular expressions of the new events, refer to the AI-Scripts 7.0R1.0 release notes  .
Starting Release 7.0R1.0, AI-Scripts has deactivated events listed in Table 3
Starting in Release 6.0R1.0, AI-Scripts monitors the following events—SMQ Chip:SMQCHIP( 0) Fabric RED drops message is logg ed on , CMALARM: Error (code: 1219, type:Major, MQCHIP( 0): Possibl e Remot e PFE fault detected, err_c ell total/rate, XMCHIP(1): FI: Cell underfl ow at the state stage, LUCHIP(1) RMC 0 Unc orrectable ECC syslog messages, CHIP_S TREAM_BL OCKED: ICHIP (0) one or mor e stream block ed detected, and CHA SSISD_IFDEV_GET_B Y_NAME_F AIL: Unable to retrieve informa tion for interface device : Cannot allocate memory.
Starting in Release 5.0R6.0, AI-Scripts monitors unstructured Major Alarm messages from alarmd on MX960 devices.
Starting in Release 5.0R4.0, AI-Scripts monitors RED drop profiles.
Starting in Release 5.0R3.0, AI-Scripts monitors when the chassis process is unable to obtain information about an indicated device and the MQCHIP(0): Possible Remote PFE fault detected, err_cell total/rate event.