All,
I'm trying to upgade a 2 host cluster from 6.5 to 6.7U3. But remediation fails in early stage. The messaage is
"Could not stage image profile '(Updated) HPE-ESXi-6.7.0-Update3-iso-Gen9plus-670.U3.10.5.0.48': ('MSCC_bootbank_smartpqi_1.0.4.3008-1OEM.670.0.0.8169922', 'Could not find a trusted signer.')"
What does that actually mean and how to correct the issue?
These are HP DL380G9 -servers.
When upgrading our ESXi Mellanox, HBA300 and NVMe firmware, we want to be sure that the upgrade is on VMwares compatibility list.
To upgrade firmware we use Dell Open Manager. We start upgrading NVMe firmware.
Dell open manager will install version 1.1.2.
Vsan health says that it is not on the Compatibility list. It says that version 1.1.1. should be installed.
When I check her:
https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=43428&vcl=true
It says that only version 1.0.4 is compatible with ESXi 6.7.U2.
I am totally confused??
I would like to hear how other ensure that when they upgrade firmware, that it all is on the compatibility list??
Dear all,
After some work I was able to put together an automated ESXi deployment with WDS (in my lab, all nested VMs).
After pure "deployment", I wanted to add automatically the hosts to a lab vCenter. So I use the excellent script that can be found here.
This script join all hosts to my vcenter successfully but it adds them with the IP address, which is expected.
But I don't like that and I would like to add the hosts with their DNS name as William Lam did here previously.
So I added the part in bold, but it doesn't work... And worst : I don't know where to find the logs nor tell if the syntax is ok.
Can you give me some help please ? Thanks in advance
The script :
import sys,re,os,urllib,base64,syslog,socket
import urllib.request as request
import ssl
# used for unverified SSL/TLS certs. Insecure, not good for public.
ssl._create_default_https_context = ssl._create_unverified_context
## Variables that need to be filled out for different environments ##
# URL of vcenter, just the IP address
vcenter = "vcenterfqdn"
# Data center
#cluster = "<datacenter>/host/<cluster>"
cluster = "DatacenterName/host/ClusterName"
# vCenter credentials
user = "account"
password = "password"
# host ESXi credentials
host_username = "root"
host_password = "password"
url = "https://" + vcenter + "/mob/?moid=SearchIndex&method=findByInventoryPath"
passman = request.HTTPPasswordMgrWithDefaultRealm()
passman.add_password(None,url, user, password)
authhandler = request.HTTPBasicAuthHandler(passman)
opener = request.build_opener(authhandler)
request.install_opener(opener)
#cont = ssl._create_unverified_context()
#ssl._create_default_https_context = ssl._create_unverified_context()
req = request.Request(url)
#cont = ssl._create_unverified_context()
#page = request.urlopen(req, context=context)
page = request.urlopen(req)
page_content = page.read().decode('utf-8')
#print(page_content)
reg = re.compile('name="vmware-session-nonce" type="hidden" value="?([^\s^"]+)"')
nonce = reg.search(page_content).group(1)
headers = page.info()
cookie = headers.get("Set-Cookie")
params = {'vmware-session-nonce':nonce,'inventoryPath':cluster}
e_params = urllib.parse.urlencode(params)
#print(e_params)
bin_data = e_params.encode('utf8')
req = request.Request(url, bin_data, headers={"Cookie":cookie})
page = request.urlopen(req)
page_content = page.read().decode('utf-8')
#print(page_content)
clusterMoRef = re.search('domain-c[0-9]*',page_content)
if clusterMoRef:
print("Found cluster: " + cluster)
else:
opener.close()
sys.exit(1)
# cert stuff
cmd = "openssl x509 -sha1 -in /etc/vmware/ssl/rui.crt -noout -fingerprint"
tmp = os.popen(cmd)
tmp_sha1 = tmp.readline()
tmp.close()
s1 = re.split('=',tmp_sha1)
s2 = s1[1]
s3 = re.split('\n', s2)
sha1 = s3[0]
if sha1:
print("Hash: ", sha1)
else:
opener.close()
sys.exit(1)
xml = '<spec xsi:type="HostConnectSpec"><hostName>%hostname</hostName><sslThumbprint>%sha</sslThumbprint><userName>%user</userName><password>%pass</password><force>1</force></spec>'
# Code to extract IP Address to perform DNS lookup to add FQDN to vCenter
hostip = socket.gethostbyname(socket.gethostname())
if hostip:
print("IP address of host: ", hostip.strip())
else:
opener.close()
sys.exit(1)
try:
host = socket.getnameinfo((hostip, 0), 0)[0]
except IOError, e:
print("Failed to perform DNS lookup for " + hostip.strip())
sys.exit(1)
else:
print("Successfully performed DNS lookup for " + hostip.strip() + ' is ' + host)
sys.exit(0)
# could add logic to do DNS lookup, but no dns in our environment.
xml = xml.replace("%hostname",host)
xml = xml.replace("%sha",sha1)
xml = xml.replace("%user",host_username)
xml = xml.replace("%pass",host_password)
print(xml)
# now join to vcenter cluster
try:
url = "https://" + vcenter + "/mob/?moid=" + clusterMoRef.group() + "&method=addHost"
params = {'vmware-session-nonce':nonce,'spec':xml,'asConnected':'1','resourcePool':'','license':''}
e_params = urllib.parse.urlencode(params)
bin_data = e_params.encode('utf8')
req = request.Request(url, bin_data, headers={"Cookie":cookie})
page = request.urlopen(req).read()
except IOError as e:
opener.close()
print("Couldn't join cluster", e)
sys.exit(1)
else:
print("Joined vcenter cluster!")
url = "https://" + vcenter + "/mob/?moid=SessionManager&method=logout"
params = {'vmware-session-nonce':nonce}
e_params = urllib.parse.urlencode(params)
bin_data = e_params.encode('utf8')
req = request.Request(url, bin_data, headers={"Cookie":cookie})
page = request.urlopen(req).read()
sys.exit(0)
"The appliance cannot be used or prepared because a failure was encountered. An error occurred while starting service 'vpxd-svcs'.
I have created a domain controller, and given VCSA a DNS record within said DC. After stage 1, I am not able to proceed with stage 2 because of this issue. I am also unable to access any log output because it's all in Chinese-looking gibberish. I have also put in a reverse lookup zone. I have talked with the networkers and they have said the IPs for VCSA, the management laptop, and our hosts were all correct. Is there anything I am missing?
After a fresh installation, it will generate about 120G of virtual flash in the system disk.Partition table appears as VMFSL.Can I turn it off?
Because I only have one hard disk, the virtual flash caused me poor and poor space.
Im trying to install on a blank VM. I have the bootable usb with the os plugged into it but cant boot off or install. Any ideas?
Hi,
Preparing to upgrade my 6.5 environments to 6.7 U2 and have a question relating to the 6.7 U2 announcements regarding the depreciation of an external PSC.
My existing 6.5 environment consists of 2 clusters each managed by their own VCSA's connecting to a single PSC providing a single sign-on domain for both VCSA's. I am having trouble finding anything that will show me what my architecture would look like after 6.7 U2. I am aware I could still use the same architecture with 6.7, but I will have to deal with this sooner or later so I might as well deal with it now.
Thanks
Hi all,
I post here due to the slow response time of our case with VMWare. I had to roll back (power back on and rejoin to AD) our Windows vCenter server 6 since this migration did not work. I thought I had a smooth upgrade going after I found out I had to add our vmware service account the Replace a Process Level Token privelage in windows. Once I fixed that minor thing the migration assistant worked well.
The VCSA deployed, powered off the Windows vCenter machine, the new one joined to AD and then eventually after some time it gave an error.
Analytics Service registration with Component Manager failed. I downloaded a log file and inside the log package more details of the error is found in this file /var/log/firstboot/analytics_firstboot.py_14589_stderr.log
2020-04-13T16:28:06.223Z Failed to register Analytics Service with Component Manager: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:719)
2020-04-13T16:28:06.231Z Traceback (most recent call last):
File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 214, in register_with_cm
cloudvm_sso_cm_register(keystore, cisreg_spec, key_alias, dyn_vars, isPatch=is_patch)
File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 706, in cloudvm_sso_cm_register
serviceId = do_lsauthz_operation(cisreg_opts_dict)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 997, in do_lsauthz_operation
ls_obj = LookupServiceClient(ls_url, retry_count=60)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 307, in __init__
self._init_service_content()
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 287, in do_retry
return req_method(self, *args, **kargs)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 297, in _init_service_content
self.service_content = si.RetrieveServiceContent()
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 557, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 363, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1385, in InvokeMethod
conn.request('POST', self.path, req, headers)
File "/usr/lib/python3.5/http/client.py", line 1123, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python3.5/http/client.py", line 1168, in _send_request
self.endheaders(body)
File "/usr/lib/python3.5/http/client.py", line 1119, in endheaders
self._send_output(message_body)
File "/usr/lib/python3.5/http/client.py", line 944, in _send_output
self.send(msg)
File "/usr/lib/python3.5/http/client.py", line 887, in send
self.connect()
File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1032, in connect
six.moves.http_client.HTTPSConnection.connect(self)
File "/usr/lib/python3.5/http/client.py", line 1277, in connect
server_hostname=server_hostname)
File "/usr/lib/python3.5/ssl.py", line 385, in wrap_socket
_context=self)
File "/usr/lib/python3.5/ssl.py", line 760, in __init__
self.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 996, in do_handshake
self._sslobj.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 641, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:719)
2020-04-13T16:28:06.233Z Exception: Traceback (most recent call last):
File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 214, in register_with_cm
cloudvm_sso_cm_register(keystore, cisreg_spec, key_alias, dyn_vars, isPatch=is_patch)
File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 706, in cloudvm_sso_cm_register
serviceId = do_lsauthz_operation(cisreg_opts_dict)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 997, in do_lsauthz_operation
ls_obj = LookupServiceClient(ls_url, retry_count=60)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 307, in __init__
self._init_service_content()
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 287, in do_retry
return req_method(self, *args, **kargs)
File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 297, in _init_service_content
self.service_content = si.RetrieveServiceContent()
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 557, in <lambda>
self.f(*(self.args + (obj,) + args), **kwargs)
File "/usr/lib/vmware/site-packages/pyVmomi/VmomiSupport.py", line 363, in _InvokeMethod
return self._stub.InvokeMethod(self, info, args)
File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1385, in InvokeMethod
conn.request('POST', self.path, req, headers)
File "/usr/lib/python3.5/http/client.py", line 1123, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python3.5/http/client.py", line 1168, in _send_request
self.endheaders(body)
File "/usr/lib/python3.5/http/client.py", line 1119, in endheaders
self._send_output(message_body)
File "/usr/lib/python3.5/http/client.py", line 944, in _send_output
self.send(msg)
File "/usr/lib/python3.5/http/client.py", line 887, in send
self.connect()
File "/usr/lib/vmware/site-packages/pyVmomi/SoapAdapter.py", line 1032, in connect
six.moves.http_client.HTTPSConnection.connect(self)
File "/usr/lib/python3.5/http/client.py", line 1277, in connect
server_hostname=server_hostname)
File "/usr/lib/python3.5/ssl.py", line 385, in wrap_socket
_context=self)
File "/usr/lib/python3.5/ssl.py", line 760, in __init__
self.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 996, in do_handshake
self._sslobj.do_handshake()
File "/usr/lib/python3.5/ssl.py", line 641, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:719)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 314, in main
fb.register_with_cm(analytics_int_http, is_patch)
File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 225, in register_with_cm
problem_id='install.analytics.cmregistration.failed')
cis.baseCISException.BaseInstallException: {
"componentKey": "analytics",
"detail": [
{
"id": "install.analytics.cmregistration.failed",
"localized": "Analytics Service registration with Component Manager failed.",
"translatable": "Analytics Service registration with Component Manager failed."
}
],
"problemId": "install.analytics.cmregistration.failed",
"resolution": {
"id": "install.analytics.cmregistration.failed.res",
"localized": "Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",
"translatable": "Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."
}
}
2020-04-13T16:28:06.233Z VMware Analytics Service firstboot failed
I google search this and found this vmware kb
https://kb.vmware.com/s/article/67198
This lead me down the rabbit hole of enabling ssh and bash so I could winscp our root cert ca pem file onto the box. I did this and copied our root ca certificate which is a windows 2012 R2 certificate authority to /etc/ssl/certs.
/usr/lib/vmware-vmafd/bin/dir-cli trustedcert publish --cert /etc/ssl/certs/Root-CA.cert.pem
It imported successfully (or so it told me)
I hit retry and it was the same error. I then rebooted the new VCSA thinking maybe it needs to be rebooted to take affect. It rebooted but changed its IP address to the final IP that the old windows vcenter was. So I changed it back to the temporary ip address using DCUI so the migration wizard could contact it. I still get the same error when retrying the migration wizard that is running on my windows box "Analytics Service registration with Component Manager failed".
I then followed this guide to try to replace the vSPhere 6.0 Machine SSL certificate with a VMCA issued certificate
https://kb.vmware.com/s/article/2112279
However I get an error and tells me to check the and in the certificate-manager.log. An excerpt from that log right around the ERROR lines:
2020-04-13T16:52:47.565Z INFO certificate-manager MACHINE_SSL_CERT certificate replaced successfully. SerialNumber and Thumbprint changed.
2020-04-13T16:52:47.662Z INFO certificate-manager lstool command currently being executed is : ['/usr/java/jre-vmware/bin/java', '-Djava.security.properties=/etc/vmware/java/vmware-override-java.security', '-cp', '/usr/lib/vmidentity/tools/lib/lookup-client.jar:/usr/lib/vmidentity/tools/lib/*', '-Dlog4j.configuration=tool-log4j.properties', 'com.vmware.vim.lookup.client.tool.LsTool', 'get-site-id', '--no-check-cert', '--url', 'https://drvcenter.diamondcu.com:443/lookupservice/sdk']
2020-04-13T16:52:49.487Z ERROR certificate-manager 'lstool get-site-id' failed: 1
2020-04-13T16:52:49.490Z ERROR certificate-manager Error while replacing Machine SSL Cert, please see /var/log/vmware/vmcad/certificate-manager.log for more information.
2020-04-13T16:52:49.490Z ERROR certificate-manager 'lstool get-site-id' failed: 1
2020-04-13T16:52:49.492Z INFO certificate-manager Performing rollback of Machine SSL Cert...
Now, not sure what to do, and just crickets with vmware support... I powered off the VCSA, powered back on the windows vcenter, rejoined to to AD and rebooted and now were back to vcenter 6.0 update 3.
Any ideas? The vmware certificates always put us through utter hell on the windows environment and it seems its going to continue to be that way on the VCSA.
We really would like to migrate off of the Windows Server 2008 R2 vms running vcenter 6.0. This is our DR site. I haven't even touched production yet. I wouldn't be surprised if our production site will give us difficulties. I can't install the latest windows vcenter 6.0 patch... error 1603 starting some service... and none of the kb articles helped (removing some vmware java stuff, etc..). So I can't wait to get off of the Windows platform and upgrade.
DR Vcenter 6.0.0 build 14510545 - attempting first. - Running on fully patched Windows Server 2008 R2
SRM virtual appliance 8.2
vSphere replicaiton virtual appliance 8.2 (its receiving inbound from hq)
2 ESXi 6.0.0, 15169789 hosts - HP 380g8's, eventually will take them to latest ESXi 6.5 build using HP's custom image. Hosts are not officially supported past 6.5.
HQ Vcenter 6.0.0 build 9313458 - will do second. - Running on fully patched Windows Server 2008 R2
SRM virtual appliance 8.2
vSphere replicaiton virtual appliance 8.2 (Its replicating 28 vms to the DR site).
8 ESXi 6.0.0, 15169789 hosts. Dell FC640's, eventually will take them to latest ESXi 6.7 build using Dells custom image.
Hello everyone,
today I had to upgrade the firmware of my 3ware RAID controller in order to start my - quite old - server with ESXi 4.1. Before this the server wasn't starting at all from one day to another.
Now I face two issues which I am not sure if they existed before.
I have a RAID 10 - configuration (please see attachment) with 6 disks.
Am I right that disk 4 is missing at all and disk 3 has a failure an should be replaced?
Thanks for your help in interpreting the picture!
Daniel
We have HP ProLiant DL380 Gen9 and they are on the compatibility list. I'm looking to see if anyone has upgraded without losing any settings using the HP custom image and outline what the process looks like.
We have VCSA 6.7.0.43000 Build 15976714 with ESXi 6.0.0, 5224934
We are looking to upgrade to ESXI 6.7 U3 and I see they have an HP image= available to use here:
https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI67U3-HPE&productId=742
If I set the image as a baseline in update manager will it perform an upgrade or clean install?
Any process outlines will help.
Thanks in advance
I am in the middle of upgrading the host cluster in our lab environment from ESXi version 6.7U3 to 7. I have already updated the vCenter Server appliance to version 7. I have created a baseline using the ESXi 7 ISO and have tried to update the cluster using the Life Cycle Manager but the scan says that baseline is compatible. I have vSAN configured and DRS is set to fully automatic mode.
Hardware wise, the lab consists of a Dell VRTX chassis with 4 M640 blade servers. Each blade has 2 x Intel Xeon Silver 4114 CPUs & 384 GB of RAM. I believe the hardware should be compatible, the compatibility matrix suggests so.
Anyone have an idea as to why the baseline would be incompatible?
Hello,
I have two HP Gen8 servers that are not in the compatibility matrix for anything newer than ESXi 6.5. I downloaded both an offline bundle zip (HPE-ESXi-6.5.0-Update2-preGen9-650.U2.9.8.3) and also an ISO as well.
First in vSphere 6.7 under Update Mnager > ESX images, I tried to upload the .ISO file VMware-ESXi-6.5.0-Update3-14990892-HPE-preGen9-650.U3.9.6.10.1-Dec2019.iso, and it uploads ok but then I get an error message in the recent tasks list that says "The uploaded upgrade package cannot be used with VMware vSphere Update Manager". It does not say why and there are no further details.
So then I thought maybe I can use the zip file, so I uploaded the offline zip file in Update Manager under the updates tab. It show sup there now at the very end of page 8 of all of my updates. I created a baseline called 6.5 upgrade, and found that patch and added it in. I attached this baseline to one of the HP servers that needs it and when I do a compliance check its not coming up as non-compliant. In short, VUM doesn't think the 6.0 ESXi needs it.
Whats the best way to upgrade two ESXi 6.0 to 6.5 under vCenter 6.7?
Dear Professional,
I would like to install vSphere Hypervisor Evaluation Version on my PC,
but as I login the download page and try to click the blue button which is for download,
the page never changes and download never starts.
I wonder there are any prerequisites or something necessary but I don't have for installing vSphere Hypervisor.
If you could tell me the cause and solution, I would really appreciated.
I have the hardware and all the necessary 'bits', I think in order to start setting up my home lab. Looking for help / guidance on the best practices and what I 'should' avoid doing in the build. The plan is for 2 separate ESXi servers, one for production and one for development. As well as an instance of vCenter that will manage both.
Hardware:
2x HP DL380 G7
2x Cisco 3750G
1x D2600 storage
My initial thoughts is to have vCenter virtualized on the development side, inorder to prevent any impact to the production? Also, what is a recommended way to start the basic setup so that it can be scaled up for future projects. Thanks for any help or guidance.
Cheers!
Hi All,
Is a new license key required for ESXi host upgrade 6.7U2 to 7.0 and vCenter 6.5 to 7.0 enterprise Plus.
Regards,
I found I have a HP DL380 Gen 8 server still on ESXi 5.0
This command worked perfectly to upgrade a 6.0 to 6.5 but can I go straight to 6.5 from as early as 5.0? Obviously I added the --dry-run to see the output before running it.
esxcli software profile update -d /vmfs/volumes/1fe43b18-44f1ee63/iso/VMware-ESXi-6.5.0-Update3-14990892
-HPE-preGen9-650.U3.9.6.10.1-Dec2019-depot.zip -p HPE-ESXi-6.5.0-Update3-preGen9-650.U3.9.6.10.1 --dry-run
Hello everyone! Currently running ESXi 6.0 on a Dell T430 and wanting to do 2 important things :-)
I've just updated all the firmware on the Server, and got the link of the optimized ESXi 6.7 isos.
Since this is a production Machine, I would like to be 100% safe when doing the above.
1. What is the best way of backing up (the boot-up is an SD card inside the Server) the ESXi boot-up image or files so that in case the upgrade goes sideways, I can just use the backup SD.
All the VMs are replicated to another Dell T440 Server running ESXi 6.7 so we've got those covered. Also, from an earlier instruction, I was able to backup the host configuration to a text file.
https://kb.vmware.com/s/article/2042141
2. Once I've done Step 1, please advise on best way to get from 6.0 to 6.7? I get conflicting info when doing research.
Is VServer Center the way to go? It's not installed but I have a license to do so from my Essentials subscription.
Or just stick with the regular upgrading via the iDrac Enterprise Console? (Dell)
Thanks in advance for your assistance.
Dean
So we had a critical finding come up for our hosts, some are 6.5 and some are 6.7 that there is a driver update required to correct an issue.
I download the package and create a baseline, attach it to the identified hosts and then check for compliance
Some indeed do come up as non-compliant which is great
However more than half of them (all the 6.5 hosts) come up as compliant with the baseline.
Both download links are above (there doesnt appear to be a specific 6.5 version of the driver the 6.0 version says in its description that it contains the 6.5 version.
I query the hosts manually to just make sure and the result I get back is that version 1.4.6 is installed yet it is "compliant" with the baseline that has version 1.4.10 which includes the fix.
How is this even possible?
Am I downloading the wrong package
Also surely if skyline picks up multiple hypervisor versions are installed including the correct download link for all versions of the hypervisor detected rather than just 6.7 would be advisable?
Hi,
Currently these ESXi are running on 6.0 Update 1 and managed by a Windows server vCenter.
They are using a Standard Switch
A possible option to move away from windows vCenter and to cosolidate management is to migrate them to a VCSA 6.7U3
Yes these ESXi are old but look to be still supported by VCSA 6.7U3 and then maybe I can look to upgrade them to 6.5
Assuming the traffic from the VCSA to these ESXi is open would this just be a matter of:
1) Remove the ESXi from current vCenter Inventory
2) Add these hosts to VCSA 6.7
As I understand this can be achieved without VM downtime/impact
Any thoughts or suggestions about the above process?
Thanks
Hi
Is it possible to upgrade vSphere 6.5 direct to vSphere 7.0 ?
(No need upgrade to vSphere 6.7 first)
Rgds
Alan