Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > Network Performance Monitor (NPM) > Upgrade multiple Orion Platform products - Video

Upgrade multiple Orion Platform products - Video

Table of contents

Updated January 9, 2017

Overview

In this video (23:46), we will show you the steps for upgrading multiple products on the Orion Platform. We will upgrade NPM 10.5, SAM 5.2 and NTA 3.11 to their latest versions. In this scenario, we will also be upgrading an additional polling engine.

If you are currently using NPM version 10.3 or earlier, we recommend that you perform a fresh installation.

 

Environment

All Orion Platform product versions

 

Related Resources

 

Video Transcription

 Before you start this process, you should perform the following steps in order to upgrade successfully:

  •  Review system requirements
  • Gather credentials
  • Run all Windows updates
  • Backup your database
  • Schedule the upgrade
  • Notify your company

For additional information, we recommend that you check out the “Upgrading the Orion Platform” video.

Also, if you are planning to migrate your Orion Platform server, we recommend that you upgrade before doing the migration.

For more information on this process, please watch the “Migrating an Orion Platform Product Installation" video.

https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Upgrading_the_Orion_Platform_-_Video

https://support.solarwinds.com/Success_Center/Network_Performance_Monitor_(NPM)/Migrating_an_Orion_Platform_Product_Installation_-_Video

We begin by going to the Product Upgrade Advisor and selecting each of the products that is currently installed.

Next we click Auto-Add Latest Versions of Products Selected, and then click Check Compatibility.

Since we are already logged into the Customer Portal, the products are immediately available for download.

There are a few things to take note of here:

First, our environment does meet the requirements for these upgrades.

Second, these are the steps we need to follow in this specific order.

Third, we have the option of downloading each of these new product versions directly from this page or we can export or email this list as a PDF file.

And finally, because we are upgrading NTA to 4.2 from 3.11, there are architectural changes to the product which we need to be aware of. If we click on the link to the FAQ page, we can review these changes in detail.

In version 3.11, NTA held its information in the Orion database. In versions 4 and later, that information is currently held in a Flow Storage Database. This is a separate database server. It needs to be 64bit and meet all the requirements outlined in this document. It is important to note that this server must be configured in your environment before you begin the upgrade process.

For the purposes of this demonstration, we do have a properly configured server available where we will install the Flow Storage Database.

For production environments, SolarWinds recommends that you have a separate SQL server, a separate NPM server and a separate database for NTA. Because we are also upgrading an additional polling engine, we will need a total of 4 separate servers for this upgrade scenario.

 

Before we run the installation, we need to make sure that the maintenance is current.

We can check that by navigating to the SolarWinds License Manager. As you can see, all of our products have a future expiration date so we are okay to proceed.

However, if any of these had expired, we would need to apply the license from the Customer Portal before continuing.

The next step is to open the Orion Service Manager and shutdown all services on the main polling engine. Also, because we are upgrading an additional polling engine, we need to shutdown everything on that one as well.

Once this step is completed, we can go to the Upgrades folder where we previously downloaded and extracted all the necessary files from the Upgrade Advisor. Accoring to our upgrade path, we need to start with SAM 5.5.

Right click on the file and select Run as Administrator.

You do have the option to send data and usage statistics to SolarWinds. For the purposes of this demonstration, we will select NO.

We have backed up our database, so we type YES and click Next.

We accept the License Agreement and we are ready to begin.

Once the installation is complete, click Finish to exit the setup wizard and launch the configuration wizard.

Click Next to continue. Since we are not changing any of these service settings, we can click Next again and start the configuration process.

We are performing multiple upgrades in this scenario, we don't want to launch the Orion Web Console yet.

At this point, we are going to switch to our additional polling engine and upgrade SAM here as well.

We have already stopped all services on this server so we can close the Orion Service Manager and navigate to the upgrades folder.

We right click on the relevant installer file and select Run as Administrator.

When the setup wizard opens, we go through these selections the same way we did for the previous upgrade.

Once the setup wizard has completed the installation, click Finish to close it and launch the configuration wizard.

Since we are not going to change any of these service settings we can click Next to start the configuration.

Okay. The configuration was successful on the additional polling engine, so we can switch back to our main Orion server and go to the next step of our upgrade.

 

If we take a look at our upgrade path for this multiple product scenario, we see that the next step we need to complete is to upgrade NPM 10.5 to NPM 10.7.

Once again, we start by shutting down all services on the primary Orion server. We then close the Service Manager and run the NPM 10.7 installer file.

We make the necessary selections on these first few screens and then click Next to start the installation.

When the application upgrade is complete, we click Finish and launch the Configuration Wizard.

The database settings will stay the same so we can just click Next.

