Juniper Secure Analytics Patch Release Notes

Transcription

1 Juniper Secure Analytics Patch Release Notes January patch resolves several known issues in Juniper Secure Analytics (JSA). Contents Administrator Notes Installing Patch Part 1. Staging Files and Pretesting your Deployment (required) Part 2. Installing the JSA ISO on the Console Appliance Part 3. Installing the JSA ISO on all other Managed Hosts Part 4. Installation Wrap-up Clearing the Cache Known Issues and Limitations Resolved Issues Feedback Requesting Technical Support Self-Help Online Tools and Resources Opening a Case with JTAC Revision History

2 JSA Patch Release Notes Administrator Notes About this Upgrade These instructions are intended to assist administrators with updating appliances from JSA to JSA patch 7 using an ISO file. This ISO can update JSA, JSA Risk Manager, JSA Vulnerability Manager products from to version Patch 7. These instructions inform administrators how to update their deployment to the latest version. If you have a software installation, need the latest memory requirements, or are making use of off-board storage, it is recommended that you review the Juniper Secure Analytics Upgrading JSA to Guide to prevent issues. JSA uses an ISO file to update hosts to the latest software version. A minimum of JSA r2 patch (or later) is required to be able to upgrade to JSA Patch 7. Each host must be updated individually, this includes HA secondary appliances. 1. This update includes a change to how login authentication works for fallback LDAP, Radius, or Active Directory on administrator accounts. If the external authentication server is unavailable, not all administrators will be able to fall back to their local administrator passwords without a configuration change. This change was implemented in JSA or later. If you have already address this issue in a previous update, then this message can be ignored. 2. TLS v1.0 and TLSv1.1 is disabled in this release and connections to the user interface for legacy browsers might be rejected. 3. WinCollect agents at version or older use TLSv1.0 and TLS v1.1 connections to upgrade agents, which is disabled in JSA (all patch version). Administrators with managed WinCollect agents must upgrade to WinCollect before installing JSA Patch 7. WinCollect is a pre-requisite for JSA Stand-alone WinCollect agents are not impacted by this requirement. 4. Customized routes or static routes configured manually in JSA are not preserved after the upgrade to JSA completes. 5. Any iptables rules configured by the administrator should be reviewed and noted for clean up post installation. The interface names have changed in JSA due to the Red Hat Enterprise 7 operating system updates and administrators who reference interfaces will need to update iptables rules manually. 6. You must be on JSA r2 or later to upgrade to JSA Patch The upgrade from JSA will use a.iso file. In the past, support has stated that ISOs are for new appliance installs only, but JSA is going to be an exception to this rule because of the Red Hat kernel update requirements. 8. Each HA appliance must be updated individually using the ISO file. The SFS file is capable of allowing the primary appliance to update the secondary, but the ISO file does not support this functionality. If you run the ISO setup on an HA primary, you should wait for the update to complete, then run the setup on the HA secondary. 9. There is no patch All option as JSA uses an ISO file to upgrade. The ISO must be mounted to the appliance and run locally on each host. 2

3 Installing Patch The upgrade will take longer than expected due to the kernel changes to Red Hat 7 Enterprise. Early upgrade customers are reporting 2 to 2.5 hours to upgrade the Console appliance. Administrators should be aware of this longer time frame to plan their maintenance windows. 11. Utilities or custom scripts that power users might have created for their JSA deployment should be copied off of the system. During the update a warning is displayed that only data in /store is going to be preserved. After the appliance reboots, any scripts, 3rd party accounts, or utilities in /tmp, or /, or /root will be deleted. This does not impact ISO files mounted initially using /root as the this clean up only occurs later in the installation procedure. Current JSA Version Upgrades to JSA Patch 7? JSA (any patch level) or earlier No JSA (any patch level) No JSA No JSA r2 or later Yes, the latest ISO can upgrade directly to JSA Patch 7. Use these release notes to complete this process. JSA to JSA Patch 6 No, JSA users should use the SFS file to upgrade JSA systems to JSA Patch 7. See the JSA Patch 7 SFS release notes. Installing Patch 7 on page 3 Part 1. Staging Files and Pretesting your Deployment (required) on page 4 Part 2. Installing the JSA ISO on the Console Appliance on page 6 Installing Patch 7 Ensure that you take the following precautions: Back up your data before you begin any software upgrade and verify that you have recent configuration backups that match your existing Console version. If required, take an on demand configuration backup before you begin. For more information about backup and recovery, see the Juniper Secure Analytics Administration Guide. HA appliances should have primaries in the online state and secondary as standby for their HA pair status. If you have off-board storage configured, see the Juniper Secure Analytics Upgrading JSA to Guide as there are special instructions for administrators with /store using off-board storage. If you installed JSA as a software install using your own hardware, see the Juniper Secure Analytics Upgrading JSA to Guide for partition information. 3

