The vRealize Production Test Tool was released in April this year to allow people to do health checks on their vRealize Automation, vRealize Business and vRealize Operations solutions to ensure your environments are running as planned and the most important part to me, being able to quickly prove the environment is working to your customer/consumers.
The tool is free and has been updated to version 1.2 at the time of this posting. Once once you have downloaded the tool you need to browse to the location where you saved the tool via command prompt and run the config command on the tool like the example below.
You accept the EULA after of course reading every single word and promising your first-born child and then get to the configuration UI.
Click on either vRealize Automation, Operations or Business on the left hand side and start filling in all your information.
If you have selected the vRealize Automation option and have your vRA portal load balanced then ensure the vRA URL is the VIP URL of your load balancers. The rest of the information is fairly straight forward.
For the endpoints I clicked the add button a few times to add additional fields so that I could enter not just my vCenter endpoints but also my vRO and NSX endpoints.
For the vRA Tenant name above go to https://your-vra-instance.com/vcac and check the name under your tenants tab and put in the exact name including the case.
Now save the configuration and close the UI. Now you can run the tool via command prompt by running the java -jar vrealize-productiontest-1.2.0.jar run –oobList VRA command like the example below.
Open up the configuration UI again by running the config command as shown below
For vRealize Business click the option on the left and fill in the required information. The vRA tenant name can be retrieved via the method mentioned above in the vRA section ensuring the case sensitivity is maintained.
Once complete save the configuration and close the UI
Now you can run the test via command including the VRB acronym at the end to run the vRB test.
Once it completes running it will give you the number of tests runs and most importantly how many failures you may have.
You can then see the output of the report under the folder you ran the tool from /report/VRPTReport.html and it gives you a brilliant break down of the tests and where you may have had failures. The remediation and cause fields are URLs to VMware KB articles to fix the issues. In my lab I have three failures as you can see in the screenshot below.
I haven’t gone through the vROPs setup but it follows very much the same method as the vRA and vRB sections. I really like the tool although it isn’t perfect for enterprise distributed installations and I had quite a few hassles with the vRA tool working but it is good and coupled with the vRA management pack for vROPs it gives brilliant reporting of your environment.