Upgrade 11.4.1: Appendix A. Offlne Upgrade Using CLI

Document created by RSA Information Design and Development on Apr 23, 2020Last modified by RSA Information Design and Development on Apr 28, 2020
Version 2Show Document
  • View in full screen mode
 

You can use this method if the NW Server host is not connected to Live Services.

Prerequisites

Make sure that you have downloaded the following files from RSA Link (https://community.rsa.com/) > NetWitness Platform > RSA NetWitness Logs and Network > Downloads > RSA Downloads to a local directory:

  • If you are upgrading from an 11.2.x.x or 11.3.x.x release to 11.4.1.0, download:
    netwitness-11.4.0.0.zip
    netwitness-11.4.1.0.zip
  • If you are upgrading from an 11.4.0.x release to 11.4.1.0 release, download:
    netwitness-11.4.1.0.zip
  • If you are using external repository, you can update the external repository with the latest upgrade content. For more information, see External Repo Instructions for CLI upgrade.

Procedure

You must perform the upgrade steps for NW Server hosts and for component servers.

Note: If you copy and paste the commands from PDF to Linux SSH terminal, the characters do not work. It is recommended to type the commands.

  1. Stage the 11.4.1.0 files to prepare them for the upgrade:
    • If you are upgrading from 11.2.x.x or 11.3.x.x, you must stage 11.4.0.0 and 11.4.1.0. Log into the NW Server as root and create the following directories:

      /tmp/upgrade/11.3.0.0

      /tmp/upgrade/11.4.0.0
      /tmp/upgrade/11.4.1.0
      and then copy the package zip files to the /root directory of the NW Server and extract the package files from /root to the appropriate directories using the following commands:
      unzip netwitness-11.4.0.0.zip -d /tmp/upgrade/11.4.0.0
      unzip netwitness-11.4.1.0.zip -d /tmp/upgrade/11.4.1.0
    • If you are upgrading from 11.4.0.0 to 11.4.1.0, you only need to stage 11.4.1.0. Log into the NW Server as root and create the following directory:

      /tmp/upgrade/11.3.0.0

      /tmp/upgrade/11.4.1.0
      and then copy the package zip file to the /root directory of the NW Server and extract the package files from /root to the appropriate directory using the following command:
      unzip netwitness-11.4.1.0.zip -d /tmp/upgrade/11.4.1.0
  2. Note: If you copied the .zip file to the created staging directory to unzip, make sure that you delete the initial .zip file that you copied to the staging location after you extract it.

  3. Initialize the upgrade, using the following command:
    upgrade-cli-client –-init --version 11.4.1.0 --stage-dir /tmp/upgrade

  4. Upgrade the NW Server host, using the following command:
    upgrade-cli-client –-upgrade --host-addr <IP of Netwitness Server> --version 11.4.1.0
  5. When the NW Server host upgrade is successful, reboot the host from NetWitness Platform user interface in the Hosts view.
  6. Repeat steps 3 through 5 for each component host, changing the IP address to the component host which is being upgraded.

Note: You can check versions of all the hosts, using the command upgrade-cli-client --list on the NW Server host. If you want to view the help content of upgrade-cli-client, use the command upgrade-cli-client --help.

Note: If the following error is displayed during the upgrade process:
2017-11-02 20:13:26.580 ERROR 7994 — [ 127.0.0.1:5671] o.s.a.r.c.CachingConnectionFactory : Channel shutdown: connection error; protocol method: #method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0)
the service pack will install correctly. No action is required. If you encounter additional errors when updating a host to a new version, contact Customer Support for assistance (https://community.rsa.com/docs/DOC-1294).

External Repo Instructions for CLI upgrade

  1. Stage the 11.4.1.0 files to prepare them for the upgrade:
    • If you are upgrading from 11.2.x.x or 11.3.x.x, you must stage 11.4.0.0 and 11.4.1.0. Log into the NW Server as root and create the following directories:

      /tmp/upgrade/11.3.0.0

      /tmp/upgrade/11.4.0.0
      /tmp/upgrade/11.4.1.0
      and then copy the package zip files to the /root directory of the NW Server and extract the package files from /root to the appropriate directories using the following commands:
      unzip netwitness-11.4.0.0.zip -d /tmp/upgrade/11.4.0.0
      unzip netwitness-11.4.1.0.zip -d /tmp/upgrade/11.4.1.0
    • If you are upgrading from 11.4.0.0 to 11.4.1.0, you only need to stage 11.4.1.0. Log into the NW Server as root and create the following directory:

      /tmp/upgrade/11.3.0.0

      /tmp/upgrade/11.4.1.0
      and then copy the package zip file to the /root directory of the NW Server and extract the package files from /root to the appropriate directory using the following command:
      unzip netwitness-11.4.1.0.zip -d /tmp/upgrade/11.4.1.0
  2. Note: If you copied the .zip file to the created staging directory to unzip, make sure that you delete the initial .zip file that you copied to the staging location after you extract it.

  3. Initialize the upgrade, using the following command:
    upgrade-cli-client –-init --version 11.4.1.0 --stage-dir /tmp/upgrade
  4. Upgrade the NW Server host using the following command:
    upgrade-cli-client –-upgrade --host-addr <IP of Netwitness Server> --version 11.4.1.0
  5. When the NW Server host upgrade is successful, reboot the host from NetWitness UI.
  6. Repeat steps 3 and 4 for each component host, changing the IP address to the component host which is being upgraded.

Note: You can check versions of all the hosts, using the command upgrade-cli-client --list on the NW Server host. If you want to view the help content of upgrade-cli-client, use the command upgrade-cli-client --help.

Note: If the following error displays during the upgrade process:
2017-11-02 20:13:26.580 ERROR 7994 — [ 127.0.0.1:5671] o.s.a.r.c.CachingConnectionFactory : Channel shutdown: connection error; protocol method: #method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED - broker forced connection closure with reason 'shutdown', class-id=0, method-id=0)
the service pack will install correctly. No action is required. If you encounter additional errors when updating a host to a new version, contact Customer Support for assistance (https://community.rsa.com/docs/DOC-1294).

Previous Topic:Enable New Features
You are here
Table of Contents > Appendix A. Offline Upgrade

Attachments

    Outcomes