mjheaberlin

I was trying to do this today using ${ } and found out it doesn't work. It would also be beneficial to use this functionality with Baselines as well.

Would love to see this feature for Cisco routers and switches as well, not just ASAs.

2921 and 2901 currently.

Hi, so we did get this working. I know one issue was the @ symbol in the client ID, you need to change that to %40. I believe there may have also been issues with SW servers not trusting certs from the URLs (sorry I don't admin our SW, I'm on the Prisma SD-WAN side). 

Now that we are using Strata Cloud Manager (SCM), we've attempted this again and the SolarWinds software presents an error. "Login to Prisma Orchestrator failed: An error occurred while sending the request." We have confirmed our client ID, client secret, and TSG ID are correct to retrieve an auth token and can…

I'm interested in this as well. I created a service account and when trying to add orchestrator in SolarWinds, the test fails. @"emanc93" , based on the api.sase.paloaltonetworks.com URL, I'm assuming we need our SD-WAN devices migrated from the original CloudGenix portal over to Palo's portal. We're currently pending our…

My team member who is responsible for our SolarWinds deployment opened a ticket and we found in our case it was because our inventory job was disabled. I think this was from an issue where the job had an end date which caused it to disable itself.

Has anyone found a solution for this? I don't use the wizard to select ports, but essentially have just found the same issue. A config change template that I know was working previously that operated on interfaces based on the interface description ("InterfaceAlias") has stopped working. It seems it's not looking at the…

You should be able to do this with Config Change Templates. I do this with Cisco switches, but I look for an interface description to determine if I take action or not. There is an example CCT with the "interface" tag that you can look at as an example. I didn't use this one specifically, I made my own where I hardcoded…

Just an example, to verify object-groups are created with node specific hosts. Second and third octets would change per node: host 10.10.10.5 host 10.20.20.5 host 10.30.30.5 I have a custom property I can reference in scripts, host ${baseIP}.5, but that doesn't work in Baselines. This could also apply to interfaces.

I'm hoping to see some consistency across the different NCM features. For example, I can use custom property variables in Script Management, but not in Baseline Management. Also, I can "group by" just about anything and "select all" in Config Management, but again, not in Baseline Management. The later makes using…