It has multiple ways of monitoring, including pings, SNMP, WMI, and so on. The user interfaces is pretty good, easy to get started.

There is a free download for up to 10 nodes.

https://www.paessler.com/

https://www.paessler.com/san-monitoring

FYI

just FYI, for monitoring I am a big fan of Paessler's PRTG.

--- kenw

Thank you, Yaroslav, for that most interesting answer. Yes, jumbo frames are now fully disabled, and no further issues since -- so far, anyway. This isn't a heavily loaded system. Fascinating that jumbos can cause such problems, but I have to say, not really surprising. I've never been a big fan of ...

Just by the way, I ran the Microsoft Failover Cluster Manager validation wizard on my network configuration, and it came up 100% fine. Is there any sort of validation we can run for the StarWind side, particularly the iSCSI aspect? OH! and it's worth noting, if you see an error occasionally in the l...

Thanks Yarislav. It's interesting that you should mention the jumbo frames. I did initially have a problem related to them months ago, when I replaced the network switch between the two servers, because I forgot to enable jumbo frames on the switch. Being an HP Procurve switch, it listed a lot of er...

Going through the event logs, I see a event ID 108 from MSiSCSI saying "Status 0x00001069 determining that the device interface <…> does not support iSCSI WMI interfaces. If this device is not an iSCSI HBA then this error can be ignored." Is this event relevant for StarWind iSCSI connectio...

There's been another sync failure: HV4 is reporting all channels down to HV3. That might be starting to be a pattern. The Microsoft Failover Cluster stayed up and one StarWind host stayed up, but it's reporting all connection lost to the other host -- again. The "failed" VSAN service is ta...

The logs are there, as described, one pair immediately after crash, one later. Yesterday things were looking stable so I got brave and tried manually triggering another Cluster Aware Update using the script from https://www.starwindsoftware.com/blog/whip-your-hyperconverged-failover-cluster-into-sha...

OK, I've removed SSD and RAM cache for both CSV and Witness devices on both hosts. That's a total of eight swdsk files that needed to have cache and storage sections removed. For what it's worth, those documents didn't specifically mention the *_HA files at all, but I figured they had to be done as ...

Here's an update. I'm still digging through event logs and such. It happened again this afternoon, very similar if not the exact same thing. One host (HV4)'s VSAN stayed up and synced, and the Failover Cluster stayed up, but the other host (HV3) lost virtually all iSCSI connectivity, and both its Wi...

Yaroslav, are there known conflicts or recommendations re: StarWind VSAN and Windows Backup on hosts? My VSAN went down abruptly (again), apparently right at the time a backup was scheduled to start. To be clear, I am NOT trying to backup VSAN images. The symptom was that all iSCSI channels -- both ...

Just a comment, it may seem trivial and obvious, but... I think it's really cool how the Microsoft Failover Cluster software continues to see all Cluster Shared Volume (CSV) volumes as up and running, and continues to host the cluster virtual machines up and running, even when one of the StarWind VS...

I made the link changes following your instructions. That worked very nicely, thank you! However, the zero percent synch readings didn't change afterward. I've vaguely wondering if that had to do with my shutting down both servers at the same time, triggering a full synch. OK, the failing hard drive...

Thank you VERY much for that excellent detailed analysis, Yaroslav! First, just so you know, the CSV storage on KMHV3 had already been identified as failing, and I have replacement storage sitting here waiting to be swapped in as soon as I have the cluster fully synchronized. I'm not sure why the CH...

That you for that checklist, Yaroslav. The documentation you suggested, https://www.starwindsoftware.com/resource-library/starwind-virtual-san-for-hyper-v-2-node-hyperconverged-scenario-with-windows-server-2016/ is impressive. It looks like a great deal of work went into it, and it covers much more ...