cbomholt

I am giving SW the opportunity to make the change, there just needs to be expectations set to when the fix will be in place. Currently, we're holding on deploying vSphere (which was on the road map for this month), because we won't be able to monitor with Solarwinds. To push out plans usually requires a date to be pushed…

To echo the sentiments of many, the lack of a definitive release date for this functionality is disconcerting at best. At this point, it would be beneficial to have an official statement such as: it will be out in version 9.x SP? which is targeted for release in Month, Year. From my end, it doesn't matter as much if that…

 Definitely is an SP2 problem, it goes away when I go down to SP1. The problem is, about 40% of our app monitors go to status unknown on SP1 :( I'll probably just go back to sp2 and if necessary, manually recreate the templates in question. Please submit this to dev to fix at the next service pack. C

So this worked quite well- Have a question about reporting on the data though... I can run avg/min/max out of report writer (apm historical statistic report), but I would like to see 95th percentile on the statistics... Any ideas?

 No dice... Tried running configuration wizard as well as re-installing SP2 to no avail. Any other thoughts?

how much netflow do you do?

I've tried to do this as well, but the other issue that I'm having with that field is that some VM's are showing as "physical". Besides that, I took a quick glance through the nodes table and didn't find a hardware field... Not sure where it is hiding

 browsing to select the file > clicking submit > getting the error

Donald, We have two different Orion deployments with the following; Deployment 1 Orion - 10K elements Orion Polling Engine - 10K elements Orion Polling Engine - 10K elements DB Server Deployment 2 Orion - 10K+ elements EOC/NCM - Same server DB Server Let me know if you have any questions on how this is working for us. What…

DO NOT UPGRADE TO vSphere even with update 1! We upgraded 4 months ago and have down time every week. If my SAN has any sort of issue we lose connectivity in the entire environment every time. There are undocumented bugs every time we turn around. DO NOT SEEK THE UPGRADE Sorry to hear, FWIW we've had a lot of success with…

Yeah, that wasn't what I was going after. I'm attaching two files. The first is an example rule, and the second is an example of the violation details screen. The problem is that the violation is the last line there, but there's nothing to signify that is a violation and not a pass. I would expect there to be a red X or !…

The solution is a real SQL query, not limiting the data you want to report on. The problem is that the scheduled reports load web pages. Data can be gotten via other means, but it would be nice if these didn't act by displaying web pages that will timeout if given too much data.

2 issues... 1.) For anyone else reading this, it's in the ActionDefinitions table, not the AlertActions table (my AlertActions is empty). PackageOrion NPM v9 SL2000Version9.1.0ReleaseOrion Version 9.1.0 - October 2008 2.) Please submit this as a feature enhancement request. This is a very unnecessary pain to change this…

take a closer look at what traffic you're seeing and what you're not. Could be unexpected differences due to ingress/egress differences. netflow by default is ingress, although i think it's egress configurable on 6500's. cisco has a really nice netflow config docs www.cisco.com/.../tech_configuration_guides_list.html

I would also like to be able to do this. So far I've had to use address group filters to be able to get a report accessible via the website. Scheduling graph reports would be ideal.