Networking details for the new PSC VM virtual appliance ( this is a temporary IP and the new PSC will use your existing PSC IP once its done upgrading): Make sure it is deployed on your VSAN cluster and enable thin provisioning if required: The new PSC virtual appliance VM name, and root password: Doing a bit of testing on how iSCSI multipath would work and failover scenarios when iSCSI VSAN host owner moves or fails.ġ- Download vCenter 6.7 ISO and launch vCenter UI Installer:įirst start by Upgrading External PSC so connect to that:Ģ- Insert vCenter details and credentials so that the installer reads the existing PSC virtual appliance in your existing VSAN cluster:ģ- Insert vCenter details and credentials so that the installer deploys the new PSC virtual appliance in your existing VSAN cluster: I have another post being prepared on how to configure iSCSI target service on VSAN to support Microsoft WSFC “Windows Server Failover Cluster” and Virtual Machines hosted on a VSAN cluster. vCenter as before will build new appliances and import existing configuration, while VUM will be used to update vSphere hosts to 6.7, and last but not least, VSAN disks would be upgraded to version 6.0. Upgrade is easy, straightforward, and very fast even when upgrading the vSphere build which now only reboots once automatically thus causing less wait and disruption not to mention quick boot. Actress| Krishna: The Power of Indrakeeladri.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |