Archive for the ‘VMware vSphere 6.7’ Category

VMware vSphere – how to check NVMe Drives Total Bytes Written (TBW) with PowerCLI

Montag, März 16th, 2020

A maximum Total Bytes Written (TBW) guarantee is typically provided by the vendor in their specifications this value describes how data can be written to the entire device until the warranty expires and the current value can be checked with S.M.A.R.T.

 

Connect to the ESXi Host with SSH Identify NVMe drives

# esxcli nvme device list
HBA Name Status Signature
——– —— ———————
vmhba0 Online nvmeMgmt-nvme00610000

Get the „Data Units Written“ counter

# esxcli nvme device log smart get -A vmhba0 |grep Written
Data Units Written: 0xe1c78d

The counter is hexadecimal and convert it to decimal this can be done also from the command line

# printf „%d\n“ 0xe1c78d
14796685

VMware vSphere 6.7 – USB Network Native Driver

Montag, Februar 24th, 2020

USB Network Native Driver – the ASIX USB 2.0 gigabit network ASIX88178a, ASIX USB 3.0 gigabit network ASIX88179, Realtek USB 3.0 gigabit network RTL8152/RTL8153 and Aquantia AQC111U

VMware vSphere 6.7 – a NUMA deep dive

Samstag, Februar 22nd, 2020

VMware vSphere 6.7 – Virtual Machine vCPU and vNUMA Rightsizing

Samstag, Februar 22nd, 2020

VMware vSphere 6.7 – larger and more demanding workloads like databases on top of the latest generations of processors with up to 24 cores special care must be taken in vCPU and vNUMA configuration to ensure performance is optimized

This table outlines how a virtual machine should be configured on a dual socket 10 core physical host to ensure an optimal vNUMA topology and performance regardless of vSphere version where the assigned memory is less than or equal to a pNUMA node

This table outlines how a virtual machine should be configured on a dual socket 10 core physical host to ensure an optimal vNUMA topology and performance regardless of vSphere version where the assigned memory is greater than that of a pNUMA node

Nvidia Tesla P4 GPU – designed to optimize complex graphics operations and enable them to run at high performance without overloading the CPU

Mittwoch, Februar 19th, 2020

VMware vSphere 6.7 – Client IP Pools

Samstag, Februar 8th, 2020

VMware vSphere 6.7 – Client IP Pools

VMware vSphere 6.7 – if a CPU has more than 32 cores a additional CPU licenses will be required

Freitag, Februar 7th, 2020

Update to VMware’s per-CPU Pricing Model

VMware vSphere ESXi – host displays an error and fails to boot when two ESXi installations are on the same system

Donnerstag, Januar 23rd, 2020

VMware vSphere ESXi – host displays an error and fails to boot when two ESXi installations are on the same system

VMware Lifecycle Product Matrix – Supported Products, as of January 1, 2020

Samstag, Januar 4th, 2020

VMware vSphere ESXi – remote install using SuperMicro IPMI

Samstag, Januar 4th, 2020

VMware vSphere ESXi – a really nice SuperMicro IPMI feature that allows out-of-band (OOB) management of your server. Accessing the IPMI interface is simple by using a browser to browse out to the IP address you see during POST

VMware vSphere vSAN 6.7 P01 – Storage migration of an Oracle RAC with no remediation required for shared disks anymore

Sonntag, Dezember 15th, 2019

VMware vSphere vSAN 6.7 P01 – by default in a VM the simultaneous multi-writer “protection” is enabled for all. No More Eager Zero Thick (EZT) requirement for Oracle RAC multi-writer disks starting VMware vSAN 6.7 P01 (ESXi 6.7 Patch Release ESXi670-201912001)

VMware vSphere ESXi Hypervisor 6.7 – Limitations and Features

Montag, November 25th, 2019
  • No vCenter integration or clustering
  • No backups from third-party backup solution
  • Maximum of 8 vCPUs for VMs running on ESXi 6.7 free
  • Maximum of 2 CPUs in your physical ESXi host
  • Maximum RAM 12TB
  • No VMware Support

VMware vSphere ESXi Hypervisor 6.7 – USB Network Native Driver for ESXi

Sonntag, November 10th, 2019

USB Network Native Driver for ESXi

VMware vSphere 6.7 – the ultimate guide to convert RDM to VMDK

Donnerstag, Oktober 31st, 2019

The ultimate guide to convert RDM to VMDK – you can use the Advanced option in Storage vMotion ->Change the disk format as “Thin or Thick” from the disk format drop down for the RDM disk, select the destination datastore and proceed with the storage vMotion. Once storage vMotion is completed, virtual RDM disk will be converted to VMDK

VMware vSphere 6.7 – cannot import *OVF file from vCenter 6.7 to 6.5

Mittwoch, Oktober 30th, 2019

Cannot import *OVF file from vCenter 6.7 to 6.5

 

Export the VM from 6.7 as normal

Machen Sie eine Sicherungskopie der *.ovf Datei
Editieren sie die *.ovf Datei und entfernen sie bitte folgende Einträge:

<File ovf:id=“file3″ ovf:href=“<VM Name>.nvram“ ovf:size=“8684″/>
<vmw:Config ovf:required=“false“ vmw:key=“flags.vbsEnabled“ vmw:value=“false“/>
<vmw:Config ovf:required=“false“ vmw:key=“flags.vvtdEnabled“ vmw:value=“false“/>
<vmw:Config ovf:required=“false“ vmw:key=“bootOptions.efiSecureBootEnabled“ vmw:value=“false“/>
<vmw:ExtraConfig ovf:required=“false“ vmw:key=“nvram“ vmw:value=“ovf:/file/file3″/>

Speichern Sie die *.ovf Datei ab
Der Import sollte nun Fehlerfrei durchlaufen