Manually Configuring and Installing AI-Scripts on Devices

Within AIM, devices that are configured for AIS manually are automatically added to the device group that is associated with the AIM archive location to which 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.

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

1. Download AI-Scripts install packages. See Downloading AI-Scripts Install Packages.
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-aim {…}

      This configuration determines the AIS archive location where JMBs are deposited for a device.

   3. Configure the commit script:
      user@host#set groups juniper-ais system scripts commit file jais-activate-scripts.slax optional

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

   4. 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 configuration (except with a special command).

   5. Apply the juniper-ais group:
      user@host#set apply-groups juniper-ais
   6. (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 AI-Scripts from the /config/scripts/directory; otherwise, the system reads AI-Scripts from the /var/db/scripts/directory. The /var/run/scripts directory will always point to the right scripts directory.

3. Verify that the syntax of a configuration is correct by using 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-aim {
                       archive-sites {
                           "ftp://anonymous@10.7.0.124/aimdemo";
                       }
                   . . .

6. If you have not moved the AI-Scripts to the device, do so now. See Downloading AI-Scripts Install Packages.
7. Install the AI-Scripts package using the following command (see AI-Scripts Installation Commands):
   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";
               }
           }
       }
   }