mcbridea

I suggest you open a ticket so we can fully investigate.

Not today but we are adding more report flexibility soon.

Just to make sure - is it all up and running for you now?

This is probably happening because the device does not support the dot 11 MIB.

If your main Orion is working well you should use at least that level of hardware. The minimums are the same as the main Orion.

NetFlow Traffic Analyzer supports v9.

That is not possible now. What you could do is beef up the SQL server and maybe bargain for a 30 day report instead of 90 days. Here is a paper on performance that may help. http://www.solarwinds.com/documentation/Orion/docs/OrionPerformance.pdf

I'm not certian I understand the question but this is how NPM determines if a node is down. Node is pinged in a regular ping cycle. If the node dos not respond, NPM sets the node status to warning and starts a fast ping cycle for that node. NPM fast pings the device for the time set in the Setting interface as Node Warning…

Hi rsprim, We are moving to a new licensing and Toolset is the first produt to implement it. I appreciate your feedback as it will help us to plan for this type of an environment. I'll share the feedback with the licensing Product Manager as well. To help you get through this I suggest you give support a call. Andy

Not presently. I'll move this to the feature enhancement section.

Thanks for the input - We are looking a new ways to display data so we will take this into consideration.

Hi Rob, There's not enough info here to troubleshoot this. Can you open a ticket with support? Andy

The ability to alert by number of occurrences per time period is an open feature enhancement request. What you can do is specify how often you wish to check a value. This Technical Reference and the Administrator Guide have the details on how alerts work and how to set them up.

Thank you for posting this!!

Which product is this for?

From what I can find those are both outbound extOutput.1 (1.3.6.1.4.1.2021.8.1.101.1) : number of filtered messages (integer) extOutput.2 (1.3.6.1.4.1.2021.8.1.101.2): number of spams detected (integer) From the description I wouldn't find it unusual for both to have the same value. Maybe I'm missing something? Andy

Hi Eric, Cisco has cleaned up NetFlow a lot so it typically has little impact on the device. The impact you will have on the device and the NTA database depends a lot on how many exporters flows you implement and how many flows you send to Orion NTA. The big switches have the ability to handle a lot of data so start small…

Thanks SLXer - We will take a look at this. Andy

Hi Don, Make sure Enable automatic addition of NetFow sources, and Allow monitoring of unmannaged interfaces are checked in NTA Settings. Andy

If the reboot is always at the same time you can exclude that period from the alert.

NTA does resolve IP addresses to DNS names so that's how you will see things like you tube traffic. It doesn't work like a sniffer.

There are several HTTP sites with bandwidth testers. You could script to one of these. Google "Bandwidth Test".

Is the web component installed on an different server?

Hi Michael, I am seeing the same behavior. Can you open a ticket so we can track this as a customer issue? Andy

Hello, So that I have a clear picture of what you want to accomplish, are trying to detect/enforce that those lines are present? If that is the case we could do it with one rule. Andy McBride Loop1 Systems SolarWinds Training and Engineering Services

1: Is it feasible to store Netflow data for 90 days? (we currently store data for 14days). Yes, but performance depends on how much NetFlow data you have. How large in NetPerfMon now? How many NetFlow sources do you have? 2: Will this slow down Orion NPM performance? It could. Check out these recommendations for minimizing…

By nothing happens, do you mean that the node does not show up in UDT?

We are looking at this type of ability - stay tuned!

I would create a custom property and assign that property to the long response time nodes. Then create an alert for nodes w/ that custom property. After that make sure you add logic to not alert on the nodes w/ the custom property in the general response time alert. Otherwise you will get 2 alerts. See this doc.…

Do the workstations have SNMP enabled and configured?