Description

This article provides a summary of how to upgrade Advanced Insight Scripts (AI-Scripts) on SRX Chassis Clusters to AI-Scripts Release 5.0R2 or later, from 4.x versions. Troubleshooting steps are also provided.

Symptoms

Junos Space Service Now 15.1R1 and later supports the installation and upgrade to AI-Scripts Release 5.0 Event Profiles on most Junos OS devices.

However, for SRX Chassis Clusters discovered on the master-only VIP, loopback, or redundant interface, Service Now will raise a warning if a user attempts to upgrade an SRX Chassis Cluster that has AI-Scripts version 4.x or earlier, on the secondary node, and will not proceed with the upgrade attempt. To avoid this problem, follow the Upgrade Procedure in the Solution below. If you did not follow the Upgrade Procedure and are encountering the upgrade failure, follow the Troubleshooting Procedure in the Solution below.

Solution

The cause is that with the new "No-Commit" feature provided by AI-Scripts Release 5.0, installation on the primary SRX cluster node must write files onto the secondary node. If an older version of AI-Scripts has been installed on the secondary node, a file overwrite attempt will cause the installation to become corrupted. Both Service Now and AI-Scripts check for this condition and disallow the AI-Scripts upgrade accordingly. For this case, AI-Scripts must be uninstalled from both SRX cluster nodes. This can be done in Service Now if it was used to initially install the older AI-Scripts and has not been deleted and rediscovered in the Junos Space Network Management Platform. However, using Service Now to delete AI-Scripts off the primary node will not automatically delete it from the secondary node. The customer must either toggle cluster node mastership and uninstall from the "other node," or might need to uninstall AI-Scripts manually from the device CLI, as discussed below.

Service Now will not raise a warning for an SRX cluster node managed independently on its respective fxp0 interface, but the upgrade and installation could fail during commit due to the configuration database being locked for editing. For this case, retrying the job or reinstalling the AI-Scripts 5.0-based Event Profile on only the failed SRX cluster node should resolve the issue.

To upgrade to AI-Scripts Release 5.0 on your SRX Chassis Cluster, follow the Upgrade Procedure below.
If you upgraded AI-Scripts on your SRX Chassis Cluster and encountered an installation error, then follow the Troubleshooting Procedure below.

Upgrade Procedure:

  1. Important : Before upgrading AI-Scripts to 5.0R2 or later on an SRX Chassis Cluster, any older version of AI-Scripts must be removed from both nodes in the cluster.

    AI-Scripts uninstall procedure:

    1. Uninstall scripts from the primary node of the SRX Chassis Cluster with the command request system scripts delete .

  2. Once the uninstall from the primary node is completed, uninstall the script bundle from the secondary node of the SRX Chassis Cluster with the command request system scripts delete .

Note: The AI-Scripts uninstallation procedure is not required if upgrading from AI-Scripts 5.0R2 or later.

Troubleshooting Procedure:

AI-Scripts must be uninstalled separately from both nodes of an SRX Chassis Cluster. If uninstallation of AI-Scripts is initiated at the same time on both nodes, the operation might fail on one of the nodes. If the uninstallation operation fails on one of the nodes, use the "Retry on Failed Devices" option from the Junos Space Job Management page to try uninstalling AI-Scripts again from the failed node.

If AI-Scripts is upgraded from an older version (Release 4.1R8 and earlier) to Release 5.0 on a device where the older version  is not present, but the corresponding AI-Scripts configuration is present, then the configuration information for both the old and new releases might be incorrectly merged. Perform the following steps:
  1. Delete the older AI-Scripts configuration, if present, before upgrading to AI-script Release 5.0 and later. This can be accomplished by executing the following Junos OS operational mode command on the device:

> op remove-jais remove-jais-configuration true

  • In rare cases, AI-Scripts and/or the associated Junos configuration might still remain. This can be verified by executing the following commands:

> show version

Output from the above command would include " AI-Scripts [version] " or " JUNOS AIS Script Suite [version] ".

> show configuration | display set | match juniper-ais

Output from the above command would include:

set groups juniper-ais system scripts commit allow-transients;
set groups juniper-ais system scripts commit file jais-SN-activate-scripts.slax optional
set groups juniper-ais event-options destinations juniper-aim archive-sites /var/tmp/
set apply-groups juniper-ais

If any of the above AI-Scripts commands exist, manually remove them with the following procedure(s):

Remove AI-Scripts:

> request system scripts delete

Remove the associated Junos configuration:

> edit
# rollback
# delete groups juniper-ais
# delete apply-groups juniper-ais
# show | compare
# commit confirmed
# commit and-quit


Related Information