Installing the JSA 7.3.3 Fix Pack 1 (Patch 1) Software Update
JSA 7.3.3 Fix Pack 1 (Patch 1) resolves reported issues from users and administrators from previous JSA versions. This cumulative software update fixes known software issues in your JSA deployment. JSA software updates are installed by using an SFS file. The software update can update all appliances attached to the JSA Console.
The 22.214.171.12491203144110 SFS file can upgrade JSA 7.3.1, or JSA 7.3.2 to JSA 7.3.3 Fix Pack 1 (Patch 1). This document does not cover all the installation messages and requirements, such as changes to appliance memory requirements or browser requirements for JSA. For more information, see the Juniper Secure Analytics Upgrading JSA to 7.3.3.
Ensure that you take the following precautions:
Back up your data before you begin any software upgrade. For more information about backup and recovery, see the Juniper Secure Analytics Administration Guide.
To avoid access errors in your log file, close all open JSA webUI sessions.
The software update for JSA cannot be installed on a managed host that is at a different software version from the Console. All appliances in the deployment must be at the same software revision to update the entire deployment.
Verify that all changes are deployed on your appliances. The update cannot install on appliances that have changes that are not deployed.
If this is a new installation, administrators must review the instructions in the Juniper Secure Analytics Installation Guide.
To install the JSA 7.3.3 Fix Pack 1 (Patch 1) software update:
- Download the 126.96.36.19991203144110 SFS from the Juniper Customer Support website.
- Using SSH, log into your system as the root user.
- To verify you have enough space (5 GB) in
/store/tmpfor the JSA Console, type the following command:
df -h /tmp /storetmp /store/transient | tee diskchecks.txt
Best directory option: /storetmp
It is available on all appliance types at all versions. In JSA 7.3.0 versions /store/tmp is a symlink to the /storetmp partition.
2nd best directory option: /tmp
This directory is available on all appliances, but in 7.3.0 versions is significantly smaller and moving a file here can cause services to stop. If you leave a file in /tmp for 10 days without completing the SFS update, it might get cleaned up by Red Hat's tmpwatch cron job.
3rd best option: /store/transient
The store/transient directory was introduced in JSA 2014.1 and is allocated 10% of the overall /store directory. However, this directory does not exist on all appliances and might not be an actual partition on all appliances.
If the disk check command fails, retype the quotation marks from your terminal, then re-run the command. This command returns the details to both the command window and to a file on the Console named diskchecks.txt. Review this file to ensure that all appliances have at minimum 5 GB of space available in a directory to copy the SFS before attempting to move the file to a managed host. If required, free up disk space on any host that fails to have less than 5 GB available.
In JSA 7.3.0 and later, an update to directory structure for STIG compliant directories reduces the size of several partitions. This can impact moving large files to JSA.
- To create the
/media/updatesdirectory, type the following command:
mkdir -p /media/updates
- Using SCP, copy the files to the JSA Console to the /storetmp directory or a location with 5 GB of disk space.
- Change to the directory where you copied the patch file.
- Unzip the file in the
/storetmpdirectory using the bunzip utility:
- To mount the patch file to the /media/updates directory,
type the following command:
mount -o loop -t squashfs /storetmp/188.8.131.5291203144110.sfs /media/updates
- To run the patch installer, type the following command:
The first time that you run the software update, there might be a delay before the software update installation menu is displayed.
- Using the patch installer, select all.
The all option updates the software on all appliances in the following order:
No order required for remaining appliances. All remaining appliances can be updated in any order the administrator requires.
If you do not select the all option, you must select your console appliance.
As of the JSA 2014.6.r4 patch and later, administrators are only provided the option to update all or update the Console appliance. Managed hosts are not displayed in the installation menu to ensure that the console is patched first. After the console is patched, a list of managed hosts that can be updated is displayed in the installation menu. This change was made starting with the JSA 2014.6.r4 patch to ensure that the console appliance is always updated before managed hosts to prevent upgrade issues.
If administrators want to patch systems in series, they can update the console first, then copy the patch to all other appliances and run the software update installer individually on each managed host. The console must be patched before you can run the installer on managed hosts. When updating in parallel, there is no order required in how you update appliances after the console is updated.
If your Secure Shell (SSH) session is disconnected while the upgrade is in progress, the upgrade continues.