Hi I am using your product on the unlimited demo at the moment (very good product by the way), and need to ask a question.

I have a 4 node Hyper-V cluster on windows 2008 r2 which shuffles the Hyper-V VM's around when a node fails.

My question is:

Is it better to not monitor the cluster itself and monitor the health of the nodes and monitor the virtual servers individually?

Many Thanks,

Paul

Article Comments

If you monitor the cluster IP, then if one of the nodes goes down, the sensors monitoring things like services on the cluster will continue to be monitored so in this way, monitoring the cluster is helpful. The problem arises when VM's move hosts, the VM ID that the sensor uses will change and the sensors won't work any longer. Ideally, monitoring them through an SCVMM server would be best since through it the IDs don't change but if this isn't possible then monitoring the hosts directly would also work.


Mar, 2014 - Permalink

PRTG now supports monitoring of Virtual Machines which were moved by Live Migration. Use the Hyper-V Virtual Machine Sensor with the System Center Virtual Machine Manager (SCVMM) as parent device and the monitoring will continue after the VM changed the physical host.

Do also have a look at our manual for further information.


Aug, 2014 - Permalink

Hi,

So what do you do if you only have a standard windows failover cluster with 2 or 3 nodes and where SCVVM or SCCOM is not being used?

Thanks.


Apr, 2015 - Permalink

Hi,

I'm afraid that installing a virtual machine with the SCVMM in order to monitor the cluster status is the only native possibility with PRTG at the moment. Otherwise, you would need to write a custom sensor. Please have a look here for the documentation:

Setup > PRTG API > Custom Sensor

Best regards


Apr, 2015 - Permalink