rob.hock

Not sure if you've had a chance to check out VRF support in the 10.7 beta- but we would love your feedback. If you haven't signed up yet, sign up can be found here: NPM 10.7 Beta 2 Survey

This is indeed possible with NPM 11.5 RC: What We're Working On: New Alerting Engine There is a new "All Alerts that could be triggered by this object" resource available.

We do not have a public demo instance up at present unfortunately.

We're certainly tracking NSX adoption for support. Curious - what sort of new problems are you encountering with NSX?

If you were to install the sensor on individual endpoints- yes. Currently at the server level we would have aggregated metrics.

At first pass I would say that it is because we are not polling topology data for that connection. A support ticket would straighten it right out.

Improving the granularity of security permissions is certainly something we need to do, and the community has shown support for the idea via this FR. While we wish we could tackle everything all at once, we don't have an unlimited number of devs. After that it comes down to prioritization- we currently working on several…

Check out the 10.7 RC with node and interface thresholds. Yes, we're still working on volumes.

rob.hock<at>solarwinds.com

Makes perfect sense. Also Custom Properties may provide similar functionality: http://www.solarwinds.com/resources/videos/video-tutorial-managing-custom-properties-in-orion-npm.html

I love it when I get called out. We definitely can do much to improve granularity of permissions, and it can't wait too much longer. There are plenty of good ideas in this thread on the sort of roles / rights we should implement, so please keep it coming. At a minimum when we're looking to migrate alerting to the web (What…

There is indeed an upgrade path for current LANsurveyor customers, your sales rep should be able to assist with the details.

Ashley, Unfortunately we can't give ETA on when we would have it, however I'm fairly certain we won't have it before Q2 of next year, if that helps your planning.

Trapeze support shows up in NPM 12 Beta4: NPM 12.0 BETA4 + QOE NOW AVAILABLE

Indeed sir- these devices should be detected correctly in NPM 10.7, which reached RC yesterday. Installer is available in your customer portal.

In order to enable local data queuing, we take advantage of a built-on MS technology called MSMQ. We would simply need MSMQ installed on the APE and main poller. (Installing Message Queuing (MSMQ)) Length of data retention in the event of outage is a function of how active the APE is. In our testing this was "typically"…

This new functionality is in NPM 10.7 RC, released yesterday: NPM 10.7 RC1 Now Available

In this case, are you restarting SNMP on your devices and the volumes are showing up as new?

We did indeed fix this behavior in many places where it was inconsistent in 10.7. If we missed one, please let us know.

Assuming we had the ability to automagically determine dependencies, how would you imagine interacting with them? Or correcting the calculations if we were wrong? How else would you want to use them besides alert suppression?

The Network Packet Analysis Sensor (NPAS) is deployed to a dedicated windows system with a dedicated interface attached to a span/tap/etc.

Have you had a moment to check out our new beta? NPM 12.0 Beta3 Now Available We would love your feedback on the new alerting functionality if you happen to have time for a call next week.

In NPM 11.5, you can enforce this per user by executing a SQL query similar to: UPDATE [dbo].[Accounts] SET [AllowViewCopCheck] = 'Y' WHERE AccountID='...'

Unfortunately not seeing the form submit on the back-end. Can you perhaps PM me your SWID?

A bit of a taller order Each module handles style in a slightly different way, and some older ones may even hardcode in a few places. I'll inquire as to what we may be able to share.

Apologies if it wasn't clear sir - the user login provides the access control. If the user have right right to see alert(in web) they will see it in Desktop notification. If user doesn't have right to see that alert the will not see notification. Account / alert limitations are applied.

This should indeed be fixed in 10.6 and work with ESXi 5.1. If we're still having issues, a support case would be the way to go and we can dig into it.

You may be interested in the new wireless heat-map functionality currently in Beta: NPM 12.0 Beta3 Now Available

That is correct sir- thank you! I will pass this to our doc team to update.

Often times this is caused by bad DNS records as WMI does a funny forward/reverse look up. Let's validate fwd/rev DNS is correct for all the IPs in the error message as well.