Performing the application server and remote device agent upgrade

This topic describes how to upgrade the TrueSight Network Automation application server, remote device agent, and the associated components.

Upgrading the application server

A typical upgrade is performed by running the Network Automation installer. Perform the procedure appropriate to the OS used on your computer:

Important: Applicable only if you are upgrading from version 8.9.x

These steps are applicable only if you have multiple application servers in your environment and you plan to transfer the content containing sensitive data across these application servers. For example, Device Security Profiles can contain sensitive data. Transfer refers to importing, exporting, and pushing content using any available method and using Web Services and REST APIs to perform any operation across these servers.

Do the following:

Upgrade one instance to the latest version.
Navigate to the BCAN_DATA directory and copy the keystore.jceks file.
Log on to another instance that you want to upgrade.
Navigate to the BCAN_DATA directory and paste the keystore.jceks file.

Notes

If you want to change from internal to external authentication, or from external to internal authentication as part of the upgrade process for your application server, see Switching authentication type .
During an upgrade of the application server, the installer upgrades the database schema. If you want to preserve your existing database, you must perform a silent upgrade with the -J SKIP_DB_UPGRADE option. For more information, see Preserving the application server database.
If any of the routers that manage endpoints in your environment are defined with multiple IP addresses, you need to enable the Alternate Addresses dynamic field once the upgrade is complete. See Enabling the Alternate Addresses dynamic field.

Switching the authentication type

This section describes how to switch the authentication type used by your Network Automation application server during an upgrade.

Switching from local to external authentication

If you have been using local authentication for your site and you want to switch to external authentication (Active Directory, LDAP, RADIUS, TACACS, or SAML 2.0), perform the following tasks:

Note

After switching from local to an external authentication method, an existing local user would be unable to log on to Network Automation.

Run the Network Automation installer on your application server, and during the upgrade process select the external authentication option.
When the upgrade is complete, log on to the Network Automation system.

Switching from external to local authentication

If you have been using external authentication (Active Directory, LDAP, RADIUS, TACACS, or SAML 2.0) for your site, and you want to switch to local authentication, perform the following tasks:

Run the Network Automation installer on your application server, and during the upgrade process select the local authentication option.
When the upgrade is complete, use the reset password script (reset_password.bat for Microsoft Windows, reset_password.sh for Linux) to reset the password for all users.
These scripts are in the BCAN_HOME \tools directory. See Tools-and-scripts for more information about this script.
Log on to the Network Automation system.
You are prompted to change your password.

Preserving the application server database

You can control how the Network Automation installer treats an existing database only during silent upgrade. By default, the installer upgrades the database schema. You can use the following command-line options to alter this default behavior:

You can use either or both the command-line options in a silent installation. For more information about silent installation, see Running the installer in silent mode.

Upgrading the remote device agent

If you are upgrading the application server, you must also upgrade all remote device agents to the same version as TrueSight Network Automation.

A typical upgrade is performed by running the Network Automation installer. Perform the procedure appropriate to the OS used on your computer:

Upgrading an embedded PostgreSQL database

BMC does not recommend using the Network Automation embedded PostgreSQL database as Network Automation warehouse database because this database is not maintained (backed up, restored, or upgraded) and is removed during the Network Automation system upgrades, thus resulting into the data loss for Network Automation. Using an embedded PostgreSQL database as a data warehouse database also results in poor performance.

In case you have used the embedded PostgreSQL database as the data warehouse database, back up the same before upgrading Network Automation and then restore the same after upgrade. Later, you can migrate the Network Automation data warehouse database to a dedicated standalone PostgreSQL database server. For information about backing up and restoring an embedded PostgreSQL database, see Maintaining-the-database.

Rolling back the upgrade

You can roll back the upgrade if you face any issues post upgrade. Rolling back to a previous version of Network Automation is a multi-step process and is possible only if you have a database backup from the version prior to upgrade.

Perform the following tasks to roll back the application server upgrade:

Uninstall the current version.
Install the previous version from which you have upgraded.
Restore the database from the backup. For instructions, see the database documentation.

Perform the following tasks to roll back the remote device agent upgrade:

Uninstall the current version.
Install the previous version from which you have upgraded.

Next step in the upgrade process

Now that you have successfully upgraded application server and remote device agent, the next step in the upgrade process is to complete the post-upgrade activities.