Author: Michael Schroeder

Posted on

Remediate vSAN Policy ‘Out of Date’

Every object in vSAN (OSA) has an assigned storage policy. If no custom policies have been defined, objects are assigned the factory-installed vSAN default policy. Compliance of the selected policy with the current state is checked regularly. If the object is compliant with the assignes policy, the compliance status is set to ‘Compliant’.

However, it can happen that several objects in the cluster show the compliance status ‘Out of Date’. This will be shown in Skyline Health as an informative note. In the example below, several VMs with their vDisks were out of date.

Remediation in vSphere-Client

If there is only one or very few objects, the affected VM can be highlighted in Skyline Health. By doing so, we switch to the context of this VM and we can see details about namespace-object (VM Home) or the vDisks under Configuration > Policies. In the dialog (image below) we can select the object and click on ‘Reapply VM Storage Policy’. Usually this is enough to bring all objects of the VM back to the ‘Compliant’ state.

Continue reading “Remediate vSAN Policy ‘Out of Date’”
Posted on

Remove an unknown Disk from a vSAN Cluster

A failed capacity disk was removed from a vSAN 7 cluster before it could be logically detached from the disk group. The result is a remaining unknown disk device in the disk group that cannot be removed in the vSphere Client.

In such cases, esxcli is sometimes the more powerful tool.

We need to connect by SSH to the affected vSAN host.

Collect Information

Let’s check all registred disk devices on the node.

esxcli vsan storage list

A detailed list of all cache and capacity devices of this host will be displayed.

Output of disk devices (shortened)

Among the 24 active disks was the unknown zombie device. The only remaining feature was the vSAN UUID. The UUID can be used to detach the device from the configuration.

Remains of a physically removed disk in the vSAN configuration.

Extraction

The UUID of the missing unknown device was “52b17786-183b-e85f-f7f3-4befb19f67b0”. Using this information, we can remove it from the configuration.

esxcli vsan storage remove --uuid 52b17786-183b-e85f-f7f3-4befb19f67b0

The process takes a few seconds. Checking again with the esxcli vsan storage list command showed that the device was removed.

Posted on

vExpert 2023 – Subprogram Nominations

VMware annually grants the vExpert award to individuals who have made a special contribution to the VMware community. This can be either through publications, presentations, blogs, or work in the VMware User Group (VMUG). I am pleased to be part of the vExpert community for the seventh year in a row in 2023.

In addition to the common vExpert, there are subprograms for specialized application branches.

I applied for the three sub-programs vExpertPro, Application-Modernization and Multi-Cloud and was accepted in all three categories.

vExpertPro

The mission of the vExpert PRO program is to create a global network of vExperts willing to find new vExperts in their local communities, support them, and mentor them on their way to becoming vExperts.

For this purpose, vExpertPro exist in many regions of the world. I have been a member of this group since 2021 myself and have been confirmed for another year.

vExpert Multi-Cloud

The multi-cloud area covers large parts of the VMware Compute portfolio. The term cloud includes not only the public cloud, but also local data centers (private cloud) and combinations of both approaches (hybrid cloud). This includes numerous products such as vSphere, vSAN, VMware Cloud Foundation (VCF), Aria, VMware Cloud on AWS, Site Recovery Manager (SRM) or vCloud Director (VCD).

I submitted my first application for this relatively new vExpert path in 2023 and was accepted. Many thanks to the business unit for the decision.

vExpert Application Modernization

Application Modernization is all about Tanzu and Kubernetes, as well as the ecosystem around these technologies. The background was described in great detail by Keith Lee in his article “Announcing the VMware Application Modernization vExpert Program 2023“.

Posted on

Update Tanzu Workload Management

This is a brief guide on how to upgrade Tanzu Workload Management within the vSphere cluster.

Kubernetes Release and Patch Cycles

Kubernetes versions are specified as x.y.z following Semantic Versioning terminology, where x is the major version, y is the minor version, and z is the patch version. For example, v1.22.6 denotes a minor version 22 with patch level 6. Minor versions are released approximately every 3-4 months. In the meantime, there are several patches within the minor version.

The Kubernetes project maintains release branches for the last three minor versions (1.24, 1.23, 1.22). Since Kubernetes 1.19, newer versions receive patch support for about a year. So keeping the Kubernetes versions in Tanzu up to date is highly recommended.

Step 1 – Update vCenter

This step is not mandatory, but recommended. Updates on vCenter are often accompanied by a new Kubernetes versions. You can see notifications about updates in the vSphere Client.

Continue reading “Update Tanzu Workload Management”