Host GS: Apply Updates

Document created by RSA Information Design and Development on Nov 23, 2016
Version 1Show Document
  • View in full screen mode
  

The Hosts view displays the software version updates available in your Local Update Repository and you choose and apply the updates you want from the Host view. See the Populate Local Update Repository topic in System Maintenance for information on how the Local Update Repository gets populated.

Procedure

This procedure tells you how to update a host to a new version of Security Analytics. 

Note: When you update the Security Analytics (SA) Server Host, Security Analytics backs up the System Management Service (SMS) configuration files (excluding the wrapper.conf file) from the /opt/rsa/sms/conf directory to/opt/rsa/sms/conf_%timestamp% directory. This is a precautionary measure for the rare occasion when you may need to restore the SMS configuration from backup. To do this, replace the files in the /opt/rsa/sms/conf  directory with the files backed up to the /opt/rsa/sms/conf_%timestamp% directory after the update.

  1. (Conditional) For Multiple Security Analytics Server deployments only, SSH to each Secondary SA Server Host and make sure the the puppetmaster is enabled using the following commands:
    chkconfig --add puppetmaster
    chkconfig --level 3 puppetmaster /etc/init.d/puppetmaster start
  2. For more information, see the Multiple Security Analytics Server Deployment topic in the Deployment Guide.
  3. Log in to Security Analytics.
  4. In the Security Analytics menu, select Administration Hosts

Note: If you have a non-Security Analytics Server host running a version that is earlier than the 10.6.0 update path (that is, earlier than 10.4.1) and you updated your Security Analytics Server Host to 10.6.0, the non-Security Analytics Server host will display “Update Path Not Supported” in the Status column of the Hosts view and you cannot update it from this view. Contact Customer Care to update the non-Security Analytics Server host on the unsupported path. 

  1. Update hosts in the sequence recommended in Update Hosts in Correct Sequence.
    1. Select the version you want to apply from the Update Version column. If you want to update more than one host to that version, select the checkbox to the left of the hosts.
      Update Available is displayed in the Status column if you have an version update in your Local Update Repository for the selected hosts.
      If you:
      • Cannot find the version you want, populate your Local Update Repository. For more information, see the Populate Local Update Repository topic in System Maintenance.
      • Do not have enough disk space in your Local Update Repository to download a version update, the Repository Space Management dialog is displayed with the contents and disk space status of the repository. You can delete versions that you do not need to free enough disk space to download the version you want. See Free Local Update Repository Disk Space for instructions. 
  1. Click Update from the toolbar. The Status column tells you what is happening in each of the following stages of the update:
  2. After the host is updated, Security Analytics prompts you to Reboot Host.
  3. Click Reboot Host from the toolbar.
    Security Analytics shows the status as Rebooting... until the host comes back online. After the host comes back online, the Status shows Up-to-Date. Contact Customer Care if the host does not come back online.

Note: If you have DISA STIG enabled, opening Core Services can take approximately 5 to 10 minutes. This delay is caused by the generating of new certificates.

You are here
Table of Contents > Host Maintenance Procedures > Apply Updates

Attachments

    Outcomes