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

ADVANCED INSIGHT SCRIPTS (AI-SCRIPTS)

2.5 RELEASE NOTES

6 October 2010 Revision 1

These release notes accompany Release 2.5R1 of the Advanced Insight Scripts (AI-Scripts). AI-Scripts are Junos event scripts used to enable Juniper Networks J Serie s, M Serie s, MX Series, T Series, EX Series, and SRX Series devices to:

 React to specific incident events that occur and provide relevant information for analysis  Periodically collect data on events that can be used to predict and prevent risks in the future  Package all incident and intelligence event data into a structured format, such as a Juniper

Message Bundle (JMB), and send it to an archive location to be collected and displayed by the Advanced Insight Manager (AIM) application

Contents

You can also find these release notes, the Advanced Insight Scripts (AI-Scripts) Release Notes, and the AIS User Guide on the Juniper Networks Technical Publications Web page, at

http://www.juniper.net/techpubs/software/management/ais/

Summary of Release 2.5 Features..................................................................................................3

AI-Scripts 2.5R1 ........................................................................................................................3

AI-Scripts Operation.........................................................................................................................3

AI-Script Modes................................................................................................................................3

Events Detected by AI-Scripts.........................................................................................................5

Current Software Release..............................................................................................................30

Outstanding Issues ........................................................................................................................30

Issues Fixed Since Last Release...................................................................................................31

Junos PRs That Affect AI-Scripts...................................................................................................31

Installing AI-Scripts ........................................................................................................................32

AI-Scripts System Requirements ............................................................................................32

AI-Scripts/AIM Compatibility....................................................................................................32

AI-Scripts Installation Methods................................................................................................32

Downloading AI-Scripts Install Packages................................................................................32

AI-Scripts Install Package Versioning .....................................................................................33

AI-Scripts Install Locations on Devices...................................................................................33

Automatically Installing AI-Scripts Overview...........................................................................33

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes

Automatically Installing AI-Scripts ...........................................................................................34

Manually Configuring and Installing AI-Scripts on Devices.....................................................34

AI-Scripts Commands....................................................................................................................38

Installing an AI-Scripts Package....................................................................................................38

Upgrading an AI-Scripts Package...........................................................................................38

Deleting an AI-Scripts Package...............................................................................................38

Rolling Back an AI-Scripts Package........................................................................................38

Not Saving Copies of AI-Scripts Package Files During Installation ........................................38

Removing AI-Scripts Packages After Installation....................................................................38

JUNOS Documentation and Release Notes..................................................................................39

Requesting Technical Support.......................................................................................................39

Self-Help Online Tools and Resources...................................................................................39

Opening a Case with JTAC.....................................................................................................40

Revision History.............................................................................................................................40



2 Copyright

2010, Juniper Networks, Inc.

Summary of Release 2.5 Features

This section describes key features of the current AI-Scripts release.

AI-Scripts 2.5R1

Features

 Empty FPC heap / jtree attachments suppressed in AI-Scripts. (PR 540766)  Remove trend-data section from AI-Scripts problem event-scripts. (PR 556345)  Apply AI-Scripts JMB file permissions workaround for Junos PR/513414. (PR 556607)

Event-Scripts

 Added AI-Script event for mrvl_brg_port_stg_cist_init. (PR 545325)  Added AI-Script event for cm_read_i2c errno:5. (PR 545466)  Added AI-Script event for /kernel: ifd_request: RTM_ID <48> should only do pointchanges.

(PR 545468)  Added AI script for event %KERN-3: jsr_prl_recv_ack_msg(). (PR 556009)

Resolved Issues

Summary of Release 2.5 Features

 Trim the link for the KB note for the event pfestat_req_receive. (PR 545464)  AI-Scripts workaround for JUNOS PR/520377, which generates duplicate cha ssis-module

subtags in Routing Engine section on M320 and some EX Series platforms. (PR 548758)  Modify the problem description field in problem-event-mrvl_brg_port_cist_init.slax to include

the related KB link. (PR 549035)

 Trim the KB link for AI-Scripts problem-event-GenCfgBloberror.slax. (PR 551498)  AI-Scripts problem events for protocol-neighbor-related issues in BGP, OSPF, RSVP, and

ISIS have been removed. (PR 555122)  Modify attachments in AI-Scripts event-script problem-event-ichipregerr.slax. (PR 555489)

AI-Scripts Operation

AI-Scripts do the following tasks:  React to specific incident events that occur on devices and provide relevant information about

the problems for analysis

 Periodically collect data on events that can be used to predict and prevent risks in the future  Package all incident and intelligence event data into a structured format, such as a Juniper

