RichardLetts ✭✭✭✭✭

1. Open a support case with Solarwinds -- there is a feature request out there that is more than 5 years old, but everyone opening a support case for traps will help make this through. really, this will help other users get this feature in the product sooner. 2. please search thwack, I've written a LOT of replies on how to…

I wrote a database trigger for NPM11 that prevents this modify it as needed for your enviroment and NodesData in NPM12 on days when we delete nodes we make sure they are all appropriate tagged, I disable this trigger, we delete the tagged nodes, then I re-enable it. I cannot tell you how many times this has saved one of my…

Is there a way to turn off pulling the aruba client stats (globally)? I know some people make use of this, but it's a lot of data, and I think it's causing some of the polling problems we're seeing.

This can be done as a custom SQL alert on nodes this is where clause for the trigger condition: select nodeid,caption from nodesWHERE Nodes.CPULoad >= 70 AND Nodes.Caption LIKE 'usappserv%'and(select count(*) from nodes WHERE Nodes.CPULoad >= 70 AND Nodes.Caption LIKE 'usappserv%') >=2 this will generate alerts for nodes…

Aside: the only DWDM/Optical equipment I've come across with a rational and sensible SNMP implementation is Adva optical; the other two (three now) I've used do something similar to what you have. Try using the 'conditions' tab like this:

is the custom property editor fixed?

create a custom SQL alert on a node, with a condition that looks something like this: inner join syslog on syslog.nodeid=nodes.nodeid WHERE syslogseverity = 3 AND datetime > Dateadd(hour, -1, Getdate()) AND message LIKE '%NTP Server Unreachable' Change the where clause to match your syslog messages.

I would open a support case. the Job engine should not be stopped -- you may have a corrupt database file (the job engine has its own tracking database) and it needs to be cleaned up. Thanks

what happens if you add the interfaces on nodes that are members of the group to the group? I don't want an interface down on a node to cause the status of the group to become down unless it (the interface) is explicitly in the group -- I have routers and switches with hundreds of interfaces, and any one of them is almost…

it does not include the scaleability engines in the assessment.

have you followed this? SolarWinds Knowledge Base :: Links provided to acknowledge alerts using the ${AcknowledgeURL}variable do not respect SSL…

there was probably a process running from NCM.. like a backup job or something that prevented the file from being overwritten. When you rebooted the process got killed and the 7.5.1 install worked.

I take information from the SNMP traps from the [aruba] controllers and flag the AP down immediately which speeds this up considerably. In my environment I have to check the AP status on the primary and backup controllers since an AP will be up/down/missing on one, and down/up/missing on the backup. i.e. on startup a…

Awesome! I have 4 additional pollers, so that should be able to cope with 200K flows/second. [I seem to often bleed on the size edge of some of the Solarwinds products so it's nice to have someone running a larger install of any product.]

is there an idea for this for us to vote on?

IMNSHO UDT discovery is broken, it's been more broken since 2.0 when the way one configured ARP-table reading changed. a) there is no periodic rediscovery function b) there is no easy way to filter UDT ports on a large scale... we have over 4000 switches and 300,000 user-access ports, yet we have 576,000 ports in…

SNMPversion =1 or 2 This only really affects the use of the awesome GetBulk operator 64-bit counters should be disallowed in snmpv1, except there are some broken snmp implementations out there that do not support getbulk properly, but do have working 64-bit counters...

It's a brand new Macbook Air running 10.10.3 My laptop bit the dust and my ipad 1 was getting old, so it was time for an upgrade; wouldn't you know it, the first site I went to caused my browser to crash....

Honestly: Strength: we have a well-working FoE install. Weakness: My Orion Admin quit at the end of the year (I'm hiring if anyone is interested). The server operating systems we are running on are not supported by 12.2 and WAN-HA in that version I am being forced off FoE in March (and not enough time to get the changes…

this is untrue; NPM12 is supported with the FoE -- we've been running that way for several weeks now

In the case of Thin APs their status is pollled through the wireless controller that are connected to and have a different set of alerts. note: if you have controllers with a 'failover' configuration the same AP may be down on the backup controller and up on the active controller and alerts are somewhat hard to get right.

I think that making the internal components all use UTC would make for a great idea.

very roughly 81.77 bits / second / element

On your database server have you looked at the SQLserver activity monitor to see if anything is 'stuck' there? If you have database issue then you should see processes 'suspended' and waiting for something [I use task state of non-blanks to see what is running, and what is stuck] this is fairly typical on our database…

"Alert me when a polling engine has not updated the database in 10 minutes" is a good alert that should be enabled (if it is not already)

the checklist is very good (second link) -- i used it for a recent move.

At the risk of pointing out that the numbers of elements are not linearly correlated correlated with the Polling rate. Consider four of our polling engines below (All four servers are identical, aside from the nodes being polled.) The two pollers running at 50% or less have more than 10,000 elements on them…

This requires a plugin that crashes all of the time on machines here (shockwave I think).

on a Juniper switch we define apply-groups that have common sets of settings; then we apply the groups to the interfaces this means that we consistently set things on interfaces across all switches. e.g. when we moved all trunk interfaces to support JUMBO frames so we added that apply group to the trunk interface apply…

neat... notes: 1) the '2' is part of the mib definition: all switches should be using 2 for blocking as this is an IEEE MIB 2) you can move the 'Where' clause into one of the subqueries, that might make it work faster (as there are fewer rows to be joined from 'A' to 'B'). When working with SQL queries it's helpful to…