Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Upgrading from Pre-4.3 NorthStar with Analytics

 

The special upgrade procedure described in this topic is only necessary if you use NorthStar Analytics and you are upgrading to NorthStar Release 5.1 from a version of NorthStar earlier than Release 4.3.

In all other cases, you can install NorthStar using the procedure described in Installing the NorthStar Controller.

Export Existing Data (Recommended)

This procedure involves running a utility called es_export_import_util.py on the NorthStar application server to export and save your existing data prior to upgrade.

The utility exports data to a file called exportdata.tar.Z in the /opt/northstar/northstar_bundle_5.1.0/db_migration directory.

Note

db_migration directory will be created after RPM bundle is installed (Step 3 in Step-by-Step Procedure).

Ensure that this directory has available space equivalent to at least 10% the size of your Elasticsearch database. For example, a 10GB Elasticsearch database would require 1GB in the /opt/northstar/northstar_bundle_5.1.0/db_migration directory.

Note

Elasticsearch (ES) data is stored on NorthStar Analytics server (if analytics is installed on a separate server than the application) under /opt/northstar/data/elasticsearch/ directory. You can measure the space of this directory as an estimate of ES DB size using the following command:

When you begin this procedure, the script will tell you how much disk space is required and give you the option to stop the procedure if you do not have enough space to continue.

The amount of time required for the export utility to complete depends on the number of export days and Elasticsearch cache memory/CPU cores you have. You can use the utility’s -l option to reduce the number of export days.

You can use the following command to see the utility’s full set of supported export options:

To export and save your existing data, use the following procedure:

  1. Download the NorthStar 5.1.0 software from the NorthStar Controller Software Download page.
  2. Transfer the downloaded tar.gz file to the NorthStar application server.
  3. Untar the Northstar_bundle:
  4. Install the RPM bundle:
  5. Navigate to the db_migration directory:
  6. Launch the export utility and type yes to continue if you agree with the setup information provided. An example follows:

Next, upgrade the NorthStar server. Do one of the following:

Upgrade Procedure with NorthStar Application and NorthStar Analytics on the Same Server

NorthStar analytics must be reinstalled on each NorthStar application server. Use the following procedure:

  1. Do one of the following:

    • If Junos VM is present on the same server as the NorthStar application and NorthStar analytics, back up your JunosVM configuration. (Restoration of the JunosVM configuration is performed automatically after the upgrade is complete as long as you use the net_setup.py utility to save your backup):

      1. Launch the net_setup.py script:
        [root@hostname~]# /opt/northstar/utils/net_setup.py
      2. Type D and press Enter to select Maintenance and Troubleshooting.
      3. Type 1 and press Enter to select Backup JunosVM Configuration.
      4. Confirm the backup JunosVM configuration is stored at '/opt/northstar/data/junosvm/junosvm.conf'.
    • If Junos VM is present on a different server, separate from the NorthStar application and NorthStar analytics, proceed to Step 2.

  2. Save the iptables.
    iptables-save > /opt/northstar/data/iptables.conf
  3. On the NorthStar application server, navigate to the NorthStar 5.1.0 directory:
  4. Uninstall NorthStar analytics:
  5. If Junos VM is present on the same server as the NorthStar application and NorthStar analytics, uninstall the NorthStar JunosVM RPM:
  6. Uninstall Python and its dependency RPMs, and upgrade the NorthStar application:
  7. Reinstall NorthStar analytics:

Upgrade Procedure with NorthStar Application and NorthStar Analytics on Separate Servers

  1. On the NorthStar application server, navigate to the NorthStar 5.1.0 directory:
  2. Upgrade the NorthStar application:
  3. On each NorthStar analytics server:
    1. Untar the Northstar_bundle:

    2. Install the RPM bundle:

    3. Navigate to the db_migration directory:

    4. Uninstall and reinstall NorthStar analytics:

  4. On the NorthStar application server, prepare and redeploy HA analytics data collector settings:

    Select G (Data Collector Setting) from the main menu, and then B (Prepare and Deploy HA Data Collector Setting) from the Data Collector Configuration Settings menu. See Installing Data Collectors for Analytics for more information.

  5. On the NorthStar application server, ensure that analytics data collector connectivity is UP. From the net_setup.py utility main menu, select G (Data Collector Setting), and then select 9 (Test Data Collector Connectivity) from the Data Collector Configuration Settings menu.

Update the Netflow Aggregation Parameter

Between NorthStar Controller Release 4.2.0 and 4.3.0, the possible values for the netflow_aggregate_by_prefix parameter changed. If you are ugrading from Release 4.2.0, you must edit the parameter in the /opt/northstar/data/northstar.cfg file to reflect a valid Release 5.1.0 value.

To edit the value, perform the following steps:

  1. SSH to the NorthStar server.
  2. Using a text editor such as vi, edit the netflow_aggregate_by_prefix= statement in the /opt/northstar/data/northstar.cfg file as follows:
    • If you had the value set to 1 in NorthStar Controller Release 4.2.0, change the value to always.

    • If you had the value set to 0 in NorthStar Controller Release 4.2.0, change the value to disabled.

  3. Manually restart the netflowd process:

Import Existing Data (Recommended)

In this procedure, you run the es_export_import_util.py utility again on the NorthStar application server to import the data you previously exported and saved.

  1. Log in to the NorthStar application server.
  2. Navigate to the db_migration directory:
  3. Launch the import utility: