kweise · Director, Solutions Engineering · ✭✭✭✭✭

Geoo, In report writer, create a new report. When the New Report window opens, scroll down. You should see a report type called "Advanced SQL." Select that report type. When the design window opens, click the SQL tab. You can enter the SQL statements into that tab. Hope this helps!

Thanks Allison! It's not the most comfortable long distance bike out there, but it's a lot of fun! I just did a ride around all 5 Great Lakes at the beginning of this month. For some reason though, my wife opted out of that one. :)

If you go to the Report Grouping tab for your report in Report Writer, you should be able to add your custom property as a Report Group. Click the drop down list labeled "Add New Group," select the custom property you want your report grouped by, and then click the Add Report Group button. Your custom property should be…

I guess the tough issue is that each implementation can be a little different - and hence what has been my experience for v10 may not be yours... I like your disclaimer Dave! I'm interested in everyone's upgrade tales as well. I haven't made the move from 9.5 to 10 yet, but I'm planning to in the next few weeks. I'm…

How about a hint when 9.1 SP2 will be out? Sorry Denny, but I couldn't resist trying to be the first one to ask! Keep up the good work.

mdcrabtree If you edit the web display properties of the UnDP transform for the battery runtime, you can select to display a chart view on a view (node details in this example.) That should get you the runtime in minutes displayed as text in a chart. Hope this helps!

You can read about it in the Orion Blog section here:

Thanks ET. I've changed my maintenance settings to process all expired IPs and set the maximum minutes to process IPs to 5 minutes. I'll see how that runs overnight and make any adjustments necessary. Thanks again for your help!

Thanks Michael. I've passed that on to our DBAs. That will probably be welcomed news to them, since our Orion database is on a shared SQL server with about 16 or so other databases. Thanks again for your help!

In report writer, create a new report and select Advanced SQL as the type of report you want to create. You can paste the SQL code into that report and modify the query for your environment.

I agree with Jeff. I would think an interface that is admin shutdown would show as shutdown and not unplugged. I'd like to know what is unplugged versus what has been admin shutdown.

Byron, You're right, but I don't think he's talking about an alert. He's just talking about how long it takes for the Node's icon to change from green to red and be classified as down on the Orion web site.

That sounds vaugely familiar but I can't find that setting anymore. However, there is a setting under Orion Polling Settings for Node Warning Level. It sets the number of seconds before Orion marks devices as down. I'm guessing the default is 120 seconds. It's at the bottom of the page under Calculations & Thresholds.

We're on 8.5.1 SP3. You'll only see names if a user (who has rights to) acknowledges the alert either in the web console or in the Advanced Alert manager on your Orion server. If no one has acknowledged the alert, there won't be a user name or time in those columns. To acknowledge the alert in the web console, the user…

Add me too. The issue with duplicate nodes being added to inventory is the primary reason I don't use sonar discovery. Adding some sort of check to prevent duplicate nodes should be doable. By default, the IPAM module won't allow you to add duplicate subnets. 

I know you can get 1 minute intervals looking at the charts in system manager, but I've always wondered why the web interface only goes down to 5 minute intervals.

Maybe you are running into a different issue than I have. I get the same message you mentioned, but I did forget to mention that I'm using the additional web server to access Orion. If I browse to the web console on my primary Orion server, the report works. I only get the error trying to access the historical NetFlow…

Thanks Andy!

Yeah, I was afraid you weren't able to reach those interfaces when I was typing my reply. Short of getting funding for a snmp-enabled switch out there, I think your best bet is adding the up and down speeds. It's not perfect but I think it's as accurate as you'll get with what you have in place. 

You're welcome. I'm glad you got it working!

Did support give you any idea if the fix will be included in a service pack or if it would be released as a hotfix? I've got the same problem with some of my reports and I also get a SQL error when I try to access volume info. 

I'm not sure you can export from multiple sources. For the NTA, your export source IP address needs to match the IP address Orion is using to monitor the node. Why do you need to export from both interfaces?

I would like to see a lab version as well. Currently, our 'lab' environment consists of a VM server that runs on my desktop machine. If I want to eval a new module, I install an eval version of Orion and then an eval version of the module. I then add and configure nodes, etc to get the install populated with enough devices…

Yes, the additional poller is another NPM server. Unless it's changed, your NTA module will only install on your primary (first) Orion server. You can't install it on an additional polling engine. You will have to patch both servers when you upgrade Orion. I would think you could install the additional poller on server…

See my suggested answer a few posts back. I think the problem is in the WHERE clause. When you add a filter for availability < 100 in the report wizard, it isn't average availability < 100. The WHERE clause gets evaluated before the average availability is calculated. You'll have to use a HAVING…

Sympaval, What version are you running now? I'm not sure if you can upgrade an eval version or not. I don't think I've ever tried it. If you are running version 9.5 and just need SP4, you might be able to call Solarwinds sales. I think they could have a sales engineer work with you to get just the service pack. If you…

Brandon, I still occasionally run into this problem. At some point (maybe going to 9.1) the job engine file file changed from JobEngine.sdf to JobEngine35.sdf. I've attached the blank version of the JobEngine35 file to this post. I'm not on 9.5 yet, so I can't say if it works or not, but I believe it is a more up to date…

If it were me, I'd set the alert to trigger once the bandwidth exceeded the CIR of 64Kbps instead of using a percentage. That's assuming you want to be alerted when you exceed your CIR.

Thanks for the update, Brandon!

Dan, This is a complete shot in the dark, but could the way you have the flow exports set up be causing the duplicate information? It looks like you've got both ip route-cache flow and ip flow ingress/egress set up on your interfaces. Ip route-cache flow and ip flow ingress do the same thing, but I'm wondering if having…