VCP4

Other Resources

• VMware VCP Forum
• VCP4 Blueprint
• vSphere Documentation
• Simon Long blog

Plan, Install and Upgrade VMware ESX/ESXi

Install VMware ESX/ESXi on local storage

Minimum Hardware Requirements

• 64bit CPU (AMD Opteron, Intel Xenon [inc Nahalem])
  • CPU Virtualisation features required to support 64bit VM's
• 2GB RAM
• 1+ NIC
• SCSI, Fibre Channel or Internal RAID controller
• LUN, SAS or SATA (SATA must be connected through a SAS controller)

Notes

• ESX's hardware clock should be set to UTC
• IPv6 not supported during installation

ESXi Specifics

• All blank internal disks are formatted with VMFS (except 4GB VFAT scratch/swap partition, used for vm-support dumps)
• Direct Console is used to
  • Configure host defaults
  • Set-up administrator access
  • Troubleshoot
• If no DHCP found during install, default 169.254.0.0 / 16 address assigned

vSphere Editions

Edition	Features
Standard	6 cores/CPU, 4way vSMP, 256GB/ESX, Update Manager, HA
Advanced	12 cores/CPU, Hot Add, FT, vShield, VMotion
Enterprise	6 cores/CPU, Storage vMotion, DRS
Enterprise Plus	12 cores/CPU, 8way vSMP, maxGB/ESX, vNetwork Distributed Switch, Host Profiles, 3rd Party Multipathing

Upgrade VMware ESX/ESXi

Pre-Upgrade Backups

• Backup ESX Host Config
  • Back up the files in the /etc/passwd, /etc/groups, /etc/shadow, and /etc/gshadow directories (shadow dir's may not exist).
  • Backup any custom scripts
  • Backup any .vmx files
  • Backup any local images etc on local VMFS
• Backup ESXi Host Config
  • Use vSphere CLI to run vicfg-cfgbackup --server <ESXi-host-ip> --portnumber <port_number> --protocol <protocol_type> --username username --password <password> -s <backup-filename>
• VM backup
  • Snapshot before upgrade

Upgrade Scenarios

Method	Notes
with Host Clusters	Use Update Manager. Upgrade VC, Update Manager, ESX, VM, licenses
without Host Clusters	Use vSphere Host Update Utility (good for estates < 10 ESX's), runs from VC Client
vMotion	Migrate VM's from ESX v3 to v4, then perform required VM upgrade
Upgrade vMotion	When upgrading from ESX v2, VM's are migrated from VMFS v2 to v3 and upgraded
Cold migration (with VC)	Move VM's through VC to v4 ESX's and power-up, then upgrade VM
Cold migration (without VC)	Manually move VM's to v4 ESX's and power-up, then upgrade VM
VC on new machine	Backup DB, copy across SSL folder to new machine, run install

ESX/ESXi Upgrade

• DHCP not recommended
• Limited support for v2.5.5, all later versions fully supported
• Need to specify a local VMFS for Service Console VM (not ESXi)

Rollback

• ESX
  • Run rollback-to-esx3 command in Service Console, delete ESX v4 Service Console following restart
  • Restore backed up files
• ESXi
  • During boot, press Shift + R to boot into the Standby (ESX3) build
  • Restore backup using vicfg-cfgbackup -l

Install and Configure vCenter Server

Install vCenter Server

Minimum Requirements

• 2x CPU's (2GHz)
• 3GB RAM
• 2GB disk
• Microsoft SQL2005 Express

Scale	VC	CPU	Memory
50 ESXs, 250 VMs	32 bit	2	4 GB
200 ESXs, 2000 VMs	64 bit	4	4 GB
300 ESXs, 3000 VMs	64 bit	4	8 GB

• Database must be 32bit only, regardless of VC's OS (default database on 64bit SQL is 64bit)

Manage vSphere Client plug-ins

Plug-In	Description
Update Manager
Converter Enterprise
vShield Zones	App aware firewall, inspects client-server and inter-VM traffic to provide traffic analysis and app-aware firewall partitioning
Orchestrator	Workflow engine to manage automated tasks/workflows
Data Recovery	Backup and recovery. Centralised management of backup tasks (inc data de-duplication).

Deploy and Manage Virtual Machines and vApps

Create and Deploy Virtual Machines

• VM Hardware v4 runs on ESX3 or ESX4, v7 runs on ESX4 only

Disk Types

• Thick - traditional (can convert to Thin via Storage vMotion)
• Thin - minimal space usage (conversion to Thick is manual process)

SCSI Controller Types

• BusLogic Parallel
• LSI Logic SAS
• LSI Logic Parallel
• VMware Paravirtual
  • High performance to provide better throughput with lower ESX CPU usage
  • Only VM h/ware v7 with Win2k3, Win2k8 or Red Hat Ent v5
  • Not supported with
    • Boot disks (use a standard adapter for VM's OS/boot disk)
    • Record/replay
    • Fault Tolerance
    • MSCS Clustering (so also SQL clusters)