Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1 Release Note page 16

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes
Table 1: Events Detected by AI-Scripts (continued)
EVENT ID
IDP_INTERNAL_ERROR
IKED_CFG_PATRICIA_ERROR
JCS_BBD_LOAD_FAILURE
JCS_BBD_LOCAL_MISMATCH
JCS_BBD_NOT_FOUND
JCS_BBD_NOT_VALID
JCS_BBD_PARSE_ERROR
JCS_BBD_PEER_MISMATCH
JCS_KERNEL_RSD_LINK_DOWN
JCS_MM_COMMUNICATION_ERROR
JCS_READ_BANDWIDTH_ERROR
JCS_READ_BBD_ERROR
JCS_SWITCH_COMMUNICATION_ERROR
JSRPD_DAEMONIZE_FAILED
JSRPD_EVLIB_EXIT_FAILURE
JSRPD_SOCKET_LISTEN_FAILURE
JSRPD_SOCKET_RECV_HB_FAILURE
KERNEL:.*jsr_prl_recv_ack_msg.* received PRL
ACK message
KERNEL:GENCFG: op 2 (Gencfg Blob) failed.*
16
DESCRIPTION
The IDP daemon encountered an internal error.
A call to a Patricia tree library function returned an error.
The JCS process (jcsd) could not load blade bay data for the specified
blade.
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.
The blade bay data was not found for the specified blade.
The blade bay data for the specified blade is invalid.
The blade bay data for the specified blade did not parse correctly.
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.
The JCS process (jcsd) has disabled kernel RSD communication for the
specified reason.
The JCS process (jcsd) could not send an SNMP request to the
Management Module because of the indicated error.
The indicated error occurred when attempting to read the current switch
bandwidth.
The indicated error occurred when attempting to read the current blade bay
data via a sysctl call.
The JCS process (jcsd) could not send an SNMP request to the indicated
Switch Module because of the indicated error.
The Juniper Services Redundancy Protocol process (jsrpd) could not create
a version of itself to run in the background as a daemon.
The Juniper Services Redundancy Protocol process (jsrpd) returned from
an event loop, which it should never do.
The Juniper Services Redundancy Protocol process (jsrpd) could not
successfully listen on a socket.
The Juniper Services Redundancy Protocol process (jsrpd) was not
successfully received on a socket.
Non-stop routing replication message acknowledgment received by backup
Routing Engine.
Kernel error message generated because it does not have a handler for a
certain GENCFG blob message.
©
Copyright 2010, Juniper Networks, Inc.