Message Bundle (JMB), and send it to a remote archive location so that it can be collected

and displayed by Advanced Insight Manager (AIM)

AI-Script Modes

AI-Scripts operate in two distinct modes:  Reactive (incident-driven)—A trigger event occurs and is detected on a device. An AI-Script

is executed. An AI-Script builds a Juniper Message Bundle (JMB) with event and router data,

and sends it to a designated AIM archive location.

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes

Each AI-Script corresponds to a specific device event. The list of device problem events that

can be detected and reported will evolve over time. See Table 1 on page 3.  Proactive (intelligence-driven)—AI-Scripts monitor device system resources for fluctuations

that could signal a future problem. AI-Scripts collect intelligence data for analysis. A tailored

AI-Script builds a JMB with intelligence data and sends it to a designated remote AIM archive

location.

4 Copyright

2010, Juniper Networks, Inc.

Events Detected by AI-Scripts

Table 1 on page 3 lists the events detected by Release 2.5 of the AI-Scripts.

Table 1: Events Detected by AI-Scripts

EVENT ID

ACCT_MALLOC_FAILURE The accounting statistics process could not allocate memory from the

ACCT_XFER_POPEN_FAIL A failed call to the popen() function when the accounting statistics process

ASP_IDS_INV_CLEAR_QUERY The intrusion detection services (IDS) receives a request to clear

ASP_IDS_INV_CLEAR_QUERY_VER The intrusion detection services (IDS) receives a request to clear

ASP_L2TP_NO_MEM The Layer 2 Tunneling Protocol (L2TP) could not allocate the memory it

DESCRIPTION

heap.

invokes the indicated command to transfer the indicated file.

information from the IDS tables. The request includes the indicated type of query, which the IDS cannot interpret.

information from the IDS tables. The request version number did not match the version number of requests that the IDS can service.

needed to create a flow for the indicated tunnel and session.

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.

ASP_PGCP_IPC_PIPE_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 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 The audit process (auditd) could not create a RADIUS object handle used

for various RADIUS operations.

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 The audit process (auditd) could not create a RADIUS accounting request

for the indicated reason.

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 The generic authentication service process (authd) could not allocate an

authentication object for the indicated reason.

AUTHD_SERVER_INIT_BIND_FAIL The generic authentication service process (authd) could not bind the

server to the address specified.

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

AUTHD_SERVER_INIT_LISTEN_FAIL The generic authentication service process (authd) could not initialize

AUTHD_SETSOCKOPT_FAILED The generic authentication service process (authd) could not set socket

AUTHD_SOCKET_FAILED The generic authentication service process (authd) could not open a

AUTOCONFD_AUTH_NO_MEM The memory allocation (malloc) for username authentication failed. AUTOD_RECV_FAILURE The autoinstallation process (autod) received the indicated error when it

AUTOD_SEND_FAILURE The autoinstallation process (autod) receives the indicated error when it

AUTOD_SOCKET_CREATE_FAILURE The autoinstallation process (autod) receives the indicated error when it

AV_PATTERN_KL_CHECK_FAILED The device is unable to use the Kaspersky pattern file. The error message

DESCRIPTION

listening on the server for the indicated socket.

options during the indicated operation.

socket during the indicated operation.

tried to receive data on a socket.

sends data on a socket.

creates a socket.

provides information to give to Juniper Networks technical support.

AV_PATTERN_TOO_BIG The pattern file size specified in the server ini t ialization file (server.ini)

exceeds the maximum prescribed limit.

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 The bidirectional forwarding detection pr ocess (bfdd) could not read a

message available on the indicated type of pipe.

BFDD_WRITE_ERROR The bidirectional forwarding detection process (bfdd) could not write a

message to the indicated type of pipe.

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 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 The chassis process (chassisd) could not open the indicated bus device,

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_CLOCK_FAILURE The chassis process (chassisd) determined that the indicated clock source

failed in the indicated way.

CHASSISD_CMB_READBACK_ERROR The chassis process (chassisd) could not read back information from the

6 Copyright

Chassis Management Bus (CMB) about the indicated component (fieldreplaceable unit, or FRU).

2010, Juniper Networks, Inc.

