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

VMware vSphere 5 Data Center Virtualization (VCP5-DCV) Course Curriculum

Study the VCP5-DCV curriculum: ESXi, vCenter Server, SSO, virtual networking, storage, VM management, vMotion, HA, FT, DRS, security, monitoring, and hands-on labs.

This curriculum covers the concepts and administration tasks associated with VMware vSphere 5 Data Center Virtualization and the VCP5-DCV certification. It is designed for administrators building a lab environment as well as engineers preparing for exam-style questions.

The material assumes basic knowledge of server hardware, TCP/IP networking, DNS, VLANs, Windows or Linux administration, Active Directory, SAN and NAS storage, and command-line administration. Product menus and capabilities can vary between vSphere 5 releases, editions, and licensing levels, so verify feature availability in the lab version being used.

Learning objectives

• Explain how virtualization abstracts, consolidates, isolates, and shares physical compute, memory, network, and storage resources.
• Deploy and configure ESXi hosts and vCenter Server Appliance components.
• Manage vSphere inventory, identity, permissions, virtual machines, templates, and vApps.
• Design and troubleshoot standard and distributed virtual networking.
• Configure VMFS, NFS, Fibre Channel, FCoE, RDM, and iSCSI storage.
• Perform migrations, snapshots, guest customization, and virtual hardware changes safely.
• Configure resource controls, monitoring, alarms, HA, Fault Tolerance, vSphere Replication, DRS, EVC, and maintenance mode.

1. vSphere and virtualization foundations

Server virtualization uses a hypervisor to present physical hardware as logical resources that multiple virtual machines can consume. A virtual machine (VM) is an isolated software-defined computer containing virtual hardware and a guest operating system.

• Abstraction: the guest sees virtual CPUs, memory, disks, and network adapters rather than direct physical devices.
• Consolidation: several workloads can share one physical host, improving hardware utilization.
• Isolation: faults and resource use are separated between VMs, subject to configured limits and host availability.
• Sharing: the hypervisor schedules CPU time, allocates memory, and forwards network and storage I/O among workloads.

Core virtualization concepts

CPU virtualization maps virtual CPUs, or vCPUs, to physical processors and schedules runnable VM work. A VM with multiple vCPUs is not automatically faster; it must have enough parallel work and the host must schedule those vCPUs efficiently. CPU features such as the NX/XD bit and processor generation affect compatibility during migration.

Physical memory belongs to the ESXi host. A VM receives configured virtual memory, while ESXi manages the mapping between guest addresses and physical memory. Under contention, ESXi can use transparent page sharing, ballooning, memory compression, and swapping. These mechanisms have different performance costs and should be monitored rather than assumed to be equivalent.

Physical networking uses switches, ports, NICs, VLANs, and cables. Virtual networking uses virtual switches, port groups, VMkernel adapters, virtual NICs, and physical uplinks. The physical switch and the vSphere configuration must agree on VLAN, speed, duplex, trunk, MTU, and failover behavior.

vSphere component roles

Inventory hierarchy

A typical inventory contains datacenters, folders, clusters, hosts, resource pools, vApps, networks, datastores, and VMs. Inventory placement affects organization, permissions, alarms, and resource management. A folder is organizational; a resource pool controls compute allocation; a vApp groups related application VMs and can define startup order.

2. ESXi deployment and basic host administration

ESXi is installed directly on supported server hardware. Before installation, verify CPU virtualization support, memory, storage controllers, network adapters, firmware, boot media, and the VMware hardware compatibility information for the intended release.

Installation and first configuration

1. Boot from the ESXi installation media.
2. Select the target disk and keyboard layout.
3. Set the root password and complete installation.
4. Reboot from the installed disk.
5. Use the Direct Console User Interface, or DCUI, to configure the management network.
6. Set the hostname, IPv4 address, subnet mask, default gateway, DNS servers, and DNS domain.
7. Configure time services and verify NTP reachability.
8. Apply an appropriate license and confirm host connectivity from a management client.

The management VMkernel interface carries host management traffic. DNS forward and reverse records and consistent time are especially important when adding hosts to vCenter Server and configuring authentication.

esxcli system version get
esxcli network ip interface ipv4 get
esxcli network nic list
esxcli network ip dns server list
esxcli hardware cpu list
esxcli system maintenanceMode set --enable true

Use the vSphere Client or vSphere Web Client to review host status, hardware health, datastores, networking, licensing, services, and recent tasks. The Client Integration Plug-in supports browser-based operations such as client integration and certain guest or console functions; install it only from the compatible vSphere software distribution.

