mdriskell ✭✭✭✭✭

ONE RING TO RULE THEM ALL!!!

You may have misinterpreted what I was saying. I said unless something came along that was universally adopted and just as simple it shouldn't die. What I don't want to see happen is 10 vendors coming out with 10 different ways to do it. Microsoft has already started that precedent by deprecating SNMP in favor of WMI. What…

Flapping interface detection is best dealt with traps. No NMS system can poll frequently enough without impacting the devices its polling to detect an interface bouncing rapidly.

I just brought this up yet again on a UX call I participated on. Hopefully one of these days this can get done.

I was thinking of a feature request the other day. Since systems can now be monitored via WMI and mount points are not discoverable via SNMP but only WMI or a script why not discover MPs on a WMI managed node. Glad to see you beat me to it +1. I'm intrigued by the Windows service control but wondering how the users will…

This would have been an awesome feature for my last employer who was a Managed Service Provider. Has my vote.

That would be ideal but not only for interfaces I could see that used across the entire product suite (nodes, volume growth, applications)

Are you referring to also being able to cross reference the data? One of the key examples we struggle with is I pull the IPTable listing from several cisco and juniper devices. It returns an interface index number. However the interface descriptions are in a completely separate table so there is no way to correlate the two.

I used to work with a web developer. Any time I got to a screen where I had to click with my mouse to enter text instead of just hitting enter. I would curse him on behalf of all web developers

Adding our own MIBs would be a great feature request. The fact that we have a 7-10 day turnaround to get MIBs is painful. I've started looking for a replacement tool to handle SNMP traps as I haven't seen movement and they aren't going away. I need something flexible.

I agree peter....making it pretty is far less important than making it functional. What I find troubling is I see several votes and comments from long time users or even SolarWinds MVPs and unless I'm just not recognizing a name I don't see one single comment from a staff member. I'd really like to see the NPM product…

Good point. Right now they do show (in the trap viewer) the NodeID if they come from the same IP as one in monitoring but that is where the relationship ends. None of the custom properties can be used. If I unmanage a node trap rules still apply. You would think there would be more of a cohesive union between these parts…

First of all this is great and has been needed for a long time. I do have one question though. Will we be able to see all support cases tied to the SWID or only our own? 

LOL I snapped that during the premiere and sent it to Danielle & Kellie stating it was great product placement . And FYI my cable company brags on how great they are...I would never switch from my DTV.

If you cannot add the device via SNMPv3 then you cannot receive SNMPv3 traps. The credentials used to monitor a device via V3 are the same credentials used to decrypt the traps.

I'd suggest trying Volume Status = Unknown. Unknown means we are failing to poll the volume which would be the case if it was removed from the OS.

Just to be clear are you trying to add the Windows Server via SNMPv3 or something specific to whatever building management app you are utilizing? Windows server doesn't support SNMPv3 and SNMP itself has been deprecated as of Server 2012.

I have gone that route as well in the past so I had both a local copy and a network copy.

Awesome stuff as usual @"chad.every"

Yes but what about the other conditions like hostname, IP addr, and SNMP string are they set to *

Is it at the top of your list? Can you post screen shots of each section?

That keeps it from being stored in the db period...it hits your server and is filtered before it writes to the db. You are correct though it doesn't stop the network traffic...you have to kill that from the sources. If these are all windows servers you can turn off that send auth trap piece I mentioned earlier....Will stop…

You create it from the Trap viewer on the Solarwinds server itself. Create a rule with these conditions and put it at the top. Be sure to use any source, any snmp string.

Apparently K. I L L is not allowed

I would still filter these out so you don't kill your DB...after you get the known ones cleaned out you could turn it back on to see if new ones occur.

Disturbedguy, That sounds exactly like my symptoms...I could list and test but the polling itself didn't collect anything SNMP related. I only restarted Orion services in my case because just as you showed you could list resources and test so I knew SNMP was working.

It hadn't happened in a week but it was happening nightly so I migrated all but a small amount of nodes off of that poller so I'm not sure if it wasn't failing because of the repairs or because I decreased the load. The escalation engineer I worked with had me to a full repair of NPM, SAM, and core yesterday. I then…

I uploaded the working template to thwack...hope this helps out other HPUX users as this was a major hurdle we have been trying to overcome for us.

I don't know of a way to do that on a server....maybe netstat -a but not sure. If it were me I'd use a sniffer.

Now that you say no SNMP data has been collected for the node it reminded me I had this same issue about a month ago. Is SNMP collecting data properly for any nodes? Anyway my symptoms were I could test SNMP without issue and it would come back successful but polling SNMP did not work. I restarted all my Solarwinds…