monitoringlife · Monitoring Engineer · ✭✭✭✭✭

It could, there are a lot of possible causes. The virtual interface is its own entity separate from the physicals that make it up. Try clearing the interface counters then observing (and compare the ACL drops). If its not that let us know, or give TAC a ping to see what the cause is.

@"donrobert5" provided great intel. there is a cost for each AWS, I don't believe its published and you will have to ask sales. Directing traffic is something you will have to do with a load balancer / proxy / VIP. Its not natively supported. 

Do you have an ACL/Firewall placed on the interface? ACL drops count as 'discards' as far as SNMP sees them. 

I think there is an out of the box alert you can copy for this but here is an example: You can take a look at what is possible and the out of the box alerts on the demo (https://hco.demo.solarwinds.com/Orion/Alerts/Default.aspx). Cisco should work fine as long as your network engineers are populating the 'bandwidth'…

Extra polling engines need customer service to add a license (per poller) for each APE (dont forget to ask for HA license if you use it) Without internet access you will need to do a manual activation. You only need to whitelist the license URL to avoid this process From the whitelist KB: licenseserver.solarwinds.com…

Create a user (on the DB you need to query) with same SID as the local user from the Orion DB. 

I would take a look at the demo and see if it fills your use case

Highly recommend WPM if you have a license for it. Synthetic/real user monitoring is a must (in my opinion). 

Might be used for binding to AD when adding groups.

Have you tried updating or adding entries in IP address group management (/apps/nta-ipgroups/management), and/or your Applications (/Orion/TrafficAnalysis/Admin/ManageApps.aspx)? Wondering what version your on (and which version you started with)? My older install does not have these present. 

Did you have a certificate assigned to your MPE and AWS (additional web servers)? web-servers need/required to have a certificate assigned in 2023.x and you have to manually run the Configuration Wizard on the MPE/AWS to set this the first time. 

I have a bunch of hardware health stuff, every vendor is unique (side eye to UCS being the hardest to get into SW). The older HP's need the agent WBEM software (WBEM Providers) installed to mine the metrics from Windows nodes. HP Insight I believe is their central management/monitoring software, don't need that for SW to…

If you already have the script written (and have SAM license) its fairly short path to adding a script monitor and alerting on the script output. If your node does not support SSH so the node can natively support the SAM component you could put it on another node or polling engine. 

Sorry not clear on what your asking. Assuming you mean the credential you monitor your nodes with? Changing the password is fairly easy you can update the credential via Credential Manager ('/Orion/Admin/Credentials/CredentialManager.aspx').

Do you have 443 and/or 8124 open between SolarWinds and DPA? 

this thread the same error your getting? SQL queries does not work after upgrading to 2023.1

Every shop has their own unique security and compliance needs. As long as your leadership are happy and your upgrades are working, whatever gets the job done is fine in my book. Using a local admin does rule out any account GPO issues. 

Agreed. Making the SOP to 'use a local admin' is to reduce support ticket load. Most of my clients don't allow the practice, and I would not be able to login without and auditable account unique to me. 

You make any progress the report issue?

No stress, we got to look out for each-other. 

you have to do it on the poller, not just the MPE if you have additional polling engines (I had to do this on 30+ APEs). If it was working before the upgrade and that didn't fix it, open a case with support. 

Adding one I forgot, if your powershell monitors are failing after upgrading try this fix: PowerShell monitors post 2023.1.

PowerShell monitors post 2023.1 might need this setting: https://support.solarwinds.com/SuccessCenter/s/article/SAM-Powershell-not-working-after-2022-3-Upgrade?language=en_US

Gave it 20 minutes and looks like it does populate properly, so I think were good to go. Thanks for bringing this up. Going to go add this to the interfaces details pages. Would like to see SW treat it like a defect and add it as a default.

Are you on a summary page or a detail page? Edit the page (top left corner) Add the resource

I spot checked mine. Looks like they are not present on the interface details page, but can be added

Thanks for posting and not doing the normal xkcd reference.

I am also in the 20+ poller gang, so I feel you on maintenance that has to be done on a per poller basis. I recognize some of these as clearing the subscriptions, not sure on the others. But that only has to be done once (save restarting services on all the APE's, and I'v had mixed feedback from support if restarting…

I dont think their internal tooling are public. But I would just grep on 'ERROR' (case sensitive) and it will get you fairly close. Active diagnostics is also a good place to spot check for issues. I would also look into orion insights if you have not tried it before.

Assuming you mean to access the website, you can use LDAP logins or SAML. If this is for monitoring accounts, you should be able to add non domain accounts for Windows/Linux/SNMP without issue.