3. vCenter Server deployment, inventory, and SSO

vCenter Server communicates with ESXi hosts and provides centralized inventory, permissions, alarms, clusters, templates, vMotion coordination, HA, DRS, and historical performance data. The vCenter Server Appliance packages vCenter services in an appliance deployment and can be suitable for lab or supported production scenarios.

Deployment approaches

• Simple Install: installs the required vCenter components in a guided sequence with fewer manual decisions.
• Custom Install: allows separate choices for services, network settings, database configuration, SSO, and deployment topology.

In vSphere 5, services can include vCenter Server, vCenter Single Sign-On, Web Client services, and the historical Inventory Service role. Follow the appliance installer requirements for IP addressing, DNS, hostnames, passwords, storage, and service startup.

1. Deploy and configure the appliance or install the selected vCenter components.
2. Configure SSO and an identity source.
3. Open the management client and create a datacenter.
4. Create folders and, where appropriate, a cluster.
5. Add ESXi hosts by hostname or IP address.
6. Review certificates, credentials, licensing, host state, networking, and datastore visibility.

Single Sign-On and identity integration

vCenter Single Sign-On (SSO) authenticates users and issues tokens that allow authorized access to vSphere services. An identity source is a directory or authentication provider containing users and groups. Active Directory integration lets vCenter use domain identities instead of maintaining separate local accounts for every administrator.

SSO deployment modes in vSphere 5 determine whether sites share authentication services and how components communicate. Configure password policies, token lifetime and renewal controls, administrator accounts, and directory connectivity according to the environment’s security requirements. Confirm time synchronization and name resolution before diagnosing authentication failures.

4. Virtual machine architecture and lifecycle

A VM consists of a configuration, virtual hardware, storage files, virtual NICs, and a guest operating system. Common files include:

• VMX: text configuration file describing virtual hardware and VM options.
• VMDK: descriptor and data files representing virtual disks.
• NVRAM: stores firmware settings.
• Log files: record VM events and device activity.
• VM swap file: supports VM memory management when required.
• Snapshot files: delta disks and metadata that track changes after a snapshot.

Virtual hardware versions determine which devices and capabilities are available. Configurable hardware includes vCPUs, memory, virtual disks, SCSI controllers, virtual NICs, CD/DVD devices, USB devices, boot firmware, and console options. Change hardware only after checking guest operating system support and whether the VM must be powered off.

Virtual disks and adapters

Choose a virtual network adapter based on guest support and required performance. Install VMware Tools after the guest operating system because Tools improves drivers, time coordination options, clean shutdown, heartbeat reporting, and other integration features. Install the appropriate package for Windows or Linux and verify the service is running.

Basic VM workflow

1. Create a VM and select its guest operating system and virtual hardware version.
2. Attach a virtual disk and connect a virtual CD/DVD device to installation media.
3. Connect the VM NIC to the correct port group.
4. Power on the VM, use the console, and install the guest operating system.
5. Install VMware Tools and validate networking, time behavior, and clean power operations.
6. Use guest shutdown whenever possible; reserve forced power-off for unresponsive systems.
7. Remove a VM from inventory only when its files must remain; delete from disk only after checking backups, dependencies, and ownership.

5. Virtual networking

A virtual switch forwards frames between VM NICs, VMkernel adapters, and physical uplinks. A port group defines connection settings for a class of ports. A VMkernel adapter provides host services such as management, vMotion, iSCSI, and storage traffic.

Network configuration and failure handling

Configure management, VM, vMotion, and storage traffic on suitable port groups. Apply VLAN IDs that match the physical switch configuration. Use redundant uplinks where possible, select a load-balancing algorithm, define active and standby order, and choose link-status or beacon-based failover detection as appropriate.

Security policies include promiscuous mode, MAC address changes, and forged transmits. These should normally remain restricted; enable exceptions only for documented appliances or workloads. Traffic shaping controls egress bandwidth and burst behavior according to the configured policy.

esxcli network vswitch standard list
esxcli network ip interface list
vmkping <destination-address>

For a network incident, compare the VM port group VLAN with the physical trunk, inspect uplink failover order, verify NIC teaming, check speed and duplex, and examine physical switch-port and NIC errors. Test each VMkernel path separately when diagnosing management, vMotion, or iSCSI connectivity.

6. Storage foundations and datastores

ESXi can consume block storage through Fibre Channel, FCoE, and iSCSI, or file storage through NFS. A datastore provides the namespace and management boundary used for VM configuration files, virtual disks, logs, snapshots, and templates.

