brianlee22 ✭✭✭✭✭

In the past I had issues where I saw user pc's connected to switches that they are definatly not connected to. My issue resolved it self when I realized that I was monitoring trunked ports. I don't know if this will help you or not but at least it's an idea.

Up and down status use the Default Node Interval which we use to poll every 120 seconds. The same is set for the Default Interface and Volume Poll Interval. This means every 2 minutes it looks at the node/interface/volume in question now in those 2 minute intervals it will mark the node down in 2 minutes as well (listed as…

Normally when alerts do not seem to work properly I tend to remove everything except for what necessary for it to trigger and expand it from there. What I did was create my own custom property for volumes and filled in the fields for the devices I care about and if no one wants to be notified or see the device in question…

This is what I was refering to click edit which is circled in red and then you get the level sorts.

In your node tree window you need to click the edit button and change your grouping level. You can remove the root group and just have it group by subgroups like you want.

Found the solution for this: https://thwack.solarwinds.com/message/109956#109956 It appears to have worked for me and I saw this Among my THWACK searches. lasher Apr 22, 2010 11:26 AM (in response to andrew) That would be something like: (Message NOT LIKE '*A.DS2*')

The only way to do it at this point in time is to create unique group details pages. At this point there does not appear to be a way to designate which group opens what group details page if multiple ones were created. You can try playing with the View Limitations options but I am not completely sure that will do exactly…

I update NPM first if theres an update the rest which ever I happen to choose. Never had a problem doing that way. I do the same for the additional pollers

Before we had the subviews everything was under the Summary tab. Now that we can organize by subviews I moved a lot of things we did not need to see for a basic overview of a device to its own categories. Also it helped remove items that did not apply to all devices.

It depends on how you have your alarms setup. If you have custom property fields setup that your alerts trigger off of you can just blank the field out and then your done. You can always delete the nodes in question. If you have a general email alert setup To: General@yourdomain.com for all nodes showing high ping response…