User manual JUNIPER NETWORKS ADVANCED INSIGHT SCRIPTS 2.5 RELEASE NOTES REV 1

[. . . ] 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 Series, M Series, 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 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/. Contents Summary of Release 2. 5 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 AI-Scripts 2. 5R1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 AI-Scripts Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] The Layer 2 Tunneling Protocol process (l2tpd) could not create a context for handling asynchronous events. The indicated error occurred while the process using libesptask was connecting to the SNMP master agent. The process using libesptask could not set the size of the kernel receive buffer, which allows it to accept the largest possible packet from the Simple Network Management Protocol (SNMP) master agent. 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. A Junos process could not retrieve the system default IP address from the kernel because the address is not defined there. A Junos process created a child process to execute the indicated command. A Junos process could not perform the indicated operation on the indicated SNMP engine data file. A Junos process could not perform the scan operation on the indicated SNMP engine data file. Various system processes use Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Reliable Data Protocol (RDP) sockets. A Junos process (mspinfo) could not establish initialization of the RPC client. A Junos process (mspinfo) could not establish initialization of the KCOM subsystem. L2CPD_SYSTEM_CALL_FAILED L2TPD_EVLIB_CREATE_FAILED L2TPD_EVLIB_CREATE_FAILED L2TPD_SERVER_START_FAILED LIBESPTASK_SNMP_CONN_PROG LIBESPTASK_SNMP_SOCKOPT_RECVBUF LIBESPTASK_SNMP_SOCKOPT_SENDBUF LIBJNX_DEFAULT_IP_ADDR_NOT_SET LIBJNX_EVLIB_FAILURE LIBJNX_EXEC_SIGNALED LIBJNX_REPLICATE_RCP_ERROR LIBJNX_SNMP_ENGINE_FILE_FAILURE LIBJNX_SNMP_ENGINE_SCAN_FAILURE LIBJNX_SOCKET_FAILURE LIBJSNMP_NS_LOG_EMERG LIBMSPRPC_CLIENT_INIT_FAILED LIBMSPRPC_CLIENT_KCOM_FAILED 18 Copyright© 2010, Juniper Networks, Inc. Events Detected by AI-Scripts Table 1: Events Detected by AI-Scripts (continued) EVENT ID DESCRIPTION LIBMSPRPC_CLIENT_KCOM_NO_IF A Junos process (mspinfo) could not find any configured and active extension-provider interfaces. Remote execution of the command given from the Routing Engine to the PIC failed. Remote execution of the command given from the Routing Engine to the PIC failed. Remote execution of the command given from the Routing Engine to the PIC failed. Remote execution of the command given from the Routing Engine to the PIC failed. An attempt to bind a server socket for receiving client requests failed. An attempt to attach a socket to the management routing instance for communication between the Routing Engine and GGSN-C PICs failed. Unless a new license is installed, the feature will become inactive after the grace period expires. Unless the scale license is upgraded, the license will scale back to the licensed limit after the grace period expires. Strict license enforcement will remain active until a new license is installed. Unless a new license is installed, the feature will become inactive after the license expires. A system call made by the Link Layer Discovery Protocol process (LLDPD) failed. [. . . ] View the configuration: Example Configuration for AIM groups { juniper-ais { system { scripts { commit { allow-transients; file jais-activate-scripts. slax { optional; } } load-scripts-from-flash; } } event-options { destinations { juniper-aim { archive-sites { "ftp://anonymous@10. 7. 0. 124/aimdemo"; } . . . Example Configuration for Junos Space groups { juniper-ais { system { scripts { commit { allow-transients; file jais-activate-scripts. slax { optional; } } } } 36 Copyright© 2010, Juniper Networks, Inc. Installing AI-Scripts interfaces { lo0 { unit 0 { family inet { address 127. 0. 0. 1/32; } } } } event-options { destinations { juniper-aim { archive-sites { "scp://lab@127. 0. 0. 1://var/tmp" password " . . . Install the AI-Scripts package using the following command (see "AI-Scripts Commands" on page 3): user@host# request system scripts add <package-name> 8. Verify that the AI-Scripts are activated: user@host# show groups juniper-ais | display commit-scripts system { scripts { commit { allow-transients; file jais-activate-scripts. slax { optional; } } } } event-options { event-script { file problem-event-pfecrash. slax; file problem-event-dcrash. slax; file intelligence-event-main. slax; file SPD_EVLIB_CREATE_FAILURE. slax; file SPD_DAEMONIZE_FAILED. slax; file RPD_TASK_FORK. slax; . . } destinations { juniper-aim { archive-sites { "ftp://anonymous@10. 7. 0. 124/aidemo"; } } } } Copyright© 2010, Juniper Networks, Inc. 37 Advanced Insight Scripts (AI-Scripts) 2. 5 Release Notes AI-Scripts Commands Installing an AI-Scripts Package on page Upgrading an AI-Scripts Package on page 3 Deleting an AI-Scripts Package on page 3 Rolling Back an AI-Scripts Package on page 3 Not Saving Copies of AI-Scripts Package Files During Installation on page 3 Removing AI-Scripts Packages After Installation on page 3 Installing an AI-Scripts Package To install an AI-Scripts install package on a device, use the following command: user@host> request system scripts add package-name Upgrading an AI-Scripts Package To upgrade an AI-Scripts package, perform steps 1, 7, and 8 of "Manually Configuring and Installing AI-Scripts on Devices" on page 3. Deleting an AI-Scripts Package To delete AI-Scripts from a router, use the following command: user@host> request system scripts delete Rolling Back an AI-Scripts Package After the deletion of an AI-Scripts install package, you can roll back to the last installed package by using the following command: user@host> request system scripts rollback Not Saving Copies of AI-Scripts Package Files During Installation To prevent the installer from saving copies of AI-Scripts package files in the /var/sw/pkg directory, use the following command: user@host> request system scripts add no-copy package-name NOTE: If you use the no-copy option during the jais installation, the jais package cannot be rolled back. You can specify the no-copy option in AIM Device Group settings by selecting the no-copy check box. Removing AI-Scripts Packages After Installation To remove the AI-Script bundle after successful installation, use the following command: user@host> request system scripts add unlink package-name You can specify the unlink option in AIM Device Group settings by selecting the unlink check box. 38 Copyright© 2010, Juniper Networks, Inc. JUNOS Documentation and Release Notes JUNOS Documentation and Release Notes For a list of related JUNOS documentation, see http://www. juniper. net/techpubs/software/junos/ If the information in the latest release notes differs from the information in the documentation, follow the JUNOS Release Notes. [. . . ]