rob.hock

Certainly not an expected behavior. Support ticket may be the best path forward: http://www.solarwinds.com/support/

Compatible in what regard? 10.4.2 and 10.7 support the same SNMP flavors.

Try adding the line feed (CHAR(10)) before the CHAR(13) carriage return.

Is the issue the server comes back, but not all services come back? Could we perhaps just monitor all the services we are concerned with using SAM?

As long as there is a licensed module (NPM/SAM/etc) we shouldn't be seeing this message. Support ticket may be the best path forward. SolarWinds Customer Support - We're Here to Help

All installers should be available in the customer portal. Not certain what version(s) you are running, but APM has been retermed SAM (Server and Application Monitor.) The ancillary applications (Report Writer, etc) get installed with the main module, NPM, SAM, etc.

We haven't been able to repro this internally. Is there perhaps a ticket number I can track?

Dave, This behavior would be expected at present. The results of the last A record lookup for that host are stored in the DB. In the event DNS lookup fails, NPM is still able to poll the device via last-known IP for that host. To test for DNS lookup failure- SAM has a built in DNS user experience template.

David is right, the likely culprit is VMWare permissions. Usually configuration of VCenter / ESXi hosts is the same procedure and as simple as putting in the credentials for discovery. If it's still having issues, DM me and we can have a SE assist further.

This is definitely a known feature request. We hope to be able to provide this functionality in a future release.

Have you considered configuring IPSLA operations for your environment?

Nkoos: here's a 10-minute tutorial to get you started: Video Tutorial: Universal Device Poller in Orion NPM - Videos | SolarWinds

Would you perhaps be able to post a screenshot of the trigger condition?

I see you've installed the new 54Gb/s Aruba APs... That does indeed appear to be a unit of measure issue. Would you perhaps be able to send a SNMPWalk of the WLC? rob.hock{at}solarwinds.com

This issue has affected previous versions intermittently, but should be fixed in NPM 10.7. Workaround would be to execute the Report Writer in Windows 2k3 compatibility mode.

If those units have been up forever, it's possible the uptime counter they are reporting rolled over. Might just restart the management card- always a good time to upgrade the firmware too.

If you have a moment, sign up for the NPM 12 Beta: NPM v12 Beta2 Now Available There are quite a few improvements to hardware health that would likely address this.

Check the registry under: “HKEY_CURRENT_USER\Software\VB and VBA Program Settings\Network Performance Monitor”

As Zack Mutchler says - "it depends" - check out the conversation here: Re: Polling Intervals - Best Practices

If you're running NPM 10.7 or greater, you can create a custom CPU&Memory poller under "Manage Pollers"

Devin, It may be best to involve our support team at this point: SolarWinds Customer Support - We're Here to Help

The new web-based reports may be easier to work with: http://www.solarwinds.com/documentation/Orion/docs/WebConsoleReportingGuide.pdf

Is this with the web-based report scheduler introduced in 10.7?

If I am reading that correctly, it appears those interfaces are only in a down state for a couple seconds. Even at 60 second polling interval, it would be statistically improbable for us to see the interface in the down state.

On the original alert, check the reset conditions and reset action. Likely you need to create a reset action to email when the device comes back.

Hi Brian, you should be able to just use a local account for polling. When configuring WMI polling, just enter the username with no domain prefix:

By creating a group and using "mixed" status, this may work here.

Edit the file C:\Program Files (x86)\Solarwinds\Orion\AlertingEngine.exe.config and before the last line (</configuration>) add following: <system.net> <defaultProxy> <proxy proxyaddress="http://192.168.1.10:3128"/> </defaultProxy> </system.net> Change to the correct proxy address and port. This should work “in general”…

Julion, Apologies, I'm not certain of the example there. Would you perhaps be able to provide some further background on what you would like to see?

If you Edit the resource, you can change it to a Top XX