Lt.Ripley

Comments

  • I use this feature as well but it does not always work for us. We have a support call open with SolarWinds right now because we can't follow cluster resources that are DHCP instead of static. They are detected initially with correct info, but then the IP reverts to one of the cluster host nodes instead of the resource. 
  • I'm having this same problem since our upgrade on Thursday - even just a basic SMTP monitor. We just upgraded to NPM 10.6, SAM 6.0 & WPM 2.0.1. We added hotfix 2 for NPM & SAM but not hotfix 3 yet (though likely going to do so asap now). The initial poll is stuck in progress, and all of the charts and data show "error…
  • I contacted support to see if there was something we could do about not properly reading the ESX host information. They said ESX v4.0 and higher no longer displays any disk information in SNMP and this is why we can't see it. I just tried to pursue this since we do have it working on one ESX v4.0 server. Shall likely…
  • We have granted all the groups the right to logon locally thru the local security policy. I don't know why some members of an AD group work fine while others don't (ie. we added the AD group for all of our server admins. Half of them work fine, the other half don't at all. Only fix thus far is to add those users…
  • Sorry, I should have confirmed, we're running NPM v10.1.2, APM v4.0, with an ESX credential (that at one point was given admin to see if it was a permissions issue). Monitoring ESX 3.5 worked, then there was an upgrade to v4.0 and so started our problems. We now have one single ESX v4.0 server that we can see all resources…
  • Sorry, I should have included all of that information. We're running NPM 10.2 (with APM 4.2 SP1). The error is very short. Just a "Message from webpage" dialog box that says "Ignoring discovery interface failed", but no other details, and nothing apparent in the eventlog. I have seen that message before when an object has…
  • That's good enough for me. This must have been human error then. Thanks.
  • Yes we do have scheduled discoveries running but this doesn't correct it without intervention. If I discover and import the new vmxnet adapter, the VM will still show as warning with one NIC in an unknown state until I manually delete that old vmxnet adapter. 
  • To resolve the majority of our issues, we were instructed to disable the reverse DNS lookup in Orion (in web console | Settings | Polling Settings | uncheck Perform reverse DNS lookup | Submit). Most of our Windows hosts are using DHCP and the few that are still static are set to be changed this year. We too have had to…