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

Monitoring Hyper-V servers

We have only 2 servers running Hyper-V and I would like to monitor these but I believe to do this I have to poll the Nodes using WMI as opposed to SNMP, this presents a problem to me as I poll the hardware status of disks, memory chips, fans etc using SNMP UnDP's which aren't available to me if I change the node to WMI.

Has anyone else got this problem and if so what have they done about it, I am assuming I am going to have to add two nodes with the same IP address one being polled using SNMP and the other WMI, will this cause NPM/SAM any issues.

Any advice on the best way to still be able to monitor the hardware status of the server using SNMP and also be able to monitor Hyper-V would be appreciated.

Thanks in advance,

John

Find more posts tagged with

Accepted answers

All comments

LGarvin

I poll the hardware status of disks, memory chips, fans etc using SNMP UnDP's which aren't available to me if I change the node to WMI.

There are a couple of ways you can approach this.

You can define a second 'node' for that host (e.g. a second logical IP Address) and monitor one 'node' with SNMP for your UnDP and the other 'node' with WMI to get the Hyper-V stats.

Or, a better alternative for monitoring both hardware status and Hyper-V, if your hosts are HP, Dell, or IBM is to use SAM, which can do it all via WMI (no UnDP required).

9-10-2014 2-23-33 PM.png

vinay.by

I am assuming I am going to have to add two nodes with the same IP address one being polled using SNMP and the other WMI, will this cause NPM/SAM any issues.

If you want to go with a 2 node addition, you can add it to a different polling engine (additional poller) , as far as I understand it would not create an issue.

kreases

I have created a second node using the same IP address but on our secondary poller using SNMP although I am interested to know how you got the above hardware display using SAM as we do use HP servers. Currently I have UnDP's set up to return hardware status of various components and I have alerts set up to email us when the status changes if the above is possible with my servers I certainly could cut down on the UnDP's but I can't see a template in my SAM that gives me what you are showing.

mwb

Please vote on this feature request to allow users to mix polling options so we're not forced to choose between SNMP hardware details and WMI asset and disk information:

https://thwack.solarwinds.com/ideas/2836