SOPs for Enterprise Software Upgrade

Purpose

This section provides a brief description of the steps required for build upgrade, validation, and rollback/downgrade procedures.

For NetStorm, NetDiagnostics, NetOcean, and NetCloud

Here, the procedure for upgrading, validating, and rollback of the build described is for NetStorm. For other products (ND, NO, and NC), minor changes are required in the build name accordingly. Rest steps are the same.

Upgrading a Build

Follow the below-mentioned steps to upgrade a build:

  1. Log in to a machine with root user.
  2. Go to path $NS_WDIR/upgrade.
  3. Copy third-party and netstorm build from Build Hub (http://10.10.30.16/home) or get it from your Cavisson representative.
  4. Now, first upgrade the third-party build.

Example: ./thirdparty.4.1.10.20_Ubuntu1604_64.bin

  1. Now, upgrade netstorm build.

Example: ./netstorm_all.4.1.10.20.Ubuntu1604_64.bin

  1. Run the migration shell for any database changes:

nsi_migrate_database -t <testrun> -s <tablespace>

Where, testrun is the current TR running and tablespace you can find using following command:

    • psql test netstorm
    • select * from pg_tablespace;
  1. Run the below migration shell to update alert history if there is a change in current build installed on controller:

nsi_migrate_alert_history_table

Example: nsi_migrate_alert_history_table -t 1234

Where, 1234 is test run number.

  1. After upgrading the build, perform drop schema by following the below-mentioned steps:

psql test postgres

drop schema config cascade

  1. Run the shell to create schema again.

cd bin($NS_WDIR/bin)

./ndi_crt_confui_tbl_def_val.sh

Note: If the schema is dropped before build up-gradation, then no need to execute a shell script. It will be called automatically during netstorm installation.

Validating the Upgrade

Follow the below-mentioned steps for validating the build is upgraded successfully or not.

  1. After upgrading the build, check build up-gradation information is displayed or not.
  2. Build version can be checked by command: nsu_get_version

root@netstorm-ML10Gen9:/home/netstorm/work/.rel# nsu_get_version
NetStorm:Version 4.1.10 (build# 20)
GUI:Version 4.1.10 (build# 20)
CMON:Version 4.1.10 (build# 20)
LPS:Version 4.1.10 (build# 20)
NDC:Version 4.1.10 (build# 20)
NETDIAGNOSTICS:Version 4.1.10 (build# 20)
THIRDPARTY:Version 4.1.10 (build# 20)
JAVA:Version 1.8.0_121
TOMCAT:Version 7.0.59

Rollback/Downgrade the Build

If there is an issue in upgrading the build and build is not upgraded successfully, the process needs to be rolled back by following the below-mentioned steps:

  1. Go to $NS_WDIR/.rel
  2. Copy Build to $NS_WDIR/upgrade from which you want to Rollback.
  3. Follow steps 4 and 5 of the Build up-gradation process.

For NetVision

Below is the procedure for build upgrade, validate, and downgrade for NetVision.

Upgrading the Build

Follow the below-mentioned steps to upgrade a build:

  1. Copy build in upgrade directory from build hub or ask from your Cavisson representative.
  2. Change permissions of third-party and netstorm build.
  3. Execute third-party build in the same path.
  4. Execute netstorm build in the same directory.
  5. Check build up-gradation by using nsu_show_netstorm.
  6. Copy the latest configuration file from $HPD_ROOT/samples (cav_nv.js).

Validating the Upgrade

Follow the below-mentioned steps for validating the build is upgraded successfully or not.

  1. Check HPD server is running.
  2. Check continuous monitoring test is running.
  3. Check all Sessions are capturing in GUI.
  4. Check sessions are moving to DB.
  5. Check if no Exception is coming in GUI by looking all links available.
  6. Check if session replay is working.
  7. Check if parsers are running and aggregating the data.

Rollback/Downgrade the Build

If there is an issue in upgrading the build and build is not upgraded successfully, the process needs to be rolled back by following the below-mentioned steps:

  1. Go to the .rel path of the machine.
  2. Copy previous build to upgrade path from the current path.
  3. Upgrade both third-party and netstorm build.
  4. Change the new configuration file from $HPD_ROOT/samples or copy from the backup if available.

For NetForest

Below is the procedure for build upgrade, validate, and downgrade for NetForest.

Upgrading the Build

Follow the below-mentioned steps to upgrade a build:

  1. Download the new build from the build hub or ask your Cavisson representative.
  2. Copy new build on installation location.
  3. Untar the build.
  4. Make the configuration changes (host, port) in conf
  5. Mention the data path (for nfdb).
  6. Start the application.
  7. Take the backup of the old build.

Validating the Upgrade

Follow the below-mentioned steps for validating the build is upgraded successfully or not.

  1. Check the process is running or not by the following command:
    ps -ef| grep nfdb (for nfdb)

ps -ef| grep node (for nfui) or check data on GUI

Rollback the Build

If there is an issue in upgrading the build and build is not upgraded successfully, the process needs to be rolled back by following the below-mentioned steps:

  1. Kill the process of old builds
  2. Take the backup