Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

VI3 Host with Update 4 being listed under Net-SNMP Vendor

We have quite a few VI3 servers we are in the process of adding to Orion for monitoring. We recently upgraded one of them to Update 4 from VMWare. When we add that host to Orion it gets placed under the Net-SNMP vendor not VMWare, Inc. We have tried removing and re-adding it multiple times with no success. Has anyone else had this issue? Any fixes for this or is there a way to manually move the host to be listed as a VMWare, Inc. device not Net-SNMP?

Thanks,

Darrin

Find more posts tagged with

Accepted answers

bshopp

We are working on this. We are going to have to change how we gather that data and go through VMWare's API, so this is not a simple change that we can release quickly. Our plan is to have this updated support via API in the next release.

All comments

bshopp

Update 4 or do you mean ESX4 or vCenter4? If ESX4, the new version, this is a known issue. VMWare with ESX4 are no longer populating their MIB's which we use for pulling ESX data. There is a different thread here on thwack all about this topic if you are interested.

dwiens

No this is still VI3 or ESX3 just running Update 4. My server engineers are telling me this is like a service pack.

bshopp

Hmm, it sounds like they are not populating the MIB's properly anymore that we are using. Any chance you can do a MIB Walk of the device in question to verify?

dwiens

Sorry for the late response. I ran the MIB walk and the host that is being placed in Net-SNMP is not responding to any of the VMWARE MIBs (i.e. VMWARE-VMINFO-MIB 1.3.6.1.4.1.6876.2.3.1.3.0.0). I did hte MIB walk of a host with Update 3 (service pack 3 essentially) and it did respond to the VMWARE MIBs. I guess they (VMWare) did kill SNMP in update 4. Any updates on Solarwinds working with VMWare to get this resolved? I know VSphere (VI4 or whatever you want to call it) is having the same issues.