3 Replies Latest reply on May 8, 2015 10:33 AM by RichardLetts

    Planning NPM+Module Upgrades

    bharris

      I'm not sure where to put this because this is a overall upgrade Solarwinds question.  As our main application is NPM, I thought this was the best place to post this.

       

      Anyway, I am planning on upgrading our current environment to the latest versions. 

       

      This is what our environment currently looks like: Orion Platform 2013.2.1, SAM 6.0.2, IPAM 3.1.1, NCM 7.0.2, NPM 10.6.1, NTA 3.11.0, WPM 2.0.1, UDT 2.5.1, IVIM 1.9.0

       

      This is the upgrade path that I came up with from following the upgrade path page on Thwack.  Does this path look OK?  I was also wondering if you guys upgrade to the most latest modules for the current version of NPM and then upgrade to the next NPM version of if you just take the minimum module upgrade required for the next NPM upgrade, which is how I approached creating this upgrade path.

       

      NCM 7.2.2 => NPM 10.7 => SAM 6.1 => IPAM 4.1 => NTA 4.0.X => NCM 7.3 => WPM 2.1 => UDT 3.0.2 => NPM 11.0.1 => IPAM 4.2 => IPAM 4.3 => NCM 7.3.2 => UDT 3.1 => NTA 4.1 => UDT 3.2 => NPM 11.5.1 => SAM 6.2.X => WPM 2.2

        • Re: Planning NPM+Module Upgrades
          RichardLetts

          wait till the end to do the NTA upgrades.

           

          If you look at the releases notes for each product they tell you the minimum version you can upgrade from -- I will skip versions if I can

          e.g.

          NTA 2.2.1 ⇒ NTA 3.0 ⇒ NTA 3.1 ⇒ NTA 3.7 ⇒ NTA 3.9 ⇒ NTA 3.11 ⇒ NTA 4.1

          so you don't need to install NTA 4.0

           

          Orion Network Configuration Manager (NCM) Integration; Upgrade Path with NPM:  NPM 10.6 ⇒ NCM 7.2.2 ⇒  NPM 11.0.1 ⇒ NCM 7.3.2

           

          I don't have SAM or WPM, so i don't know where they would fit in the string of upgrades but I'd do it in this order:

          NCM 7.2.2 => NPM 10.7 => SAM 6.1 => IPAM 4.1 => WPM 2.1 => UDT 3.0.2 => NPM 11.0.1 => IPAM 4.2 => IPAM 4.3 => NCM 7.3.2 => UDT 3.2.2 => NPM 11.5.1 => SAM 6.2.X => WPM 2.2 => NTA 4.1


          itallic -- I'd pause somewhere around there as there are three big changes coming to the database coming: Time to take backups, make sure the system is stable and have a 'restore point' in case you need to roll-back.

           

          Bold -- major structural change in the product.

          NCM 7.3.2 with additional pollers merges the Cirrus and NPM databases

          UDT 3.1/2 changes how you add nodes; you will need 3.2.2 to make things happier.

          NPM 11.5.1 has major database changes as well as the new alerting engine

          NTA 4.1 -- needs a flow storage database; this upgrade is pretty much independant of the NPM and other products once you reach NPM 11.x