mcbridea

Hello and welcome to the Alert lab! I would recommend doing the first 3 in advanced alert manager so you can also set a custom property of something like "Name contains CR" in your trigger condition. That will knock out the first 3. 4 is a active feature enhancement request we have NetFlow alerts. If you have not had a…

The settings for auttomatic addiditions of NetFlow sources works only if the source device and interface are already managed in NPM. We have seen this issue when a device has interface reindexing issues. What type of device is this and does have persistent interface indexes?

I have not seen a limiter but you can suppress multiple devices. Check out this post

Checking the DB to determine if a parent is down seems like a bad solution. If this is the case I would expect the "supperession" functon to work randomly.

What do you need to accomplish with this?

Hi Scott, Please do open a ticket on this one. Andy

Yes - You'll have to add SNMP monitoring for the server and then add the interfaces.

Does this cover what you need?

Hi MatheiuJM, The VoIP license is set to match the Orion license. With the continued growth of VoIP this generally works well for a lot of our clients. If we priced by voice path or such, chances many customers would have to come back for new licenses as they add VoIP infrastructure. With the VoIP for Orion 100 you can…

Your question, "Is there any way to create an alert for a group that I have created in NCM?" is very vague. What type of alert? What do you want to accomplish? The post reads a lot more like you just want to vent about SolarWinds and perhaps sell PRTG along the way. If you really are inteested in creating a report, please…

Hello Bogor, Please add this to the "Tell us your unknown devices" thread. Andy

You can use custom props, just as you did before groups, to specify an email target.

A node going down is not immediately detected. The node will go into a warning state on the next poll and then show down once the warning period has expired and the device cannot be reached. During the warning period Orion fast polls the device to determine if it is truely down.

You can mix status sources, they can be from the custom poller and node by using the Type of Property to monitor drop down.

Are you getting any error messages in the Traffic Analysis Evevts Resource?

Yes - the gauge appears to be backwards. I'll alert the IP SLAM team.

Check in Admin -> manage views, choose the view you are having problems with and click Edit . Look for View Limitations at this level.

That choice is not available today.

The error OIDs are rolling SNMP counters which are fed by IOS. Clearing the counters in IOS has no effect on SNMP counters. The numbers are cumulative for the given time period. So errors today will have a running count for today only.

Not all the information you get in the show ip sla commands will be in the Orion UI. I'll mark this for the PM to comment, I think it is a feature enhancement request.

Check on the node details page for one of these devices to see if that information is populated in Orion (Node Details) . If it is not, rediscover the device and see if it shows up. Let me know if this helps.

The 2 hour chart shows data in 15 minute points, so 7-8 GB is about right for 50 Mbps.

The information you got is inaccurate. The VoIP module is being expanded to include several IP SLA operations that are not VoIP related, making it a much more powerful offering. VoIP monitoring is still included but it will be renamed to IP SLA Manager to better address the expanded functionality. See…

Hi Gerritt, Did you get this resolved? Andy

Are you doing an F to C transformation? If so, maybe somone accidendly began monitoring the poller instead of the transformation.

Take a look at the content exchange area for APM templates http://thwack.com/search/thwacksearch.aspx?q=Oracle&s=search&stype=g&sub=42

The installer will make the setting.

Hi netmon, Can you tell me about the SQL setup? Andy

Have you tried a scheduled discovery? That should detect the changes and correct the monitoring.

That is a screaming SQL box. It is hard to know how the SAN will handle that load but DAS is historically much faster. The numbers for the F anf G drives must be off as RAID 10 always yeilds an even number of disks.