Blogs

Answer

• To upgrade up to AI-Scripts Release 4.1R9 and earlier, follow the steps below:

1. Install the newer version of the AI-Scripts using the request system scripts add <package name> CLI command.
2. Verify that the AI-Scripts are activated:

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

NOTE: For upgrading AI-Scripts on an SRX cluster, see KB 30556

• To upgrade AI-Scripts from Release 5.0R1.0 to Release 5.0R2.0 and later releases, follow the steps below:

NOTE: Before upgrading AI-Scripts from Release 5.0R1.0 to Release 5.0R2.0, ensure that you uninstall AI-Scripts 5.0R1.0 from the device (all Routing Engines of a multichassis device). If AI-Scripts Release 5.0R1.0 is not uninstalled before installing AI-Scripts Release 5.0R2.0, the first commit of AI-Scripts Release 5.0R2.0 may take excessively long time.

NOTE: If AI-Scripts Release 5.0R2.0 is taking a long time to commit, execute the show configuration groups juniper-ais command on the device. Following lines in the output indicate AI-Scripts Release 5.0R1.0 configuration still present on the device:
commit {
allow-transients;
file jais-SN-activate-scripts.slax {
optional;
}
file jais-activate-scripts.slax {
optional;
}
}

Delete the AI-Scripts Release 5.0R1.0 configuration from the device manually and then try reinstalling AI-Scripts Release 5.0R2.0. For information about deleting AI-Scripts configuration manually, see “AI-Scripts Commands FAQ”.

1. Install AI-Scripts Release 5.0R2.0 and later releases on all Routing Engines of a device using Service Now.
   NOTE: For information about installing and configuring AI-Scripts on a device using Service Now, see Installing an Event Profile on a Device by Using Service Now section of the Service Automation Administration. To only install AI-Scripts on a device without configuring AI-Scripts, on the Install Event Profile page of the Service Now GUI, clear the Alter device configuration to enable AI-Script events on devices check box.
2. Execute the show version command to verify that AI-Scripts is installed on all Routing Engines.
3. Verify that the AISBundle_Info.xml file is present at /var/db/scripts/commit. The file contains the definition of the events to be monitored on the device.
4. Activate the AISBundle_Info.xml by using the op ais-param-set event-file /var/db/scripts/commit/AISBundle_info.xml command.
5. To activate the default event profile bundled with the AI-Scripts package, execute the op ais-param-set event-file default command on the primary Routing Engine.
6. The op ais-param-set event-file command pushes the event profile to all the Routing Engines of a device.