NPM 2024.X Upgrade feedback

Currently in progress of installing Update 2024.1 on a single poller with npm/nta.

Update #1 - Install took a bit longer then expected, didn't have any error during the pre-flight check list. once that was completed, had the installer stall with a error against some 3rd party FTP services running in the background, once they where closed, retry on the installer again. no issues and console came up again. initial checking shows everything is operational.

Find more posts tagged with

Install

feedback

npm

2024.1

Accepted answers

All comments

sswords

As you stated, install went well. All apears to be functional as before. However, the stated CloudGenix API monitoring is not complete. I do not see any real details, VPN Links, WAN Links, etc. Just an inventory of devices in our tenant. Aside from that it all appears to function as it did before the upgrade.

bmrad

Did you configure your Prisma (Cloudgenix) following these instructions?
https://documentation.solarwinds.com/en/success_center/npm/content/npm-prisma-sdwan.htm

You should see something like this:
https://hco.demo.solarwinds.com/Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:590

sswords

I have. I'm in the scenario where I have been monitoring our Edge Devices via SNMP for a few years now. I upgraded to 2024.1 (NPM not HCO, but either way). I added the Orchestrator and it found my edge devices and associated them, however, even after adding the appropriate widget(s), the VPN Link/WAN Uplink information never shows. I have also begrudgingly deleted my edge devices and orchestrator from the deployment, re-added the Orchestrator, and discovered the edge devices via the orchestrator to no avail. Im wondering if there is a Prisma side requirement that I'm missing here. Such as a minimum software version. The required OID according to the docs is there for my Ion 2k's, 3k's, and 9K's, so I'm not too sure what the issue is. I'm going to spend a little time in the logs this morning and see if I can get some direction.

Thanks for the reply! I appreciate it!

-Update:I've got some log entries in the Sdwan.Collectors.Jobs log claiming that the tunnel polling is skipped due to the fact that there are no uplinks on the edge nodes. Could be related. I'm looking into the advanced config link in the documentation for possible fixes.

2024-02-13 09:12:14,776 [STP SmartThreadPool Thread #15] WARN SolarWinds.Orion.Pollers.Framework.PollerBase - No Prisma uplinks was found for Node ID 1706 because there is no data from API request, tunnels polling is skipped.

sswords

From your support team:

"Good day, and thank you for your patience as we check this internally.

As I consulted this with our Application Engineers, this is still a known limitation for the feature at the moment and is still in the works in improving it.

For now, API-only Edges do not support linking of interfaces to WAN Uplinks as polling of Prisma API-only Edge interfaces is not implemented.

As for SNMP+API Edges, we only do linking for "Port" WAN Uplinks with "Ethernet" interfaces:

Rest assured that we will let everyone know when this feature is fixed and improved."

Apparently it sounds like if you use subinterfaces, or bypass pairs don't bother attempting to monitor this through SolarWinds unless a simple list of devices and up/down status is all you're looking for. I have what I need in the Prisma SASE portal and will just stick with that. I was just hoping to get my monitoring done through SolarWinds.

Just thought I'd let you know what other parts of your company are telling the customer are "known limitations". I don't think I have the patience to wait for this to be resolved/supported/implemented/fixed/improved at this point. Perhaps a documentation update (more details on what is not supported) would avoid issues like this moving forward.

Thanks for your time.

Steve Swords