Events Detected by AI-Scripts

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CHASSISD_COMMAND_ACK_ERROR The chassis process requested that the indicated component (field-

CHASSISD_COMMAND_ACK_SFM_ERROR The chassis process (chassisd) requires an acknowledgment from each

CHASSISD_FAN_FAILURE The indicated fan or impeller failed. The chassis process (chassisd) raised

CHASSISD_FASIC_FTOKEN_ERROR The chassis process (chassisd) detected an underflow or overflow error on

CHASSISD_FASIC_FTOKEN_INIT_ERROR The chassis process (chassisd) encountered an error while initializing

DESCRIPTION

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 performed any additional action necessary to guarantee that the FRU came online.

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.

an alarm and increased the speed of the remaining fans (and impellers, if applicable) to full speed.

the indicated F chip on the indicated Control Board (CB).

memory at the indicated address for 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_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 The chassis process (chassisd) detected that F chips were not yet

initialized on the Control Board (CB).

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 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 The indicated routine failed with a read error at the indicated address and

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CHASSISD_FASIC_PIO_WRITE_ERROR The indicated routine failed with a write error at the indicated address and

CHASSISD_FASIC_PLL_ERROR The chassis process (chassisd) could not lock a phased-lock loop (PLL) for

CHASSISD_FASIC_RESET_ERROR The chassis process (chassisd) could not reset the indicated F chip on the

CHASSISD_FASIC_SRAM_ERROR The chassis process (chassisd) detected that SRAM failed to initialize for

CHASSISD_FCHIP_CONFIG_MD_ERROR The chassis process (chassisd) detected an invalid number of Md chips for

CHASSISD_FCHIP_HSR_ERROR The chassis process (chassisd) detected an error in the high-speed

DESCRIPTION

the indicated F chip on the indicated Control Board (CB).

indicated Control Board (CB).

the indicated F chip on the indicated Control Board (CB).

the indicated F chip, Packet Forwarding Engine, and Flexible PIC Concentrator (FPC).

receiver (HSR) subsystem for the F chip with the indicated characteristics.

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 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 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 The indicated routine failed with a read error at the indicated address and

CHASSISD_FCHIP_PIO_WRITE_ERROR The indicated routine failed with a write error at the indicated address and

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 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 The high-speed transmitter (HST) read routine failed at the indicated

address on an F-chip register.

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 The chassis process (chassisd) could not open the indicated file for the

8 Copyright

indicated reason.

2010, Juniper Networks, Inc.

Events Detected by AI-Scripts

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CHASSISD_FM_ERROR During execution of the indicated fabric management routine, the indicated

CHASSISD_FM_ERROR_SIB_L_FB_HSR In a routing matrix, packets traverse both electrical and optical media as

CHASSISD_FM_ERROR_SIB_L_FB_SMF In a routing matrix, packets traverse both electrical and optical media as

DESCRIPTION

error occurred between the indicated Switch Interface Board (SIB) and the indicated Packet Forwarding Engine on the indicated Fle xible PIC Concentrator (FPC).

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.

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 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 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_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_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 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 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_GBUS_NOT_READY The GBUS was not ready when the chassis process (chass isd) first tried to

power it on, and the power-up operation timed out.

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CHASSISD_GBUS_READBACK_ERROR There was an error when the chassis process (chassisd) tried to read back

CHASSISD_HSR_FIFO_ERROR A first-in, first-out (FIFO) read error occurred during execution of the

CHASSISD_I2C_BAD_IDEEPROM_FORMAT The chassis process (chassisd) determined that the ID EEPROM format

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

CHASSISD_I2CS_READBACK_ERROR The chassis process (chassisd) cannot read back information from the I2C

CHASSISD_IFDEV_DETACH_FPC The chassis process (chassisd) detached the interface devices for all PICs

DESCRIPTION

information from the GBUS on the indicated component (field-replaceable unit, or FRU).

indicated routine on the indicated high-speed receiver (HSR).

specified for the indicated type of hardware component (field-replaceable unit, or FRU) is not valid for it.

device.

slave (I2CS) about the indicated component (field-replaceable unit, or FRU).

on the indicated Flexible PIC Concentrator (FPC).

CHASSISD_IFDEV_DETACH_PIC The chassis process (chassisd) detached the interface devices for the

indicated PIC.

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 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 T he chassis process (c hassisd) dropped an interprocess communication

(IPC) message because the message queue had already reached maximum capacity.

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 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_MAC_ADDRESS_ERR 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_ERR The chassis process (chassisd) could not obtain a media access control

10 Copyright

(MAC) address for the indicated fabric interface because of an internal error.

2010, Juniper Networks, Inc.

Events Detected by AI-Scripts

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CHASSISD_MALLOC_FAILURE The chassis process (chassisd) could not allocate memory. chassisd tried

CHASSISD_MBE_DETECTED A multibit ECC parity error was detected in the Routing Engine DRAM. CHASSISD_OVER_TEMP_CONDITION The temperature of one or more components (field-replaceable units, or

CHASSISD_OVER_TEMP_SHUTDOWN_TIME The chassis process (chassisd) shut down the device because the

CHASSISD_PEM_OVERLOAD The indicated power entry module (PEM) reported an output voltage

DESCRIPTION

to continue functioning, but the lack of memory usually causes the process to fail. An administrator needs to restart it.

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.

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.

overload condition.

CHASSISD_PEM_VOLTAGE The indicated power entry module (PEM) reported a problem with its

output voltage.

CHASSISD_PIC_HWERROR The indicated PIC experienced a hardware error. The chassis process

(chassisd) did not bring the PIC online.

CHASSISD_POWER_CONDITION The temperature of the indicated Routing Engine exceeded the indicated

temperature, which is the upper of two thresholds.

CHASSISD_PSU_ERROR The chassis process (chassisd) detected the indicated error condition for

the indicated power supply unit (PSU).

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 The chassis process (chassisd) detected the input voltage/warning fault

condition for the indicated power supply unit (PSU).

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

condition.

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 The indicated power supply unit (PSU) reported a problem with its output

voltage.

CHASSISD_RE_OVER_TEMP_CONDITION The temperature of the indicated Routing Engine exceeded the indicated

temperature, which is the upper of two thresholds.

Advanced Insight Scripts (AI-Scripts) 2.5 Release Notes

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CHASSISD_RE_OVER_TEMP_SHUTDOWN The chassis process (chassisd) performed the indicated action because

CHASSISD_RE_OVER_TEMP_WARNING The temperature of the indicated Routing Engine exceeded the indicated

CHASSISD_SBE_DETECTED Too many single-bit correctable ECC parity errors were detected in

CHASSISD_SIB_INVALID_SLOT The chassis process (chassisd) detected the presence of a Switch

CHASSISD_SMB_INVALID_PS The chassis process (chassisd) could not set the status (enabled or

DESCRIPTION

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.

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.

Routing Engine DRAM.

Interface Board (SIB) in an invalid slot. The SIB remains offline.

disabled) for a power supply because it received the indicated power supply status code, which is invalid.

CHASSISD_SMB_IOCTL_FAILURE The indicated ioctl() operation failed at the indicated address on the s ystem

management bus (SMB).

CHASSISD_SMB_READ_FAILURE A read() operation failed at the indicated address on the system

management bus (SMB).

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 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 The chassis process (chassisd) exited unexpectedly and reported the

indicated error.

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 The chassis process (chassisd) could not initialize the voltage sensor for

the indicated component (field-replaceable unit, for FRU).

CONNECTION_CHASSISD_FAIL The alarm process (alarm d) was unable to connect to the chassis process

(chassisd).

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

12 Copyright

(craftd).

2010, Juniper Networks, Inc.

Events Detected by AI-Scripts

Table 1: Events Detected by AI-Scripts (continued)

EVENT ID

CONNECTION_RTLOGD_FAIL The alarm proc ess (alarmd) was unable to connect to the Juniper

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

COSD_GENCFG_WRITE_FAILED The class-of-service (CoS) process (cosd) uses GENCFG to read and

COSD_MALLOC_FAILED The class-of-service (CoS) process (cosd) could not dynamically allocate

COSD_RTSOCK_LIB_ERR The class-of-service (CoS) process (cosd) uses rtsock library for reading

COSD_RTSOCK_WRITE_FAILED The class-of-service (CoS) process (cosd) uses rtsock to read/write data

COSD_UNEXPECTED_EXIT The class-of-service (CoS) process (cosd) waits for the event notifications

DESCRIPTION

Networks J Series Services Router (JSR) log process (rtlogd).

message.

write data from the kernel. If the write fails, the kernel returns an error.

memory, for the indicated reason.

and writing data from and to kernel. The specified error occurred while using rtsock library to read/write data.

from kernel. If the write fails kernel returns an error.

and processes the events that it is registered for. There was an error during event-handling initialization.

COSD_UNKNOWN_TRANSLATION_TABLE The class-of-service (CoS) process (cosd) did not recognize the indicated

translation table type from the rtsock library. Daemon Crash A Junos daemon crash occurred with a core dump. 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 The interface process (dcd) encountered an error while trying to load the

kernel interface configuration over the routing socket. DCD_PARSE_STATE_EMERGENCY The interface process (dcd) encountered an unhandled internal state

during interface parsing. 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 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 When DCD is allocating heap memory, it uses a private memory allocato r

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.

+ 28 hidden pages

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

Specifications and Main Features

Frequently Asked Questions

User Manual