rob.hock

If you edit the interface, you can set customer bandwidth:

Unfortunately we can't yet use a whole web-based report in a view. We can however create custom table / custom chart resources in views identical to those used in reporting.

Good point. We will definitely look at improving this in alerting.

Unfortunately it looks like multiple actions may be required here. If you were to sign up for the 10.7 beta (NPM 10.7 Beta 2 Survey) you would see new alerting functionality which should satisfy this use case.

Are you seeing the discards reflected via CLI as well, or just in the Orion interface?

Have you tried to change the time period or interval on the 7 day or "today" chart? Would you happen to know if you are using the "classic" charts?

Very likely an NCM issue. Go to Settings -> NCM Settings -> Node Inventory and Uncheck "Extend VLANS inventory option".

We've done a lot of work on reporting in the NPM 10.6 beta. If you would like to check it out, please sign up here.

That's correct - it's an RC for the SR. No additional features, but quite a few fixes outside of what has been released in HF format.

Once a node on next poll doesn't answer – we start Fast Poll – ping each 10 sec during the Warning Interval (SWNetPerfMon-Settings-Default Fast Poll Interval). The period can be made shorter – up to 10 sec (MIN) which means 1 addition ICMP poll. The warning interval is a GLOBAL setting, so making that shorter will affect…

Perhaps you are using a new installer with an old key? If you log into the SolarWinds Customer Portal (https://customerportal.solarwinds.com/CustomerPortal/Index.aspx) you can grab the new key.

ICMP redirect potentially? Could try to switch to SNMP status and see if similar results are obtained.

The AppInsight metrics for fragmentation are updated once an hour, so this may not reflect the present statistics. Check out this KB for tips on reducing fragmentation further: http://knowledgebase.solarwinds.com/kb/questions/3202/Critical+index+fragmentation+detected+during+database+maintenance Please bear in mind, that…

Which version of NPM are you running? If less than 10.7, we would suggest upgrade. We fixed some issues related to this a few releases ago.

New alerting engine in 11.5 includes a macro for downtime: ${N=Alerting;M=Downtime}

We identify devices by sysobjectid, which for new or exotic devices may not be in our DB. Check out this KB: http://knowledgebase.solarwinds.com/kb/questions/3535/SolarWinds+shows+my+device+vendor+as+%22Unknown%22.+How+do+I+get+SolarWinds+Orion+to+recognize+my+device+and+device+vendor%3F Also NPM 11.5 introduces new "Node…

The screenshots appear to have blank values- but regardless polling intervals are configurable. As long as your polling completion rate is acceptable, feel free to adjust within reason.

Assuming you are doing this to have a "Who's on Call" resource. Have you checked out Alert Central? Alert Central - Free Alert Management Software by SolarWinds It's free, and has this precise functionality (in addition to being able to manage your on-call rotation / time zones / etc.)

It never hurt to stop the SolarWinds (or any other dependant) services before bouncing the DB server as well.

As a matter of fact, this functionality is being tested in our SAM 6.0 beta. Sign-up is available here: SolarWinds Orion SAM 6.0 Beta Participation Survey

Global search is definitely something we are interested in. Assuming you had a pervasive search- what else would you use it for?

NPAS vs. SPAS doesn't really make a difference if we're filtering traffic for the same nodes, we'll still have the same accuracy of response time data. Here's a quick video on how ART / NRT are calculated: Deep Packet Inspection Tool - Top Deep Packet Analysis | SolarWinds

Jeff, Have we checked to see if “Show all updates, for all currently installed SolarWinds products, including previously ignored updates” is checked?

We haven't heard any other complaints. We'll dig into it. If they are recurrent and annoying, the display could also be disabled.

If you're alerting on Group or Group Member objects, there won't be node properties available for alerting. You could use Name or URI to get the NodeID.

There are a lot of variables in that question, but in spirit it should not be an issue. If you are running into polling timeouts due to latency, the timeouts are configurable under Settings->Polling Settings

At present we would not have the ability to filter pre (or during discovery.) How many interfaces are we talking about, and on what gear?

Surely - our Server and Application Monitor module has built in HTTP and TCP port monitor types: http://www.solarwinds.com/documentation/en/flarehelp/SAM/Content/OrionAPMPHComponentTypesTcpPort.htm

The Quality of Experience dashboard in NPM 11RC has built-in signature for Office 365. Check out the announcement here: NPM 11.0 Release Candidate Now Available!

I was unable to reproduce the issue with the same environment (minus fusion VM.) It may be good to get support involved to step through it: http://www.dameware.com/technical-support.aspx