havox

Comments

  • I have opened a case as well referencing yours. Case ID #1091601. Thanks, Jon
  • This was for the vCenter appliance. I did get this fixed by upgrading VMAN to 7.0 and NPM to 12.0.1. Thanks, Jon
  • How do you enable x/y mode? Is that somewhere in the recorder interface? Sorry, I don't have a ton of experience with WPM. -Jon
  • BTW, I am using WPM 2.2.1.
  • Thanks for all the suggestions. After opening a case with VMware, it looks like the snmpd won't start on the vCenter appliance. I have tried it on the standard port 161 and unused ports as well (51000). VMware still has the case and are trying to figure out why. I will update once I get an answer so no one else has to beat…
  • No firewalls. They are both in the same subnet as well.
  • Found it. Add the new group called DC1 and then change the "Show Only" field to Groups on the Add Orion Objects to your New Group screen.
  • Opened a case with Solarwinds support and the problem was that we are using custom incident tables in our Servicenow implementation. Solarwinds is only capable of pointing to the default tables. This is per Solarwinds development, so I guess I have to get our development group to create some scripts to bypass this.
  • We had the same issue when trying to monitor our vCloud environment. I wanted alerts from the ESX hosts themselves, but not VMs running on those hosts. We had a Solarwinds service account that had read-only access to the vCenter, the Data Center, and the ESX hosts only. The service account has permissions to the objects…
  • The new VMware appliance is Linux-based, so does that change the way NPM behaves?
  • We were doing something similar with a VPN that we wanted to make sure that it was up all the time. We setup the UDP using the cikeTunRemoteValue OID (1.3.6.1.4.1.9.9.171.1.2.3.1.7) to grab the IP addresses on the far end of the tunnel. The MIB Value Type is Raw Value and the SNMP Get Type is GET TABLE. We only cared about…
  • Yep, "VMs with Bad Tools" under Reporting in your Orion Console. You can also do it if you are using VMAN.
  • It looks like Panduit MIBs are not in the Solarwinds MIB database. The OID is 1.3.6.1.4.1.19536.
  • I was able to the Emerson PDUs reporting on current utilization relative to the over current alarm threshold. I used OID 1.3.6.1.4.1.476.1.42.3.8.30.40.1.39. I am still working on APC ATS and Panduit PDUs.