VMware PowerCLI Blog
It was the bane of my existence at one time. The priority one ticket, all the VM guest on a particular Datastore have paused themselves. What could it be, how could this have happened? It was always the same cause at one of my clients. They did not have very large Datastore sizes and some Tech had created a SnapShot three months ago and forgot all about it. Sure enough the delta file had grown to a size that consumed all the free space on the Datastore.
It never seemed to sink in, no matter how many times I sent out the reminder email for proper SnapShot edict. Someone would forget and I would find forgotten machine SnapShots. So this script was born to police them so to speak. It rolls through all the vCenter names you place in the “$vcenters” variable and hunts down existing SnapShots. It generates a warning email and a CSV report based on the “$limit” variable.
In the script you will also see in the “IF” statement that triggers an alert it also checks to see if the Datastore has “SRM” in its name. My client at the time was placing “SRM” in the name’s of all their replicated Datastores. SnapShots for us on replicated Datastores where not permitted without
This script is an oldie for me. It is one of the first PowerCli scripts I put into production. The script takes vCenter names which are placed in the $vcenter variable at the top of the script. It proceeds to loop through each one of the vCenters and build up information on each one of the powered on guest it finds. There are decent amount of data points for each of the guest. The report is widely used at my current gig so I believe it can be handy to have.
Get Cluster HBA Info
This is really just a one liner to grab the WWN of the Host Bus Adapters on a vSphere cluster group. First off if you copy and past this make sure no line breaks come over it is all one line. Your also not going to be able just run this bad boy on your PowerCli session. At the very begging of the command where it says "Your-Cluster-Name" your going to have to plug in your own cluster name. If you leave the export-csv cmdlet on the end of the command you might want to cahnge the ".csv" output file name. I wrote this a long time ago and I only used it in a Fiber based environment so your mileage may vary. Take the export-csv off the command and let it dump out to the terminal. This way you can tweak what you are getting if you do want to eventually add a file based output at the end. It always help me when my buddies on the storage team would ask me to confirm the WWN on their management software. Apparently on the solution they were using for fabric management they had to manual enter this information. :(