Hello @RandyColvin Currently update using H5 Client is not available. It will list the updates available. To perform actual update use Management interface by visiting https://<VC IP>:5480. Th...
See more...
Hello @RandyColvin Currently update using H5 Client is not available. It will list the updates available. To perform actual update use Management interface by visiting https://<VC IP>:5480. The error banner suggests same - For the selected target version, use GUI installer or CLI to proceed with upgrade and vCenter Server Management Interface for update.
vSphere 8.0 (vCenter Server and ESXi ) do not support certificate with weak signature algorithms, such as sha1WithRSAEncryption. Just check if the certificate you are using is with weak signature...
See more...
vSphere 8.0 (vCenter Server and ESXi ) do not support certificate with weak signature algorithms, such as sha1WithRSAEncryption. Just check if the certificate you are using is with weak signature algorithms. Check the below KB for more details. https://kb.vmware.com/s/article/89424
Hello @jeffj2000 , Just to clarify few points. - As part of VCSA upgrade via vami ui or cli you will encounter warnings. Based on whether you have dual driver problem in your host there will be an ...
See more...
Hello @jeffj2000 , Just to clarify few points. - As part of VCSA upgrade via vami ui or cli you will encounter warnings. Based on whether you have dual driver problem in your host there will be an automatic scan and VCSA upgrade pre-check will catch that and notify you. So no need to worry as VCSA upgrade itself will highlight dual driver related problems. - If your ESX are not impacted with dual driver, second time precheck will allow VCSA upgrade. ~Anil
Hello L, Can you check if time settings in your vCenter and ESX are same and vCenter time is set to NTP or Host sync ? My guess, this is happening due to time settings. Check if vCenter time is pr...
See more...
Hello L, Can you check if time settings in your vCenter and ESX are same and vCenter time is set to NTP or Host sync ? My guess, this is happening due to time settings. Check if vCenter time is proper or try to sync it with NTP and see if it resolves. ~Anil
Hello dbutch1976, Just few clarifications and suggestions, - Do you have standalone vCenter or in linked mode. ? - Taking snapshot with vCenter powered on should not have any issue and as per VMwa...
See more...
Hello dbutch1976, Just few clarifications and suggestions, - Do you have standalone vCenter or in linked mode. ? - Taking snapshot with vCenter powered on should not have any issue and as per VMware donot have any such guidance. I am not sure if any operations related any running service might be running and when you restored that config file for that service might have deleted. - Just to be clear, The recommended backup and restore process for the vCenter Appliance is via https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vcenter.install.doc/GUID-3EAED005-B0A3-40CF-B40D-85AD247D7EA4.html (File based backup and restore allows you to take automatic scheduled backups) - If you want to go with snapshot, preferably just go for it if it is standalone vCenter and not in linked mode. - You can refer to this blog which explains, why snapshot can create a issue with linked mode, https://blogs.vmware.com/vsphere/2019/10/considerations-for-vsphere-component-backup-and-restore-part-2.html - Just a suggestion, for vCenter (whether standalone or linked mode) try to use file based backups.
Hello Bill Dossett, I can see you have already got your answer. Just adding few points from my side. - Always upgrade external PSC first and then vCenter - Upgrade all the nodes in federation to...
See more...
Hello Bill Dossett, I can see you have already got your answer. Just adding few points from my side. - Always upgrade external PSC first and then vCenter - Upgrade all the nodes in federation to same version. As mentioned better to go to latest release, 6.7.0 U3q which has security fixes. ~Anil
Hello Ger, Password issue in 65 is known issue. Refer to this KB , https://kb.vmware.com/s/article/2147144 if you want to reset your root password. Let me know if this doesnot help.
Your Welcome Werner, Glad to hear this worked for you. This is kind of known issue due to the patching DB having some stale entry from an earlier successful upgrade. Will look if any existing KB ava...
See more...
Your Welcome Werner, Glad to hear this worked for you. This is kind of known issue due to the patching DB having some stale entry from an earlier successful upgrade. Will look if any existing KB available for this. ~Anil
Hello Thomasqwerty, Can you confirm if you have downloaded this file and started installer from this iso. 65 to 70 is migration based upgrade and you need to use the complete iso to do that. For ref...
See more...
Hello Thomasqwerty, Can you confirm if you have downloaded this file and started installer from this iso. 65 to 70 is migration based upgrade and you need to use the complete iso to do that. For reference iso file name is "VMware-VCSA-all-7.0.3-19234570.iso" Let me know if that works for you. ~Anil
Hello Werner, Can you try following and let me know if it resolves. - Log in to your vCenter Appliance via SSH. - Run following command: software-packages unstage - Start the update process a...
See more...
Hello Werner, Can you try following and let me know if it resolves. - Log in to your vCenter Appliance via SSH. - Run following command: software-packages unstage - Start the update process again. - software-packages stage --iso --acceptEula
vmdir can go into standalone mode when system sees some kind of inconsistency between replication partners. I believe you have linked mode VC's ? Glad to see currently you are unblocked.
1) Ran the pre-check script which reported no faulty nodes 2) Upgraded the vcenter to 7.0u3 which was success-full. 3) File based backup via sftp still fails. Hello vjrk83 Can you share the out...
See more...
1) Ran the pre-check script which reported no faulty nodes 2) Upgraded the vcenter to 7.0u3 which was success-full. 3) File based backup via sftp still fails. Hello vjrk83 Can you share the output from file, /var/log/vmware/applmgmt/backup.log ? In parallel check if space available in the file server.
You can provide gateway ip as dns ip secondly after stage1 stop the installer. Open stage2 deployment using 5480 port and then use same ip under fqdn. So that pnid will be ip itself
