In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I will show you HOW TO: Correctly configure physical uplinks for teaming and failover on a VMware vSphere Distributed Switch vDS.
I created a video here, which shows you how to create a vDS for VMware vSphere.
In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I will show you HOW TO: Export and Backup the VMware vSphere Distributed Switch (vDS) configuration of a VMware vSphere Distributed Switch (vDS).
It is important once you have created a vDS to ensure you keep regular backups, if the need arises you need to restore vCenter Server.
I created a video here, which shows you how to create a vDS for VMware vSphere.
I will show you HOW TO: Increase the capacity of an existing VMware vSphere vSAN datastore by adding new storage devices.
The storage devices we are using in this VMware vSphere vSAN datastore are Intel Optane devices.
If you are creating a design for VMware vSphere vSAN for a Production environment, please ensure you read the VMware Cloud Foundation Design Guide 01 JUN 2023 – this should be regarded as The Bible!
In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I will show you HOW TO: Create a VMware vSphere vSAN using Intel Optane NVMe storage devices.
The storage devices we are using in this video are the Intel® Optane™ SSD DC P4800X Series 375GB, 2.5in PCIe x4, 3D XPoint™, but this procedure can be use to add any compatible storage devices in ESXi to a vSAN datastore.
This video follows on from the follow video in this series
If you are creating a design for VMware vSphere vSAN for a Production environment, please ensure you read the VMware Cloud Foundation Design Guide 01 JUN 2023 – this should be regarded as The Bible!
In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I will show you HOW TO: Create a VMware vSphere Distributed Switch (VDS) for use with VMware vSphere vSAN for the VMware vSphere vSAN Cluster.
VMware vSphere Distributed Switch (VDS) provides a centralized interface from which you can configure, monitor and administer virtual machine access switching for the entire data center. The VDS provides:
Simplified virtual machine network configuration
Enhanced network monitoring and troubleshooting capabilities
Support for advanced VMware vSphere networking features
As my 10GBe switch in this VMware vSphere Lab has LACP functionality I have decided to demonstrate how we configure the vDS for a LACP LAG. Link Aggregation Control Protocol (LACP) is one elements of an IEEE specification (802.3ad) that provides guidance on the practice of link aggregation for data connections, it’s used on trunks or port channels, to bond two ethernet ports together. It is only supported using a VMware vSphere Distributed Switch (VDS) , it is not supported on a VMware vSphere Standard Switch (VSS).
This video covers the following
Creation of the VMware vSphere Distributed Switch (VDS).
Creation of Portgroups with vLANs for Management, vMotion and vSAN.
Creation of the LACP LAG.
Adding vDS to hosts in the vSphere Cluster.
Migration of existing VMKernel portgroups from VSS to VDS.
Testing the VMware vSphere Distributed Switch (VDS).
If you are creating a design for VMware vSphere vSAN for a Production environment, please ensure you read the VMware Cloud Foundation Design Guide 01 JUN 2023 – this should be regarded as The Bible!
In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I will show you HOW TO: Remediate a vSphere Cluster VMware ESXi 7.0U3d to ESXi 7.0U3n including adding the DELL OEM Addon for ESXi 7.0.3 – A12 using VMware vSphere Lifecycle Manager (vLCM) from a single image
This video took over 7 hours to record to Remediate the vSphere Cluster, don’t worry in post we were able to reduce to approximately 35 minutes, the reasons were issues which we discuss as we troubleshoot the cluster, as we remediate the cluster.
Issues encountered, which we discuss and remedy throughout the video
Failed to vMotion – caused by incorrect network speed.
Failed to vMotion – caused by different generation CPU.
Failed to remediate a host – caused by incompatible VIBs.
Failed to remediate a host – caused by unknown error.
Server failed to boot – caused by failing ECC memory modules.
In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I will show you how to change the LBA sector size of storage media to make it compatible with VMware vSphere Hypervisor ESXi 7.0 and ESXi 8.0.
Only an LBA sector size of 512 bytes is compatible with VMware vSphere Hypervisor ESXi 7.0 and ESXi 8.0.
In this video we use an Intel® Optane™ SSD DC P4800X Series 375GB, 2.5in PCIe x4, 3D XPoint™, but this procedure can be use to change the LBA format of any storage media, SSD, HDD, NVMe
In this video presentation which is part of the Hancock’s VMware Half Hour HOW TO Video Series I explore two inexpensive 10Gbe network interfaces suitable for the #homelab for use with VMware vSphere vSAN.
In this video, I will show you how to perform a Physical to Virtual conversion of a Windows XP physical workstation computer to VMware vSphere Hypervisor 7.0 (ESXi 7.0) using VMware vCenter Converter Standalone 6.2.0.1 Build 8466193 not the latest bug fixed version VMware vCenter Converter Standalone 6.3 Build 20575345 from VMware.
I discuss the 0-day security issues found in VMware vCenter Converter Standalone 6.2.0.1 Build 8466193 which was the reason VMware “pulled” the download from their website on the 2 February 2022.
We have removed vCenter Converter from the list of VMware product downloads. This is a precautionary measure to protect our customers from using legacy technology that does not comply with VMware’s high standards for security and stability. We apologize for any inconvenience this may have caused.
Offering unsupported products based on legacy technology presents potential security and reliability risks to our customers. The last release of vCenter Converter occurred in May 2018, and its support officially ended in December 2019. While we understand some customers may want to use this tool, the risks reached a level where we had no choice but to remove it from the download site.
One of our top goals is to maintain the safety and stability of our customers’ workloads. As part of a technology’s evolution, we must consider the technical standards the customers must comply with. When a straightforward update cannot meet compliance requirements, the product needs to undergo a thorough rebuild. This is the case with vCenter Converter, whose functionality will be migrated to a modern platform based on a reliable technology stack.
Work on a renewed version of vCenter Converter is already in progress. Although we cannot commit to any specific timelines for its release, the updated tool will meet our high standards for security and stability, providing enhanced functionality and supporting the latest technologies available in vSphere virtual machines.
On the 11th October 2022 VMware released VMware vCenter Converter Standalone 6.3 Build 20575345, which has the security issue fixed.
I also demonstrate that VMware vCenter Converter Standalone 6.3 Build 20575345 seems to have an issue installing on a Windows XP Service Pack 3 computer unlike VMware vCenter Converter Standalone 6.2.0.1 Build . VMware does not support the installation of VMware vCenter Converter Standalone 6.3 Build 20575345 on legacy operating systems, that are no longer supported by the vendor.
You will have to assess the risk of using VMware vCenter Converter Standalone 6.2.0.1 Build 8466193 in your organisation, or use a different third party tool to create physical to virtual conversions.
The operating system used in this demonstration is Windows XP Professional, but the same procedure can be used for any Windows operating system.