IT Course Directory: VMware, Linux, Networking, and Raspberry Pi

VCP5-DCV: VMware vSphere 5 Data Center Virtualization Course

Learn vSphere 5 administration, ESXi, vCenter Server, virtual networking, VM deployment, vMotion, Fault Tolerance, lifecycle management, and VCP5-DCV exam skills.

Course overview

This course introduces the administration of a VMware vSphere 5 virtual infrastructure and provides a practical foundation for VCP5-DCV certification preparation. You will learn how ESXi hosts run virtual machines, how vCenter Server manages multiple hosts, and how networking, storage, migration, availability, and maintenance features fit together.

The course assumes basic knowledge of computer hardware, operating systems, Windows administration, IP addressing, subnetting, default gateways, DNS, and network troubleshooting. A small lab with one or more physical or nested ESXi hosts is useful for practice. Use the VCP5-DCV curriculum to organize your study and the course activities to reinforce each skill.

1. Virtualization and vSphere fundamentals

Why use server virtualization?

Server virtualization allows one physical server to run several isolated software-defined computers. Each virtual machine receives virtual CPU, memory, disk, and network devices while sharing the physical host's underlying resources.

• Hardware consolidation: Several workloads can use one physical server, reducing unused capacity.
• Isolation: A failure or configuration change in one virtual machine is separated from other machines.
• Provisioning speed: New servers can be created from templates or existing disk images.
• Mobility: Compatible virtual machines can be moved between hosts.
• Operational flexibility: Administrators can schedule maintenance and redistribute workloads more easily.

Core terms

A virtual machine is a software-defined computer that runs a guest operating system. A hypervisor provides the layer that presents virtual hardware and schedules access to physical resources. An ESXi server is a host: a physical server running the hypervisor. The collection of hosts, virtual machines, storage, networks, and management services is the virtual infrastructure.

In vSphere, ESXi runs the workloads. vCenter Server provides centralized management. The vSphere Client is the administrator's interface. Datastores provide VM files, virtual switches and port groups provide connectivity, and features such as vMotion and Fault Tolerance use these foundations to provide mobility and availability.

2. vSphere architecture and components

How the components work together

An administrator connects to an ESXi host directly for host-level work or connects to vCenter Server for centralized operations. vCenter Server communicates with managed ESXi hosts and maintains an inventory. A VM is stored on a datastore, runs on an ESXi host, and connects through a port group on a virtual switch. Physical network adapters, called uplinks, connect virtual switching to the physical network.

3. Planning a small virtual infrastructure

Host hardware and resources

Check processor compatibility, supported network adapters, storage controllers, memory capacity, and firmware before installing ESXi. Size hosts for more than the current workload: account for the management layer, operating-system overhead, growth, maintenance, and failover capacity.

• Use compatible processors and enable required virtualization features in firmware when applicable.
• Install enough memory for the planned VMs plus ESXi overhead and operational reserve.
• Provide multiple network adapters when separating management, VM, storage, or migration traffic.
• Plan reliable storage with adequate capacity, performance, and redundancy.
• Document server names, asset identifiers, firmware versions, and physical port connections.

Network and IP planning

Assign a unique, preferably static, management IP address to every ESXi host. Record the subnet mask or prefix, default gateway, DNS servers, hostname, VLAN information, and physical switch port. Verify that the administration workstation, vCenter Server, ESXi hosts, DNS, storage networks, and migration networks can communicate as required.

Storage and management layout

A small environment can use one vCenter Server, one or two ESXi hosts, a management network, a VM network, and a datastore accessible to the hosts. Separate traffic logically or physically when performance, security, or availability requirements justify it. Shared storage is particularly important for many migration and availability designs because the destination host must access the VM's files.

Before deployment, prepare DNS records, IP addresses, VLANs, switch ports, time settings, administrator credentials, installation media, datastore capacity, and a recovery plan. Create a simple diagram showing vCenter Server, ESXi hosts, storage, physical switches, and network purposes.

