Advanced Insight Scripts (AI-Scripts) Operation

ACX Series

ACX2000

ACX2100

ACX2200

EX Series

EX2200

EX3200

EX3300

EX4200

EX4500

EX4550

EX6210

EX8208

EX8216

EX9208

EX Virtual Chassis Series

EX3300-VC

EX4200-VC

EX4500-VC

EX6200-VC

MIXED-MODE-EX-VC

EX-XRE

QFX Series

FX-JVRE

QFX3500

QFX3500S

QFabric System

J Series

J2320

J2350

J4350

J6350

SRX Series (Branch)

SRX110

SRX210

SRX220

SRX240

SRX550

SRX650

SRX Series (Data Center)

SRX1400

SRX3400

SRX3600

SRX5600

SRX5800

LN Series

LN1000

LN2600

M Series

M10I

M120

M320

M40E

M7I

MX Series

MX10

MX2010

MX2020

MX240

MX40

MX480

MX5

MX80

MX960

T Series

M320

T1600

T320

T4000

T640

TX Matrix Series

TX Matrix

TX Matrix Plus

ACX Series

ACX1000

ACX1100

SRX Series (Branch)

SRX100

ACCT_MALLOC_FAILURE

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

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_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_PGCP_IPC_MSG_WRITE_FAILED

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

AUDITD_RADIUS_OPEN_FAILED

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

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_SERVER_INIT_BIND_FAIL

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

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 gets the boolist corrupted, reboots to fix that, and in the process Routing Engine Mastership switches. If there is only one Routing Engine, it will reboot also on occurrance of this message. At that point the affected Routing Engine will run off its alternate media, usually Compact Flash.

AUTHD_SETSOCKOPT_FAILED

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

AUTOCONFD_AUTH_NO_MEM

The memory allocation (malloc) for username authentication failed.

AUTOD_SEND_FAILURE

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

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_WRITE_FS_FAILED

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

BFDD_WRITE_ERROR

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

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_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_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_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_FASIC_FTOKEN_ERROR

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

CHASSISD_FASIC_HSL_CONFIG_ERROR

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

CHASSISD_FASIC_INIT_ERROR

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

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_WRITE_ERROR

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

CHASSISD_FASIC_RESET_ERROR

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

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_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_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_WRITE_ERROR

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

CHASSISD_FHSR_READ_REG_ERROR

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

CHASSISD_FHST_READ_REG_ERROR

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

CHASSISD_FILE_OPEN

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

CHASSISD_FM_ERROR_F13_FB_HSR_TXP

In a Tx-Plus routing matrix, 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 an error in the electrical path between the indicated ports on the F13SIB and the indicated ST-SIB-L on the indicated LCC.

CHASSISD_FM_ERROR_F13_FB_TX_VC

