1 3 4 5 6 7 Previous Next 224 Replies Latest reply on Apr 27, 2018 4:39 PM by serena Go to original post
      • 100. Re: NPM 12.2 Upgrade Experience Feedback?
        rschroeder

        Life might be better (?) if everyone just went out & got the latest download of the Updater/Hotfix . . .

         

        It is for me.

        • 101. Re: NPM 12.2 Upgrade Experience Feedback?
          oiram

          Life is great regardless But Orion Installer 1.3.1 (offline one) for sure helps, especially in case of isolated (no internet access) systems.

          • 102. Re: NPM 12.2 Upgrade Experience Feedback?
            wlouisharris

            Hey Bartley, what server O/S verions are you running?  I am running Windows 2012 server and NPM 12.1.  We had extreme difficulties with installers when we were on Windows 2008 R2 server, but as we refreshed to 2012 server we are having less problems.  What are the specs on your servers?   We have 70 gig C and 40 Gig H on our pollers and all our servers are 8CPU/32 gig of RAM VM's.

            1 of 1 people found this helpful
            • 103. Re: NPM 12.2 Upgrade Experience Feedback?
              wlouisharris

              We had a similar issue after upgrading to version 12.1 where we had a memory leak.  It turns out our problem was related to a bad dashboard.  The dashboard was doing a long running query that never finished and spike memory.  It has been my experience with the product most CPU and memory issues are tied back to something that we have done environmentally.  We have had better experiences after applying all the latest hot fixes.

              • 104. Re: NPM 12.2 Upgrade Experience Feedback?
                bartley

                In the meantime, i think most of issues are solved. The new installer 1.3.1.493 that comes with the latest HF worked fine. datacopy over WAN still takes quite a long for me so the online installer still is causing quite a large downtime, so an offline installer will still be preferable for me.

                Also support helped me very good, i think most of my issues are solved now.

                1 of 1 people found this helpful
                • 105. Re: NPM 12.2 Upgrade Experience Feedback?
                  bartley

                  All of my servers are running on Windows 2012 R2.

                  The latest installer and HF solved quite a lot of my issues.

                  1 of 1 people found this helpful
                  • 106. Re: NPM 12.2 Upgrade Experience Feedback?
                    wlouisharris

                    Keep us posted.  I also have a Windows 2012 R2 environment.  We had a lot of problems with version 11.5 and 12.01.  We really stabilized our environment with version 12.1 so we are holding off on upgrading to 12.2.  We will probably do version 12.2 in QA soon.

                    • 107. Re: NPM 12.2 Upgrade Experience Feedback?
                      ecklerwr1

                      We're upgrading two Orion systems from NPM 11.5.3 all the way up to 12.2 and moving off Windows 2008R2 and SQL 2008 today which means... upgrade in place to 12.1 then move the database over to brand new VM's already running 12.1 then upgrade it to 12.2 with the new installer!  Wish me luck friends!!!

                       

                      All of your help and comments have helped us to plan this all out over the past few months!

                      1 of 1 people found this helpful
                      • 108. Re: NPM 12.2 Upgrade Experience Feedback?
                        rschroeder

                        You'll have a great upgrade experience, I predict.

                         

                        The new installers/updaters are much improved over last October.

                         

                        I wished I'd had SW Support WebExed in to assist my process, but after all was done, and had multiple issues, serena was gracious and kindly provided early access to unpublished installers that cleaned up so many issues across five pollers and all my SW modules (NPM, NCM, NTA, IPAM, UDT, VNQM, HA).

                         

                        If I could, I'd send myself a message back in time to last September to say "Be patient; wait until February 2018 to do your SW upgrades, and you'll avoid a lot of frustration."

                         

                        1 of 1 people found this helpful
                        • 109. Re: NPM 12.2 Upgrade Experience Feedback?
                          serena

                          Yay! Even better, all of those unpublished installers are all published and accessible for all to enjoy.

                          1 of 1 people found this helpful
                          • 110. Re: NPM 12.2 Upgrade Experience Feedback?
                            ecklerwr1

                            We're in the middle of this upgrade on a couple systems right now.  We've gotten hung up on the upgrade of NPM and it's complaining about not being able to communicate with the NTA database.  This morning it was working fine on the old versions so no changes to the host machines or anything happened but it won't work now.  Installer is saying "Cannot connect to NTA Storage Database" 4.2 when trying to update NTA on the Orion server it cannot can not communicate with the flow storage database.  This was all working before here in place.  We opened a case and had to leave a message.  I don't know the new case number yet.  Support didn't send the case number.  Support said they'd send an upgrade guide and they didn't do it.  We're stuck now with our in production main SolarWinds Orion system down trying to do the upgrade to 12.2.  As I'm sure you would understand this is VERY frustrating. We're a large company with thousands of nodes under management.

                             

                            Thanks for your comments Rick I really appreciate it!!!  Hopefully we'll be able to get through this upgrade and have it running before Monday.  It hasn't been completely smooth so far :^{

                            • 111. Re: NPM 12.2 Upgrade Experience Feedback?
                              serena

                              Did you use the NTA standalone installer available in your customer portal for the NTA upgrade? Walk me through the installers that you downloaded and used please

                              • 112. Re: NPM 12.2 Upgrade Experience Feedback?
                                ecklerwr1

                                The AZ Solarwinds upgrade is finally complete.  My initial outage window estimate of eight hours on Friday was a bit off since it actually took from 0800 Friday until 0400 on Sunday morning (total 44 hours, btw).  The problem was that there were both a lot of steps and that these steps took a long time to complete.  In fact, though, there was relatively few actual problems encountered, maybe two or three, and all were handled with relative dispatch.  Relevant details below:

                                 

                                Modules:

                                NPM      == Network Performance Monitor

                                NCM      == Network Configuration Manager

                                SAM      == Server & Application Monitor

                                NTA       == NetFlow Traffic Analyzer

                                WPM     == Web Performance Monitor

                                 

                                Steps:

                                1. Backup database on existing SW instance.
                                2. Shutdown additional poller on existing instance.
                                3. Upgrade NPM 11.5.3 to 12.0
                                4. Upgrade NCM 7.4 to 7.5
                                5. Upgrade NPM 12.0 to 12.0.1
                                6. Upgrade SAM 6.2.3 to 6.3
                                7. Upgrade NCM 7.5 to 7.5.1
                                8. Upgrade NTA 4.1.2 to 4.2
                                9. Upgrade NPM 12.0.1 to 12.1
                                10. Upgrade NTA 4.2 to 4.2.2
                                11. Upgrade NCM 7.5.1 to 7.6
                                12. Upgrade SAM 6.3 to 6.4
                                13. Install identical versions on new hosts using new SQL Server
                                14. Shutdown old SQL Server
                                15. Restore existing SW DB to new SQL Server
                                16. Install new NoSQL DB Server software on new Flow DB server
                                17. Copy flow data from old Flow DB server to new Flow DB server (this >400GB copy took 11 hours by itself)
                                18. Reconfigure Solarwinds to use new Flow DB server.
                                19. Deploy new additional poller on azdc-mon05.
                                20. Deploy new additional webserver on azdc-mon06.
                                21. Use new SW installer to perform final upgrade:
                                  1. Upgrade NPM 12.1 to 12.2
                                  2. Upgrade NCM 7.6 to 7.7
                                  3. Upgrade SAM 6.4 to 6.5.0
                                  4. Upgrade NTA 4.2.2 to 4.3
                                  5. Install WPM 2.2.1
                                22. Upgrade NoSQL server software to 4.3
                                23. Run Configuration tool one last time.

                                This is why we always needed improved installer(s).  It is getting better.

                                1 of 1 people found this helpful
                                • 113. Re: NPM 12.2 Upgrade Experience Feedback?
                                  rschroeder

                                  Ugh--what an ugly and time-consuming process.  Trying to decide when to upgrade is the key, I think.  On the one hand you have things working acceptably and people are accustomed to seeing their resources in Solarwinds.  On the other hand the product is growing, improving, adding new fixes and features and functionality with every update.

                                   

                                  Upgrade too early and you won't benefit from the experiences and modifications brought to the process and the patches and hotfixes by people who discover problems--which may cost you weeks or months of frustrating time working with SW Support.  Plus, you have to explain to your peers, your boss, and your customers why things aren't working properly, and when they WILL be working.

                                   

                                  Or, wait too long to upgrade and you can end up with versions that can't be upgraded directly to the present release.  Which may mean a LOT of intermediary upgrades steps, and additional learning curve and problems you hadn't expected.

                                   

                                  Based on my last upgrade from NPM 12.0.1 to 12.2, I'd say that waiting four months from the announcement of the Release Candidate might be a mark I'll try to hit in the future.  Waiting through two or more entire versions to upgrade can be challenging when it's time to do the deed. 

                                   

                                  Previously, I'd experienced so many frustrations that I tended to wait instead of upgrade.  But I can see from your endeavour that waiting may be as bad as going through the version-related issues immediately.

                                  • 114. Re: NPM 12.2 Upgrade Experience Feedback?
                                    ecklerwr1

                                    It's a delicate balance I think.  We definitely waited too long on these two systems... that was the first one... we still have another to do yet!  Having an installer like we have now is a BIG improvement from the old method.

                                    1 of 1 people found this helpful
                                    • 115. Re: NPM 12.2 Upgrade Experience Feedback?
                                      jeepinandy58

                                      My experience is not good. I attempted the upgrade last week, had issues, called in got some assistance but it is still not working. Sent an email to the person I was working with Friday, no response....considering a variety of factors, I was okay with that. Sent another email today and at the end of my day....no response. Not liking this at all. Fortunately for me, I am still running the old version which is a good thing considering I work for a decent size city that cannot afford to be down.

                                      • 116. Re: NPM 12.2 Upgrade Experience Feedback?
                                        ecklerwr1

                                        Keep us posted about this.  It's important to know what kind of support people are getting.  Even my upgrade required a couple calls to SW Support to get through what I did.  What really complicated things was having to move the database to new SQL Server and Orion to new Windows servers.  12.2 NPM won't install on Windows 2008R2.

                                        • 117. Re: NPM 12.2 Upgrade Experience Feedback?
                                          David Smith

                                          ecklerwr1  wrote:

                                           

                                          We're upgrading two Orion systems from NPM 11.5.3 all the way up to 12.2 and moving off Windows 2008R2 and SQL 2008 today which means... upgrade in place to 12.1 then move the database over to brand new VM's already running 12.1 then upgrade it to 12.2 with the new installer!  Wish me luck friends!!!

                                           

                                          All of your help and comments have helped us to plan this all out over the past few months!

                                          Eek - I'm due to run an upgrade from NPM10.7 all the way to 12.2 - They have NPM, NCM, NTA, SAM, IPAM, UDT, WPM & VNQM - This might take a while!

                                          What will your new systems run 2012, 2014, 2016?

                                          • 118. Re: NPM 12.2 Upgrade Experience Feedback?
                                            ecklerwr1

                                            I'm using Windows 2012R2 right now.

                                            • 119. Re: NPM 12.2 Upgrade Experience Feedback?
                                              jeepinandy58

                                              We were running NPM 11.5.2 on Windows 2008. Installed new servers, Windows 2012; installed 11.5.2 on the new servers (evaluation mode so that we can have it running and tested before pulling the plug on the 2008 servers). Install failed, called tech support. They got us through 11.5.2, then 12.0.1 and then 12.2 but none of the installs were tested until we tried the configuration wizard on 12.2. We were advised to continue the install process; in hindsight, I would ensure that all versions/upgrades were fully functional before moving on to the next version. I am currently on hold waiting for tech support to come on line. I understand having issues (that's why we have tech support) but I had let the person that I had been working with know that I was ready and waiting yesterday morning as soon as I got to work, I did not hear back from them until after I had left yesterday evening that they were going to be out the rest of the week and I should call in.... might be a good reason for that but after not hearing back from them on Friday, I am not real happy. Will keep posting as the install/upgrade continues.

                                              • 120. Re: NPM 12.2 Upgrade Experience Feedback?
                                                serena

                                                Wow 10.7.  Care to share your upgrade experience when you do that upgrade?

                                                • 121. Re: NPM 12.2 Upgrade Experience Feedback?
                                                  serena

                                                  There was one case where it wasn't being dismissed but that was fixed in a hotfix. Have you upgraded to the latest hotfixes for the platform?

                                                  • 122. Re: NPM 12.2 Upgrade Experience Feedback?
                                                    Manilyn Ramos

                                                    my installer hangs in "downloading installers for: SolarWInds COre, 2017.3" from the remote sites does anyone here knows on how to resolve this? and do we have offline installers for additional poller?

                                                    • 123. Re: NPM 12.2 Upgrade Experience Feedback?
                                                      jeepinandy58

                                                      Just got done with tech support and 12.2 is up and running. Not sure if it's okay to give a shout out to the people that helped but it's working. Learned a couple of things that may benefit others. Previously I said that I would ensure that all versions/upgrades were fully functional-while on the phone with tech support I was told that would probably be a waste of time. As long as the product installs correctly, it is (and was) best to upgrade in the manner that we did; then, if there are problems you fix the final version.

                                                       

                                                      Prior to calling tech support I went into the log files and copied 4 errors that I was getting and pasted them into a file. I shared this with tech support, the one they keyed in was

                                                       

                                                      "Website configuration failed:

                                                      •   •  Connection to SolarWinds® Information Service did not succeed.

                                                      Last error: The socket connection was aborted. This could be caused by an error processing your message or a receive

                                                      timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'."

                                                       

                                                      Tech support advised that we needed to run a file that was a .NET 4.6 fix it tool. I had a hard time following along but was told this was a MD5 issue-this is not a Md5 hashing issue

                                                      http://downloads.solarwinds.com/solarwinds/Release/PreRelease15/Beta/SolarWinds.FixIt.Md5.1.0.0.7-Beta1.zip

                                                      Due to our network settings, this file could not be downloaded from the server, tech support had me download it and then I copied it over to the server. At that point, I turned control back over to tech support. They extracted and ran it, then repaired the Solarwinds Orion Core Service 2017 (Control Panel). After that we ran the Configuration Wizard again. CF finished successfully this time and 12.2 is running. I was told that I should check all my existing alerts as some may not work the same in 12.2. I logged in to the new web site, I was expecting the initial web page to look very different but it looks about the same. It appears that the main difference is the way we will access adding nodes, alerts, etc.

                                                      1 of 1 people found this helpful
                                                      • 124. Re: NPM 12.2 Upgrade Experience Feedback?
                                                        David Smith

                                                        So depending on your SQL version you could run the upgrade directly on the new box - or at least that is what I'm looking to do.

                                                        1 3 4 5 6 7 Previous Next