rob.hock

SJA- The default polling intervals in 10.4 were indeed 120 seconds. Perhaps someone tuned up that original install?

This is related to the new zoom-level aggregation. Since we are automatically aggregating nodes of multiple locations, the aggregated groups could have many locations. We could definitely improve this behavior.

To further expand on Lada's explanation: admin rights are required for SQL reporting as SQL doesn't respect security and limitations. Imagine a scenario where you have multiple customers in the same instance, and you want to segregate their data so neither can see the other's data. Having direct SQL access breaks down this…

At present it is not possible to create custom (non-HTTP) applications. If you would perhaps be able to send over a small PCAP of the desired traffic we can look at future inclusion. rob.hock(at)solarwinds.com

Did you try to create the idea in the feature request forum?

Hi Jeff, Apologies for the difficulties sir. Is there a support case opened so we can reference it? In the interim, it sounds like you have been successful in removing topology calculation to reduce load (not that this is a solution, just a workaround.) Since you're on 10.7, there is also a method of removing topology…

You can specify the web resource to display table data like below. Right click on the poller. :

If you happen to be using NX4500 or NX6500, SNMP walks of the devices would be super handy. Please feel free to email them to me: rob.hock{at}solarwinds.com

That's odd. Feel free to send over a SNMP walk. You could also manually set the speed on the interface properties as a workaround in the interim.

Typically SNMP would be considered lighter weight from a host / query / network perspective.

Apologies for the frustration. Likely support is referencing this MS update: Microsoft Security Advisory: Update for minimum certificate key length VMWare has a KB on how to address: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2037082

This KB may be helpful: http://knowledgebase.solarwinds.com/kb/questions/2790/Network+Atlas+is+unable+to+connect+to+the+SolarWinds+Information+Service+%28SWIS%29

* Agent footprint/impact on host server? Depends on volume of traffic- "typically" around 10% CPU. Good general rule is to factor 1 core per 100Mb/s sustained * How does it handle LACP configured NICs on servers? Teamed interfaces are OK * What does the QoE application actually use for measurement? Max or Avg times? Both…

- Can we upgrade NPM from 10.6.1 to this version? Yes - Are there any changes/requirements for this version similar to NTA 4.and NCM 7.3 (design)? We introduce new sensors that can be installed on endpoints. - Does this version provide "Role assignments". Example: only need to give "Unmanage/Manage nodes" but not to modify…

A Network PAS would be deployed to a dedicated system (physical or VM) attached to a dedicated interface on a network device.

We're installing a packet-filter driver on the endpoints (or dedicated sensor) and analyzing packet data. Check out the GA announcement FAQ for further detail: ANNOUNCING GENERAL AVAILABILITY OF NPM 11.0

Did you manually deploy the agent (install MSI by hand) or push from the "Manage Sensors" grid?

The CPU / Memory isn't reserved, but rather the sensor would use up to those maximum numbers if required.

Apologies for the difficulties in getting these issues resolved. Following up with support now.

Present limit is 1000 sensors. Unfortunately we haven't published pricing yet. Apologies sir.

It is indeed separate from SAM statistical monitoring. Based on packet-level data observed by the sensors, we are able to identify and monitor response time on ~1200 applications.

Thank you sir. Documentation is still a work in progress, but we will have it available shortly.

Indeed- simply install a sensor on each server, or install a Network sensor and span traffic to it.

No major issues. The driver was actually an install-time issue with RC1 where config wizard finished with error where case sensitive DB - INFORMATION_SCHEMA used.

No known issues, but I will follow with support.

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

Check out this sample report: http://thwack.solarwinds.com/docs/DOC-169153

*Arggg* - may ye walk the plank if'n it don't get implemented... Thanks Stephen- made my day.

Indeed- parking the license and re-activating after bringing up in the new environment would be the safest bet. 

All, Apologies for the negative experiences on the support side. I've asked our support management team to reach out so we can figure out what we need to do to improve in the future. Please let me know if there are any questions or concerns in the interim. Regards, Rob