Posts Tagged ‘vcenter’

Trying to upgrade Vcenter 6.5 to 6.7 , The following error comes up

Cannot validate target appliance configuration as not enough information from the source appliance can be collected. For more details check out the server logs

Fix

SSH into new 6.7u1 applicance:

“software-packages install –url –acceptEulas”

and then

“shutdown reboot -r “patch reboot””

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Upgrade VCenter

In order to ensure protection is not affected when upgrading or replacing a vCenter, the vCenter database should be preserved

Upgrade then make sure Replication all comes back green

 

Upgrade Hosts

Before Upgrading the Hosts to the latest ESXi , double check the current version of Zerto supports the version you are putting on or you will get the error on Upgrade “VRA unsupported esx version”

Migrate all VM’s to other VPG’s , migrate 6 VM’s at a time

Once VM’s migrated , shutdown VRA and VRAH , restart upgrade host

You can migrated VCC machines to other hosts without effecting replication

https://nolabnoparty.com/en/vsphere-6-7-upgrade-esxi-6-5-to-6-7-pt-3/

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently we started getting errors for our Vcenter address which was a subdomain of our main domain which had a proper certificate for the website. Chrome picked this up and then uses HSTS to make sure all subdomains have a valid cert ( Without an easy option to Bypass ) 

However to bypass just type either word below when presented with the error

thisisunsafe” or “badidea

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently after rebooting a VMWare server , the VCenter Server service would not start  

The description for Event ID 1000 from source VMware VirtualCenter Server cannot 

C:\ProgramData\VMware\VMware Virtual Center\Logs. Look at the vpxd.log

<YYYY-MM-DD>T<TIME> 02128 error ‘App’] [VpxdReverseProxy] Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions.

Checked NetStat and something was running on port 80. Looks like IIS had been installed with default settings which puts default site on port 80. Changed this to another port , reboot IIS and this fixed the issue

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)