Upgrade a Standalone Server

Install the Software › Upgrade a Standalone Server

Upgrade a Standalone Server

A standalone deployment consists of a single server that hosts all of the components: the Harvester and the NFA console. Complete the steps in this topic to upgrade the Harvester and NFA console on a single Windows server or virtual machine.

Notes:

A standalone upgraded deployment of CA Network Flow Analysis 9.1.3 uses a two-tier architecture, even if you previously had a standalone deployment with three-tier architecture.
If you interrupt and restart the upgrade, the upgrade resumes from your most recently saved change.

Before You Begin: Verify that the server is upgrade-ready as described in Verify Preparation of the Windows Servers.

Follow these steps to complete the Harvester phase of the upgrade:

Run the Console tool:
1. Log in to the standalone server as a user with administrator privileges for the system and for CA Network Flow Analysis.
2. Verify that the consoletool-exe.jar file is on the server--for example, on the Desktop. If you do not have this file, download it.
  The Console tool prepares the system for the upgrade.
3. Double-click the consoletool-exe.jar file in Windows Explorer or enter the following string at a command prompt:
```
java -jar consoletool-exe.jar
```
  To launch the Console tool by double-clicking the file, Windows Explorer must have the correct association for .jar files.
  
  The ConsoleInfoToPollerTool<yyyy-mm--dd>.log file opens when the Console tool completes--whether the tool completes successfully or fails. The log is saved in the <install_path>\Reporter\Logs\ directory.
  
  The Console tool cannot complete successfully if the system has undeployed interface aggregations or unscheduled merge or delete interface tasks. If the tool does not complete successfully, note the error messages in the log file and contact CA Support.
Stop the pump service:
1. Click Start, Programs, Administrative Tools, Services.
2. Right-click the NetQoS Reporter/Analyzer Pump service.
3. Select Stop in the right-click menu.
  The pump service stops.
Start the Harvester phase of the upgrade: Double-click the NFHarvesterSetup9.1.3.exe file. If you do not have this file, download it to the server as described in Prerequisites.
A check verifies that the server has a supported version of the Java Runtime Engine (JRE) installed. If the check fails, an error message opens. You cannot launch the installation or upgrade program until this problem is corrected.

If the server passes the Java prerequisite check, the program starts and the language selection screen opens.
Verify that the appropriate language is selected, then click OK.
The Welcome screen opens.
Click Next in the Welcome screen.
The CA NFA Harvester License Agreement screen opens.
Review and accept the license agreement:
1. Read the license agreement and scroll down.
2. If you want to continue under the terms of the license agreement, click the option to accept it. This option is activated when you scroll to the bottom.
3. Click Next.
  Prerequisite tests are run to identify problems on the server. If a problem is found, an error message opens. A critical problem causes the program to exit. A Pre-requisite Check Warning message or other warning message opens for non-critical problems, which gives you the option to make corrections now or after the installation or upgrade is complete.
Review the test results in the Pre-requisite Check Warning message, if it opens:
1. Correct problems now or wait until the program finishes. For more information about the warnings, see the Troubleshooting section.
2. Click OK to close the message.
  Your system is tested to determine whether the installed version of CA Network Flow Analysis is supported for upgrade. If a supported version is located, the Upgrading Existing Installation message opens.
  
  Once the server passes the required checks and you close any warning messages that appear, the Choose Install Folder screen opens. This screen displays the original root installation path as the default setting.
Verify that the specified installation directory is correct, then click Next.
Important: If you do not use the original installation path, the upgraded software will not run properly.

If the program does not find certain expected directories in the installation path, an error message opens and the upgrade stops. This problem does not occur when the previous software installation is fully functional.

The Pre-Installation Summary screen opens.
Review the pre-installation information, then click Install.
The Installing Harvester screen opens, which shows the progress. When the upgrade is complete, the Install Complete screen opens and reports any errors that occurred.
(Optional) If errors occurred during the upgrade, see the following logs for details:
- General installation log: <install_path>\Harvester_Install_<timestamp>.log (where <timestamp> is the time that the log was created)
- Upgrade migration log: <install_path>\migrator.log
Click Done in the Install Complete screen.
The Harvester upgrade program closes.

Follow these steps to complete the NFA console phase of the upgrade:

Start the NFA console upgrade software: Double-click the RAConsoleSetup9.1.3.exe file in Windows Explorer. If you do not have this file, download it to the server as described in Prerequisites.
A check verifies whether a supported version of the Java Runtime Engine (JRE) is installed. If the check fails, an error message opens. You cannot launch the upgrade program until this problem is corrected.

If the server passes the Java prerequisite check, the program starts and the language selection screen opens.
Verify that the appropriate language is selected, then click OK.
The Welcome screen opens.
Click Next in the Welcome screen.
The NFA Console License Agreement screen opens.
Review and accept the license agreements:
1. Read the NFA console license agreement and scroll down.
2. If you want to continue under the terms of the NFA console license agreement, click the option to accept it This option is activated when you scroll to the bottom.
3. Click Next.
  The Third-Party License Agreement screen opens.
4. Read the third-party license agreement and scroll down.
5. If you want to continue under the terms of the third-party license agreement, click the option to accept it. This option is activated when you scroll to the bottom.
6. Click Next.
  Prerequisite tests are run on the server. If an error message opens that requires attention, see Troubleshooting.
Review the test results in the Pre-requisite Check Warning message, if it opens:
1. Correct any noncritical problems now or wait until the upgrade program finishes.
2. Click OK to close the message.
  A test verifies that the installed version of CA Network Flow Analysis is supported for upgrade. The Singlebox Confirmation message opens when the verification is complete. This message asks you to confirm that you want a standalone deployment of CA Network Flow Analysis.
Review the Singlebox Confirmation information and click OK.
The Pre-Installation Summary screen opens after a moment.
Review the pre-installation information, then click Install.
The Installing NFA screen opens. Progress is shown in the status bar and messages. When the NFA console upgrade is complete, the Install Complete screen opens.
Exit from the upgrade program:
1. Select one of the restart options:
  - Yes, restart my system: Restart the system as soon as you click Done.
  - No, I will restart my system myself: Defer the restart to be performed manually.
2. Click Done.
  The upgrade program closes after a moment. If you selected the option to restart now, the system restarts and the upgrade is finalized.
  
  If you upgraded from ReporterAnalyzer 9.0.1, migration of DSA database table data begins as soon as the CA NFA DSALoader service restarts. If you have many agents and an extensive amount of stored data, migration may continue for some time. When migration is complete, the CA NFA DSALoader service stops itself and does not restart. The service state change is recorded in the following log: \Netflow\Logs\dsaLoaderErrors-<yyyy-mm-dd>.log. Reports have limited access to historical (15-minute) data until the migration is complete.

Note: The revision history shows that the software is upgraded to the correct version. To display the revision history, complete the following substeps:

Start MySQL by entering the following command in a Command Prompt window: mysql
Display the revision history by entering the following command:
select * from revision_history

Next: Complete the post-upgrade tasks.