83 Replies Latest reply on Dec 11, 2017 10:09 AM by rschroeder

    NPM 12.2 Upgrade Experience Feedback?

    orioncrack

      Anyone have any upgrade experiences for the general release?

       

      We are looking to upgrade our entire SW suite in addition to NPM and would like to hear any feedback.

       

      Also, is the RC code the same as the GR code?

       

      Thanks in advance

        • Re: NPM 12.2 Upgrade Experience Feedback?
          cjfranca

          What the Version now ?

          • Re: NPM 12.2 Upgrade Experience Feedback?
            driegel

            Everything went extremely smooth for me. I upgraded NPM, SAM, NCM, UDT, IPAM, and VIM. Much faster upgrade than normal and didn't run into any issues.

            2 of 2 people found this helpful
            • Re: NPM 12.2 Upgrade Experience Feedback?
              apap

              We built out a new server to finally get off of 2008.   I was rather dreading this migration and update but it could not have been smoother.   I scheduled a 6 hour downtime window and we were back up and running in just over two ( and of course half of that time was waiting for the Website Optimization to complete )    We migrated/updated  NPM, NCM, IPAM, SAM, WPM and NTA.   No issues.

              • Re: NPM 12.2 Upgrade Experience Feedback?
                r0berth1

                Upgraded from NPM 11.5.2, NTA, SAM, and SRM for that version all the way to 12.2. took a while but the Upgrade advisor helped a lot. only issue is that every time a page refreshes the stupid pencil popup screen keeps coming up. how do you stop that? this is driving me crazy and I can not figure out how to turn it off.

                • Re: NPM 12.2 Upgrade Experience Feedback?
                  bmallon

                  Finally an all-in-one update installer!

                   

                  My upgrade went relatively smooth. I had a little trouble with upgrading my additional poller because it kept timing out. The poller install package has a hard limit of 30 min to gather all the info from the main poller. I found that if you grab 'CoreInstaller.msi' and 'MIbs.msi' from C:\ProgramData\Solarwinds\Installers on the main poller and manually copy them to your additional poller you can cut a bunch of that 30 min window. Copy those files to your desktop. Then start the install on the additional poller. As soon as you start, you need to look for C:\Users\[your user]\AppData\Local\Temp\2\SWOrionSetup[datestamp]\subinstallers\CORE_2017.x\. (This directory won't be created until you start your install.) Immediately paste those files you copied over to your desktop into this directory and it'll shave off almost a gig of download (depending on the number of modules in your environment) and help keep you from timing out.

                   

                  It's well worth the upgrade. I'm looking forward to future upgrades with the new all-in-one installer.

                  2 of 2 people found this helpful
                  • Re: NPM 12.2 Upgrade Experience Feedback?
                    christopher.t.jones123

                    The only feedback i have is that after the upgrade a number of thresholds for ASA hardware health seemed to be messed up (using Orion defaults). to stop the alerts i had to go in there and set custom thresholds. The values it populated were correct, just the thresholds were messed up.

                     

                    But im loving the new ASA insight and ACL insight it has.

                     

                    As far as upgrade process i enjoyed the new installer that they have for it. No longer needing to go through the upgrade adviser was nice. was able to update 4 products (NPM 12.2, NCM 7.7, SAM 6.4 HF 1, and NTA 4.2.3) all in under an hour. And there were no issues or errors with the actual install process. Like i said the only problem that i encountered is what was described above.

                    • Re: NPM 12.2 Upgrade Experience Feedback?
                      rschroeder

                      This afternoon I had a successful upgrade from NPM 12.0.1 to 12.2.  Thanks to serena and her peers, I think we all learned some useful things about users like me, and ASA 5525-X's, and the upgrade process.

                       

                      Time will tell how much new learning curve I have in front of me, but this upgrade certainly shows tremendous progress towards simplifying and making a "complete" upgrade of all SW products intuitive and successful.

                       

                      It went more smoothly, and much better, with less frustration on my part, than all previous Solarwinds upgrades I've done.

                       

                      Kudos to you Solarwinds!

                      • Re: NPM 12.2 Upgrade Experience Feedback?
                        BakerD

                        Environment before upgrade.

                        NPM 12.1, NTA 4.2.2, VMAN 7.1, IPAM 4.5.0, NCM 7.6, SAM 6.4, SRM 6.4

                         

                        First about a month ago I started preparing and moved our main NPM/Orion from 2008 server to 2016.  Then a few weeks ago moved NTA from 2008 to 2016.  Our SQL was/is already on a new platform being supported.  We used to have STM or the old profiler running on a 2008 server too, but no longer use it so just disabled that integration to be left with just SRM.

                         

                        Ran the new install file.  I didn't note all the warnings, but nothing was a red flag not allowing me to continue.  Even though we have more RAM and CPU cores than required, it complained because our VM environment has 2.2GHz and not the required 3.0 I think it said.  Another warning was on our VMAN 7.1 saying we would either need to migrate after the upgrade, or moved to VMAN 8 appliance.

                         

                        This was probably the smoothest large update I have done as we had 5 product updates.  I was nervous and worried.  Once finished, I ran NTA 4.3.2 on our separate DB server.  I then ran the VMAN wizard to change from 7.1 appliance to the new VMAN Orion poller.

                         

                        Total outage was around 35 mins for us.

                         

                        I have noticed some bugs/issues, but as for the upgrade process I'm relieved and hope they continue to build on this and become more comfortable for all.

                        • Re: NPM 12.2 Upgrade Experience Feedback?
                          hoppingubu

                          Upgrade 12.2 RC1 - RC3 to 12.2 official. Seems kind of weird, but RC3 became the defacto official.

                           

                          Anyway, I have noticed some interesting anomalies that have been a bear to troubleshoot.

                           

                          First: One of my ASA devices would not show serial number and site to site VPN. In fact I have to make sure that only the Node Details my SolarWinds is selected to provide the SNMP data for the details. Anything other poller the device will become an unknown.

                          Second: I just went and looked at the reports to find the report that provides the inventory which would let me mitigate the fact that one of three ASA devices doesn't show the serial number and behold, there are 0, ZERO reports listed.

                          Third: One of the best outputs of in these recent versions is being able to monitor site to site VPNs, stopped working. While working with tech support I found out that there is going to be a HOT FIX to repair something.

                          I am working to get a separate SQL server stood up which will help I think and eventually a physical server to remove it from the sometime sketchy virtual environment.

                          • Re: NPM 12.2 Upgrade Experience Feedback?
                            Spiky

                            so i went with the upgrade just now   i have npm, ncm, ipan and udt

                             

                             

                            and this is the error i got, and now i have a complete  unusable system

                             

                             

                            • Re: NPM 12.2 Upgrade Experience Feedback?
                              rschroeder

                              If I might be so bold as to offer Installer Error Reports suggestions:

                              1. It's unnecessary to indicate "we detected a problem."
                              2. The largest text on the page should be applied to the actual problem.
                              3. The robot overwhelms the page, indicating a problem, but no solution.  In fact, no one here knows how to help a dazed robot, so we're left stunned & confused too.  Although the robot IS pretty cute.
                              4. Lose the "Close the installer" link, and replace it with the instructions necessary to diagnose, troubleshoot, and correct the problem.  A link to installer logs might be useful, if those logs stated the problem, like "A duplicate version of ActiveDiagnostics version 12345 was detected.  Cancel this installation of that same product and restart the process, skipping installing ActiveDiagnostics", or the equivalent.

                               

                              2 of 2 people found this helpful
                              • Re: NPM 12.2 Upgrade Experience Feedback?
                                xr64t

                                Performed the upgrade this afternoon (NPM, UDT, NTA, NCM).  Installer went smoothly and probably around an hour.  NPM 12.1 was the old platform and Win 2K16 server.

                                 

                                Unfortunately, it created havoc in my environment.  My most critical ASA 5520 failover pair became unusable and started rebooting.  I had to unmanage them in Orion to get them stable again (after powering off each as Orion was reporting them with dead fans and temp warnings as well as the reboots). It also caused a number of Cisco APs in my environment to become unresponsive and reported them as rebooting repeatedly.  The telnet/SSH console was so unresponsive that I couldn't manage to login.  Changed them to ICMP only polling and service was restored.

                                 

                                Also have a Citrix SD-WAN appliance with a similar symptom and reporting in Orion as rebooting every 30 minutes now. I checked the appliance and it doesn't appear to be restarting so this may be a SYSUPTIME reporting issue, although I have 4 other SD-WAN appliances on the network that aren't reporting issues...

                                 

                                I have a case open and awaiting feedback.... beware on upgrading your prod environment.

                                 

                                PS: I noticed some else reported the 0C temp reporting on their ASA.  I have a 5525-X failover pair reporting the same.  It is also reporting the fans are all spinning at 0 rpm.  Might need to report that as well.

                                 

                                Cheers,

                                Aaron

                                  • Re: NPM 12.2 Upgrade Experience Feedback?
                                    serena

                                    Can you send us your support ticket #?

                                      • Re: NPM 12.2 Upgrade Experience Feedback?
                                        xr64t

                                        Thanks Serena.  My ticket number is 1300154

                                        • Re: NPM 12.2 Upgrade Experience Feedback?
                                          xr64t

                                          Hi Serena,

                                           

                                          I have just just found that the "default" view for a device that is not identified correctly is now "ASA View".  So all the Access Points I moved to ICMP polling and any not using SNMP is displaying in ASA view which is completely useless for anything other than a ASA firewall.

                                           

                                          I might log another ticket to get the default views restored.

                                           

                                          EDIT:   Found the setting in views and found the "unknown" view had changed to "Node Details ASA Summary" during the upgrade.  Changed this back to "Node Details - Summary" and issue resolved. :-)

                                           

                                          Thanks,
                                          Aaron

                                          1 of 1 people found this helpful
                                            • Re: NPM 12.2 Upgrade Experience Feedback?
                                              JiriPsota

                                              During upgrade we do a background inventory to find out if there are some ASA nodes that supports new ASA pollers.

                                              If ASA pollers are discovered for some nodes, we assign new ASA view to their MachineTypes (ViewsByDeviceType) if they are set to “default”.

                                              It looks like there has to be some node with Unknown MachineType (at least before upgrade) that supports ASA pollers, so we have changed a view to “ASA view” for “Unknown”.

                                               

                                              If you want us to investigate further, please create a ticket and upload diagnostics.

                                               

                                              Thanks,

                                                JP

                                        • Re: NPM 12.2 Upgrade Experience Feedback?
                                          safenetwork

                                          Hello,

                                          We've some serious problem after the upgrade from version 12.1 to 12.2.

                                          The installation part was fine without any error but the license store is now corrupted.

                                          We tryed to follow this thread :

                                          https://support.solarwinds.com/Success_Center/Orion_Platform/Orion_Documentation/Corrupted_license_store

                                          However we have an error when trying to launch migration.exe /ExpireAll command , reporting that The license store is not in valid state

                                          Anyone have this problem?

                                          We've already opened the Case #1295467 but we're still awaiting an answer from the support service .

                                          Thanks in advice

                                          • Re: NPM 12.2 Upgrade Experience Feedback?
                                            ecklerwr1

                                            I'll have to watch this thread...

                                            • Re: NPM 12.2 Upgrade Experience Feedback?
                                              felipepaes

                                              The upgrade was smooth, I liked the new monitoring for ASA and I see a great future for that, but I am also having the same issue as I see many people complaining regarding Health Monitoring at some of my ASA's.

                                              I have opened a ticket to check that and the conclusion was that the IOS version of the devices I am having trouble are older than the ones that are showing the information correctly.

                                              OK, I understand that but before the firewall insight feature, it was possible to verify these sensors at that devices. And I cannot simply go ahead and upgrade many devices that are currently running stable only to correct monitoring system problems.

                                              I hope there is a hotfix coming soon.

                                                • Re: NPM 12.2 Upgrade Experience Feedback?
                                                  rschroeder

                                                  There IS a hot fix available for NCM 12.2; I don't know if it addresses your ASA issues, though.  Check it out and apply it--it sounds like it's helped plenty of people already.

                                                   

                                                  I recently upgraded to NCM 12.2, and applied the hot fix.  The only issues I've seen so far have been my ASA 5525-X models aren't getting the right hardware (CPU/Memory/Fan/Temp) polling anymore, and the default views of classes of nodes don't automatically include latency graphs.  Those are VERY easy to add into NPM's views, and applying it to one ASA's views applies it to all ASAs views.

                                                   

                                                  There's definitely a learning curve to cover the ways I saw & did things with NPM 12.0.1 and 12.2.  But it's been pretty intuitive, and the installers are only getting easier and more comprehensive.

                                                   

                                                  I worked with Solarwinds Technical Support today on a different topic, and learned that a new, more-global upgrade / hot fix installer is being developed and used/tested in-house at SW.  It sounds wonderful, and I bet by this time next year we'll all be able to use it to upgrade and patch multiple servers & pollers & Orion applications with a single click.

                                                   

                                                  • Re: NPM 12.2 Upgrade Experience Feedback?
                                                    rschroeder

                                                    I checked out the Shared Thwack Pollers and found one that provided much more ASA hardware & interface information.  I tested it and found it compatible with my ASA's.  Downloaded it, applied it, and now my firewall admins are significantly more impressed with NPM.

                                                     

                                                    Check it out, see if it is good for your ASA's.

                                                  • Re: NPM 12.2 Upgrade Experience Feedback?
                                                    foonly

                                                    I went from Orion Platform 2017.1.1 SP1, VIM 7.1.0, VNQM 4.4.0, DPAIM 11.0.0, NPM 12.1, QoE 2.3, NTA 4.2.2, NCM 7.6, NetPath 1.1.0, CloudMonitoring 1.0.0, SAM 6.4.0

                                                     

                                                    to .... wait, I can no longer scrape that from the bottom of the web window. Must be a graphic element now. Reverting to Soviet mode copy and paste (eyeballs, fingers, and keystrokes):

                                                     

                                                    to Orion Platform 2017.3, VIM 8.0.0, VNQM 4.4.1, DPAIM 11.0.0, NPM 12.2, QoE 2.4, NTA 4.2.3, NCM 7.7, NetPath 1.1.2, CloudMonitoring 1.0.0, SAM 6.4.0

                                                     

                                                    The new downloads are somewhat confusing. I normally go through the Upgrade Advisor to determine the exact products I need to download, and then download the full packages, which I guess is called the offline package now. I saw the note that said

                                                     

                                                    IMPORTANT! The latest releases - NPM 12.2, NCM 7.7, SRM 6.5, UDT 3.3, IPAM 4.5.2, VNQM 4.4.1 and NTA 4.2.3– utilize a new SolarWinds Orion installer that handles product compatibility and upgrades for you.

                                                     

                                                    I tried the Online package, which is marked as recommended. I cannot recommend it after my experience. Originally, I was just going to upgrade IPAM to 4.5.2. The Online package made it clear that it was going to upgrade all upgradable products, and that I would have to wait for each download. So I canceled, and tried the Offline. When I went to apply hotfixes, I realize that it wanted Orion Platform 2017.3 Hot Fix 1, which I think implies NPM12.2.

                                                     

                                                    So I checked the Upgrade advisor, and it does not list IPAM 4.5.2 - only 4.5.1, because 4.5.2 is the new style.

                                                     

                                                    So I proceeded to download the offline for that NPM12.2, ran into various severe errors during install, and concluded that I needed to uninstall, then reinstall various existing, old modules.

                                                     

                                                    But the download page no longer lists the old modules. There's a link for Archived HotFixes, but even it is not complete.

                                                     

                                                    The HotFixes listed for current versions are sometimes odd. For IPAM 4.5.2, it lists IP Address Manager v4.5.1 Hot Fix 1. Do I really need that?

                                                     

                                                    I finally reinstalled all previous versions (because I'm a packrat, and maintain on-disk copies for just this eventuality), and decided to do the online install. I got various Config Wizard errors for almost every product. I pressed on, and finally got a run of the Config-Wizard that came up clean. I don't feel at all comfortable with the result.

                                                     

                                                    Problems I would like to see you address:

                                                     

                                                    • Provide downloads of older versions of products and their hotfixes
                                                    • Provide Release Notes downloads for all products on the download page instead of just at the documentation page
                                                    • Make sure Release Notes list product prerequisites. IPAM does not - it says "IPAM 4.5.2 is an Orion Platform product, and consumes Orion Platform 2017.3."  It did not say that Orion Platform 2017.3 requires NPM 12.2 - I sorta surmised that. I cannot download Orion Platform 2017.3 separately. Odd use of the verb, "consumes", BTW.
                                                    • Make it clear which versions on Orion/Admin/Details/OrionCoreDetails.aspx, the Orion Platform Details page go with which product and which version. Mark shared components as such. List all this is the Release notes.
                                                    • Make sure the Online packages give an estimate of the amount of data to download and can recover from HTTPS failures without a complete abort (we have an HTTPS cache that messes up sometimes).
                                                    • Make sure the Offline packages check prerequisites properly, and issue helpful messages.
                                                    • Make it clear how to do re-installs when using Online install method.
                                                    • Perhaps consider making Offline install packages for the components, like Orion Platform 2017.3.
                                                    • Explain your install logic better so I can make decisions better. When do shared components get re-installed? What are the ramifications of re-installing each component - e.g. which ones require the Config Wizard to run? Which products can I install back to back without running the Config-Wizard after each?

                                                     

                                                    Thanks!

                                                      • Re: NPM 12.2 Upgrade Experience Feedback?
                                                        tigger2

                                                        "because I'm a packrat, and maintain on-disk copies for just this eventuality"

                                                         

                                                        I do this both at work and home.

                                                        I always feel bad about doing it (wasting both my time and disk space) and then once in a blue moon it really pays off nicely.

                                                        I really wish vendors (everyone who releases code) would always provide a way to get to old releases so I wouldn't have to do this, but I've been bitten just enough to not even trust them if they did

                                                        • Re: NPM 12.2 Upgrade Experience Feedback?
                                                          rschroeder

                                                          Agreed.  It sounds like you've experienced many of the things I did during my upgrade.

                                                           

                                                          More interesting (to me) is the fact that running certain hot fixes followed by the Scaleability Engine updates on the pollers resulted in dual Wizards opening on every APE.  Running each simultaneously guaranteed both to fail.  Running the first one all the way through to completion, even though the other Wizard popped up part way through, was the path to success.  Once the first Wizard was successful, then running the second to the end would work.  It's crazy that two would show up at the same time.

                                                           

                                                          Perhaps simpler to fix, but harder to recognize, was that the Wizards would pop up BEHIND the NPM front end page.  Definitely a loss of time discovering all the Wizards had started up behind the browser window.  I figured I'd messed up somehow, and tried starting them again.  Which failed.

                                                           

                                                          By accident I was moving the browser about the RDP window and discovered the Wizard waiting for my input behind ID.  Hmph!

                                                          1 of 1 people found this helpful
                                                        • Re: NPM 12.2 Upgrade Experience Feedback?
                                                          stevenstadel

                                                          Our Upgrade Experience. We have a semi-large environment with 9 additional polling engines and one additional web server. We went from NPM 12.1, UDT 3.2.4, IPAM 4.3.2, NTA 4.2.2, SRM 6.4.0, NCM 7.6 to the latest versions using the new installer that included the latest hotfixes.

                                                           

                                                          I like to wait until the first batch of hotfixes are released before upgrading, which is the reason for our delay.

                                                           

                                                          Ran this upgrade in conjunction with a replacement of the primary polling engine. We did a 2012 R2 server swap for the primary engine. All the other APEs, Fastbit DB server, and AWS have been upgraded prior to 2012 R2 over the last few months. The migration method we followed kept it simple by using the same hostname and IP.

                                                           

                                                          Total outage time was 8.5 Hours.

                                                           

                                                          First 3 hours

                                                          We upgraded the NTA fastbit server to the latest version. Next removed the licences from the primary server for our modules and shutdown the services on all the APEs and primary polling engine. We exported the primary server's SSL cert from IIS Manager and copied the legacy reports folder as outlined in the migration guide.

                                                           

                                                          The rest of the first few hours went fairly went well with the primary server hostname and IP swap to a new 2012 R2 node, and the initial install. Loved the "check what you want install" method which automatically included the latest hotfixes. There was one warning on the install where NCM wanted 3.0 GHz processors, instead of the 2.7 GHz ones that are presented to the node. We present 20 cores to the primary engine and have never had a CPU issue so we kept moving forward. One thing that popped up was the NTA install wanted to use a local drive for the initial install, instead of the fastbit server. We did not have the option to select a separate fastbit database server.

                                                           

                                                          This first issue was fixed by downloading and running the seperate NTA 4.2.3 install module on the primary engine and selecting the separate server / database option.

                                                           

                                                          We ran the config wizard 3 x on the primary server, which extended the install time. (1st with initial install, 2nd for NTA installation, and 3rd because the NTA installation caused a website runtime error where we couldn't generate the website). This was the first of two calls to support we had. I opened a case online, then called in and was able to get someone right away. Turned out the fix was to run the config wizard a third time.

                                                           

                                                          Once the primary engine's website was presented we started the upgrade of the 9 x additional polling engines. Eight of these installs went great. The last one turned out to be a problem. We used the new Scalability Installer retrieved from our local Orion server/website. Settings - Polling Engines - "Download Installer Now".

                                                           

                                                          Eight of our polling engines are local to the primary engine, and last one is remote in a separate datacenter. The local APE upgrades all executed without incident. We ran the updates all at the same time and they all completed successfully.

                                                           

                                                          The last remote polling engine kept on timing out, and we opened another support call, first by creating the ticket online then directly reaching out and calling support. Support hold time was about 25 mins before we were able to start working on the issue. We spent the next 4 hours working with support an trying to get the files copied over, circumventing the copy process from the installer. We used a new technique as the one outlined on thwack and in the current KB didn't resolve the issue. Failed to download or run the Scalability Engine installer from the main server - SolarWinds Worldwide, LLC. Help and Su…

                                                           

                                                          Our suspicion was that the KB only dealt with the largest Core MSI, the eventual solution was to follow the KB except that we copied the subinstallers folder out of %temp%\SWOrionSetup, whenever the timeout occurred. Coping the files before exiting the installer allowed us a head-start on the next time we tried the install. We then copied the subinstallers folder back to %temp%\SWOrionSetup and updated the time stamp folder name, then ran the installer again, repeating as necessary until all the installation files were copied.

                                                           

                                                          Working with Brian from support was a great experience. Kudos to him

                                                           

                                                          The last issue that we had was a minor one with the additional web server installation. The initial installation hung on the NCM Integration Module uninstall. A restart of the installer solved that issue.

                                                           

                                                          All-in-all we strayed a half hour out of my planned 8 hour outage window, and I am pleased with the responsiveness of the Website while exploring the new features. I submitted an enhancement request to increase the timeout or allow an offline upgrade for APE. Scalability Engines Installer - Enhancement to allow increase timeout for remote APEs

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

                                                              Thank you for this in depth feedback. We are working on improving the timeout architecture for the remote APEs, so I've flipped that feature request to what we're working on. I hope to hear your feedback the next time you're upgrading to see how we've done to improve that scenario for you.

                                                                • Re: NPM 12.2 Upgrade Experience Feedback?
                                                                  lynchnigel

                                                                  Our upgrade from previous versions went extremely well, the web based online and all in one experience started with a check of the environment. We have an additional poller and a VM with NTA which it detected and told me about the fastbit upgrade which I needed to do after along with the additional poller.

                                                                  It did the complete upgrade and then run through the configuration wizard. We have

                                                                  So took all in all about 30-40 minutes (as I wasn't really checking)

                                                                  Sucked the main poller install down to the additional poller went fine then the config wiz runs.

                                                                  Upgraded NTA server which went fine

                                                                   

                                                                  We has warnings about our server:

                                                                  CPU requirements

                                                                  DISCOVERED: 15/11/2017 21:33:36

                                                                  DESCRIPTION: Your environment does not meet the minimum CPU requirements for the following products: Web Performance Monitor 2.2.1. Performance may be slower than expected.

                                                                  RESOLUTION: For better performance ensure that you have more than 4 CPU cores that are faster than 3000MHz.

                                                                   

                                                                  but have installed it all - we had issues with a service stopping and stopping after the upgrade but tech support helped which was this, and doing this helped alot!
                                                                  https://support.solarwinds.com/Success_Center/Server_Application_Monitor_(SAM)/Tweaking_performance_of_Windows_Server


                                                                  2 of 2 people found this helpful
                                                                    • Re: NPM 12.2 Upgrade Experience Feedback?
                                                                      ecklerwr1

                                                                      Wow this is interesting extra information.  I'm wondering now how these settings might help some of my other busy servers that do a lot of network activity!

                                                                        • Re: NPM 12.2 Upgrade Experience Feedback?
                                                                          rschroeder

                                                                          After going through the same upgrade, I found several items that improve performance by adjusting them:

                                                                          • Ensure failing NetPath monitors are removed.
                                                                          • Reduce logging to NPM and offload it to a SIEM.  I can easily send seven or eight million syslog messages per second (yes, PER SECOND!) to NPM, and NPM's SLX onboard syslog environment only scales up to two million per second.  Overloading NPM with syslog messages results in some pretty quirky behavior; save yourself the trouble and send big syslog outputs elsewhere.  Our Security Admins want our 80+ ASA's syslogging in Debug Mode, and our WLC's do the same.  Both of those kinds of appliances generate far more syslog information than NPM's syslog can handle.
                                                                          • Ensure hot fixes and patches are applied.  I wish SW had a one-touch button that automatically went out and discovered my products and then discovered their patches & hot fixes, and showed me what to install, and that even offered a way to automate the process with a single click if I wanted.  Applying the right updates & patches & fixes, in the correct order, and rebooting and distributing the updates to all APE's in the right order, too--well, that would be heaven.
                                                                          • Over the last fourteen years I'd retired a couple of main NPM instances and converted them to APE's.  But the upgrades / installs over that time didn't reveal that NTA still thought those to main instances should be primary NTA servers.  Only yesterday did I discover that, and learned the process to remove them.  That improved performance, too.
                                                                          • Cleaning up nodes that send syslog is also very useful.  We'd had an environment that operated off of resilience and duplication, so switches & routers & firewalls were reporting syslogs to two different APE's, AND to two different SIEM's.  Reducing that duplication at the nodes has improved NPM's performance.

                                                                           

                                                                          The list of tweaks goes on and on, but every little modification shows a corresponding improvement in NPM's performance.  But I'd be lying if I said I wouldn't want a few Solarwinds second-level engineers to come and go through my environment with a fine-toothed comb and make recommendations/suggestions, or actually do tweaks and clean-ups for me.

                                                                    • Re: NPM 12.2 Upgrade Experience Feedback?
                                                                      stevenstadel

                                                                      Few further issues that I'd like to share since our upgrade.

                                                                       

                                                                      To recap our upgrade included replacing the primary server with a new 2012 R2 node and a clean install. Turns out the installation included some hotfixes but not all. SAM 6.4 HF 2 was not installed and consequently we were unable to gather windows mount volume metrics, to our surprise after the install. The hotfix was installed on the APEs as they were upgraded and not replaced with a new node. Seeing the HF installed on the APEs and not the primary added to the confusion.

                                                                       

                                                                      SAM 6.4 Hotfix 2 resolved the Windows Mount issue. A few days after that installation we realized we had issues with RabbitMQ not responding and the backup MSMQ overloading and filling up the HDD. This leak also caused intermittent SAM monitors stopping with ephemeral ports being exhausted.

                                                                      Ephemeral Port Exhaustion - SolarWinds Worldwide, LLC. Help and Support

                                                                       

                                                                      A complete uninstall and reinstall of RabbitMQ, along with running the configuration wizard on the primary engine with all the APEs shutdown resolved our issues. It was important for all the APEs to be shutdown.

                                                                       

                                                                      We have been running stable now for a week.

                                                                       

                                                                      One note I'd like to pass along is I would love to see better release notes that specifically call out which hotfixes are included in the Core roll-up Hotfix bundle.