mdriskell ✭✭✭✭✭

Yeah unfortunately the traps don't tell you what is doing the invalid polling just that it is occurring.

would it be too much to ask for screen shots of all the tabs except for the actions?

Thanks steve....I'll test that at the next outage....Had another one at 12:45. I have since moved almost everything off of poller 1 to minimize impact except a small handful of "test nodes" so I can see if it fails. Still waiting to hear from support....submitted diags almost 7 hours ago.

Sorry for the multiple posts..not sure what was going on but they weren't showing up on my end.

8500 elements is right on the edge of the limit for one polling engine alone having the SQL server on that same server would definitely be pushing it...Disk IO is a likely bottleneck.

I agree completely...I am working on a Solarwinds implementation with over 5000 switch ports. We want to monitor all of the ports for traffic and errors but could care less when a non critical port went down. I did configure a custom property so I could only alert on the interfaces that were important to us but that doesnt…

I like to alert on any node status other than up, unmanaged, or unreachable. I want to know when something is down, unknown, or in warning.

 Just for fun I moved the trigger action from 3 1/2 to 5 minutes and I still am seeing several resets where triggers never occurred. Also even with the hotfix I still see that even when a device does actually trigger, it is hit or miss if the action actually takes place. I always get the reset action just not always the…

If a device is configured to send an authentication failure trap and you are doing a discovery or polling say (public, private, ACTUALSNMP) Then you will get a failure for the ones that aren't configured on the device public/private usually. It means something queried SNMP using an invalid string. You can filter these out…

Please post your current conditions.

Please post your current conditions for the alert.

Can you please post your current alert conditions. 

actually if I can get approval I can run that myself using PSEXEC. Thanks man. Now back to my original complaint...A monitoring sofware that doesn't alert when a key monitoring component (SNMP) isn't functioning.

Good to know it's not just me....This a major issue for us as I am no longer matching rules I have set (my conditions matched the OID). I did go ahead and reapply the MIB database in the off chance there was corruption and restart the services. No joy. I have submitted the diagnostics to support. I need some kind of…

Prior to the upgrade I had received 489 unique trap types and none of them were SNMPTraps.7 post upgrade I have received 40 unique traps and the second highest unique value is SNMPTraps.7 with 34000 + Traps I upgraded at 1:30 PM on Friday select TrapType, Count (*) as Occurances from Traps Where DateTime <= '2011-12-02…

I get the same error mcbridea. Not found

mdriskell, The query is already written to exclude devices with blank sysname. Thanks, I didn't notice that in the query and did not want to risk running it and blank out 200 device names. I will give this a try the next time I go through to make the changes.

Holy Wonderous Workaround Batman! Ok that may work but this code is deselecting...when I am ignoring I actually need to select them(I can easily uncheck the ones I don't want because they are so few)...Can you alter the code for selecting? I know nothing of javascripting (I'm just really figuring out SQL if I try to figure…

Need to confirm two things. 1. That Orion can still talk via SNMP to the device. 2. That the SNMP location is configured on the devices.

What does your disk IO look like? Go to perfmon and look at your average disk queue length for your disks. Look individually not total. The polling engine time is the system time of the polling engine. I would suspect you are having performance issues with both the solarwinds server and the DB running on the same box. How…

Updated the MIBs on my toolset and the OID is correct....So shouldn't be a MIB Database issue.

Here is the template I uploaded with this script. Hope this is helpful to someone else as well.

I wrote my script to validate that an NTP response was received. Doesn't really matter what the device you point it to is as long as it is acting as an NTP server. So if you have devices that are failing I'd assume they aren't acting as NTP servers.

Yes you should keep getting them. Can you post a screen shot of that section?

K I L L was supposedly removed from the ban when I complained about that before let's see....kill

My VM team is convinced there is no issue....I can't filter out on the nodes with problems because then if I have a real issue it won't show up. I've told my NOC to just deal with it for now

Looks like the NPM polling restarts by killing the services but the SAM polling does not unless I rebuild the SDF files.

I used Lasher's suggestions to increase the chunksize on the stored procedures to fix our issue. I have passed that information along to solarwinds support for a potential sp or hotfix. Have you tried Lasher's suggestion?

Sorry I no longer have it. If you are having similar issues I recommend engaging with support.

What version of .Net Framework is on the box?