4. Installing and configuring ESXi

Installation sequence

1. Confirm hardware compatibility, firmware settings, boot media, and the intended installation disk.
2. Boot the physical server from the ESXi installer.
3. Select the installation target and set the root password.
4. Reboot from the ESXi installation disk and record the host identity.
5. Open the local ESXi configuration interface and configure the management network.

Management network configuration

The management network carries administrative communication between the ESXi host, vCenter Server, and administration workstations. Configure the host's management VLAN or switch connection, IPv4 address, subnet mask or prefix, default gateway, DNS servers, and hostname.

Host name:       esxi01.example.local
Management IP:   192.0.2.21
Subnet mask:     255.255.255.0
Default gateway: 192.0.2.1
DNS server:      192.0.2.53
Management VLAN: 20

The values above are examples only. Use addresses appropriate for your lab or organization. After saving the configuration, verify the physical switch port, VLAN alignment, uplink, gateway, DNS resolution, and client reachability. Test both the hostname and IP address where DNS is configured.

ping <management-ip>
ping <esxi-hostname>

When a host becomes inaccessible

• Confirm the management IP and subnet settings locally on the host.
• Check the cable, NIC link, physical switch port, VLAN, and virtual-switch uplink.
• Verify that the gateway and DNS settings match the intended network.
• Use local host access to correct a bad management configuration before changing remote settings.

5. Deploying and managing vCenter Server

vCenter Server provides centralized inventory, permissions, monitoring, and access to features that require coordinated management of multiple hosts. It does not replace ESXi: ESXi continues to run the VMs, while vCenter Server coordinates administrative operations.

Adding a host to inventory

1. Connect to vCenter Server with an account authorized to add hosts.
2. Select the intended data center or management object.
3. Choose the operation to add an ESXi host.
4. Enter the host's fully qualified name or IP address.
5. Supply the ESXi connection credentials and accept the security prompt when the identity is verified.
6. Review host summary, networking, storage, and alarm status after the task completes.

Organize inventory by data center, cluster or host group, folders, and meaningful names. Keep organizational structure consistent with responsibility, location, environment, or service. Permissions are evaluated through users, groups, roles, and object inheritance. Grant only the rights needed for a task and avoid using unrestricted administrator access for routine work.

If a host cannot be added, check reachability between vCenter Server and the host, credentials, DNS resolution, host connection state, and whether the host is already managed elsewhere.

6. Using the vSphere Client

The vSphere Client presents inventory objects and task-specific controls. Learn to distinguish the inventory view from the summary, monitor, configuration, permissions, events, and task panes.

• Use the inventory to select a data center, host, datastore, network, or VM.
• Use summary views to check power state, capacity, alarms, and connections.
• Use configuration views to change host networking, storage, and system settings.
• Use tasks and events to determine whether an operation succeeded and to find failure details.
• Use permissions and roles to review administrative access.

Routine work includes powering VMs on or off, opening a console, editing virtual hardware, checking datastore usage, reviewing host alarms, and placing a host into maintenance mode when appropriate.

7. Deploying and administering virtual machines

VM deployment workflow

1. Choose a host or cluster and start the new-VM wizard.
2. Select a name, guest operating-system family, and compatible virtual hardware version.
3. Select a datastore with enough capacity and suitable performance.
4. Assign virtual CPUs, memory, a virtual disk, and a network adapter.
5. Attach installation media and select the correct port group.
6. Power on the VM, open its console, and install the guest operating system.
7. Install appropriate guest tools when supported, then verify drivers, time behavior, IP settings, and application operation.

Routine VM operations

Powering off a VM is equivalent to removing power from a physical computer, so use a guest operating-system shutdown when possible. Restart, suspend, console access, snapshots, and hardware changes should follow workload and change-control requirements. Monitor CPU, memory, disk, network, alarms, events, and datastore capacity rather than judging health from power state alone.