This message is reminding us that we need to make sure that the Additional polling Engine server has been shut down. Once we confirm that it has, then we can click Next.

We are using the existing account so we can click Next.

We will use the existing location for the website so again we can click Next.

We confirm our settings and start the configuration.

Skip website optimization.

We don't want to launch the Orion Web Console yet so we un-check that box and click Finish.

The next step in our upgrade path is to install NPM 10.7 on the Additional Polling Engine.

Whenever you perform multiple upgrades, there is going to be lots of repetition. The steps for upgrading the Additional Polling Engine are exactly the same as they were for the Orion server.

We make sure all the services are stopped and close the Service Manager.

Navigate to the correct installer file, right click on it and select Run as Administrator.

 

We run through the setup wizard and perform the installation.

Click Finish and start the Configuration Wizard

We can click through all of these selections because they are the same as the ones we made on the Orion server. Then click Next to run the configuration.

Click Finish and we are ready to move on to the next step in our upgrade.

According to the Upgrade Advisor, the next step is to upgrade to SAM 6.1.1 on the primary Orion server. We know the installer is going to remind us that services on the additional poller need to be shut down, so we can do that now while we are still here.

We switch back to the primary server and shutdown everything.

Close the Service Manager and run the SAM 6.1.1 installer file.

Once the installer has finished, we run through the Setup Wizard the same way we have before.

And then click Finish.

Sometimes this dialog box appears. It wants us to verify who is performing the upgrade. Click Continue and we will go to the Configuration Wizard.

Click Next through these pre-selected options.

Skip website optimization.

One thing to note is that sometimes when you skip website optimization during a multiple step upgrade, the configuration wizard may not be able to build a web request to the website because it can't verify that the page is actually coming up. This should not be a concern because when we have completed the final step in our upgrade path we will let website optimization run. It just means that this part might go slowly so just be patient and allow the configuration wizard to continue.

Okay. It did manage to pass without failing the website check, so we can deselect this check box once again and click Finish.

Next, we will go to the additional polling engine and perform the same upgrade there.

Stop services. Run the SAM 6.1.1 installer file. Click Next to run a compatibility check. Click Next. Type Yes. Accept the license agreement. And start the installation.

Click Finish. Verify registration. And launch the Configuration Wizard. Okay the configuration was successful which completes that step of our upgrade.

Before we switch back to the primary polling engine, we will confirm that all services are stopped here because that will be a requirement for the next step.

Let's review our upgrade path and see where we are in our process.

We just completed the upgrade to SAM 6.1.1 on both the primary polling engine and the additional polling engine.

Next, we will upgrade NPM 10.7 to 11.5.3.

We start by shutting down all services in the Service Manager. Run the installer file.

This is telling us that we need to install the .NET Framework update. In order to continue, we need to click Install.

To complete the .NET installation we will need to reboot.

Once we are back to our desktop, the installation should continue right where it left off. Click RUN. Sometimes after a reboot, the update can take some time to complete. Be patient and wait for the installer to respond. (pause) There it goes.

Click through these first few selections.

For this demonstration, we will select Enable QOE Later and click Next.

When the installation is done, click Finish and launch the Configuration Wizard.

Once again, we are not making any changes in the Configuration Wizard so we can click Next through all of these screens.

Okay. Sometimes when we skip website optimization the website configuration will fail. Since we will be optimizing the website when we perform the final upgrade step, this is not a problem. Click Finish and we can proceed with the upgrade on the additional poller.

Stop all services and close the Service Manager.

Run the NPM 11.5.3 additional poller file.

Allow it to install the .NET Framework update.

When that's done, reboot the computer and let the installer pick up where it left off.

Make these selections and click Next to complete the installation.

Confirm registration.

Click Next through the Configuration Wizard set up. And click Finish when it is done.

 

Let's take a look at our upgrade path and see what we need to do next.

We have completed the upgrade to NPM 11.5.3 on both the primary polling engine and the additional polling engine. So now we will upgrade to SAM 6.2.3 on both of our pollers.

We start by shutting down all services. We are doing this on the primary Orion server but we also need to do it on the additional polling engine as well.

Close the Service Manager and run the correct installer file.

Once again, we run through the Setup Wizard and complete the installation.

Click Finish(pause) confirm registration (pause) and launch the Configuration Wizard.

Click Next through the pre-selected configurations and allow the Wizard to run.

Skip website optimization for now. And then click Finish.

We will now go through the exact same steps for our additional poller.

We stop services and run the installer file.

Click through these setup screens and continue the upgrade.

Click Finish(pause) verify registration (pause) and start the Configuration Wizard.

When it is done, click Finish.

We have completed the upgrade to SAM 6.2.3 on both of our pollers and now we are going to upgrade to NPM 12.

Once again, we start by shutting down services and closing the Service Manager. We have already shut down service on our additional poller and you will need to do that as well before continuing with the next step of the upgrade.

Run the NPM 12 installer.

Install the .NET Framework and then restart the computer.

Once we return to the desktop, we will run the installer and allow it to continue from where it left off.

Follow the prompts and click Next.

Click Finish and launch the Configuration Wizard.

 

Once again, since we are upgrading without changing any of our settings, we can just click Next through all of these.

Skip website optimization and click Finish.

Next, we will perform the same upgrade on our additional polling engine.

Stop all services and close the Service Manager.

Run the installer and install .NET Framework when prompted.

 Restart the computer and complete the installation.

When done, click Finish.

 

Run through the Configuration Wizard the same as before.

And when it's done, click Finish.

Let's take a look at where we are in our upgrade process.

We just completed the upgrade to NPM 12 on both our primary poller and our additional poller.

Next, we are going to upgrade to NTA 4.2. This step needs be performed on our NTA Flow Storage Database server. This server must meet certain requirements that are outlined in detail on the "NTA 4 installation FAQ" page which can be found in the SolarWinds Success Center.

On our NTA server, we are going to select the NTA 4.2 installer and right-click on it to Run as Administrator.

This is telling us we need to install .NET in order to continue. We will click Install.

In this case, it installed .NET without requiring a reboot so we can continue from here.

The NTA installer package is universal, which means it can install its components on any of these devices. The installer will proceed based either on what it recognizes in the environment or what we select.

We'll click Next and select the second option: I would like to install the NTA Flow Storage Database on this server. Orion NPM is already installed on a different server.

Now we need to enter the credentials for our primary database so that this server can receive flows from that one.

Enter the IP address, username and password, and then select the database from the drop down menu.

Click Test Connection.

The test was successful so we can click Next

 

This is warning us that our system does not meet the minimum suggested requirements. For full production deployments, we recommend that the Flow Storage Database should have at least 4 CPUs and 16 gigs of RAM.

Since this is just a demonstration we don't need to be concerned with this, so we will just acknowledge the warning and continue.

 

This brings us to the Setup Wizard where we can click through these next few screens (pause) and start the installation.

We click Finish and move on to the configuration process.

 

This is where you can designate a device for backups. Although this step is not required, we strongly encourage you to do so. Click OK and wait for the configuration process to finish.

And that's it!

The next step in our upgrade path is to install the NTA package on the primary server.

Once again, we start by shutting down all services and closing the Orion Service Manager. Remember, this needs to be done on the additional polling engine as well.

After that, we navigate to the NTA 4.2 installer and right-click to Run as Administrator.

This is the same universal package that we just installed on the Flow Storage Database. Now we are going to install it on our primary server.

Next, we will select the first option: Install NPM and NTA on two separate servers.

This brings up a box where we need to enter the IP address of the Flow Storage Database.

Test the connection. It was successful so we click Next.

Click through these next few screens and select Install.

Once the installation is complete click Finish, verify registration and click OK.

The options for the Configuration Wizard are pre-selected so we click Next(pause) Next(pause) and Next again to start the configuration process.

Okay. We've seen this message before. The website configuration failed because of the web request. We don't need to worry about this because we will allow website optimization to occur in the next step of our upgrade.

We just completed the upgrade to NTA 4.2 and we are now ready for the final step which is upgrading SAM 6.2.3 to SAM 6.2.4.

We start by shutting down services on our primary Orion server and closing the Service Manager.

Next, we run the installer.

Click through these screens, perform the installation and then click Finish.

Verify registration, click OK and the configuration Wizard will launch. Click Next through these settings because they are not going to change and wait for the configuration to finish.

As you can see, the Orion website is setup even though we were not prompted to perform website optimization. The reason for this is that all the website pages are pre-compiled now so they will be fast out-of-the-box and you don't need to go through the process of optimizing them.

We still need to install SAM 6.2.4 on the additional poller so we won't launch the web console yet.

 

We start by shutting down all services on the additional polling engine and closing the Service Manager.

Run the installer file. Click through the prompts and complete the installation.

Click Finish, (pause) Continue, (pause) Next, (pause)  Next, (pause) and Next again to start the configuration.

And we are done! We have successfully completed all of the steps in our upgrade path. At this point, it is a good idea to launch the Orion Web Console and verify that everything is functioning correctly in your environment.

We won't go through that step here because it is addressed in other videos.

If you have any questions about NPM, SAM, NTA or any of the other SolarWinds products, please visit support.solarwinds.com.

 

 

Last modified
13:29, 10 Jan 2017

Tags

Classifications

Public