bobmarley ✭✭✭✭✭

You need to authenticate first. Try using this command to authenticate before using other commands. Add-PSSnapin SwisSnapin $swis = Connect-Swis -host YOURORIONSERVERNAME -Trusted

There is a 'Lastboot' option available, unfortunately I don't think you are going to be able to easily tie that together with a down event because in order to change/trigger 'Lastboot' Orion needs to be able to read that value from the node using SNMP/WMI. If the node is down then it will not be responding to either. I…

I'm eagerly awaiting 12.4 to be released. I'm going to start from scratch with a brand new install on 2016 and the SQL DB's for Orion and Netflow. The platform I'm currently running on I inherited a couple years ago and they had over 30 people with admin access that didn't have a lot of experience with Orion. So when…

Since I need to go to 2016 and build out another SQL instance for Netflow anyways I think I'm just going to build up my next install from scratch -vs- trying to upgrade. Seems a lot less risky that way.

Your time = My time = You are sooooo ahead of me

Give the feature in NPM 'Netpath' a try.

I have done something similar in the past. I see your alert is a standard .bat file. Probably running on a schedule every few minutes? What I did was have the batch also send a syslog to Orion each time it ran. Then I made a SQL query in SAM that looked for that syslog message in the past X minutes based on how often your…

Try this

I have had this before trying to run scripts from SAM against a remote computer and it was a rights issue. The machine running SAM had insufficient rights to execute the script on the remote computer. The way I solved it was to add the Sam Computer 'MySamComputer@companyxyz' as a local admin on the remote machine. Do this…

I'm going to buy into it, its a pretty good product and they seem to be headed the right direction as the industry goes.

It probably discovered them because the address was included in the SNMP setup of the devices 'location' field.

I get tons of these, wish I could suppress them but they are normal then way I have my flows set up.

The main Solarwinds site http://solarwinds/ explains it. Basically they sell them in quantities that name ends in a number, then the ones that end in X or LX are unlimited licenses.

I worked with a great guy from support today - Alvhin Moldogo and figured it out! What actually was the problem was when I set the transactions up I didn't notice that I was using my personal AD account -vs- a system account. My password had changed and then the transactions failed

I would go with SJA's advice and purchase a Kiwi license if you don't already have one. Have Kiwi log the messages off to a file, database, whatever, and then make rules to only send the ones you want to alert on over to Orion. Kiwi has a large capacity because all it does is logging, whereas Orion is doing lots of other…

I upgraded to 12.0.1 as soon as it came out and everything is working fine.

Take a look here and vote. https://thwack.solarwinds.com/ideas/1145#start=125

You would also need to join up the node names and do a 'where' to filter on specific nodes if you want to use a SQL alert. 

You could always edit the SQL on the Nodes Summary page. There are some examples there. I use Status<>1 so only nodes that are down are shown, otherwise I get a bunch of nodes that are up but have interfaces down. Go here first Then here

I don't have any in Unknown status right now to verify - but give this a try. Go Manage Nodes select Interfaces then group by Status.

This happened to me the other day as well. One of the other administrators in Solarwinds was doing her monthly password changes for the SAM transactions she runs and after she changed the password in SAM the account kept locking up. Turns out the same account was also being used in our lab Solarwinds and it had not been…

You need to have an actual query here Select something from something

Awesome post Leon Adato Thank you! I've been trying to figure out how to add a button to that page so our NOC can click on it to approve the message and then send the command on along to our ticketing system to create a ticket. Thanks also to wluther and Zack Mutchler I've used some of your code from other posts here on my…

It is picked up by SNMP from the end device so if someone enters it into the router/switch/server when they configure it - it will show up when it gets polled.

I think it uses the words LIKE and NOT LIKE instead of = or <> but here are the docs. Use SolarWinds Query Language (SWQL - SWIS) - SolarWinds Worldwide, LLC. Help and Support

I have always put a filtering server in place before the messages got to the LEM or to Orion. One solution would be to have the messages forwarded first to a Kiwi Syslog Server and then have filtering rules in the Kiwi server drop the unneeded messages prior to sending them on to the LEM or Orion. Kiwi is very affordable…

Cal, could you expand on this statement? "For SCPs working for SolarWinds customers under active maintenance, you will be recognized as an SCP member within the support system and provided with an enhanced support experience" Any details you can share?

You could demo a copy of NTA

One solution you could use is have the script send Syslog messages to Orion then they will be in the Syslog table. You can then create your alerting against that.

Kiwi Syslog server is a good start.