VMFS is a clustered file system designed for shared block storage. Datastore operations include creating, browsing, expanding, mounting, unmounting, and removing. Unmounting should precede removal, and administrators must check VM registration, templates, snapshots, swap files, HA heartbeat use, RDM mappings, and backup dependencies before deleting a datastore.

Virtual SAN in the vSphere 5 context aggregates local disks from hosts into a distributed datastore. It requires compatible hosts, disks, networking, licensing, and a supported cluster design. Validate disk groups, network separation, fault-domain expectations, capacity, and health before enabling it.

7. iSCSI, NFS, Fibre Channel, and FCoE

iSCSI configuration

iSCSI carries SCSI commands over IP. An initiator is the ESXi client; a target provides storage; a LUN is a logical block device; and an IQN is an iSCSI qualified name used to identify endpoints. CHAP provides optional challenge-response authentication.

1. Create dedicated VMkernel ports and port groups for iSCSI traffic.
2. Configure VLANs, IP addresses, routing, MTU, and physical switch paths.
3. Enable a software iSCSI adapter or configure a hardware initiator.
4. Add dynamic send-target discovery or static target entries.
5. Configure CHAP consistently on the initiator and storage target if required.
6. Rescan storage adapters, verify paths and LUN presentation, and create or mount a VMFS datastore.

esxcli storage core adapter list
esxcli storage core path list
esxcli storage core device list
esxcli storage core adapter rescan --all
esxcli iscsi adapter list
esxcli iscsi adapter discovery sendtarget add
esxcli storage filesystem list

NFS and Fibre Channel

For NFS, configure a reachable export, verify server-side access controls, create the datastore with the correct server and export path, and confirm that every required host can mount it.

Fibre Channel uses host bus adapters (HBAs), FC switches, storage processors, zoning, and LUN presentation. Zoning controls which initiators and targets can communicate; LUN masking controls which hosts can see a presented LUN. FCoE uses compatible converged adapters and Ethernet-based fabric components, so validate both storage and network designs.

8. Templates, cloning, and guest customization

A template is a master VM image intended for repeatable deployment. A clone is a copy of a VM. A guest customization specification applies unique identity and network settings during deployment.

1. Build and patch a baseline VM.
2. Install VMware Tools and remove machine-specific state where required.
3. Convert the VM to a template or clone it for a one-off copy.
4. Create a customization specification with hostname, credentials, licensing, and network settings.
5. Deploy several VMs and verify unique names, identifiers, addresses, and guest connectivity.

Use templates for controlled, repeatable provisioning; use clones for independent copies or development branches; use customization specifications to prevent duplicate guest identities and addresses.

9. VM settings, disks, and boot operations

Editing VM settings can include changing CPU and memory, adding controllers, attaching disks, adding NICs, connecting ISO media, enabling VMware Tools options, and configuring boot delay. Some changes require the VM to be powered off. Adding an RDM exposes a raw LUN through a mapping file and should be selected only for a documented requirement.

Increasing a virtual disk is only the first step. The guest partition and file system must also be extended with guest operating system tools. Thin disks can inflate as blocks are written, so monitor datastore free space and provisioning reports. Boot delay is useful when entering firmware or boot-loader menus during troubleshooting.

10. vMotion and virtual machine migration

vMotion moves a running VM between compatible hosts. Memory pages are copied over a vMotion-enabled VMkernel network while the VM continues running. A brief switchover transfers the final changed pages and execution state to the destination host.

CPU identification tools help compare host feature sets. The NX/XD bit must be consistently available or masked appropriately, and EVC can present a common CPU baseline when mixing processor generations. Create vMotion VMkernel networking, test it with vmkping, verify VLAN and MTU consistency, then perform the migration and inspect task details.

11. Snapshots and recovery operations

A snapshot preserves a point-in-time view of a VM’s virtual disks by introducing delta files for subsequent writes. It is not a complete backup and should not be retained indefinitely. Snapshot chains consume datastore space, can increase I/O overhead, and complicate recovery and backup operations.

1. Create a snapshot before a narrowly defined change, documenting its purpose and owner.
2. Test the change and monitor delta-file growth.
3. Revert only when the loss of changes since the snapshot is acceptable.
4. Delete snapshots after validation; deletion merges delta data into the base disk.
5. Use consolidation when snapshot metadata has been removed but delta disks remain.

Before consolidation, verify datastore free space, check for locked disks, pause conflicting backup or replication tasks, and monitor the consolidation task until completion.

12. vApps

