Advanced Insight scripts (AI-Scripts) are specialized operational and event scripts from Juniper Networks that detect events on devices running Junos OS and provide data to analyze the events.

AI-Scripts package data in a structured format called Juniper Message Bundle (JMB) which is retrieved by Junos Space Service Now for display.

Note: AI-Scripts can be installed on devices by using Service Now. For installing AI scripts on multiple devices, we recommend that you use Service Now as Service Now can install AI-Scripts on multiple devices in a single operation. For information about installing AI-Scripts on devices running Junos OS, see Installing an Event Profile on a Device by Using Service Now.

• Testing AI-Scripts Installation
• Generating a Test JMB

1. Navigate to the /var/db/scripts/op folder.

   % cd /var/db/scripts/op

2. Execute the AIS_event_sim.sh script.

   9% ./AIS_event_sim.sh

   The following is a sample of the command output:

   AI-Scripts PROBLEM SIMULATION MENU (AI-Scripts 5.0R5/6.0R3 release)
    ====================================================== 
   1. Hardware Failure
   2. Software Failure
   3. Resource Exhaustion Failure
   4. Daemon crash [WARNING: This test could be service affecting as it kills the daemon]
   5. Unstructured Events
   6. Events that may be triggered on a Backup Routing Engine (platform dependent)
   7. Events added/modified for 4.1R9
   8. Events added/modified for 5.0R3
   9. Events added/modified for 5.0R4/6.0R1
   10. Events added/modified for 5.0R5/6.0R1
   11. Events added/modified for 5.0R6/6.0R3
   Q. Quit
   

   Please enter option [1 - 11,Q]: 3 (Select the type of the event to be triggered)
3. Enter a number from 1 to 11 to simulate an event as indicated against the number. For example, enter 3 to simulate an event caused by resource exhaustion on the device.

   When you enter 3, the events related to resource exhaustion are listed as follows:

   Calling rex-failure . . .
    RESOURCE EXHAUSTION FAILURE MENU 
    ================================ 
   1. ACCT_MALLOC_FAILURE
   2. ASP_L2TP_NO_MEM
   3. AUTOCONFD_AUTH_NO_MEM
   4. CHASSISD_IPC_MSG_DROPPED
   5. L2CPD_SCHED_SLIP
   6. L2CPD_SYSTEM_CALL_FAILED
   7. RPD_ISIS_OVERLOAD
   8. RPD_OS_MEMHIGH
   9. RT_SCREEN_TCP
   10. RT_SCREEN_UDP
   11. RTPERF_CPU_THRESHOLD_EXCEEDED
   12. SNMPD_SUBAGENT_NO_RESOURCES
   13. TASK_OS_MEMHIGH
   14. VCCPD_PROTOCOL_OVERLOAD
   15. CHASSISD_IFDEV_GET_BY_NAME_FAIL
   
   M. Return to Main Menu
   Q. Exit
   Please enter option [1 - 14,M,Q]: 9   ( Select the event to be triggered)
   RT_SCREEN_TCP . . .
   

4. Enter a number to generate a JMB for the corresponding event.

   RT_SCREEN_TCP . . .
   Enter a number to generate a JMB for the corresponding event. For example, enter 9 to generate a JMB for RT_SCREEN_TCP event. 
   

   When you enter a number corresponding to an event, the event is triggered with a renice value of 20 and hence the JMB is generated at a lower priority.

   % ps -alx | grep ais
       0  8550     1 119   8 20  2252  1548 wait   IN    ??    0:00.00 sh /var/db/scripts/op/ais_shell2.sh
       0 38837     1 160   8 20  2392  1764 wait   IN    ??    0:00.30 sh /var/db/scripts/op/ais_jmb_chm.sh 239
       0 42681     1   2   8 20  2252  1548 wait   IN    ??    0:00.01 /bin/sh /var/db/scripts/op/ais_shell.sh
       0 42690 42681   0   4 20  1748   924 fifoor IN    ??    0:00.00 cat /var/db/scripts/op/aisfifo
       0 42691 42681   2  -8 20  2076  1260 piperd IN    ??    0:00.00 grep -e /var/db/scripts/op/ais_
     928 43038 35581   0  -8  0  2068  1260 piperd S+    p0    0:00.00 grep ais
   
   

   On a device, when free disk space available in /var/tmpis between 50% to 75%, AI-Scripts generates the JMB and attachments with an additional message stating that the space has reached the warning limit.

   Jan 13 05:07:34  mx-480-sn root: AIS_PROCESSING: Background process (PID=75938) started for eventID 279
   Jan 13 05:07:37  mx-480-sn cscript: AIS_DATA_AVAILABLE: WARNING: Disk at 14 percent Full
   

   Once the disk space reaches the threshold limit, the JMB generation and the attachments are both dampened.

   Jan 13 05:12:24  mx-480-sn root: AIS_PROCESSING: Background process (PID=75938) completed for eventID 279
   Jan 13 05:14:10  mx-480-sn root: AIS_PROCESSING: Background process (PID=81322) started for eventID 310
   Jan 13 05:14:15  mx-480-sn cscript: AIS_DATA_AVAILABLE: ERROR: Disk Full: Dampening JMB attachment generation
   Jan 13 05:14:17  mx-480-sn cscript: AIS_PROCESSING: Deleted the file /var/tmp/mx-480-sn_20170113_051415_310_jmb_ais_prob
   

5. Log in to the Junos Space GUI and navigate to Service Now > Service Central > Incidents.

   An incident is generated in Service Now for the event that you generated using the event simulator. The incident is usually generated in Service Now within a few minutes after the event is generated on the device.