NPM 2019.4 Hot Fix 1 - Issue

dunky2k

Hi All,

I had an issue with NCM and TFTP Config transfers and the fix was to apply NPM 2019.4 HF1 to all of my Orion servers.

I applied this fix as instructed to my Main Poller first and then to my Additional Poller, then my HA Additional Poller and finally my HA Main Poller.

When I try to re-activate my HA Pools, i can re-enable the Additional Poller Pool, however i cannot re-enable my Main Poller Pool due to difference in software versions between Pollers (see Below)

As you can see my Primary Main Poller appears to have a different version of CloudMonitoring Installed to the others, but the same executable was applied on all servers.

How can i resolve this issue, so that all servers have the same software version to get my HA solution back to full working order.

Thanks in advance.

dunky2k

I have since resolved my issue by doing the following.

1. Copy the \Program Files (x86)\Solarwinds\Orion\Packaging\Repository\Orion.CloudMonitoring.2019.4.1.1914.opkg file from the main poller to the same location on the standby poller.
2. Edit the \Program Files (X86)\ Solarwinds\Orion\Packaging\Roots\Orion.Installer.Packaging.roots file and modified the line for Cloud Monitoring to say  <required id=”Orion.CloudMonitoring” version=”[2019.4.1.1914,]” />
3. Run the configuration wizard on the standby poller.

On completion of the configuration wizard, the HA checks now showed that the correct version of Cloud Monitoring was installed on both the Primary / Standby Pollers and I was able to re-enable my HA pool.