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

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes
Table 1: Events Detected by AI-Scripts (continued)
EVENT ID
AUTHD_SERVER_INIT_LISTEN_FAIL
AUTHD_SETSOCKOPT_FAILED
AUTHD_SOCKET_FAILED
AUTOCONFD_AUTH_NO_MEM
AUTOD_RECV_FAILURE
AUTOD_SEND_FAILURE
AUTOD_SOCKET_CREATE_FAILURE
AV_PATTERN_KL_CHECK_FAILED
AV_PATTERN_TOO_BIG
AV_PATTERN_WRITE_FS_FAILED
BFDD_READ_ERROR
BFDD_WRITE_ERROR
BOOTPD_HWDB_ERROR
CFMD_RTSOCK_OPEN_FAILURE
CHASSISD_BUS_DEVICE_OPEN_FAILURE
CHASSISD_CFEB_POWER_FAILURE
CHASSISD_CLOCK_FAILURE
CHASSISD_CMB_READBACK_ERROR
6
DESCRIPTION
The generic authentication service process (authd) could not initialize
listening on the server for the indicated socket.
The generic authentication service process (authd) could not set socket
options during the indicated operation.
The generic authentication service process (authd) could not open a
socket during the indicated operation.
The memory allocation (malloc) for username authentication failed.
The autoinstallation process (autod) received the indicated error when it
tried to receive data on a socket.
The autoinstallation process (autod) receives the indicated error when it
sends data on a socket.
The autoinstallation process (autod) receives the indicated error when it
creates a socket.
The device is unable to use the Kaspersky pattern file. The error message
provides information to give to Juniper Networks technical support.
The pattern file size specified in the server initialization file (server.ini)
exceeds the maximum prescribed limit.
The device is unable to save the contents of an antivirus pattern file to the
file system.
The bidirectional forwarding detection process (bfdd) could not read a
message available on the indicated type of pipe.
The bidirectional forwarding detection process (bfdd) could not write a
message to the indicated type of pipe.
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.
The connectivity fault management process (cfmd) could not successfully
open a routing socket to the kernel, for the indicated reason.
The chassis process (chassisd) could not open the indicated bus device,
for the indicated reason.
The chassis process (chassisd) could not turn on or turn off the power to
the indicated Compact Forwarding Engine Board (CFEB).
The chassis process (chassisd) determined that the indicated clock source
failed in the indicated way.
The chassis process (chassisd) could not read back information from the
Chassis Management Bus (CMB) about the indicated component (field-
replaceable unit, or FRU).
©
Copyright 2010, Juniper Networks, Inc.