Deltona ✭✭✭✭✭

If you are being looped back to the same node details page then the root cause is likely to be virtual machine related. Have a look at the Virtual Machine Details widget in your Node Details view. The guest status is probably Warning or Critical.

You could build a report that disaplays all discovered interfaces on nodes monitored and not yet imported. However that would require scanning the network first. Another approach would be to use the UDT module to inventory all your existing nodes, and get Interface (port) details such as description, type, mac, vlan etc.…

It usually takes some time to populate the initial data. If, however, you don't see anything updated after an hour then I suggest you try changing the account to full priv and try again, before proceeding with additional troubleshooting. We are using Pilot and CoPilot instances, both working fine. No additional polling…

You should be able to ignore this and proceed with running configuration wizard. Just for the sake of documentation, what version and type of SQL are you connecting to? You can check this by executing SELECT @@VERSION 

Hi there, Create a user in ECIQ with monitoring/read only access, then: add: api.extremecloudiq.com as a Node with Polling Method set to Orchestrators API: ExtremeCloud IQ Devices. Test your monitoring/read only access credential then add the Node. Status (api.extremecloudiq.com) and Statistics (AP's, SSID's, Channels,…

It could be many things. First thing to check, though, is if you have an AppInsight for SQL application monitor assigned to that servere. If so, then edit the Application Monitor and check whether preferred polling method is set to agent or agentless. Also, unless you are authenticating with SQL (through the agent) using a…

Please share what you found out.

Check if you are receiving anything on port 514 and what process ID is using it. In CMD with elevated privs: netstat -anob 3 | find "514" The process ID will tell you what, if any/many are using 514. You only want one listener for syslogs.

SELECT --NodeID as id, DisplayName as NodeName, Status as NodeStatus, VendorIcon as NodeVendor, DetailsUrl as NodeUrl, CASE Status WHEN 1 THEN '<b><p style="color:green">Nice one!</p></b>' ELSE ToString(Status) END as [Status] FROM Orion.Nodes

Thanks for sharing. FYI: The SAML.log log file is located in :\ProgramData\SolarWinds\Logs\Orion\ 

Thanks for sharing.

Please share the fields being used in your Datasource as well as Table columns and time settings (sample interval).

Limit the report to interface where Interfaces > Interface Type Name is equal to ieee8023adLag Or, where Port-Interface Mapping on Nodes > Port Mode is equal to Trunk

Nice work. It would be awesome to display this by IP Address Groups.

Are you by any chance receiving flow from Cisco ISR/ASR, AND are you seing Unreconized applications in your charts? https://support.solarwinds.com/SuccessCenter/s/article/NTA-application-traffic-shows-as-unrecognised I'd also check folder and filess access using the permission tool described here:…

SolarWinds NCM Connector for Cisco SmartAdvisor needs access to https://wsgx.cisco.com/ At the time of writing this, the URL returns the following error: Http/1.1 Service Unavailable

Edit the Node and do an Advanced Test to enable use of connection analyzer. You might resolve the issue by tweaking some settings that work for this 6.49 release

Did you try creating your own, using the Interactive Wizard? Settings > All Settings > Manage Device Templates > Add New > Using Interactive Wizard

Yes, assuming you are using Cisco gear. You will have to create a Universal Device Poller (UnDP) to poll the SNMP OID belonging to these counters and assign it to your Nodes. https://solarwindscore.my.site.com/SuccessCenter/s/article/Create-a-Universal-Device-Poller-UnDP?language=en_US Counters:…

It is mandatory to have an account to access the web console. The same account can be used to interact using API. Do note, that if you are accessing a SolarWinds Platform installation version 2023.1 or newer, then you will have to use :17774 in the URI instead of :17778

Thanks for that. I came to the same conclusion, that by installing the monitoring service on the SQL server that you wish to monitor would negate the need to open up a whole range of ports. However, the monitoring service needs to connect to the same SQL server instance and DB that the Sentry server is using to store…

Hi and thanks for the answer. However, unless APE's can be used with SQL Sentry, then this isn't going to work for us.

I have been waiting 3 days for our agents to update. They are currently in "Update in progress" state. Until they are done updating, we can't interact with the agent nodes.

It sounds like you're experiencing the results of a known NCM inventory issue in later releases. I would suggest you open a ticket and request assistance in repairing the inventory tables.

The issue where application monitors throw license constraint issues if polled from a free polling engine, has been resolved in 2023.2.1.

You will need a SWO (SolarWinds Observability) licens in order to get access to your own SWO instance, from where you can start monitoring the things that you mention. Having a SWO license provides you the ability to do advanced cloud native monitoring but also allows you to tie it in to your HCO on-prem installation, to…

I am using those today on almost every object type. Still need to build a few variants for the likes of applications, transactions etc. The OOTB All Alerts this object can trigger resource needs improvement and it needs to be object agnostic so that it can work with all object types such as interfaces, applications etc.

A widget that displays the root cause of the object in distress (threshold+alerts) A widget that shows which alerts apply to the currently viewed object. Finally, a widget that lists the historically triggered alerts as a count for the past 12 months.

It depends. What type of IP Conflict was discovered? https://documentation.solarwinds.com/en/success_center/ipam/content/ipam-ip-address-conflicts.htm

SAM Node licenses is based on the number of nodes that you want to perform SAM oriented monitoring on. This includes asset inventory, application monitoring, server interfaces etc. Therefore, you need to find out how many of your servers you wish to monitor these types of things on. That number needs to be covered by the…