Appendix A. Offline Method (No Connectivity to Live Services) - CLI

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

Prerequisites

Make sure that you have downloaded the netwitness-12.1.0.0.zip file from NetWitness Community (https://community.netwitness.com/) > Products > NetWitness Platform > Downloads > Version 12.1 > Full Product Downloads to a local directory:

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 12.1.0.0 files to prepare them for the upgrade.
    • Log into the NW Server as root and create the following directory:
      /tmp/upgrade/12.1.0.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 command: unzip netwitness-12.1.0.0.zip -d /tmp/upgrade/12.1.0.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.

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

  3. Upgrade the NW Server host, using the following command:
    upgrade-cli-client --upgrade --host-key <ID / display name / (hostname/ IP address)> --version 12.1.0.0
  4. When the NW Server host upgrade is successful, reboot the host from NetWitness Platform user interface in the Hosts view.
  5. Repeat steps 3 and 4 for other component hosts.

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

  1. Stage the 12.1.0.0 files to prepare them for the upgrade.
  2. Log into the NW Server as root and create the following directory: /tmp/upgrade/12.1.0.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 command: unzip netwitness-12.1.0.0.zip -d /tmp/upgrade/12.1.0.0

    3. 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 12.1.0.0 --stage-dir /tmp/upgrade
  4. Upgrade the NW Server host using the following command:
    upgrade-cli-client --upgrade --host-key <ID / display name / (hostname/ IP address)> --version 12.1.0.0
  5. When the NW Server host upgrade is successful, reboot the host from NetWitness UI.
  6. Repeat steps 3 and 4 for other component hosts.

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.