Section 8 - Deploy and Consolidate vSphere Data Center
Objective 8.1 -
Deploy ESXi Hosts Using AutoDeploy
Identify ESXi AutoDeploy
requirements:
- if using EFI on hosts they must be switched to BIOS
compatibility mode
- if using VLANs, the UNDI driver must be set to tag
frames with the proper VLAN in BIOS
- TFTP server is required
- ESXi port groups must be configured with correct VLANs
- VIBs, image profiles and auto deploy rules/rule sets
are stored in a repository (2GB is recommended space)
- require DHCP server, and for AutoDeploy replace the
gpxelinux.0 file with undionly.kpxe.vmw-hardwired
- setup remote syslog or use existing syslog server
- install ESXi dump collector
- AutoDeploy does not support pure IPv6 environment
(deploy with IPv4)
Note: AutoDeploy
server is included with the management node of the vCenter Server (Windows or
VCA)
Configure
AutoDeploy:
- Auto Deploy
service Startup Type set to Automatic
- Configure TFTP server: Web Client ‘Download TFTP Boot Zip’ and unzip it to TFTP server directory
- Set DHCP server to point to the TFTP server
- DHCP server options:
-- 66: IP Address of TFTP server
-- 67: Boot file
“undionly.kpxe.vmw-hardwired”
- Set ESXi servers to network or PXE boot
- Set up the image profile, and write a rule that assigns
that image profile to hosts
PowerCLI cmdlets
for AutoDeploy:
- Add-EsxSoftwareDepot
- Get-EsxImageProfile
- New-DeployRule
- Add-DeployRule
- Get-DeployRule
- Copy-DeployRule
Note: Subsequent
reboots of the ESXi host will then be re-provisioned by vCenter
Objective 8.2 -
Customize Host Profile Settings
Create/Edit/Remove/Import/Export/Attach/Apply/Check
Compliance/Remediate via: vSphere Web Client > ‘Host Profiles‘ icon
Objective 8.3 -
Consolidate Physical Workloads using VMware Converter
Convert Physical Workloads
using VMware Converter:
Install VMware Converter Standalone on the Physical
Machine
- Source system:
Powered-on machine
- Local or Remote:
Local
- Destination:
VMware Infrastructure virtual machine
- Data to copy:
copy all disks and maintain layout
- Install VMware
tools
- sync data (stop
services on source machine first)
Note: During
conversion can extend/remove/add a new volume, change memory and CPU
configuration, add/remove networking...
Interpret and
correct errors during conversion:
VM fails to boot after conversion...
... check SCSI
controller selected during conversion process
... BSOD try
running Windows repair
Conversion fails at 2%...
... check firewall,
IPs, DNS resolution
VMware Converter Standalone log files:
- W2008: c:\users\all users\application
data\vmware\vmware converter enterprise\logs
- W2012: c:\programdata\vmware\vmware vcenter converter
standalone\logs
To maintain a
physical NIC’s MAC Address for a P2V-d server...
... Configure the MAC address for the vNIC
using the vSphere Web Client
Comments
Post a Comment