Appendix A. Offline Method (No Connectivity to Live Services) - Command Line Interface

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 file from NetWitness Community (https://community.netwitness.com/) > Products > NetWitness Platform > Downloads to a local directory:

  • If you are upgrading from an 11.5.3.2, 11.5.3.3, 11.6.0.0, 11.6.1.0, 11.6.1.1, 11.6.1.2 or 11.6.1.3 release to 11.7.1.0 release, download:
    netwitness-11.7.0.0.zip
    netwitness-11.7.1.0.zip
  • If you are upgrading from an 11.7.0.0, 11.7.0.1 or 11.7.0.2 release to 11.7.1.0 release, download:
    netwitness-11.7.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.7.1.0 files to prepare them for the upgrade.
    • If you are upgrading from 11.5.3.2, 11.5.3.3, 11.6.0.0, 11.6.1.0, 11.6.1.1, 11.6.1.2 or 11.6.1.3, you must stage 11.7.0.0, 11.7.1.0. Log into the NW Server as root and create the following directories:
      /tmp/upgrade/11.7.0.0
      /tmp/upgrade/11.7.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.7.0.0.zip -d /tmp/upgrade/11.7.0.0
      unzip netwitness-11.7.1.0.zip -d /tmp/upgrade/11.7.1.0
    • If you are upgrading from 11.7.0.0, 11.7.0.1 or 11.7.0.2, you only need to stage 11.7.1.0. Log into the NW Server as root and create the following directory:
      • Option 1 (Manual) : Log into the /root to the directory of the NetWitness Server and create the following directory:
        /tmp/upgrade/11.7.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.7.1.0.zip -d /tmp/upgrade/11.7.1.0
        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.
      • Option 2 (Automated) : Log into the /root to the directory of the NetWitness Server and create the following directory:
        /tmp/upgrade and /root/NW
        and then copy the NetWitness 11.7.1.0 package zip files to the /root/NW directory of the NetWitness Server.
        After this, run the below command to extract, validate, and initialize the 11.7.1.0 zip files:
        [root@SA ~]# upgrade-cli-client --init --stage-dir /tmp/upgrade --download-path <download file path> --version 11.7.1.0
        Here, <download file path> is the location where you need to copy the netwitness-11.7.1.0.zip if it is downloaded to the local directory earlier.
        For Example: [root@SA ~]# upgrade-cli-client --init --stage-dir /tmp/upgrade --download-path /root/NW --version 11.7.1.0
        Once the message (INFO) Download and extraction of all the necessary NetWitness zips are completed is displayed in the console of the admin server, only then the initialization process will begin.

    Note: If you do not receive the message (INFO) Download and extraction of all the necessary NetWitness zips are completed, run the command [root@SA ~]# upgrade-cli-client --init --stage-dir /tmp/upgrade --download-path <download file path> --version 11.7.1.0 again to stage 11.7.1.0.

    IMPORTANT: After staging 11.7.1.0 (using the Option 2), if the initialization fails, run the command upgrade-cli-client --init --version 11.7.1.0 --stage-dir /tmp/upgrade. If the initialization succeeds, ignore the step 2 Initialize the upgrade and proceed with the further steps in it.

  2. Initialize the upgrade using the following command:
    upgrade-cli-client --init --version 11.7.1.0 --stage-dir /tmp/upgrade

  1. Upgrade the NW Server host, using the following command:
    upgrade-cli-client --upgrade --host-key <ID / display name / (hostname/ IP address)> --version 11.7.1.0
  2. When the NW Server host upgrade is successful, reboot the host from NetWitness Platform user interface in the Hosts view.
  3. (Conditional) If Warm Standby Server is deployed, repeat steps 1 to 4 on the Warm Standby Server host.
  4. 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 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.

External Repo Instructions for CLI upgrade

For information about setting up an external repository, see "Appendix B. Set Up External Repo" in the 11.7 Upgrade Guide for RSA NetWitness Platform. The following instructions assume that you already have an external repository set up. Go to the NetWitness All Versions Documents page and find NetWitness Platform guides to troubleshoot issues.

  1. Stage the 11.7.1.0 files to prepare them for the upgrade:
    • If you are upgrading from 11.5.3.2, 11.6.0.0, 11.6.1.0, 11.6.1.1, 11.6.1.2, or 11.6.1.3, you must stage 11.7.0.0, 11.7.1.0. Log into the NW Server as root and create the following directories:

      /tmp/upgrade/11.3.0.0

      /tmp/upgrade/11.7.0.0
      /tmp/upgrade/11.7.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.7.0.0.zip -d /tmp/upgrade/11.7.0.0
      unzip netwitness-11.7.1.0.zip -d /tmp/upgrade/11.7.1.0
    • If you are upgrading from 11.7.0.0 to 11.7.1.0, you only need to stage 11.7.1.0. Log into the NW Server as root and create the following directory:
      • Option 1 (Manual) : Log into the /root to the directory of the NetWitness Server and create the following directory:
        /tmp/upgrade/11.7.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.7.1.0.zip -d /tmp/upgrade/11.7.1.0
        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.
      • Option 2 (Automated) : Log into the /root to the directory of the NetWitness Server and create the following directory:
        /tmp/upgrade and /root/NW
        and then copy the NetWitness 11.7.1.0 package zip files to the /root/NW directory of the NetWitness Server.
        After this, run the below command to extract, validate, and initialize the 11.7.1.0 zip files:
        [root@SA ~]# upgrade-cli-client --init --stage-dir /tmp/upgrade --download-path <download file path> --version 11.7.1.0
        Here, <download file path> is the location where you need to copy the netwitness-11.7.1.0.zip if it is downloaded to the local directory earlier.
        For Example: [root@SA ~]# upgrade-cli-client --init --stage-dir /tmp/upgrade --download-path /root/NW --version 11.7.1.0
        Once the message (INFO) Download and extraction of all the necessary NetWitness zips are completed is displayed in the console of the admin server, only then the initialization process will begin.

    Note: If you do not receive the message (INFO) Download and extraction of all the necessary NetWitness zips are completed, run the command [root@SA ~]# upgrade-cli-client --init --stage-dir /tmp/upgrade --download-path <download file path> --version 11.7.1.0 again to stage 11.7.1.0.

    IMPORTANT: After staging 11.7.1.0 (using the Option 2), if the initialization fails, run the command upgrade-cli-client --init --version 11.7.1.0 --stage-dir /tmp/upgrade. If the initialization succeeds, ignore the step 2 Initialize the upgrade and proceed with the further steps in it.

  2. Initialize the upgrade, using the following command:
    upgrade-cli-client --init --version 11.7.1.0 --stage-dir /tmp/upgrade
  3. Upgrade the NW Server host using the following command:
    upgrade-cli-client --upgrade --host-key <ID, IP address, hostname or display name of host> --version 11.7.1.0
  4. When the NW Server host upgrade is successful, reboot the host from NetWitness UI.
  5. (Conditional) If Warm Standby Server is deployed, repeat steps 1 to 4 on the Warm Standby Server host.
  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.