cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Level 8

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

Thanks Serena.  My ticket number is 1300154

0 Kudos
Level 8

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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

Highlighted
Level 12

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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

0 Kudos
Highlighted
Level 7

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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_s...

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

Highlighted
Level 20

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

I'll have to watch this thread...

Highlighted
Level 7

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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.

Highlighted

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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.

pastedImage_0.png

Highlighted

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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.

Highlighted
Level 12

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

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!

Highlighted
Level 13

Re: NPM 12.2 Upgrade Experience Feedback?

Jump to solution

"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

0 Kudos