WilliamLam.com

Automating deployment of vSAN Data Protection OVA with PowerCLI

by // Leave a Comment

vSphere 8.0 Update 3 introduces a new vSAN Data Protection capability for the vSAN Express Storage Architecture (ESA) and it is currently delivered as a standalone VMware OVA (see Duncan's post in case you are wondering where to download) which, once deployed and configures, enables a new vSphere UI plugin as shown in screenshot below.


After going through the manual (vSphere UI) deployment workflow, which also included some non-traditional input like requiring the raw vCenter Server TLS certificate, I was interested in automating the deployment using PowerCLI.

[Read more...]

Quick Tip - Retrieving NSX segment information from vCenter Server

by // Leave a Comment

Since vSphere 7.0, it has been much simpler to correlate between an NSX network segment defined in NSX Manager and its representation as a vSphere Distributed Virtual Portgroup (DVG) in vCenter Server as demonstrated in screenshot below using the vSphere UI.


With the additional NSX information such as NSX Transport Zone ID, Transport Zone ID Name, Logical Switch ID, Segment Name and VNI (Virtual Network Identifier), users can streamline debugging and troubleshooting issues with their network team by quickly providing this relevant information.

I recently had a user ask about retrieving the VNI information for a given NSX segment in vCenter Server using PowerCLI, so here is a quick snippet including other NSX information for those interested.

[Read more...]

Minimum vSphere privileges to install or remove patch from ESXi

by // Leave a Comment

I recently got a question from our field inquiring about the minimum vSphere privileges that would be required to either install or remove a patch (VIB/Component) from an ESXi host. The customer was interested in using PowerCLI and specifically the ESXLI interface to automate the installation and removal of a VIB and wanted to create a custom vSphere Role with the minimum privileges, which can be done with vCenter Server or even a standalone ESXi host (properly licensed).

Since I was familiar with the underlying ESXi patch API that is used for these operations, a nice benefit of the vSphere API Reference is that it also lists the specific vSphere Privileges that is required for a given operation and in this case, it is just Host.Config.Patch privilege.

However, when the customer attempted to create a custom vSphere Role with just this privilege and perform the installation operation, they still received an error as shown in the screenshot below, which was a bit cryptic but they had assumed it was still permissions related as full administrative account had worked:

OperationStopped: Response status code does not indicate success: 500 (Internal Server Error)


[Read more...]