In a Tx-Plus routing matrix, 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_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_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 (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_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_IO_ERROR

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

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

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

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_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_PIC

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

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_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_ISSU_ERROR

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

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_MBE_DETECTED

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

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_OVERLOAD

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

CHASSISD_PEM_VOLTAGE

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

CHASSISD_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

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

CHASSISD_PSU_INPUT_BAD

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

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_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_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

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_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_READ_FAILURE

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

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_VOLTAGE_READ_FAILED

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

CONNECTION_CHASSISD_FAIL

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

CONNECTION_RTLOGD_FAIL

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

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_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/write data.

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.

Daemon Crash

A Junos OS daemon crash occurred with a core dump.

DCD_GET_ERROR

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

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_TRASHED_RED_ZONE

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

DFCD_GENCFG_WRITE_FAILED

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

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_PARSE_STATE_EMERGENCY

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

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 (pre-authentication or post-authentication failure).

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_SOCKET_FAILURE

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

ESPTASK_PARSE_CMD_ARG

This process terminated because of an internal error.

ESWD_DAI_FAILED

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

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_ST_CTL_ERROR_IN_EFFECT

This condition occurs when storm control error condition is detected.

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_PIPE_ERR

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

FPCLOGIN_IP_ADDRESS_GET_FAILURE

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

FUD_MEMORY_ALLOCATION_FAILURE

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

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_SETSOCKOPT_FAILURE

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

GGSN_ALARM_TRAP_SEND

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

GRAPH_NO_MEMORY

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

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.

IDP_DAEMON_INIT_FAILED

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

IKED_CFG_PATRICIA_ERROR

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

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.

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_VALID

The blade bay data for the specified blade is invalid.

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_MM_COMMUNICATION_ERROR

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

JCS_READ_BBD_ERROR

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

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_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_SOCKET_CREATION_FAILURE

The jsrpd process (jsrpd) could not successfully create a socket.

JSRPD_SOCKET_RECV_HB_FAILURE

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

KERNEL: rdp retransmit error

Kernel is indicating the no system buffer space is available.

KERNEL:.*jsr_prl_recv_ack_msg.* received PRL ACK message

Non-stop routing replication message acknowledgment received by backup Routing Engine.

KERNEL:.*WRITE_DMA UDMA ICRC error.*

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

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

Kernel error message generated because it does not have a handler for a certain GENCFG blob message.

KERNEL:ifd_request: RTM_ID.*

Some Junos OS daemons were not originally included in a list of processes that can modify an interface definition. These messages are only informational and can be ignored.

KERNEL:pfestat_req_receive: request.*

Kernel message regarding PFE statistics counter request.

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

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

KERNEL:rdp retransmit error

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

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

If a protocol is not configured on EX but it receives VRRP packets, all those packets will be dropped in kernel with message as ""/kernel: vlan MAC filter: 01:00:5e:00:05: reject"" can be seen in /var/log/messages. This message is seen when packets arrive for all those protocol packets for which EX is not configured/enabled. When RVI is configured on vlan , a copy of all L3 multicast control packets (IEEE well known multicast macs, like OSPF, VRRP, PIM, etc) is sent to the kernel.

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.

L2CPD_ABORT

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

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

L2TPD_EVLIB_CREATE_FAILED

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

L2TPD_SERVER_START_FAILED

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

LIBESPTASK_SNMP_CONN_PROG

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

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 Simple Network Management Protocol (SNMP) master agent.

LIBJNX_EVLIB_FAILURE

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

LIBJNX_REPLICATE_RCP_ERROR

The rcp command failed during replication.

LIBJNX_SNMP_ENGINE_SCAN_FAILURE

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

LIBJSNMP_NS_LOG_EMERG

SNMP errors with LOG_EMERG as severity.

LIBMSPRPC_CLIENT_INIT_FAILED

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

LIBMSPRPC_CLIENT_KCOM_NO_IF

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

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_WRONG_OUTPUT

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

LIBSERVICED_SOCKET_BIND

An attempt to bind a server socket for receiving client requests failed.

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

LLDPD_SYSTEM

A system call made by the Link Layer Discovery Protocol process (LLDPD) failed.

LPDFD_DYN_REGISTER_FAILED

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

LPDFD_PCONN_SERVER

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

MIB2D_REALPATH_FAILURE

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

MIB2D_SNMP_INDEX_ASSIGN

MIB2D cannot assign an SNMP index for each interface.

MIB2D_SNMP_INDEX_UPDATE_STAT

MIB2D cannot get the status of the SNMP index file.

NSD_MEMORY_ALLOC_FAILED

The network security process (nsd) could not allocate the indicated number of bytes of memory.

NSTRACED_MEMORY_ALLOC_FAILED

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

PFE Crash

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

PFE: .*L2 Cache Single-bit ECC errors.*

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

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

PFE: DFW: jtree cutover failed

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

PFE: HSL2–HSL2 detected fatal error

The FPC detected a fatal HSL2 error.

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

Potential ICHIP stream problem possibly due to IFL flooding. Potential match with PR/289104—may need software upgrade.

PFE: JBUS error

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

PFE: mrvl_dfw_log_effuse_status:Firewall rows

The TCAM error messages listed indicate a permanent non-fixable error with TCAM, if they persist after rebooting the EX Switch or Virtual Chassis (VC). These errors are TCAM hardware issues on this FPC and are not harmless. ACLs will be unreliable on this FPC.

PFE: Multiple Correctable ECC

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

PFE: NFAB(x/y): z new CRC errors detected

Fabric connection to ingress FPC is reporting a bad connection.

PFE: RCHIP: SRAM parity error

SRAM parity error detected on FPC RCHIP.

PFE: RT: Failed prefix change

These messages indicate that the Routing Engine is trying to delete routes from the Packet Forwarding Engine, but it can't because the routes aren't there. 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 can't add the routes. Later, when the Routing Engine tries to remove the routes, the prefix it’s looking for is unknown.

PFE: SHEAF: possible leak

Possible FPC SHEAF memory leak.

PFE: SRCHIP-SRAM parity error

The FPC SRCHIP has detected an SRAM parity error.

PFE:%PFE- PIO Read error.

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

PFE:.*clock error.*

Clock error reported on PFE board.

PFE:.*DFW: jtree cutover failed.*

Firewall filter configuration cannot be applied due to insufficient amount of contiguous memory on the sram.

PFE:.*mrvl_brg_port_stg_cist_init.*

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

PFE:.*ICHIP:.*New packet errors in WO HDRF, iwo_hdrf_poll_stats.*

Potential ICHIP stream problem possibly due to IFL flooding. Potential match with PR/289104 -- may need software upgrade.

PFE:.*RCHIP.*: SRAM parity error.*

SRAM parity error detected on FPC RCHIP.

PFE:.SFP receive power low warning

SFP receive power low warning.

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.

PFE:Errors ucode data error

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

PFE:Failed to find MC RT_NH entry:.*

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

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 and/or replacement. It may also indicate a false alarm thrown by the SIB/FPC.

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

This message reports that ICHIP Queued traffic in a physical queue is not being transmitted. When this condition is seen, the router will automatically change the COS configuration for the queue in order to force the queue to empty. The COS parameters will then be restored again after one second.

PFE:ICHIP(.*)_REG_ERR:.*

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

PFE:MQCHIP timed out waiting for phy_stream

The "timed out waiting for phy_stream" syslog 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.

PFE:MQCHIP(.) FI Reorder cell timeout

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

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.

PFE:PPE PPE HW Fault Trap

A trap occurred when microcode attempted to interpret data past the end of the packet. This can also been seen in connection with this syslog message: fpc1 LU 1 PPE_12 Errors lmem addr error

PFE:Route TCAM rows could not be redirected on device.*

The TCAM error messages listed indicate a permanent non-fixable error with TCAM, if they persist after rebooting the EX Switch or Virtual Chassis (VC). These errors are TCAM hardware issues on this FPC and are not harmless. ACLs will be unreliable on this FPC.

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 syslog 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."

PFE:SRCHIP(.): RKME int_status 10x100

RKME is a key match engine located in the FPC SRCHIP/RCHIP hardware. The RKME engine received the error interrupt shown.

PFE_PACKET_DISCARD_ERROR

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

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.

problem-event-ichipfcheck

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

problem-event-l2cacheerror

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-nfabcrcerror

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

Reboot reason(s): 0x2: watchdog

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

RMON_EVENT_fpc_high_cpu_utilization

High CPU utilization on FPC.

RPD_ABORT

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

RPD_ASSERT

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

RPD_BGP_NEIGHBOR_STATE_CHANGED

During the BGP negotiation with the local router, the state of the indicated BGP neighbor (peer) changed as indicated. The ESTABLISHED state is the final state in the neighbor negotiation.

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_PROFILE_FAILED

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

RPD_DYN_CFG_GET_SNAPSHOT_FAILED

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

RPD_DYN_CFG_PDB_OPEN_FAILED

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

RPD_DYN_CFG_REGISTER_FAILED

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

RPD_DYN_CFG_SCHEMA_OPEN_FAILED

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

RPD_DYN_CFG_SDB_OPEN_FAILED

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

RPD_ISIS_ADJDOWN

An IS-IS adjacency with the indicated neighboring router was terminated. The local router will no longer exchange routing information with, or direct traffic to, the neighboring router.

RPD_ISIS_OVERLOAD

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

RPD_KRT_Q_RETRIES

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

RPD_OS_MEMHIGH

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

RPD_RSVP_NBRDOWN

The RSVP neighbor to the indicated address was terminated.

RPD_TASK_FORK

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

RT_SCREEN_UDP

A UDP attack category.

RTLOGD_EVLIB_FAILURE

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

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

SAVAL_RTSOCK_FAILURE

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

SERVICED_CLIENT_DISCONNECTED

The remote client closed the connection or stopped responding.

SERVICED_COMMAND_FAILED

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

SERVICED_EVENT_FAILED

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

SERVICED_INTERNAL_INCONSISTENCY

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

SERVICED_NETWORK_FAILURE

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

SERVICED_PID_FILE_UPDATE

As a 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_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_IO

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

SERVICED_STDLIB_FAILURE

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

SNMP_RTSLIB_FAILURE

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

SNMPD_RMONFILE_FAILURE

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

SNMPD_SOCKET_FATAL_FAILURE

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

SPD_DAEMONIZE_FAILED

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

SPD_GEN_NUM_FAIL

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

SYSTEM: Alarm set: Temp Too Warm

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

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

"Scheduler Oinker" messages seen on console at various instances with various mPIM combinations.

SYSTEM:.*cm_read_i2c errno is 5.*

The chassis manager event message results from an error in calculating the DC power budget for POE interfaces.

SYSTEM:.*snp_igmp_io_flood: relay failed.*

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

SYSTEM:Alarm set Host ECC single bit parity error

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

SYSTEM:cm_ff_ifd_disable: fast failover disabled

The chassism process could not forward traffic as expected.

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 keepalives being sent from the Backup Routing Engine.

TASK_SYSTEM

A system call made by this process failed.

UI_DBASE_REBUILD_FAILED

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

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.

UTMD_MALLOC_FAILURE

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

VCCPD_PROTOCOL_LSPCKSUM

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

VRRPD_MISSING_VIP

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

WEB_MEMORY_ALLOC

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

WEB_SOCKET

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

WEBFILTER_REQUEST_NOT_CHECKED

The Web filtering failed to check a Web request.