Manually Configuring and Installing AI-Scripts on Devices

Within AIM, devices that are configured for AIS manually will automatically be added to the device group that is associated with the AIM archive location that the JMB was sent. When the AIM detects a JMB for a device that is not managed by JUNOScope Script Management, it will note it.

Figure 10 shows the basic steps you must perform to manually configure install AI-Scripts to devices to automatically detect incidents that occur during operation and to collect incident data.

Figure 10: Basic Steps to Manually Configure and Install AI-Scripts on Devices

To manually configure and install AI-Scripts on Devices, follow these steps:

1. See Downloading AI-Script Install Packages and Release Notes.
2. Configure the device configuration as follows to activate AI-Scripts:

1. Enter the device CLI configuration mode. type the configure command or the edit command from the CLI operation mode. The CLI prompt changes from user@host> to user@host# and a banner appears to indicate the hierarchy level.
2. Configure an ais destination under group juniper-ais:

user@host# set groups juniper-ais event-options destination 
juniper-junoscope {..} 

This configuration determines the AIS remote archive location for a device.

1. Configure the commit script:

user@host# set groups juniper-ais system scripts commit file 
jais-activate-scripts.slax optional

The AI-Script installer creates this script to activate AI-Scripts on the device.

1. Configure the allow-transients option to allow transient changes:

user@host# set groups juniper-ais system scripts commit 
allow-transients

Transient changes are configuration changes made by commit scripts that do NOT appear in the config (except with special command)

1. Apply the juniper-ais group:

user@host# set apply-groups juniper-ais 

This configuration applies the config-group juniper-ais.

1. (Optional) Configure the load-scripts-from-flash option:

user@host# set groups juniper-ais system scripts load-scripts-from-flash

   
NOTE: If you configure the load-scripts-from-flash option, the system reads event-scripts from /config/scripts/ directory otherwise the system reads event-scripts from the /var/db/scripts/ directory. The /var/run/scripts directory will always point to the right scripts directory based on the load-scripts-from-flash option.


 

3. Verify that the syntax of a configuration is correct, by use the configuration mode commit check command:

[edit] 

user@host# commit check 

configuration check succeeds 

4. Commit the configuration. To save software configuration changes to the configuration database and activate the configuration on the router, use the commit configuration mode command. You can issue the commit command from any hierarchy level.

[edit] 

user@host# commit 

commit complete 

5. View the configuration:

groups {

    juniper-ais {

        system {

            scripts {

                commit {

                    allow-transients;

                    file jais-activate-scripts.slax {

                        optional;

                    }

                }

                load-scripts-from-flash;

            }

        }

        event-options {

            destinations {

                juniper-junoscope {

                    archive-sites {

                        "ftp://anonymous@10.7.0.124/aimdemo";

                    }

                . . .

6. If you have not moved the AI-Script to the device, do so now. See Downloading AI-Script Install Packages and Release Notes.
7. Install the AI-Script package. (For more information about working with AI-Script packages, see the Working With AI-Scripts.

request system scripts add <package-name> 

8. Verify that the AI-Scripts are activated:

user@host$ show groups juniper-ais | display commit-scripts

user@host> show configuration groups juniper-ais | display commit-scripts    

system {

    scripts {

        commit {

            allow-transients;

            file jais-activate-scripts.slax {

                optional;

            }

        }

    }

}

event-options {

    event-script {

        file problem-event-ui_commit.slax;

        file problem-event-pic_detach.slax;

        file problem-event-pfecrash.slax;

        file problem-event-dcrash.slax;

        file intelligence-event-main.slax;

}

    destinations {

        juniper-junoscope {

            archive-sites {

                "ftp://anonymous@10.7.0.124/aimdemo";

            }

        }

    }

}