MC1903's Posts

Hi, I would like to run the vCert.sh tool on a vCenter Server that I care about, but I would like to confirm that the download has not been tainted first; as I was pointed to the file on a non-VMware site. Would anyone in GSS be able to confirm the official SHA256 hash for vCenter 7.0 Certificate Management Utility (4.7.0) vCert.sh file? #!/bin/bash #------------------------------ # Script to manage vCenter SSL certificates. # # Author: [REDACTED] #------------------------------ #------------------------------ # for debugging purposes only, uncomment the following line: # export PS4='+[${SECONDS}s][${BASH_SOURCE}:${LINENO}]: ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'; set -x; # to debug run: ./vCert 2>vCert-debug.txt #------------------------------ VERSION="4.7.0" #------------------------------   I would be most grateful. Cheers, M  

I managed to accidently power down one of my management domain ESXi hosts and realised that SDDC Manager does not report this as an issue? Should it? The only 'tell' I can find in SDDC Manager is the 0% CPU & 0% Memory usage. Hardly ideal.        

Hi, I am trying to complete a Add VI Workload Domain (vSAN) in my Lab with 4 nested ESXi Hosts and I am getting stopped at the subtask "Validate vSAN disks for ESXi Host(s)" with this error: Description Validate vSAN disks for ESXi Host(s) Progress Messages vSAN Disks Validation on the ESXi Host(s) failed: ESXi Host vcf01-m01-esx05.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one), ESXi Host vcf01-m01-esx06.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one), ESXi Host vcf01-m01-esx07.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one), ESXi Host vcf01-m01-esx08.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one) Error Message: vSAN Disks Validation on the ESXi Host(s) failed: ESXi Host vcf01-m01-esx05.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one), ESXi Host vcf01-m01-esx06.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one), ESXi Host vcf01-m01-esx07.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one), ESXi Host vcf01-m01-esx08.vcf.momusconsulting.com does not have valid boot disk (Expecting at least one) Remediation Message: Make sure that ESXi Hosts disks are eligible for use by vSAN Reference Token: BJ47Q8 Cause:   SDDC Manager Version: 4.5.0 ESXi Version: 7.0.3-20328353   My nested ESXi hosts are booted and thus have valid boot disks, so I am lost as to why this error is being kicked out. Each host has 4 disks. 1 x 12GB boot disk, 1 x 100Gb vSAN Cache disk & 2 x 250Gb vSAN Capacity disks. The vSAN capacity disks have been tagged as IsCapacityFlash =1. I have tried manually creating the /store/.capacityflash.json files on each host, as per https://kb.vmware.com/s/article/52586    [root@vcf01-m01-esx05:/vmfs/volumes/631a0f8a-7e2b33b5-a1fb-005056a94fe1/store] vdq -q > /store/.capacityflash.json [root@vcf01-m01-esx05:/vmfs/volumes/631a0f8a-7e2b33b5-a1fb-005056a94fe1/store] cat /store/.capacityflash.json [ { "Name" : "naa.6000c29580337e490eeef16ca096f84c", "VSANUUID" : "", "State" : "Ineligible for use by VSAN", "Reason" : "Has partitions", "IsSSD" : "1", "IsCapacityFlash": "0", "IsPDL" : "0", "Size(MB)" : "12288", "FormatType" : "512n", "IsVsanDirectDisk" : "0" }, { "Name" : "naa.6000c290d6ff5b9c627918f381ab94f0", "VSANUUID" : "", "State" : "Eligible for use by VSAN", "Reason" : "None", "IsSSD" : "1", "IsCapacityFlash": "1", "IsPDL" : "0", "Size(MB)" : "256000", "FormatType" : "512n", "IsVsanDirectDisk" : "0" }, { "Name" : "naa.6000c29dc55120c5120f4ea2b0819a08", "VSANUUID" : "", "State" : "Eligible for use by VSAN", "Reason" : "None", "IsSSD" : "1", "IsCapacityFlash": "1", "IsPDL" : "0", "Size(MB)" : "256000", "FormatType" : "512n", "IsVsanDirectDisk" : "0" }, { "Name" : "naa.6000c292c78fe2a69bd08fafb498c4c6", "VSANUUID" : "", "State" : "Eligible for use by VSAN", "Reason" : "None", "IsSSD" : "1", "IsCapacityFlash": "0", "IsPDL" : "0", "Size(MB)" : "102400", "FormatType" : "512n", "IsVsanDirectDisk" : "0" } ] [root@vcf01-m01-esx05:/vmfs/volumes/631a0f8a-7e2b33b5-a1fb-005056a94fe1/store]   Additionally; what is the Reference Token: BJ47Q8 referring to? Is there a lookup / log I can correlate? Any help or suggestions very much welcomed. Cheers, M  

I am trying to stand up a nested ESXi 6.x host with the date purposely about 2 years earlier than today. I have disabled/unchecked the VM options "sync time periodically" and the 4 "run VMware Tools scripts" options. I booted the VM to BIOS and reset the date back to where I wanted. Booting the ESXi installer initially shows the 'wrong' date, until just at the end, when 'Jumpstart plugin vmtoolsd activated" is executed and it syncs the current time/date with my physical host. Is there a simple way of stopping this happening? Is there an ESXi 6.x installer without the VMtools packages pre-installed - I can't see one to download? Is there any way to remove the VMtools packages from the ISO and re-package it? Any thoughts/pointers will be appreciated. Cheers, M

Hi, I am upgrading a test vRA 3-node cluster from 8.6.0 to 8.6.1, using vRSLCM, and I have noticed that the health checks from my load balancer to each individual backend node on http://{node-fqdn}:8008/health still receive 'HTTP/1.1 200 OK' when the underlying vRA site on https://{node-fqdn}/ is actually offline. Eventually the health checks do fail and the load balancer marks the node as down, but before the upgrade on that node has completed, they start to respond 200/OK again. This happens several times during the upgrade process.  It doesn't make any sense to me. If the node is down for upgrade I would expect the health check to consistently respond with something other than 200/OK, so the load balancer stops sending traffic to it. This is my first vRA cluster upgrade experience - is this usual? Cheers, M