mcbridea

Got it - Thanks!

You would be surprised how many shops use public/private. Not that that makes it a good thing! ;)

Custom SQL is not something we create for users but if there are ways I know to get past a SQL hurdle, we won't let you drown. I'm double checking an idea I have to solve this with a SQL guru here. I'll post as soon as I have something.

Also see http://www.solarwinds.com/documentation/Orion/docs/Groupsanddependencies.pdf

Pyro - are you using the ip flow-cache active 1 command on your configs? If not, this will fix it.

Use RAID 1 for OS and app, RAID 0 for temp db and logs. I the SQL box can take more drives than 6 give all those to the db in a RAID 10. 4 drives is the minimum for a RAID 10. If you can only have 6 drives you could use 2 in a RAID 0 on the db and backup frequently.

It apperas that when you choose "Bytes" for the Y axis the graphing engine automatically converts to KB, MB, TB... The data above only fills the KB range so KB is appropriate to display.

That will work if you get an additional NPM license and run the two independently of the other NPM instance. The additional NetFlow receiver alone only helps for source reachability issues as it still writes to the NPM database.

The IP SLA data for any interface on a device is reachable in the device RTTMON MIB. You may have to set up the IP SLA operation manually and then add it to IP SLA Manager.

You could make an alert for nodes not down, drives < threshold etc and then use a time filter to allow it only to fire when you want it. Or hire a town crier with a bell? "Ten O'Clock and All is Well!" ;)

If the delay gets over 2500 ms it will be seen as a ICMP failure so you are far from that. To best understand real traffic delay I suggest setting up IP SLA operations if you are a Cisco shop. Check this out for a better understanding.

Hi jonchill, We do have some logic behind the pricing of NetFlow Traffic Analyzer. NetFlow is a very data intensive technology and we need to provide a product that scales to meet the needs of all size networks. A small company may deploy NetFlow on their Internet link only and have a low flow rate. A large enterprise with…

As Ed McMahon would say "You are correct sir!"

Thanks Brandon. I have posted a UnDP poller for HA status. https://thwack.solarwinds.com/docs/DOC-175583 Many of the OIDs you list are standard, so thing like interface status and interface utilization will add just by adding the node in NPM. Have you added any of these devices yet? If so, take a look at what is provided…

What would you like to see?

Hi aarevalo, I see you posted the rquested screen shots in the ticket. I'll prompt the support agent.

I'm not sure about those items but I have marked this for the PM to look at.

Dave, I checked and we are polling these OIDs. Do you have a ticket on this? Andy

Two noteable control plane exceptions are 7600's and 6500's which implement NetFlow in ASIC but use control CPU to a lesser extent.

We do have a work around to uninstall NTA, remove db and reinstall. I know this is not a popular solution so I have escallated to find a better fix. Andy

Hi rgward, Not at this time. I assume it would be bad for your environment? Andy

That makes sense. Not that I like it a bunch.

Can't get rid of me that easily! ;) NPM now includes a Universal Device Poller (UnDP) that allow you to monitor about anything. The UnDP templates are user shareable - here is one for APC

There was a typo in your original post. Of course what you meant to type is that MRTG is consistently off. ;) For total bytes per time period we simply sum the octet counter data. That is good data for billing assuming the interface is segrated to the billed party.

You can OR the statuses you are interested in and leave off Unknown. Unknown may also indicate that the interfaces or IFIndex have changed and the interfaces are not reachable using the OIDs presently polled. In this case the Unknown status will persist until you List Resources again and select the new interfaces.

I agree. I do occasionally increase the polling frequency of stats for a single node to as rapid as 2 minutes, but doing this globally would be a huge waste of element polling. Typically, I only apply this to a node with WAN interfaces that I need to manage to tighter requirements than other interfaces.

Can't do it today, but if you post it under NPM feature requests the PM will see it.

Yep, I just got off the line w/ support and they told me it is a 7.2.2 feature, but the AG does not mention that. Looks like I'm in Windows Task Scheduler hell.

So the problem is a permissions issue with the Alerting Engine. Make sure you Use "Run as Administrator" for installations.

Hi slackerman, In SAM settings create a new template for this SNMP monitor and then add the SNMP component monitor to the template. You configure the monitor as shown in aLTeReGo'S doc link. Andy