4 JSA Patch Release Notes WinCollect is a pre-requisite for JSA and all managed agents must be updated. Stand-alone WinCollect agents are not impacted by this requirement. All appliances in the deployment must be at the same software and patch level in the deployment. Verify that all changes are deployed on your appliances. The update cannot install on appliances that have changes that are not deployed. To avoid access errors in your log file, close all open JSA webui sessions. If you are unsure of the IP addresses or hostnames for the appliances in the deployment, run the utility /opt/qradar/support/deployment_info.sh to get a.csv file with information about the JSA deployment. The CSV file will contain a list of IP addresses for each managed host. If you are unsure of how to proceed when reading these instructions or the documentation, it is best to ask before starting your upgrade. If there are messages you do not understand or want to discuss further, you can open an SR with Juniper Customer Support. Administrator Notes on page 2 Part 1. Staging Files and Pretesting your Deployment (required) on page 4 Part 2. Installing the JSA ISO on the Console Appliance on page 6 Part 1. Staging Files and Pretesting your Deployment (required) It is important that administrators pretest their deployment to ensure that they will not experience unexpected issues when updating to JSA A pretest is a common precaution that should be taken by all administrators before they install an update to locate potential issues. The pretest does not restart services and can be completed without scheduled downtime. The pretest typically takes between 3 to 5 minutes to complete on each appliance. If for some reason your SSH session is disconnected, you can reconnect to the remote host using screen. The pretest should be completed on all hosts by the administrator before you attempt to upgrade to JSA Download the JSA ISO (3.8 GB) from the Juniper Support website. 2. Using SSH, log in to your Console as the root user. 3. Type the following command: screen 4. To make the directory for the update, type: /opt/qradar/support/all_servers.sh -k mkdir -p /media/cdrom umount /media/cdrom" 4

5 Part 1. Staging Files and Pretesting your Deployment (required) 5. To verify you have enough space (4 GB) in /tmp for the ISO on all appliances, type: /opt/qradar/support/all_servers.sh -k df -h /root /var/log tee diskchecks.txt Best directory option: /root It is available on all appliance types, is the best option to host the ISO file. 2nd best directory option: /var/log This directory is available on all appliances, but there might not be the required space available. DO NOT USE: /tmp, /store/tmp, or /store/transient for your ISO upgrade. These directories are partitioned as part of the upgrade and administrators cannot use them as storage locations or mount points for the ISO file. 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 4 GB of space available in a directory to copy the ISO before attempting to move the file to a managed host. If required, free up disk space on any host that fails to have less that 4 GB available. Reminder: Utilities or custom scripts that administrators have created for JSA should be copied off of the system. During the update a warning is displayed that only data in /store will be preserved. Therefore, scripts, third party utilities in /tmp, or /, or /root will be deleted during the upgrade. 6. If there is not 4 GB of space in /root or /var/log, the administrator must make directory space for the ISO file. 7. Using WinSCP or SCP, copy the ISO to the /root or /var/log directory on the JSA Console with 4 GB of disk space for the ISO file. 8. To copy the files to all appliances, type: /opt/qradar/support/all_servers.sh -k -p /root/jsa7.3.0.patch7.iso -r /root 9. To mount the ISO on all appliances, type the following command: /opt/qradar/support/all_servers.sh -C -k mount -o loop /root/jsa7.3.0.patch7.iso /media/cdrom" 10. To pretest the Console appliance, type: /media/cdrom/setup -t The pretest output will be written to the command window. Review this output after the pretest completes. 11. Using SSH, open an SSH session to the other appliances in your deployment. JSA Support recommends that all administrators run the pretest on each host to identify issues before the update begins. 12. To pretest the managed host, type: /media/cdrom/setup -t 5

