Solarwinds-Orion-Installer.exe: timeouts during package download

I am in the middle of a new installation of NPM 12.1, NCM 7.6, IPAM 4.3.2 with the primary server and one additional poller in the US and two additional pollers in the UK.

I am trying to install the High Availability option for the UK additional pollers using the Solarwinds-Orion-Installer.exe and tolarWinds Orion Compatibility Check.

I enter the primary server and admin credentials and then specify that I want to download the Backup Server for Additional Polling Engine Protection packages.

To make a long story short, the package download times out.

If I do netstat during the download, I can see the connection between the primary and the source on TCP 17777. I also see that the network adapter on the target does not get above 2.8 Mbps receive during package download.

The NIC on the primary server does not go above 2.8 Mbps send, but if I try to install both HA's in the UK at the same time, the NIC on the primary delivers exactly twice the bandwidth (5.6 Mbps).

The latency between the primary and the targets is less than 100 milliseconds. During a regular file copy, the NIC will burst to 70 to 100 Mbps or more.

Is there something that can be done to get the package download to go faster than 2.8 Mbps over TCP 17777?

Find more posts tagged with

installer

polling engines

npm 12.1

scalability engine

High Availability

Accepted answers

serena

We have a KB for this scenario. Let me know if this helps. Failed to download or run the Scalability Engine installer from the main server - SolarWinds Worldwide, LLC. Help and Su…

All comments

chad.every

I've run across this before. Here are some steps that you can try but they aren't necessarily supported but have been verified to work.

Step #1 – Download the main product installers to each additional polling engine prior to upgrading the main

Step #2 – Extract the installers for each product module into their own directory using a tool like 7-Zip.

Step #3 – Upgrade the Main Orion server per-usual methods.

Step #4 - Run the scalability engines installer on the APE and click through until you see the screen to select installation type (AP/AW/HA)

Step #5 - Go to the %temp%\SWOrionSetup[currenttimestamp]\subinstallers\ directory on the APE where you'll see a folder for each module, e.g. CORE_2017.2.100, NPM_12.1.100. Each folder contains manifest, which has a list of files (msis) that need to be dowloaded here. All files which are needed to satisfy the requirements were extracted in step #1. Simply copy them over the appropriate directory. E.G. copy CoreInstaller.msi to the %temp%\SWOrionSetup[currenttimestamp]\subinstallers\CORE_2017.2.100 directory. If you don't know which files belong where, you can

Put Core.msi to CORE folder, that's obvious and it's the largest file by far
Put everything everywhere, that way you're sure it'll be on the right place
Continue with installer, it will skip any files that are already in place

central.services

I've thrown a wobbler at my account manager twice over this and had to resolve in a similar way. when the installer quits it deletes all the files its already downloaded and starts again. I made a complete copy of this folder before I quit the installer and then when I started the installer again I found the new temp folder and pasted the previous files into it, it took me a few cycles to get everything the first time I did it but only a couple when just upgrading a couple of components (NPM/SAM)

Solarwinds developers really need to change this behaviour with a retry dialog or just dump the silly 30 min time limit altogether.

serena

We have a KB for this scenario. Let me know if this helps. Failed to download or run the Scalability Engine installer from the main server - SolarWinds Worldwide, LLC. Help and Su…

lewisvts

The issue with this set of instructions is the scalability Engine Installer does not have a “Server Selection role screen”. The install runs immediately and initiates a SolarWinds Orion compatibility check and starts downloading packages from the Main Server. So you have no ability to PAUSE so you can copy the file.

1. I had to Pre-create a folder named CORE_xxxx.x.xxxx with the CoreInstaller.msi file already in it. (This is to save you time because you have to be very quick in this process)

2. Run the Scalability Engine installer and you will want to IMMEDIATELY copy the folder you created CORE_xxxx.x.xxxx\CORE_xxxx.x.msi to the location %temp%\SWOrionSetup[currenttimestamp]\subinstallers\

3. Let the Scalability Engine installer continue to run and I had success.

shaneshelton

Sure would be sweet if you guys would just fix this and let it download at max speed. Timing out on downloading from our primary poller over a 1Gbps link and 47ms of latency is a bit ridiculous. Plus we are forced to use your scalability installer and it doesn't work at all. Great there is a workaround, but how about you just fix your software.

serena

There are a few feature requests on this already that are being worked on. For example: