cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

SAM 6.9.1 - Upgrading from My Orion Deployment

In the comments of What We're Working On For Server & Application Monitor (Updated July, 2019) you'll notice that I specified for those of you who are on SAM 6.9, you now have the ability to upgrade your whole upgrade from the web console.

pastedImage_1.png

I'd like to explore what this means for those of you who are looking to upgrade to SAM 6.9.1 or even Orion Platform 2019.2 Hotfix 1

In the screenshot below you can see I have my Orion deployment installed with Orion Platform 2019.2, SAM 6.9, and VMAN 8.5 with VMware Events.

Clicking on Settings -> My Orion Deployment -> Updates Available takes me to the following screen.

pastedImage_4.png

I see I have a new upgrade to SAM 6.9.1 available. Clicking "Check Readiness" will allow me to see whether I meet the conditions to upgrade.

Looks like my connection to all the servers in my deployment is good.

pastedImage_5.png

Clicking 'Next" will allow me to see if there are any Preflight checks that would prevent my upgrade from occurring.

pastedImage_6.png

It looks like I need to confirm that I have backed up my database and in addition need to check into some mismatched Microsoft updates across my servers.

pastedImage_7.png

Also, I'm missing some .NET 4.8 updates, but this upgrade will install it for me on those servers. I just need to remember to reboot those machines. For those of you who aren't ready to upgrade, at this point simply hit 'cancel' and plan for your next change window.

Personally I'm ready to upgrade, so I will confirm my database backup and proceed.

pastedImage_8.png

Accept the EULA

pastedImage_9.png

and start my upgrade

pastedImage_10.png

What a wonderful feeling, I didn't have to go anywhere to look for the correct SolarWinds Orion installer. This is how all upgrades should be.

pastedImage_2.png

Note: while my main polling engine is being upgraded, my web console is down. During this time, installation progress will be shown on a temporary page, but after completion, I will be redirected to my main web console.

I recommend not closing this temporary page because the only way to navigate back to it is to RDP into the main polling engine server and clicking on the shortcut "My Orion Deployment"

Happy upgrading! Let us know how it went for you in your upgrade.

Comments

Just upgraded to the new version. Checking out the new digs...

  wrote:

Just upgraded to the new version. Checking out the new digs...

Awesome! looking forward to your feedback

Excellent

Anyone facing issues with SAM agents ?

It looks like the SAM agents can be auto-updated but these will cause the .Net Framework to also update to 4.8. This will be a risk as some applications may have an older version of .Net dependency.

Disabling Auto-update may have a compatibility issue of an older version of agent reporting to a newer platform version.

Any suggestions on AGENT Updates ?

My issue was with upgrading Linux agents. 47 out of 54 servers failed to install the SAM Linux Agent Plugin.

I have the main Orion Server and 3 APE's with my servers spread fairly evenly among them.

Only 7 servers attached to one of my APE's downloaded the plugin.

All servers are running Red Hat Enterprise Linux Server release 7.7 (Maipo) (3.10.0-106​2.9.1.el7.x​86_64 #1 SMP Mon Dec 2 08:31:54 EST 2019 x86_64) on apparently identical VM's.

Our company is on closed for the holidays, so I am not sure what will work to remediate, but have supplied the Admin team with the following:

https://support.solarwinds.com/SuccessCenter/s/article/Application-Dependency-agent-plug-in-installa... 

I had a few issues with my upgrade...

1. Centralized installer was able to connect to my more remote locations, but the software download failed to complete. I did make several attempts, then finally resorted to the off-line installers.

2. WPM - 35 of my 50 monitors failed after the upgrade. When the configuration file (SolarWinds.SEUM.Agent.Service.exe.config) got updated on my 6 players, the custom setting for domain connection needed to be performed again using SolarWinds.SEUM.AgentDomainConfigurationTool.exe. It took me a while to figure out what had changed, and just happened to see the differing values in the config file when I was updating  numWorkerProcesses="7" to numWorkerProcesses="1"

3. Linux agents. 47 out of 54 servers failed to install the SAM Linux Agent Plugin.

I have the main Orion Server and 3 APE's with my servers spread fairly evenly among them.

Only 7 servers attached to one of my APE's downloaded the plugin.

All servers are running Red Hat Enterprise Linux Server release 7.7 (Maipo) (3.10.0-1062.9.1.el7.x86_64 #1 SMP Mon Dec 2 08:31:54 EST 2019 x86_64) on apparently identical VM's.

Our company is on closed for the holidays, so I am not sure what will work to remediate, but have supplied the Admin team with the following:

https://support.solarwinds.com/SuccessCenter/s/article/Application-Dependency-agent-plug-in-installa...

All and all, my first time performing an upgrade was fairly painless.

I'm on 2019.4 and when I click on "Updates & Evaluations" I see... nothing. Do I have to configure something in my Orion environment before this works?

m-milligan  wrote:

I'm on 2019.4 and when I click on "Updates & Evaluations" I see... nothing. Do I have to configure something in my Orion environment before this works?

No configuration should be necessary. Have you opened a support ticket for this issue?

I have not. Now that I know I should be able to see something, I'll open a ticket. Thanks!

Version history
Revision #:
1 of 1
Last update:
‎07-02-2019 02:58 PM
Updated by: