superfly · Senior Network Engineer · ✭✭✭✭✭

Try this ${SQL:Select '${your variable}'/1000000} e,g, ${SQL:Select '${N=Alerting;M=Downtime}'/1440} - shows how many days node was down.

I don't know but you could try turning off the Interface Errors Statistics option. 

It doesn't look like this is possible. I think it would make a good new feature request.

I assume these are lightweight AP's? This may help https://thwack.solarwinds.com/t5/NPM-Discussions/ALL-Wi-Fi-Access-Points-Inventory-Report-SQL-HELP-Please/td-p/355780 https://thwack.solarwinds.com/t5/NPM-Discussions/WLC-Thin-Light-Weight-Access-Point-Serial-Number-Display-Report/td-p/406573

I hadn't noticed this but I have the same issue. Will need to research it more.

The build in syslog widget doesn't seem to work anymore so to see syslogs associated with a node, I added a SWQL query widget to the view with the following code SELECT TOP 100 -- Edit this number for how many messages you want to load to widget (you can modify the widget for how many messages to page) let.Name AS [Message…

This should help. https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Automatically-Add-Discovered-Nodes.htm

Does your install match the requirements of Solarwinds? https://documentation.solarwinds.com/en/Success_Center/orionplatform/Content/Core-Orion-Requirements-sw1916.htm

There are a couple of options. You can either pick the Percent Utilization of All Interfaces or Top XX Interface by Percent Utilization. I would pick the Top XX Interface by Percent Utililzation. Then you just need to click on Edit button and Filter for InPercentUtil and OutPercentUtil and set to what you're looking for.

I'm not sure what your issue is but I have this for the URL "client_url": "${N=SwisEntity;M=DetailsUrl}"

You will need to make sure that the Solarwinds server has access to the FW via SNMP. What sort of firewall is it?

Feature requests go here https://thwack.solarwinds.com/t5/NPM-Feature-Requests/idb-p/npm-feature-requests That way people can vote it up

I only keep syslogs for 7 days. As mentioned Solarwinds is not designed for huge syslog stashing. You'll need to use another product for that function.

Originally I used option 3 but then when Orion came up with the Thin AP alert out of the box, I started using it. I did modify the trigger status to be not equal to up. Worked beaut for disconnects but if an AP was disconnected for a long time, I would not receive a reconnect email.

Yes I've always used the thin AP alert successfully. I did change the trigger status to be 'not equal to Up'.

Please add your feature request here https://thwack.solarwinds.com/t5/NPM-Feature-Requests/idb-p/npm-feature-requests

Feature requests for NPM need to be added here https://thwack.solarwinds.com/t5/NPM-Feature-Requests/idb-p/npm-feature-requests But I have Firepowers and these are seen as Machine Type Firepower 2110. I'm on 2019.4

I assume you've added the srx345 into NPM. Is there a firewall in between the srx345 and Solarwinds? Or have you allowed this traffic on the srx345?

Stack switches are added into Solarwinds as a single device. Solarwinds should detect that it's a stack switch and add in the extra left hand view as seen in this image. This article gives you all the info. https://documentation.solarwinds.com/en/Success_Center/NPM/Content/NPM-Monitor-Cisco-Switch-Stacks.htm

Switch to SNMP and you should get the stats you're looking for.

This might be obvious but do the devices that failed support the running all command?

This may help? https://support.solarwinds.com/SuccessCenter/s/scp-npm-exam-guide

Your screen shots aren't displaying. Can you please fix so I can have a look at the issue?

Try removing "version 2c" from your snmp-server host command. It looks like snmp-server view is snmpV3 only.

You could try and use these variables instead ${N=SwisEntity;M=IP_Address} ${N=SwisEntity;M=NodeID}

Using syslog is really easy. For the BGP ones I just look for BGP-5-ADJCHANGE in Message Type Pattern. And for OSPF, I just use OSPF-5-ADJCHG*, OSPF-4-NEIGH_ERR* in the Message Type Pattern. If you have any hassles, just post back.

This is great except that it won't detect flapping links as the detection is too slow. Here's my original post on this from 2013 BGP Neighbour alerts.

In my experience I've noticed that when using the alerting tool for BGP status, it is too slow to alert. So you don't end up seeing any flapping as they are up/down too quick for the alert to notice. I do my BGP alerting through syslog. So I'm instantly notified of any BGP changes.

count me in

Awesome! That works beautifully. Thanks for sharing!