6 JSA Patch Release Notes Result If an appliance in your deployment fails the pretest, the administrators can take the recommended action from the pretest utility. The issue must be resolved before the update to begins to prevent downtime for specific appliances. If there are messages you do not understand or want to discuss further, you can open an SR with Juniper Customer Support. Part 2. Installing the JSA ISO on the Console Appliance on page 6 Part 3. Installing the JSA ISO on all other Managed Hosts on page 7 Part 4. Installation Wrap-up on page 8 Part 2. Installing the JSA ISO on the Console Appliance These instructions guide administrators through the process of upgrading an existing JSA install at r2 patch or later to JSA software version The update on the Console must be completed first, before you attempt to update any managed hosts to JSA You must complete: Part 1. Staging Files and Pretesting your Deployment (required) on page 4 before you begin the installation steps listed below. 1. Using SSH, log in to the Console as the root user. 2. To run the ISO installer on the Console, type the following command: /media/cdrom/setup NOTE: Upgrading from JSA r2 patch or later to JSA should take approximately 2 hours on a Console appliance. 3. Wait for the Console primary update to complete. 4. For HA appliances. If you have an HA Secondary, you can now update the secondary appliance. 5. Open an SSH session to the HA Console secondary. 6. Type the following command to update the secondary Console: /media/cdrom/setup 7. Wait for the HA Console secondary to complete the update. Result 6

7 Part 3. Installing the JSA ISO on all other Managed Hosts A summary of the ISO installation advises you of any issues. Part 3. Installing the JSA ISO on all other Managed Hosts on page 7 Part 4. Installation Wrap-up on page 8 Clearing the Cache on page 9 Part 3. Installing the JSA ISO on all other Managed Hosts After the Console and Console HA secondary are updated to JSA 7.3.0, then the rest of the deployment can updated. There is no order required for updating specific appliance types after the Console is updated. Administrators can update Event Processors, Event Collectors, flow processors in any order. You must open an SSH session to each host to run the setup command. The all_servers.sh utility is not supported for parallel ISO installations. Administrators can start the ISO update in parallel on multiple hosts, if they are not HA pairs. Administrators with appliances that are HA pairs must upgrade the primary appliance first, then the secondary managed host. You must complete: Part 1. Staging Files and Pretesting your Deployment (required) on page 4 before you begin the installation steps listed below. 1. Using SSH, log in to the Console as the root user. 2. Open an SSH session to each managed host and type the following command: /media/cdrom/setup NOTE: Upgrades for managed hosts should take approximately 1.5 hours. 3. Wait for the managed host update to complete. 4. For HA appliances. If you have an HA Secondary, you can now update the secondary appliance. 5. Open an SSH session to the manage host HA secondary. 6. Type the following command to update the secondary: /media/cdrom/setup 7. Wait for the HA Console secondary to complete the update. Result 7

