After creating my VSAN Configuration Maximum query script I thought it would also be useful to create an equivalent set of VSAN vCheck Plugins. For those of you who have not heard of or used vCheck (pretty rare unless you do not use PowerShell/PowerCLI in your environment), it is a PowerShell reporting HTML framework created by Alan Renouf. vCheck allows you to schedule a series of PowerCLI scripts/checks against your vSphere environment and produces a daily report on the things you care most about such as datastore capacity being under a certain threshold or potential snapshots growing out of control in your environment.
Given this is the primary use case for vCheck, I figure it would make sense to implement these same set of VSAN configuration maximum checks in vCheck as well. This would also give me the opportunity to learn more about vCheck as I have never used it before. If you are new to vCheck, I highly recommend you check out Jonathan Medd's article on how to get started with vCheck here.
Here is a sample report of a real VSAN environment to get an idea of what the report could look like: VSAN-vCheck-Report.html
Below are the VSAN vCheck Plugins that I have created which also includes a bonus plugin which reports on the capacity of a VSAN Datastore. You can pick and choose the VSAN plugins that you want to use in your environment and then customize the threshold parameter for each report based on your requirements.
- 990 VSAN Capacity Report.ps1
- 991 VSAN Configuration Maximum Disk Group Per Host Report.ps1
- 992 VSAN Configuration Maximum Magnetic Disks Per Disk Group Report.ps1
- 993 VSAN Configuration Maximum Total Magnetic Disks In All Disk Groups Per Host Report.ps1
- 994 VSAN Configuration Maximum Component Per Host Report.ps1
- 995 VSAN Configuration Maximum Hosts Per Cluster Report.ps1
- 996 VSAN Configuration Maximum VMs Per Host Report.ps1
- 997 VSAN Configuration Maximum VMs Per Cluster Report.ps1
For those of you who are looking to evaluate VSAN in their environment, hopefully these VSAN vCheck reports will come in handy. If there are others that you feel that might be useful, feel free to leave a comment or contribute back to the vCheck project on Github.