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

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes
Table 1: Events Detected by AI-Scripts (continued)
EVENT ID
RPD_ASSERT
RPD_ASSERT_SOFT
RPD_BGP_NEIGHBOR_STATE_CHANGED
RPD_DYN_CFG_BAD_REQ_OPCODE
RPD_DYN_CFG_BUSY_SIGNAL_FAILED
RPD_DYN_CFG_GET_PROF_NAME_FAILED
RPD_DYN_CFG_GET_PROFILE_FAILED
RPD_DYN_CFG_GET_SES_STATE_FAILED
RPD_DYN_CFG_GET_SNAPSHOT_FAILED
RPD_DYN_CFG_PDB_CLOSE_FAILED
RPD_DYN_CFG_PDB_OPEN_FAILED
RPD_DYN_CFG_PROCESSING_FAILED
RPD_DYN_CFG_REGISTER_FAILED
RPD_DYN_CFG_REQUEST_ACK_FAILED
24
DESCRIPTION
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.
The source code for the routing protocol process (rpd) includes internal self-
consistency checks. A check failed at the indicated line number in the
indicated source file, but the instance of rpd that was using the indicated
binary and had the indicated process ID (PID) continued running. The
process created a diagnostic core dump for analysis by technical support
personnel.
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.
The routing protocol process (rpd) received a dynamic configuration request
with an unexpected operation code.
The routing protocol process (rpd) failed to notify dynamic configuration
clients about its availability to process dynamic configuration requests.
The routing protocol process (rpd) tried to get the profile name from the
session snapshot and failed.
The routing protocol process (rpd) tried to load a profile from the database
and failed.
The routing protocol process (rpd) failed to get the session state from the
session snapshot.
The routing protocol process (rpd) tried to load client session data from the
database and failed.
The routing protocol process (rpd) tried to close the profile database and
failed.
The routing protocol process (rpd) tried to open the profile database and
failed.
The routing protocol process (rpd) tried to process dynamic configuration
and failed.
The routing protocol process (rpd) tried to register with the dynamic
configuration subsystem and failed.
The routing protocol process (rpd) tried to ACK a dynamic configuration
request and failed.
©
Copyright 2010, Juniper Networks, Inc.