8 JSA Patch Release Notes A summary of the ISO installation advises you of any issues. If there are no issues, administrators can now run the ISO setup on the Console HA secondary appliance, if you have an HA pair. If you do not have a Console in HA, you can then start SSH sessions to each host and run the setup in parallel. Part 4. Installation Wrap-up on page 8 Clearing the Cache on page 9 Known Issues and Limitations on page 10 Part 4. Installation Wrap-up 1. After all hosts are updated, administrators can send an to their team to inform them that they will need to clear their browser cache before logging in to the JSA. 2. To unmount the /media/cdrom directory on all hosts, type: /opt/qradar/support/all_servers.sh -C -k umount /media/cdrom" 3. Administrators can delete the ISO from all appliances. 4. Administrators who use WinCollect agents version or latest must reinstall the SFS file on the JSA Console. This is due to issues were the ISO replaces the SFS on the Console with WinCollect Once the system is upgrade to 7.3.x, the same version of WinCollect must be reinstalled on the JSA console using the appropriate 7.3 SFS for WinCollect. To install the latest WinCollect SFS on the Console, see the WinCollect release notes. 5. Review any static routes or customized routing. As mentioned in the administrator notes, all routes were removed and will need to be reconfigured after the upgrade completes. 6. Any iptable rules configured should be reviewed as the interface names have changed in JSA due to the Red Hat Enterprise 7 operating system updates. Any iptables rules that use Red Hat 6 interface naming conventions will need to be updated. Clearing the Cache on page 9 Known Issues and Limitations on page 10 Resolved Issues on page 10 8

9 Clearing the Cache Clearing the Cache After you install the patch, you must clear your Java cache and your web browser cache before you log into the JSA appliance. Before you begin Ensure that you have only one instance of your browser open. If you have multiple versions of your browser open, the cache might fail to clear. Ensure that the Java Runtime Environment is installed on the desktop system that you use to view the user interface. You can download Java version 1.7 from the Java website: About this task If you use the Microsoft Windows 7 operating system, the Java icon is typically located under the Programs pane. To clear the cache: 1. Clear your Java cache: a. On your desktop, select Start > Control Panel. b. Double-click the Java icon. c. In the Temporary Internet Files pane, click View. d. On the Java Cache Viewer window, select all Deployment Editor entries. e. Click the Delete icon. f. Click Close. g. Click OK. 2. Open your web browser. 3. Clear the cache of your web browser. If you use the Mozilla Firefox web browser, you must clear the cache in the Microsoft Internet Explorer and Mozilla Firefox web browsers. 4. Log in to JSA. Part 4. Installation Wrap-up on page 8 Known Issues and Limitations on page 10 Resolved Issues on page 10 9

10 JSA Patch Release Notes Known Issues and Limitations NOTE: None. Part 4. Installation Wrap-up on page 8 Clearing the Cache on page 9 Resolved Issues on page 10 Resolved Issues The following are the resolved issues addressed in the patch 7: AN ARIEL FILE LOCK ON DELETED FILES CAN CAUSE LOG ACTIVITY SEARCHING TO FAIL AND PREVENT DASHBOARD TIMESERIES LOADING. RESOLVES AN ISSUE WHERE A MISSING DIRECTORY FOR NAT.POST IPTABLES RULES COULD CAUSE APPLICATIONS TO FAIL TO INSTALL WITHOUT WRITING PROPER FAILURE MESSAGES. Part 4. Installation Wrap-up on page 8 Clearing the Cache on page 9 Known Issues and Limitations on page 10 Feedback We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can provide feedback by using either of the following methods: Online feedback rating system On any page of the Juniper Networks TechLibrary site at simply click the stars to rate the content, and use the pop-up form to provide us with information about your experience. Alternately, you can use the online feedback form at Send your comments to techpubs-comments@juniper.net. Include the document or topic name, URL or page number, and software version (if applicable). Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or Partner Support Service 10

11 Requesting Technical Support support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC. JTAC policies For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at Product warranties For product warranty information, visit JTAC hours of operation The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: Find product documentation: Find solutions and answer questions using our Knowledge Base: Download the latest versions of software and review release notes: Search technical bulletins for relevant hardware and software notifications: Join and participate in the Juniper Networks Community Forum: Open a case online in the CSC Case Management tool: To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone. Use the Case Management tool in the CSC at Call JTAC ( toll-free in the USA, Canada, and Mexico). Revision History For international or direct-dial options in countries without toll-free numbers, see January 2018 for the JSA Release Patch 7 ISO Copyright 2017 Juniper Networks, Inc. All rights reserved. 11

12 JSA Patch Release Notes Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. and/or its affiliates in the United States and other countries. All other trademarks may be property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. 12