Increase resources only when monitoring shows a need. Excessive virtual CPU or memory allocation can reduce overall host efficiency. Confirm that the guest operating system and applications recognize the change after editing virtual hardware.

8. Virtual networking

Virtual switches and port groups

A virtual switch forwards traffic between virtual adapters and, through physical uplinks, the external network. A port group is a named policy and connection point on the switch. VM adapters connect to VM port groups. ESXi services such as management and vMotion use VMkernel adapters connected through suitable port groups.

A basic design might include a management port group for ESXi administration, a VM port group for guest traffic, and a separate vMotion-enabled VMkernel connection. Physical switch ports must provide the expected VLANs and must be connected to the correct ESXi uplinks.

• Use clear port-group names that identify purpose and VLAN.
• Confirm that every required host has equivalent network connectivity.
• Separate management, VM, storage, and migration traffic when required by security or performance.
• Check that a VM adapter is connected and attached to the intended port group.

For a VM with no network access, check the adapter's connected and connect-at-power-on settings, port group, virtual-switch uplink, physical switch VLAN, and guest IP configuration.

9. vMotion live migration

vMotion migrates a powered-on VM from one compatible ESXi host to another while keeping the guest service available with only a brief transition. It supports maintenance, workload balancing, and planned host changes.

Migration procedure and validation

1. Prepare both hosts with compatible configuration and working migration connectivity.
2. Confirm that the destination sees the required datastore and VM port group.
3. Check alarms, reservations, CPU compatibility, and available capacity.
4. Start the migration operation and select the destination host.
5. Monitor the task and events until completion.
6. Confirm the VM is running on the target, remains connected to the intended network, and continues serving the guest application.

If vMotion fails, inspect task messages first. Then verify host management status, migration VMkernel connectivity, storage accessibility, destination resources, CPU compatibility, and network equivalence.

10. Fault Tolerance

Fault Tolerance protects an eligible VM by maintaining a primary VM and a synchronized secondary VM on another host. The secondary follows the primary's execution so that a host failure can be handled with continuity for the protected workload.

To configure Fault Tolerance, select an eligible VM, choose the protection operation, select a suitable secondary host, and review the resulting primary and secondary status. Monitor alarms, synchronization state, host placement, and task events. Test continuity in a controlled lab or approved maintenance window; do not simulate failure on an uncontrolled production workload.

11. Maintenance and lifecycle management

vSphere Update Manager supports host update planning by comparing hosts with update baselines and coordinating remediation workflows. Lifecycle work should include compatibility checks, backups or recovery validation, communication, a maintenance window, and post-change verification.

1. Inventory hosts, versions, drivers, firmware dependencies, and affected workloads.
2. Review update compliance and identify prerequisite or conflicting updates.
3. Schedule maintenance and decide how VMs will be moved or stopped.
4. Use migration or availability features to reduce disruption where supported.
5. Remediate hosts through the approved Update Manager workflow.
6. Verify host connectivity, storage, networking, alarms, VM power state, and application health.

Before placing a host into maintenance mode, identify VMs that cannot migrate because of local storage, device passthrough, affinity rules, compatibility, or resource constraints. A successful patch task does not by itself prove that applications and network paths are healthy.

12. Practical lab sequence

Lab 1: Build the first ESXi host

1. Install ESXi on a lab server.
2. Set a static management IP, subnet mask, gateway, DNS server, and hostname.
3. Connect the management uplink to the intended physical switch and VLAN.
4. From the administration workstation, test access by IP address and hostname.

Lab 2: Create a vSphere inventory

1. Deploy or connect to vCenter Server.
2. Create an appropriate data center or management structure.
3. Add one or more ESXi hosts with verified credentials.
4. Review host status, datastores, networks, alarms, tasks, and events.
5. Organize hosts and VMs using consistent names and folders.

Lab 3: Deploy a Windows VM

