Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Manually Installing AI-Scripts on Devices

 

AI-Scripts Releases prior to 5.0R2.0 can be installed on Junos OS devices manually by using CLI mode. For manual installation of AI-Scripts on devices, you require the same login credentials that you use to discover devices in Junos Space Network Management Platform.

Note

We recommend that you install AI-Scripts on devices during a maintenance window.

To install AI-Scripts Release 4.XRX or earlier manually on a device:

  1. Copy the AI-Scripts install package (example: jais-4.0R1.0-signed.tgz) to the Junos OS device using SCP or FTP.
  2. Install the AI-Scripts bundle install package in CLI mode by using one of the following commands:

    • request system scripts add <pathname>, where <pathname> is the path to the AI-Scripts bundle copied on the device.

    • request system software add <package-name> <node>, where <node> is the Routing Engine—re0 or re1 and <package-name> is the name of the AI-Scripts bundle copied on the device.

    Note
    • The request system software add <pathname> <node> command when executed on a master Routing Engine installs AI-Scripts on all backup Routing Engines of a device.

    • We recommend that the AI-Scripts installation package be placed in the /var/tmp/ directory as some platforms require the package to be stored in the /var/tmp/ directory.

    • When you install AI-Scripts in the Juniper Networks QFX3000 device, ensure that you install the events scripts only on the controller. The controller installs AI-Scripts on the node devices and enables all the events.

    The AI-Scripts install package is installed on the device.

  3. Verify that AI-Scripts is installed on all Routing Engines of the device by using the show version command.

    AI-Scripts is installed on the device if AI-Scripts [version} is displayed in the output of the show version command.

  4. From configuration mode, execute the following commands:

    set groups juniper-ais system scripts commit allow-transients

    set groups juniper-ais system scripts commit file jais-activate-scripts.slax optional

    set groups juniper-ais event-options destinations juniper-aim archive-sites /var/tmp/
    Note

    For QFabric devices, use the following command:

    set fabric administration ais enable

  5. Commit the static AI-Scripts configuration.

To install AI-Scripts 5.0 (5.0R2, 5.0R3, and 5.0R4) and later releases manually on a device:

Best Practice

We recommend you to use Service Now to install AI-Scripts Release 5.0R2.0 and later. For information about installing AI-Scripts Release 5.0R2.0 and later on a device by using Service Now, see Installing an Event Profile on a Device by Using Service Now.

Note
  • AI-Scripts Release 5.0R2.0 or later cannot be installed on QFabric devices.

  • You cannot install AI-Scripts Release 6.0R1 and later on a device manually. Service Now displays a warning message on the Service Now GUI when AI-Scripts Release 6.0R1 and later is manually installed on a device.

  1. Copy the AI-Scripts install package (example: jais-5.0R2.0-signed.tgz) to the Junos OS device using SCP or FTP.
  2. Install the AI-Scripts bundle install package in CLI mode by using one of the following commands:

    • request system scripts add <pathname>, where <pathname> is the path to the AI-Scripts bundle copied on the device.

    • request system software add <pathname> <node>, where<node> is the Routing Engine—re0 or re1 and <package-name> is the name of the AI-Scripts bundle copied on the device.

    Note
    • The request system software add <pathname> <node> command when executed on a master Routing Engine installs AI-Scripts on all backup Routing Engines of a device.

    • We recommend that the AI-Scripts installation package be placed in the /var/tmp/ directory as some platforms require the package to be stored in the /var/tmp/ directory.

    • When you install AI-Scripts in the Juniper Networks QFX3000 device, ensure that you install the events scripts only on the controller. The controller installs AI-Scripts on the node devices and enables all the events.

    The AI-Scripts install package is installed on the device.

  3. Verify that AI-Scripts is installed on all Routing Engines of the device by using the show version command.
  4. For AI-Scripts Release 5.0R1 and later, enter the configuration mode on the device and add the static AI-Scripts configuration as follows:
  5. Commit the static AI-Scripts configuration.Best Practice

    We recommend that you commit the AI-Scripts configuration during a maintenance window.

    On a multichassis system, use the commit synchronize command so that the AI-Scripts configuration is committed on all Routing Engines.

  6. Do one of the following to activate the event profile
    • If using the AISevent_info_default.xml file to define the event profile, edit the AISevent_info_default.xml file to include the events that you want to monitor on the device.

      The AISevent_info_default.xml file is present at the /var/db/scripts/commit location and includes all the event definitions that are available for a release. The default event profile automatically excludes events that are not valid for a device.

      Use the op ais-param-set event-file default command to activate the event profile.

      Best Practice

      On a multichassis system, execute the command on the master Routing Engine.

    • If using the AISBundle_info.xml file to define event profile, verify that the AISBundle_info.xml file is present in the /var/db/scripts/commit/ location.

      The file contains the definitions for the events to be monitored on the device and is stored on the device by Service Now while installing AI-Scripts.

      Use the op ais-param-set event-file /var/db/scripts/commit/AISBundle_info.xml command to activate the event profile.

The event profile is installed and configured on the device.