Migration all the object from VCSA 5.5 to VCSA 6.5 and upgrading ESXi to 6.5
Migration all the object from VCSA 5.5 to VCSA 6.5 and upgrading ESXi to
6.5
Contents
Abstract
All the core DC vCenter and ESXi
host is running in 5.5 version and we are upgrade all ESXi host from 5.5 to 6.5
version and migration all the object from VCSA 5.5 to VCSA 6.5.
Pre-check before migrate the ESXi host:
The following item is going to verified by who is going to migrate
the vCenter server.
Ø
Export the data store and port group list
Ø
Export the list of ESXi hosts on cluster wise
before migrating to VCSA 6.5
Ø
Export the list of VMs with folder name.
Implementation Plan:
Folder creation: -
·
Create host & cluster folders and VM’s
folder in vcenter2-facility. mhint as it is in vcenter-facility.mhint
Cluster creation: -
·
Create clusters in VCSA 6.5 as per the BB
standard for moving data center.
- Cluster
Features:
Turn On vSphere HA: enabled
Turn On vSphere DRS: enabled
- vSphere
HA:
!) Admission Control Policy: 13% (Change Value as per below guide)
(The values entered should be
approximately equal to the amount of resources provided by one host in the
cluster. For a cluster of 8 hosts – use 13%. For a cluster of 16 and more hosts
– use 7%).
!!) VM Monitoring:
VM Monitoring: VM Monitoring Only
Monitoring sensitivity: custom
Failure interval: 300 seconds
Minimum uptime: 120 seconds
Maximum per-VM resets: 3
Maximum resets time window: 1 hour
- Data
store Heart beating:
select any of the cluster data stores
- vSphere
DRS:
Automation Level: Fully Automated
Migration threshold: 2
o
Swap file
Location: store the swap file in the data store specified by the host
o
Assign the appropriate host profile – genpop –
to the cluster
Host Migration: -
Need to follow the below steps to
all clusters to remove the hosts from the VCSA 5.5 and add the removed host in
the VCSA 6.5.
·
Log into the vCenter 5.5
o
e.g.: - vcenter-nte1.mhint
·
Choose the cluster to remove the host one by one
o
E.g.:
fgprd-nte1-c01
·
Disconnect the host one by one from the cluster.
·
Log into the vCenter 6.5
o
E.g.: - vcenter2-nte1.mhint
·
Select the cluster to add the host which is
removed from vCenter 5.5 (Host removed cluster
and host added cluster should be same. Should follow the BB naming structure)
·
Add the ESXi 5.5 host in VCSA 6.5 vCenter
server’s cluster using root user credential.
TFTP Configuration: -
·
Click Configure/Manage > Settings > Auto
Deploy.
·
Select Download TFTP Boot Zip and keep the
download safe; you’ll need this shortly.
·
Make a note of the BIOS DHCP File Name (it
should be undionly.kpxe.vmw-hardwired).
·
Create folder under file distribution ->
Files
o
E.g.: - nte1-2, va2-2, va3-2 ….
·
Upload the following files from Boot.zip into
the created folder in the TFTP server.
o
Tramp
(no need to modified because auto deploy proxy deprecated in VCSA 6.5 server infra)
o
undionly.kpxe.vmw-hardwired
Auto deploy Configuration:
Need to configure the auto deploy
rule in VCSA 6.5 as it is in VCSA 5.5.
·
Log into the VCSA 5.5 server in PowerCLI
o
E.g.: - Connect-viserver -server vcenter-nte1.mhint -user <username> -password
*********
·
Run the following command to fetch the auto
deploy rule.
o
Get-deployrule
·
Log into the VCSA 6.5 server via GUI
o
Import custom ESXi 6.5 offline buddle ( Image
has been exported from NTE1 and stored in Jump server ). Please follow the
image creation steps, if needed https://confluence.bbpd.io:8443/display/MHITG/vCenter+6.5+AutoDeploy+Image+creation
·
Import “genpop” host profile into VCSA 6.5 (“genpop”
host profile has to be exported from NTE1).
·
Create the auto deploy rule for all cluster as
configure in VCSA 5.5 (the information collected in 2 step).
Moving VM: -
After
successful migration of all ESXi host from VCSA 5.5 to VCSA 6.5, all VMs will
be under “Discovered virtual machine”.
So, it should be moved to respective folder as it is in VCSA 5.5 server.
Based on the list taken in Check List, move the VM to
respective folders.
Post Implementation Check:
·
Verify all ESXi hosts are running with 6.5
version and compliance with attached host profile.
·
Verify all VMs are mapped with correct VM
folder.
Roll back Plan: -
Disconnect all host
from VCSA 6.5 and connect with old VCSA 5.5 one by one.
Comments
Post a Comment