This trips more people up than one would think. Make sure you select the appropriate network. After a successful deployment, the current vCSA will be shutdown, and the newly deployed appliance will assume the olds address. This will enable it to coexist with the current vCSA while the data and settings are copied over. Here you can elect to use a TEMP static IP address or DHCP for the new vCenter Server Appliance being deployed. Here you have the option to select a new deployment size based on your needs and future expected growth. Sometimes DNS may get in your way and the deployment will fail. You can either target a specif host to deploy the new vCenter Server Appliance to, or you can use the vCenter. This will open up a new wizard which will require environment specific connection details. In this example I am upgrading an existing vCSA, so that’s the option I’ll select.Įnter the details for the existing vCenter Server Appliance. You’ll be presented with several available options. Mount the ISO to a jump server Locate and launch the installer.exe. – Temp IP address will be needed briefly for the new appliance being deployed (assuming Static temp IP being used). – Current vCSA VM will need to be renamed in the inventory, else the new vCSA VM will need a temp name. – Validate adequate storage space is available.
An upgrade replaces the existing appliance, so a few extra items will be needed:
Updates patch the current vCenter appliance (vCSA). I personally like taking a snapshot of the vCenter VM. Third – validate compatibility of partner products deployed in the environment.Second – validate hardware, firmware, and drivers of ESXi hosts.
First – validate the version of the currently deployed vCenter to ensure a compatible upgrade with VMware’s Product Interoperability Matrices.Finally decided to pull the trigger and upgrade my base lab from VMware vCenter 6.7 U3 to version 7 U1.
0 kommentar(er)
