Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1 Release Note
  1. Manuals
  2. Brands
  3. Juniper Manuals
  4. Software
  5. ADVANCED INSIGHT SCRIPTS 2.5 - S REV 1
  6. Release note
Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1 Release Note

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

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
ADVANCED INSIGHT SCRIPTS (AI-SCRIPTS)
2.5
RELEASE NOTES
6 October 2010
Revision 1
Contents
©
Copyright
2010, Juniper Networks, Inc.
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/.
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
1

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1 and is the answer not in the manual?

Questions and answers

Related Manuals for Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1

Summary of Contents for Juniper ADVANCED INSIGHT SCRIPTS 2.5 - RELEASE NOTES REV 1

  • Page 1: Table Of Contents

    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...
  • Page 2 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   © Copyright 2010, Juniper Networks, Inc.

  • Page 3: Summary Of Release 2.5 Features

    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. © Copyright 2010, Juniper Networks, Inc.
  • Page 4 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. © Copyright 2010, Juniper Networks, Inc.

  • Page 5: Events Detected By Ai-Scripts

    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. © Copyright 2010, Juniper Networks, Inc.
  • Page 6 AV_PATTERN_KL_CHECK_FAILED The device is unable to use the Kaspersky pattern file. The error message provides information to give to Juniper Networks technical support. AV_PATTERN_TOO_BIG The pattern file size specified in the server initialization file (server.ini) exceeds the maximum prescribed limit.
  • Page 7 (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 register for the indicated F chip and link on the indicated Control Board (CB). © Copyright 2010, Juniper Networks, Inc.
  • Page 8 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 indicated reason. © Copyright 2010, Juniper Networks, Inc.
  • Page 9 (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 (chassisd) first tried to power it on, and the power-up operation timed out. © Copyright 2010, Juniper Networks, Inc.
  • Page 10 (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 (MAC) address for the indicated fabric interface because of an internal error. © Copyright 2010, Juniper Networks, Inc.
  • Page 11 (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. © Copyright 2010, Juniper Networks, Inc.
  • Page 12 (field-replaceable unit, for FRU). CONNECTION_CHASSISD_FAIL The alarm process (alarmd) was unable to connect to the chassis process (chassisd). CONNECTION_CRAFTD_FAIL The alarm process (alarmd) was unable to connect to the craft process (craftd). © Copyright 2010, Juniper Networks, Inc.
  • Page 13 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. © Copyright 2010, Juniper Networks, Inc.
  • Page 14 This condition occurs when STP cannot derive the base MAC address of the system. EVENTD_EVENT_SEND_FAILED Junos processes can request that the event processing process (eventd) notify them when a specific event occurs. eventd could not send an event notification for the indicated reason. © Copyright 2010, Juniper Networks, Inc.
  • Page 15 ICCPD_OPEN_ERROR The interchassis communication process (iccpd) could not initialize. IDP_DAEMON_INIT_FAILED An attempt to start the IDP policy daemon failed because an error was encountered during initialization. © Copyright 2010, Juniper Networks, Inc.
  • Page 16 Non-stop routing replication message acknowledgment received by backup ACK message Routing Engine. KERNEL:GENCFG: op 2 (Gencfg Blob) failed.* Kernel error message generated because it does not have a handler for a certain GENCFG blob message. © Copyright 2010, Juniper Networks, Inc.
  • Page 17 L2CPD_PPM_WRITE_ERROR The Layer 2 Control Protocol process (l2cpd) could not write a message on the pipe to the periodic packet management process (ppmd). © Copyright 2010, Juniper Networks, Inc.
  • Page 18 LIBJSNMP_NS_LOG_EMERG SNMP errors with LOG_EMERG as severity. LIBMSPRPC_CLIENT_INIT_FAILED A Junos process (mspinfo) could not establish initialization of the RPC client. LIBMSPRPC_CLIENT_KCOM_FAILED A Junos process (mspinfo) could not establish initialization of the KCOM subsystem. © Copyright 2010, Juniper Networks, Inc.
  • Page 19 The local policy decision function process (lpdfd) failed to register with the dynamic configuration subsystem. LPDFD_DYN_SDB_OPEN_FAILED The local policy decision function process (lpdfd) failed to open the session database. LPDFD_PCONN_SERVER The local policy decision function process (lpdfd) pconn server failed to initialize. © Copyright 2010, Juniper Networks, Inc.
  • Page 20 PFE: HSL2–HSL2 detected fatal error The FPC detected a fatal HSL2 error. PFE: I-CHIP New illegal link errors in WO DESRD Potential ICHIP stream problem possibly due to IFL flooding. Potential match with PR/289104—may need software upgrade. © Copyright 2010, Juniper Networks, Inc.
  • Page 21 Any Packet Forwarding Engine SDRAM ECC error that occurs in conjunction with a system exception message, for example: router-name fpc0 ADPC: detected 1 DDR SDRAM Single-bit ECC errors in the last 30 seconds. PFE: SHEAF: possible leak Possible FPC SHEAF memory leak. © Copyright 2010, Juniper Networks, Inc.
  • Page 22 The fabric connection to the ingress FPC is reporting a bad connection. RDD_EVLIB_CREATE_FAILURE The redundant interfaces process (rdd) could not create a context used for handling all asynchronous events (such as timers and message availability). © Copyright 2010, Juniper Networks, Inc.
  • Page 23 Remote monitoring event reporting high heap utilization on SSB. RPD_ABORT The routing protocol process (rpd) terminated because of an internal error. RPD_ACTIVE_TERMINATE After receiving multiple termination requests, the routing protocol process (rpd) exited without performing the indicated cleanup tasks. © Copyright 2010, Juniper Networks, Inc.
  • Page 24 The routing protocol process (rpd) tried to process dynamic configuration and failed. RPD_DYN_CFG_REGISTER_FAILED The routing protocol process (rpd) tried to register with the dynamic configuration subsystem and failed. RPD_DYN_CFG_REQUEST_ACK_FAILED The routing protocol process (rpd) tried to ACK a dynamic configuration request and failed. © Copyright 2010, Juniper Networks, Inc.
  • Page 25 The JSR log daemon could not create a version of itself to run in the background as a daemon. RTLOGD_EVLIB_FAILURE The JSR log daemon called the indicated event library function. The function failed with the indicated error. © Copyright 2010, Juniper Networks, Inc.
  • Page 26 As a part of normal startup, the services PICs process (serviced) locks a file and writes its process ID (PID) into it. It could not write to the file. SERVICED_RTSOCK_SEQUENCE The services PICs process (serviced) encountered a sequence error while receiving messages from the routing socket library. © Copyright 2010, Juniper Networks, Inc.
  • Page 27 The system is indicating that the sensor on an EX FPC is exceeding the temperature threshold. SYSTEM: Keepalive timeout of *. Assuming RE The backup Routing Engine assumed mastership due to an Routing Engine mastership. keepalive timeout. © Copyright 2010, Juniper Networks, Inc.
  • Page 28 The vccpd link-state database is full and no additional memory can be allocated for it. VRRPD_MISSING_VIP The indicated interface received a Virtual Routing Redundancy protocol (VRRP) packet for the indicated VRRP group in which the indicated Virtual IP address was missing. © Copyright 2010, Juniper Networks, Inc.
  • Page 29 WEB_SOCKET The Web management process (httpd) could not create a socket, for the indicated reason. WEBFILTER_CACHE_NOT_ENABLED The category cache Web filter failed to enable. WEBFILTER_REQUEST_NOT_CHECKED The Web filtering failed to check a Web request. © Copyright 2010, Juniper Networks, Inc.

  • Page 30: Current Software Release

    755 to 733 to allow JMB files to be written using the following command: chmod 733 jmb-archives4 To confirm directory permissions, use the following command: ls –l drwx-wx-wx 2 root root 4096 Sep 16 12:01 jmb-archives4 © Copyright 2010, Juniper Networks, Inc.

  • Page 31: Issues Fixed Since Last Release

    Any event script that captures an event with two or Junos OS Release 9.5R2 crash. (PR 428256) more attributes may cause eventd to crash. • Junos OS Release 9.4R3 • Junos OS Release 9.6R1 © Copyright 2010, Juniper Networks, Inc.

  • Page 32: Installing Ai-Scripts

    2. Log in to the Juniper Networks authentication system using the username and password supplied by Juniper Networks. To download the software, you must have a service contract and an access account. If you do not have an access account, complete the registration form at the Juniper Networks Web site, https://www.juniper.net/registration/Register.jsp. ©...

  • Page 33: Ai-Scripts Install Package Versioning

    The automated AI-Scripts installation process requires the following key tasks: Install and set up Junos Scope 9.0 or later. See the Junos Scope Software User Guide. Install AIM. See the AIS User Guide. Set up AIM settings. See the AIS User Guide. © Copyright 2010, Juniper Networks, Inc.

  • Page 34: Automatically Installing Ai-Scripts

    NOTE: If you are manually installing to a device that communicates with Junos Space or Service Now, your login credentials must allow discovery of devices in Junos Space. This procedure includes the configuration differences required for configuring the location for JMBs on a Junos Space device. © Copyright 2010, Juniper Networks, Inc.
  • Page 35 Transient changes are configuration changes made by commit scripts that do not appear in the configuration (except with a special command). Apply the juniper-ais group: user@host#set apply-groups juniper-ais g. (Optional) Configure the load-scripts-from-flash option: user@host#set groups juniper-ais system scripts load-scripts-from-flash © Copyright 2010, Juniper Networks, Inc.
  • Page 36 { 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; © Copyright 2010, Juniper Networks, Inc.
  • Page 37 { 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.

  • Page 38: Ai-Scripts Commands

    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. © Copyright 2010, Juniper Networks, Inc.

  • Page 39: Junos Documentation And Release Notes

    Juniper Networks website at http://www.juniper.net/techpubs/. Juniper Networks supports a technical book program to publish books by Juniper Networks engineers and subject matter experts with book publishers around the world. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration using the Junos operating system (Junos OS) and Juniper Networks devices.

  • Page 40: Opening A Case With Jtac

    Use the Case Management tool in the CSC at http://www.juniper.net/cm/. Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico). For international or direct-dial options in countries without toll-free numbers, see http://www.juniper.net/support/requesting-support.html Revision History 6 October 2010—Advanced Insight Scripts (AI-Scripts) 2.5R1 © Copyright 2010, Juniper Networks, Inc.
  • Page 41 Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Table of Contents