If your vSphere’s ESXi hosts are connected to storage via EMC’s powerpath, the convention methods of querying path info will not work. Basically, you will get zero results.
For example when you query the lun via MultipathInfo you may only see iSCSI luns listed (if you have them running), but not your datastores. Read the rest of this entry »
Getting the properties of a VM provisioned in vRA is not straight forward, you need to get those information from the IaaS Web server instead of from vRA
This site shows you how you can get to it.
I am not sure which version the author has, but in version 7.2 the properties are not so straight forward and they strangely don’t expand when exported to a JSON file. However let’s first deal with the NTLM authentication on IaaS Web via a Invoke-RestMethod call. Its actually very straight forward, but hard to find; simply speaking, you use get-credential to capture the windows credentials and input it with -credential parameter. Read the rest of this entry »
Whilst working on vRA REST API to provision new virtual machines, one of task was to get the template for that catalog item and fill in required values.
One of the values common to most templates is the datacenter_location value. By default it will be null. That is not a big deal if you don’t care which datacenter your VM is being provisioned to, but what if you want to specify a location?
... "_cluster": 1, "_hasChildren": false, "cpu": 1, "datacenter_location": null, ...
In this case the values should be as such
"_cluster": 1,
"_hasChildren": false,
"cpu": 1,
"datacenter_location": {
"classId": "Infrastructure.Compute.DataCenterLocations",
"id": "DC1"
},
This is how you can add the values into the JSON object (I am assuming that you already gotten the bearer token in the $vratoken variable) Read the rest of this entry »
As a second part from my previous post, I modified the script to run Central CLI. One thing to note, you need to add “accept”=”text/plain” into the header when running central CLI command or you will get 406 errors (sorry, I found this out in one of the blogs, but couldn’t give the proper credits).
Lastly the request returns a bunch of text and not XML or JSON.
As part of the daily checks for NSX, we need to ensure that the communication channel on all ESXi hosts are healthy.
The REST API for channel health is straight forward, just feed the list of host IDs into the API and query the hostConnStatus for the XML file. Read the rest of this entry »
Recently, some of the clusters were under memory pressure and we had to consider turning on TPS to elevate memory pressure. Now in an ideal setting, you never need to do that because upper management always makes intelligent decisions and ensures that new VM demands are always met with at least 80% capacity. Also TPS, no matter how effeciency, essentially takes up CPU cycles. Of course, back in the real world demand always excess the capacity you have. Read the rest of this entry »
Recently we found out that we had to reset the admin password due to it being locked and, I think, expired. VMware does have a KB on how to this can be done:
https://kb.vmware.com/s/article/2078313
However, what it fails to mention is that an additional step may be necessary
https://kb.vmware.com/s/article/2131633
Now, if you just reset the admin password, it will allow you to logon via SSH as admin to the appliance. However, if you try to logon as admin to the admin GUI interface, you may encounter incorrect user name/password error. This is corrected by performing the stops in the 2nd KB article.