1. Create a VM with an appropriate guest type, CPU, memory, disk, and datastore.
2. Attach Windows installation media.
3. Select the intended port group and power on the VM.
4. Install Windows, configure its IP settings, and verify network connectivity.
5. Practice graceful shutdown, restart, console access, and hardware inspection.

Lab 4: Configure networking

1. Create or select a virtual switch.
2. Connect the correct physical uplink.
3. Create a port group with the required VLAN and name.
4. Attach a VM adapter to the port group.
5. Test guest connectivity and verify the path through the virtual and physical switches.

Lab 5: Migrate and protect workloads

1. Prepare two compatible hosts with shared storage and migration networking.
2. Migrate a powered-on test VM with vMotion.
3. Validate host placement, guest connectivity, and application availability.
4. Check Fault Tolerance eligibility for a suitable lab VM.
5. Enable protection, observe primary and secondary status, and perform a controlled continuity test.

13. Troubleshooting guide

Client cannot connect to an ESXi host

• Confirm the management IP and hostname.
• Check physical connectivity, VLAN alignment, gateway, DNS, and workstation reachability.
• Confirm that the correct host address and credentials are being used.

Host cannot be added to vCenter Server

• Verify network reachability from vCenter Server to the host.
• Check host credentials and name resolution.
• Review whether the host is already managed elsewhere or has an existing connection problem.

VM has no network access

• Verify that the virtual adapter is connected.
• Confirm the selected port group and virtual-switch uplink.
• Check physical-switch VLAN configuration.
• Verify guest IP address, subnet, gateway, DNS, and local firewall settings.

vMotion is unavailable

• Confirm that both hosts are managed, compatible, and not in a failed state.
• Verify migration VMkernel connectivity and VLAN configuration.
• Check destination CPU and memory capacity.
• Confirm datastore accessibility and port-group availability.
• Read task and event messages for the specific failure.

Fault Tolerance cannot be enabled

• Check VM and host eligibility, virtual hardware, and workload constraints.
• Verify required FT networking and host separation.
• Confirm sufficient CPU, memory, storage, and synchronization capacity.
• Review vCenter task messages for unmet prerequisites.

14. VCP5-DCV certification preparation

Certification preparation should combine terminology review with repeated hands-on administration. Be able to explain not only what a feature does, but also which components it depends on and how to validate the result.

• Draw the relationship between vCenter Server, ESXi, VMs, datastores, virtual switches, port groups, and VMkernel networks.
• Practice installing ESXi and configuring a reachable management network.
• Practice adding hosts, organizing inventory, assigning permissions, and reading tasks and events.
• Deploy VMs and change CPU, memory, disk, and network settings safely.
• Explain vMotion prerequisites and diagnose migration failures.
• Explain Fault Tolerance primary and secondary roles, prerequisites, monitoring, and testing.
• Review Update Manager workflows, maintenance planning, and post-update validation.

Keep a lab log containing configuration decisions, command or wizard results, failure messages, and corrective actions. When a task feels easy, deliberately break one dependency in a safe lab—for example, use an incorrect VLAN or remove destination storage visibility—then restore it and document the symptoms.

15. Knowledge and skills checklist

• Define VCP5-DCV, vSphere, ESXi, host, VM, guest OS, vCenter Server, vSphere Client, virtual switch, port group, vMotion, and Fault Tolerance.
• Explain how compute, storage, management, and network components cooperate.
• Plan host hardware, IP addressing, DNS, VLANs, uplinks, datastores, and management layout.
• Install ESXi and verify management access.
• Add and organize hosts in vCenter Server.
• Create, install, operate, resize, and monitor a virtual machine.
• Configure VM and management networking.
• Prepare and validate a vMotion migration.
• Plan, enable, monitor, and test Fault Tolerance for an eligible VM.
• Plan host maintenance with Update Manager and verify health afterward.
• Use tasks, events, alarms, and structured checks to troubleshoot failures.

For additional study in related administration areas, see the course catalog and use the practical VCP5-DCV activities as a repeatable lab checklist.