rob.hock

That is very strange, as we are installing a packet-filter driver, and to my knowledge NR is using script injection. Was the NR config removed from web.config? We certainly don't touch webconfig

Doc should push this evening I believe. Try to remove the agents from "Manage agents" grid (so no nodes should be visible in either the agents or sensors grids) and then repush from "Manage Sensors" grid.

Definitely appreciate the feedback sir. To that point, that's why we are including sensors as part of the licensed "Core" platform. In the future, sensors may be able to feed differing data to multiple products, and tying sensor licensing / tiers to a specific product license count would get very confusing, very quickly.…

Virtual is fine. We don't have sizing guideline published yet, but if you're going to see gigabit-throughput, 4-core / 8GB is a good place to start.

With our Packet Analysis Sensors, we're actually sniffing the wire, and not using server counters or synthetic transactions. We will be able to determine the actual observed network and application response time, so you would be able to determine at a glance whether the issue is with the network or the app server(s).

Dave, Did this get sorted out?

Negative sir, they can however be exported from another (dev/test) instance and re-imported.

Uninstalling the MS update would be the best course of action until we can get a patch out. Turn time should be pretty quick.

The MIBs should be included, however it does not appear that device supports the typical IF-MIB for interface stats. We are looking at support for it, but it's unfortunately not as straightforward as rolling in the MIB. Old thread, but Denny explains the distinction rather well: Orion MIB Database – What Is It Good For?

If you could perhaps send me a SNMPWalk of that WLC? (rob.hock{at}solarwinds.com)

Correct sir - we still have a Win32-based report writer available as well.

We could sketch it out if you like: https://www.youtube.com/watch?v=2x3nItYhIWg

That makes perfect sense. When I say easily done- it is to say- easily done with what we are shipping today. We would need to create a new style of chart to accommodate for it. Would you perhaps be interested in checking out some mockups from our UX team around this?

In the 10.7 beta we introduced the ability to set node status based on SNMP response time. That would solve at least the initial issue.

Try the attached sample query in a custom table resource.

As that data is calculated, likely custom SQL would be required. Let me see if we can come up with something.

Michael, It appears from the packet capture in the support ticket, that the device stops responding to SNMP polling requests. Using the provided walk with a responder appears to function normally, so it may be device specific.

Yes sir- HF4 is cumulative.

Mike, We'll take a look at this and get back with you shortly.

Shiv, Topology mapping is dependant upon quite a few different data sources being available, and the engine (though based on LanSurveyor) does differ. We would probably ask our support team to dig into the logs to figure out the discrepancies. (http://www.solarwinds.com/support/)

Indeed- this is on the list of NA improvements. Moving NA to the web would also be highly desirable.

Not presently sir, but we'll look on it with our dev team.

Apologies for any confusion. Because SAM RC has not been released (thus APM/SAM alerts not migrating) the intent was to only have NPM customers install the RC to avoid confusion. Unfortunately for a few hours some SAM customers were provisioned in the customer portal. This was revised this afternoon. In the interim, this…

Using Custom Property fields is also high on our list. What WMI query would be useful in your organization?

Two different aspects: Report Definition - Meta data defining layout and dataset you could save as a file and share on thwack Report output - Scheduled report that would be emailed to stakeholder on a recurring basis.

Better handling of multiple contexts / multiple IPs / SNMP responders on a single device is still on our radar to address. Unfortunately priorities shuffled previously and we did not make forward progress on this. For the moment, each IP would need to be added as a separate object.

There is a UI bug on that slider under certain conditions in RC1. Check out Settings->Polling Settings->Enable Auto Dependencies.

Apologies for the frustration sir. Our MIB inclusion process should have relatively swift turn-time. If there is an outstanding request, please let me know the ticket number and we can follow-up straight away. Actually our new v12 beta (NPM 12.0 BETA4 + QOE NOW AVAILABLE) displays related functionality that allows you to…

Apologies- that post is a bit old. If you could perhaps open a support ticket and supply the mib, it will be scheduled for inclusion in next mib DB. (SolarWinds Customer Support - We're Here to Help)

Richard, Apologies, this certainly wasn't an intended "feature" but rather unintended consequence of other changes implemented for another module. We're looking at how to best address it presently.