A vApp is a logical container for related VMs, such as an application server, database server, and web server. It can group permissions and resource settings and define startup order and delays. Startup order describes orchestration; it does not replace application-level dependency checks.

13. Security, authentication, and authorization

Use the ESXi Security Profile to review services and firewall rules. The ESXi firewall should expose only required services. Lockdown Mode restricts direct host access so administration is directed through vCenter according to the configured exception behavior; test recovery access before enabling it.

Hosts can be joined to Active Directory for centralized authentication. vSphere authorization uses users, groups, roles, privileges, objects, and permissions. A role is a named collection of privileges. Permission inheritance determines whether a permission applies to child inventory objects. Assign permissions to groups, use least privilege, and create custom roles only when built-in roles do not fit.

14. Compute, memory, and resource management

Virtual SMP lets a VM use multiple vCPUs. Configure vCPU count based on workload need, not simply on the number of host processors. Hyperthreading exposes logical processors that share physical execution resources; ESXi schedules them with awareness of this relationship, but logical processors are not equivalent to additional physical cores.

Memory overcommitment occurs when configured VM memory exceeds immediately available physical memory. Reclamation can progress from transparent page sharing to ballooning, compression, and host swapping. Use performance charts to determine whether the guest, VM, resource pool, or host is under pressure.

Resource pools form a hierarchy. A pool can have shares, reservations, limits, and an expandable reservation. An expandable reservation allows a child to obtain unreserved capacity from its parent when the parent has capacity. Check the entire hierarchy before concluding that a VM is entitled to a particular amount of resource.

15. Performance monitoring, logs, and alarms

vCenter performance charts provide real-time and historical views at host, cluster, VM, datastore, disk, and network levels. Monitor CPU utilization and ready time, active and consumed memory, ballooning, compression and swapping, datastore latency and capacity, and network throughput, drops, and errors.

Log levels control the amount of diagnostic detail recorded by vCenter services. Increase detail temporarily and deliberately because verbose logging can increase storage use and complicate analysis.

An alarm contains a trigger, condition, tolerance or threshold, action, and notification. Useful alarms include host connection state, CPU or memory pressure, datastore capacity, and network or hardware health. Configure email or script actions where supported, test them, and acknowledge alarms only after recording the cause and response.

vCenter Operations Manager provides broader performance and capacity analysis than individual charts, including health trends and resource-congestion views. It complements, rather than replaces, direct investigation of host, guest, storage, and network metrics.

16. vSphere High Availability

vSphere HA restarts affected VMs on surviving hosts after a host failure. Create a cluster, enable HA, verify host agent health, configure Host Monitoring, and choose an Admission Control policy that reserves capacity for the expected failure scenario.

• Host Monitoring: detects host failure or isolation through management networks.
• Datastore heartbeating: provides an additional signal when management connectivity is impaired.
• VM Monitoring: can restart a VM when VMware Tools heartbeats indicate that the guest is unresponsive.
• VM overrides: allow selected VMs to use different restart priority or monitoring settings.

Use redundant management and heartbeat paths where possible. Review HA cluster health, admission-control status, host isolation response, restart priorities, and failover events after network maintenance or testing.

17. Fault Tolerance and replication

vSphere Fault Tolerance (FT) provides continuous availability for supported VMs by running a primary and secondary execution path. VMware vLockstep keeps the secondary synchronized with the primary so the secondary can continue after a failure. FT requires compatible hardware, networking, storage, VM configuration, and licensing, and it has workload and device constraints.

vSphere Replication copies VM changes to another supported location on a configured schedule. It supports a recovery workflow but is not the same as synchronous FT or a backup system. Define recovery objectives, target storage, permissions, network capacity, and test recovery procedures.

18. DRS, EVC, rules, and maintenance mode

Distributed Resource Scheduler (DRS) evaluates cluster resource demand and recommends or performs VM placement changes using vMotion. Automation levels range from manual recommendations to increasingly automatic placement and migration behavior, depending on configuration.

Enhanced vMotion Compatibility (EVC) masks selected CPU features so hosts with different processor generations can present a common baseline. Enable the appropriate EVC mode before mixing host generations, and confirm that every host supports the selected baseline.

Preferential rules guide placement when possible; required rules constrain placement and can prevent migration or failover. Enter maintenance mode before servicing a host so workloads are evacuated or powered down according to cluster capabilities. DRS uses vMotion to rebalance, HA restarts VMs after failures, and maintenance mode coordinates planned evacuation; these functions have different triggers and requirements.

19. Practical lab sequence

