akrekic11

Was there ever a resolution to this? We recently installed UDT as well and we are experiencing the same issue.

You must be running 7.x PANOS at minimum in order to get any sub-interface statistics via SNMP. Extended SNMP Support

I'm not sure if there is a way to alert for new volumes but if you have a discovery schedule setup for your servers it will notify on the web interface when it finds new volumes. 

I can add that this also started happening for me on a 5K Nexus after going to 10.3 from 10.2.2

It looks like the polling completion is at 99.99%. And Like I tried explaining before when I first add all of the interfaces they show up fine ( It even polled every interface once for statistical data) however afterwords they slowly all drop to unknown. I am only experiencing this issue with this single node. We are…

This worked for me thanks!

It looks like people are running into this problem for some different reasons however this did happen to me recently after upgrading to 3.2.0 so here is my story. Basically all of the 10 DC's were showing polls failing, none of the hotfixes available made any change to this for me. When I went into my DC nodes and tested…

As far as I know this cannot be done and when this happens to me the existing volume disappears and goes unknown it drives me crazy. What I have resulted to do doing is creating an alert that contains the query I will need to use to manually remove the specific volume from the database. And then I run a discovery nightly…

I would just create a custom property named 'type' or something along those lines then in the description put 'WIC'. Then when you come to your advanced alert you could put in a condition that said when custom property type = WIC

Because @ is used to declare variables in the NCM scripting language if there is an @ anywhere in the configuration its going to look for variable. I ran into a similar issue in the past and got around it by creating more variables and storing the values in them, then using those in the configuration. I'm going to assume…

I managed to resolve this but it didn't really make any sense. I had to redirect all my NPM traffic over a backup circuit during an outage on our main connection. As soon as I did this all the polling and stuff went back to normal on the node, however as soon as I switched the NPM traffic back to the main connection where…

What is this tool how do you access it or open it?

When creating a new alert if you go to the trigger actions tab and click on add a new action then choose send an email. Once you have the email alert action setup you can click on it to edit this settings and within there there is an SMTP server tab where you can enter your SMTP settings.

I think the best way to do this would be to create a new custom property for your NPM environment and assigning the name for each group to the appropriate nodes. IMO this is worth the effort as it makes other things easier like isolating nodes for alerts or NCM compliance reports.

I don't think you can acknowledge basic alerts you can only do that for advanced alerts.

I am not too familiar with UDT myself but can your solar winds server resolve the DNS for that device without using UDT?

You could adjust your alerting logic so that when status is unknown it can trigger an alert. However the way I monitor my AP's is that I have created an ICMP poller for the IP of each AP in my network which has worked well for me in keeping track of when they go down.