1. Install ESXi on a supported lab server and configure management networking, DNS, NTP, licensing, and host access.
2. Deploy vCenter Server Appliance, create a datacenter and cluster, and add two ESXi hosts.
3. Configure an identity source, join hosts to Active Directory where appropriate, and assign an operations group a least-privilege custom role.
4. Create standard-switch port groups for management, VM, vMotion, and iSCSI traffic. Apply VLAN IDs, redundant uplinks, failover order, security policies, and traffic shaping.
5. Configure software iSCSI with dedicated VMkernel ports, discover a target, apply CHAP, rescan adapters, verify paths, and create VMFS storage.
6. Mount an NFS export and compare its management and migration behavior with VMFS.
7. Create a Windows or Linux VM, install VMware Tools, test console access, networking, time behavior, and clean shutdown.
8. Convert a baseline VM to a template, create a customization specification, and deploy multiple uniquely named VMs.
9. Expand a thin virtual disk and extend the guest partition and file system.
10. Perform vMotion and Storage vMotion, then validate the VM, datastore, network, and task history.
11. Create, revert, delete, and consolidate a test snapshot while monitoring datastore capacity.
12. Create resource pools, configure shares and reservations, and observe behavior under controlled contention.
13. Create CPU, memory, datastore-capacity, and host-connection alarms with tested notifications.
14. Configure HA and DRS, test maintenance mode, and observe failover or automated placement behavior.
15. Create VM anti-affinity and VM-to-host rules for redundant or specialized workloads.

20. Troubleshooting and exam-relevant checks

Host cannot be added to vCenter

• Test management reachability and required service availability.
• Verify forward and reverse DNS and synchronized time.
• Confirm administrative credentials and inspect certificate prompts.
• Check whether the host is already managed elsewhere and review firewall settings.

vMotion fails

• Confirm vMotion-enabled VMkernel interfaces and test the path with vmkping.
• Check VLAN, MTU, uplink, and physical-switch consistency.
• Verify shared datastore visibility where required.
• Check CPU compatibility, NX/XD settings, EVC, bandwidth, and destination host configuration.

iSCSI LUN or datastore is missing

• Verify VMkernel binding, iSCSI VLAN routing, target discovery, and CHAP credentials.
• Check storage-side LUN masking and host presentation.
• Rescan adapters and inspect devices, paths, and multipathing.

Snapshot consolidation is required

• Check datastore free space and delta-file growth.
• Inspect locks and stop conflicting backup or replication activity.
• Monitor the consolidation task and review logs if it fails.

HA does not restart a VM

• Review cluster HA state, host agent health, management redundancy, and heartbeat datastores.
• Check Admission Control capacity, VM restart priority, VM overrides, and host isolation response.

Memory performance is poor

• Compare active, consumed, granted, ballooned, compressed, and swapped memory.
• Review host overcommitment, reservations, limits, shares, guest pressure, and resource-pool constraints.

VM network connectivity is intermittent

• Compare port-group VLAN IDs with physical trunk configuration.
• Inspect uplink failover, NIC teaming, load balancing, speed, duplex, and security policies.
• Check physical NIC and switch-port errors.

DRS does not move workloads

• Check that DRS and the selected automation level are enabled.
• Verify vMotion readiness, cluster capacity, migration thresholds, EVC, and CPU compatibility.
• Review affinity, anti-affinity, reservations, limits, and resource-pool constraints.

21. Knowledge checks

Use these checks after completing the corresponding labs. Explain each answer rather than memorizing a menu location.

• Networking and storage: Which traffic requires a VMkernel adapter? How must a VLAN configured on a port group relate to the physical switch? What is the difference between an iSCSI initiator, target, IQN, and LUN?
• VM operations: Why is a snapshot not a backup? What guest-side task follows a virtual disk expansion? When is a template preferable to a clone?
• Migration: Which requirements distinguish vMotion from Storage vMotion? How do CPU compatibility and EVC affect a migration?
• Security: How do a privilege, role, permission, and inheritance differ? Why should permissions usually be assigned to groups?
• Availability and scalability: How do HA, FT, replication, and DRS address different operational problems? What happens when a required DRS rule conflicts with evacuation?

22. Quick reference

vim-cmd vmsvc/getallvms
vim-cmd vmsvc/power.getstate <vmid>
vim-cmd vmsvc/power.on <vmid>
vim-cmd vmsvc/power.off <vmid>
vim-cmd vmsvc/snapshot.get <vmid>

For related infrastructure fundamentals, continue with the VCP5-DCV course, review the Free Linux Course, or study networking foundations in the CCENT ICND1 course.