madonaya

VMware vSphere leverages the power of virtualization to transform datacenters into simplified cloud computing infrastructures and enables IT organizations to deliver flexible and reliable IT services. VMware vSphere virtualizes and aggregates the underlying physical hardware resources across multiple systems and provides pools of virtual resources 220 702 to the datacenter.
As a cloud operating system, VMware vSphere manages large collections of infrastructure (such as CPUs, storage, and networking) as a seamless and dynamic operating environment, and also manages the complexity of a datacenter. The following component layers make up VMware vSphere:
Infrastructure Services

Infrastructure Services are the set of services provided to abstract, aggregate, and allocate hardware or infrastructure resources. Infrastructure Services can be categorized into:
■

VMware vCompute—the VMware capabilities that abstract away from underlying disparate server resources. vCompute services aggregate these resources across many discrete servers and assign them to applications.
■

VMware vStorage—the set of technologies that enables the most efficient use and management of storage in virtual environments.
■

VMware vNetwork—the set of technologies that simplify and enhance networking in virtual environments.
Application Services

Application Services are the set of services provided to ensure availability, security, and scalability for applications. Examples include HA and Fault Tolerance.
VMware vCenter Server

VMware vCenter Server provides a single point of control of the datacenter. It provides essential datacenter services such as access control, performance monitoring, and configuration.
Clients

Users can access the VMware vSphere datacenter through clients such as the vSphere Client or Web Access through a Web browser.connections is running headless.
heartbeat
A signal emitted at regular intervals by software to demonstrate that it is still active. The signal emitted by a Level 2 Ethernet transceiver at the end of every packet to show that the collision-detection circuit is still connected.
host
A computer that uses virtualization software to run virtual machines. Also called the host machine or host computer. The physical computer on which the virtualization (or other) software is installed.
host agent
Software that performs actions on behalf of a remote client when installed on a virtual machine host.
host-based licensing
In ESX server software, one of two modes for licensing VMware software. License files reside on the host. Feature availability is tied strictly to the host in which the file resides. See also server-based licensing.
hosted products
VMware products (including Workstation, VMware Player, VMware Server, VMware ACE, and Lab Manager) that run as applications on physical machines with operating systems such as Microsoft Windows or Linux. See also hypervisor.
host-only networking
In hosted products, a type of network connection between a virtual machine and the host. With host-only networking, a virtual machine is connected to the host on a private network, which normally is not visible outside the host. Multiple virtual machines configured with host-only networking on the same host are on the same network. See also NAT (network address translation).
host operating system
An operating system that runs on the host machine. See also guest operating system.
hot fix
An installable file that resets a user’s password, renews an expired virtual machine, or enables a copy-protected virtual machine to run from a new location.
hyperthreading
A technology that allows a single physical processor to behave like two logical processors. The processor can run two independent applications at the same time.
hypervisor
A platform that allows multiple operating systems to run on a host computer at the same time.
image-level (volume-level) backup
A process that backs up an entire storage volume.
inactive
A feature is not currently functioning because of a constraint other than user choice. Can also be used when the feature is turned off by indirect user choice. For example, a feature can be “disabled” by direct user choice or made “inactive” by indirect user choice.
incremental backup
A process that backs up only those files that have changed since the last backup, whether it is a full or incremental backup.
independent disk
A type of virtual disk that is not affected by snapshots. You can configure independent disks in persistent and nonpersistent modes. See also nonpersistent mode, persistent mode.
internal storage configuration
Storage virtualization devices are those that aggregate capacity from multiple heterogeneous arrays and manage a logical representation of this capacity. Models that belong to this group are array-based controllers only and not server-based or switch-based controllers. Most of these devices can also have physical disks installed internally that are presented to hosts as physical SAN LUNs, which are not virtualized. When these devices are supported in the internal storage configuration, this refers to the LUNs presented from disks internal to the array and not those virtualized from other arrays which they aggregate.
inventory
A hierarchical structure used by the vCenter Server or the host agent to organize managed entities. This hierarchy is a list of all the monitored objects in vCenter Server.
inventory mapping
Mapping between resource pools, networks, and virtual machine folders on the protection site and their destination counterparts on the recovery site.
IP storage
Any form of storage that uses TCP/IP network communication as its foundation. Both Network File System (NFS) and iSCSI storage can be used as virtual machine datastores. NFS can also be used for direct mounting of .ISO files for presentation to virtual machines as CD-ROM discs.
ISV (independent software vendor)
A company that develops and sells software for use on other companies’ platforms. Includes systems management vendors, imaging and provisioning vendors, storage management vendors, and so on.
LAN segment
A private virtual network that is available only to virtual machines within the same team. See also team, virtual network.
legacy virtual machine
A virtual machine supported by the product in use but not current for that product.
license activation code (LAC)
9L0-403 /> A unique code associated with one or more VMware products purchased. You receive this code after your order is processed. If you purchase your products from a VMware partner, you receive your license activation code after you register your partner activation code for your VMware account.
license file
A text file determining the license mode and entitlement to licensed features.
license key
An encrypted block of text within a license file, determining entitlement to one specific licensed feature.
license mode
The method used for licensing VMware software. A license file can be located on an ESX server host or on a license server. vCenter Server uses server-based licensing. ESX server licensing can be server-based or host-based at the option of the system administrator. See also host-based licensing, server-based licensing.
link
A hyperlink that contains a path to another object. As on the Web, links can be relative to the current object path, relative to the current server’s object root, or on a specific server, as interpreted by the current client’s host name resolver.
linked clone
A copy of the original virtual machine. The copy must have access to the parent virtual machine’s virtual disks. The linked clone stores changes to the virtual disks in a separate set of files. See also full clone.
LMHOSTS (LAN Manager HOSTS) file
A text file in a Windows network that maps NetBIOS host names to IP addresses.
lockout
See administrative lockout.
LUN (logical unit number)
An identifier for a disk volume in a storage array.
LUN Masking
A process that is used for permission management to make a LUN available to some hosts and not to other hosts. Also referred to as Selective Storage Presentation, Access Control, and Partitioning, depending on the vendor.
managed entity
A managed object that is present in the inventory. See also inventory, managed object.
managed object
An object that resides on a server and is passed between the client and the Web service only by reference. A managed object has operations associated with it but might not have properties. See also.
managed object reference
A data object created to uniquely identify a managed object.
message
A data element that is used by an operation to carry data. It lists the data types exchanged between the Web service and the client.
migration
The process of moving a virtual machine between hosts. Unless VMotion or Storage VMotion is used, the virtual machine must be powered off when you migrate it. See also migration with VMotion
migration with VMotion
The process of moving a virtual machine that is powered on and meets selected requirements, including the activation of VMotion on both the source and target hosts. When you migrate a virtual machine using VMotion, the operations of the virtual machine can continue without interruption.
MKS (mouse, keyboard, screen)
A set of basic input-output services for user interaction with a virtual machine.
MoRef (managed object reference)
A managed object has a MoRef that is server-specific. The MoRef is a pointer to an object.
MSCS (Microsoft Cluster Service)
Software that distributes data among the nodes of the cluster. If one node fails, other nodes provide failover support for applications such as databases, file servers, and mail servers.
name
A path (such as a URL) that refers to an object or the name of an item of information in the server.
NAS (network-attached storage)
A complete storage system that is designed to be attached to a traditional data network.
NAT (network address translation)
In hosted networking, a type of network connection that enables you to connect your virtual machines to an external network when you have only one IP network address and the host computer uses that address. The VMware NAT device passes network data between one or more virtual machines and the external network. It identifies incoming data packets intended for each virtual machine and sends them to the correct destination. See also host-only networking.
nbtstat command
9L0-510 A diagnostic command that helps determine how a system name or IP address is resolved. Because it can display current connections using NetBIOS over TCP/IP, nbtstat is useful for determining whether Windows systems are online from a NetBIOS view. See also NetBIOS (network basic input/output system).

o Back up the VirtualCenter 2.x SSL certificates. %ALLUSERSPROFILE%Application DataVMwareVMware VirtualCenter or
%ALLUSERSPROFILE%VMwareVMware VirtualCenter.
o Note any non-default settings, such as the IP address, the database DSN, user name, password, and assigned ports.
o Create a backup co 220 701 py of vpxd.cfg.
o The database upgrade log is at %TEMP%VCDatabaseUpgrade.log.
o By default, a vCenter Server creates a maximum of 10 simultaneous database connections.
o Datastores and networks have their own set of privileges that control access to them.
o Users are initially granted the No Access role on all new managed objects, including datastores and networks. All existing objects in vCenter
maintain their permissions after the upgrade.
o The upgrade process uses the datacenter's “Read-only” privilege.
o If the “Read-only” privilege is nonpropagating (not inherited by child objects), VMware assumes access privileges should not be assigned
to datastores and networks.
o If the “Read-only” privilege is propagating (inherited by child objects), VMware assumes access privileges should be assigned to
datastores and networks so users can view them and perform basic operations that require access.
o The “Read-only” propagating permission on a datacenter, as well as all other permissions you have set, will continue to work as expected after
the upgrade.
o You must change “Read-only” nonpropagating datastore permissions to propagating datastore permissions in order for users to access the
datastore. You can assign datastore permissions on datastore or folders containing datastore. The same goes for Network permissions.
o The “Database Consumer” sample role assigns the “Allocate Space” privilege to the datastore. “Network Consumer” sample role assigns the
“Assign Network” privilege.
o Host Update Utility does not upgrade VMFS datastores or VM
o Update Manager supports mass remediation.
o During host upgrades using the Update Manager, static IP addresses are a requirement.
o The upgrade to ESXi4 & ESX4 preserves almost all configuration data, including your networking, security, and storage configuration. The only
configuration not preserved is related to licensing.
o For ESX only, the upgrade reuses the existing /boot partition to hold the ESX 4.0 boot files. After the upgrade, the ESX 3.x installation is
mounted in the new ESX 4.0 installation under the /esx3-installation directory.
o Backup the ESX Host Configuration:
o Back up the files in the /etc/passwd, /etc/groups, /etc/shadow, and /etc/gshadow directories.
o Back up any custom scripts.
o Back up your .vmx files.
o Back up local images, such as templates, exported VMs, and .iso files.
o Backup the ESXi Host Configuration: vicfg-cfgbackup --server <ESXi-host-ip> --portnumber <port_number> - 220 702 -
protocol <protocol_type> --username username --password <password> -s <backup-filename>
o You cannot perform an in-place upgrade from ESX to ESXi (or from ESXi to ESX).
o The only ESX 2.x version that has upgrade support is ESX 2.5.5 – you can perform a migration upgrade with or without VMotion.
o Direct, in-place upgrade from ESX 2.5.5 to ESX 4.0 is not supported, even if you upgrade to ESX 3.x as an intermediary step. The default ESX
2.5.5 installation creates a /boot partition that is too small to enable upgrades to ESX 4.0. As an exception, if you have a non-default ESX 2.5.5
installation on which at least 100MB of space is available on the /boot partition, you can upgrade ESX 2.5.5 to ESX 3.x and then to ESX 4.0.
o The upgrade logs are here:
o /esx3-installation/esx4-upgrade/
o /var/log/vmware/
o For an unsuccessful ESX upgrade:
o /esx4-upgrade/
o /var/log/vmware/
o You may need to reconnect the host to vCenter Server and assign an upgraded license to your product within 60 days after the upgrade.
o The host sdX devices might be renumbered after the upgrade.
o You must convert LUN masking to the claim rule format. Run the esxcli corestorage claimrule convert command. It converts
the /adv/Disk/MaskLUNs advanced configuration entry in esx.conf to claim rules with MASK_PATH as the plug-in.
o Web Access service is disabled after you upgrade the host.
o vSphere Web Access is not supported on ESXi hosts.
o 60-day evaluation count down starts even if the host is licensed and you are not using evaluation mode.
o One advantage of using evaluation mode is that it offers full feature functionality.
o After you determine that the ESX 220 701 4.0 upgrade is stable, you can remove the ESX 3.x boot option from the ESX 4.0 bootloader menu to disable
the ability to roll back to ESX 3.x. If you deselected the rollback option, this procedure is not applicable. Run the cleanup-esx3 command
with the optional -f (force) flag.
o The cleanup-esx3 script removes the following files and references from the ESX 4.0 host:
o ESX 3.x references in the /etc/fstab directory
o ESX 3.x boot files in the /boot directory
o The rollback-to-esx3 script in the /usr/sbin/ directory

A typical VMware vSphere datacenter consists of basic physical building blocks such as x86 virtualization servers, storage networks and arrays, IP networks, a management server, and desktop clients.
This physical topology of the vSphere datacenter is illustrated in Figure 2.
Figure 2. VMware vSphere D 640 802 Dumps atacenter Physical Topology
The components that make up the vSphere datacenter topology are:
Computing servers

Industry standard x86 servers that run ESX/ESXi on the bare metal. ESX/ESXi software provides resources for and runs the virtual machines. Each computing server is referred to as a standalone host in the virtual environment. You can group a number of similarly configured x86 servers with connections to the same network and storage subsystems to provide an aggregate set of resources in the virtual environment, called a cluster.
Storage networks and arrays

Fibre Channel SAN arrays, iSCSI SAN arrays, and NAS arrays are widely used storage technologies supported by VMware vSphere to meet different datacenter storage needs. The storage arrays are connected to and shared between groups of servers through storage area networks. This arrangement allows aggregation of the storage resources and provides more flexibility in provisioning them to virtual machines.
IP networks

Each computing server can have multiple Ethernet network interface cards (NICs) to provide high bandwidth and reliable networking to the entire VMware vSphere datacenter.
vCenter Server
640-802
vCenter Server provides a single point of control to the datacenter. It provides essential datacenter services such as access control, performance monitoring, and configuration. It unifies the resources from the individual computing servers to be shared among virtual machines in the entire datacenter. It does this by managing the assignment of virtual machines to the computing servers and the assignment of resources to the virtual machines within a given computing server based on the policies that the system administrator sets.
Computing servers continue to function even in the unlikely event that vCenter Server becomes unreachable (for example, if the network is severed). They can be managed separately and continue to run the virtual machines assigned to them based on the resource assignment that was last set. After connection to vCenter Server is restored, it can manage the datacenter as a whole again.
Management clients

640 802 braindumps VMware vSphere provides several interfaces for datacenter management and virtual machine access. These interfaces include VMware vSphere Client (vSphere Client), web access through a web browser, vSphere Command-Line Interface (vSphere CLI), or vSphere Management Assistant (vMA).

This topic introduces the components of VMware vSphere.
VMware vSphere includes the following components:
VMware® ESX and VMware® ESXi

A virtualization layer run on physical servers that abstracts processor, memory, storage, and resources into multiple virtual machines.
Two versions of ESX are available:
■

vcp 4 VMware ESX 4.0 contains a built-in service console. It is available as an installable CD-ROM boot image.
■

VMware ESXi 4.0 does not contain a service console. It is available in two forms: VMware ESXi 4.0 Embedded and VMware ESXi 4.0 Installable. ESXi 4.0 Embedded is firmware that is built into a server’s physical hardware. ESXi 4.0 Installable is software that is available as an installable CD-ROM boot image. You install the ESXi 4.0 Installable software onto a server’s hard drive.
VMware® vCenter Server

The central point for configuring, provisioning, and managing virtualized IT environments.
VMware® vSphere Client

An interface that allows users to connect remotely to vCenter Server or ESX/ESXi from any Windows PC.
VMware® vSphere Web Access

A Web interface that allows virtual machine management and access to remote consoles.
VMware® Virtual Machine File System (VMFS)

A high performance cluster file system for ESX/ESXi virtual machines.
VMware® Virtual SMP

Feature that enables a single virtual machine to use multiple physical processors simultaneously.
VMware® VMotion and Storage VMotion

VMware VMotion enables the live migration of running virtual machines from one physical server to another with zero down time, continuous service availability, and complete transaction integrity. Storage VMotion enables the migration of virtual machine files from one datastore to another without service interruption. You can choose to place the virtual machine and all its disks in a single location, or select separate locations for the virtual machine configuration file and each virtual disk. The virtual machine remains on the same host during Storage VMotion.
Migration with VMotion - Moving a powered-on virtual machine to a new host. Migration with VMotion allows you to move a virtual machine to a new host without any interruption in the availability of the virtual machine. Migration with VMotion cannot be used to move virtual machines from one datacenter to another.
Migration with Storage VMotion - Moving the virtual disks or configuration file of a powered-on virtual machine to a new datastore. Migration with Storage VMotion allows you to move a virtual machine's storage without any interruption in the availability of the virtual machine.
VMware® High Availability (HA)

Feature that provides high availability for app vmware vcp 4 lications running in virtual machines. If a server fails, affected virtual machines are restarted on other production servers that have spare capacity.
VMware® Distributed Resource Scheduler (DRS)

Feature that allocates and balances computing capacity dynamically across collections of hardware resources for virtual machines. This feature includes distributed power management (DPM) capabilities that enable a datacenter to significantly reduce its power consumption.
VMware® Consolidated Backup (Consolidated Backup)

Feature that provides a centralized facility for agent-free backup of virtual machines. It simplifies backup administration and reduces the impact of backups on ESX/ESXi performance.
VMware® vSphere SDK

Feature that provides a standard interface for VMware and third-party solutions to access the VMware vSphere.
VMware® Fault Tolerance

When Fault Tolerance is enabled for a virtual machine, a secondary copy of the original (or primary) virtual machine is created. All actions completed on the primary virtual machine are also applied to the secondary virtual machine. If the primary virtual machine becomes unavailable, the secondary machine becomes active, providing continual availability.
vNetwork Distributed Switch (DVS)

Feature that includes a distributed virtual switch (DVS), which spans many ESX/ESXi hosts enabling significant reduction of on-going network maintenance activities and increasing network capacity. This allows virtual machines to maintain consistent network configuration as they migrate across multiple hosts.
Host Profiles

Feature that simplifies host configuration management through user-defined configuration policies. The host profile policies capture the blueprint of a known, validated host configuration and use this to configure networking, storage, security, and other settings across multiple hosts. The host profile policies also monitor compliance to standard host configuration settings across the datacenter. Host profiles reduce manual steps i 640 802 nvolved in configuring a host and can help maintain consistency and correctness across the datacenter.
Pluggable Storage Array (PSA)

A storage partner plug-in framework that enables greater array certification flexibility and improved array-optimized performance. PSA is a multipath I/O framework allowing storage partners to enable their array asynchronously to ESX release schedules. VMware partners can deliver performance-enhancing multipath load-balancing behaviors that are optimized for each array.

o When you restore the standard switch, a new virtual adapter is created and the management network uplink that is currently connected to
vNetwork Distributed Switch is migrated to the new virtual switch.
o The software creates these partitions:
o One 4GB VFAT scratch partition for system swap.
o One VMFS3 partition on the remaining free space.
o The installer creates a 110MB dia vcp-410 gnostic partition for core dumps.
o The scratch partition is not required (but created by default during the installation). It is used to store vm-support output, which you need
when you create a support bundle.
o Lockdown mode prevents remote personnel from logging in to the ESXi host by using the root login name. By default, lockdown mode is
disabled.
o Resetting the configuration does not remove virtual machines on the ESXi host. After you reset the configuration defaults, the virtual
machines are not visible, but you can retrieve them by reconfiguring storage and reregistering the virtual machines.
o When you perform a configuration backup, the serial number is backed up with the configuration and is restored when you restore the
configuration. The serial number is not preserved when you run the Recovery CD (ESXi Embedded) or perform the repair operation (ESXi
Installable).
o When you restore the configuration, the target host must be in maintenance mode, which means all virtual machines (including the vSphere
CLI virtual appliance) must be powered off.
o Run the vicfg-cfgbackup command with the -s flag to save the host configuration to the specified backup filename.
o When you restore configuration data, the build number currently running on the host must be the same as the build number that was running
when you created the backup file. You can override this requirement by including the -f (force) flag with the vicfg-cfgbackup
command.
o Run the vicfg-cfgbackup command with the -l flag to load the host configuration from the specified backup file.
o You can restore the ESXi Installable software by running the ESXi installation CD in repair mode. All host configuration data is overwritten by
system defaults.
o During the repair operation, your existing ESXi 4.0 Installable VMFS datastore is preserved if it is in its original location on the ESXi 4.0 boot
disk, or if it is located on another disk (separate from the boot disk). If you changed the VMFS location on the boot dis vmware vcp 410 k, it is preserved if it is
located beyond the 900MB partition.
vSphere upgrade guide
o When you upgrade from ESX 3.x/ESXi 3.5 to ESX 4.0/ESXi 4.0, you can use either the vSphere Host Update Utility or vCenter Update Manager.
o EDIT – you can also use the upgrade script (esxupgrade.sh – KB 1009440). VMware doesn’t mention the option of a fresh install at any point;
they are pushing the upgrade option as much as possible. You can’t seem to do an upgrade with the ESX4 install CD.
o Host Update Utility is used for upgrading ESX 3.x/ESXi 3.5 standalone hosts to ESX 4.0/ESXi 4.0 and for patching ESXi 4.0 standalone hosts. It is
a standalone Microsoft Windows application recommended for smaller deployments with fewer than 10 ESX/ESXi hosts, without vCenter
Server or Update Manager.
o vCenter Update Manager is for upgrading and updating ESX/ESXi hosts that are managed in vCenter Server.
o Orchestrated upgrades can be used to upgrade the VM hardware and VMware Tools.
o No VMFS upgrade is required if you are upgrading from ESX 3.x
o You must upgrade VMware Tools before upgrading virtual hardware.
o After you upgrade to vCenter Server, you cannot revert to VirtualCenter 2.x. Take appropriate backups before starting the upgrade.
o Upgrade VirtualCenter 2.x to vCenter Server 4.0:
o Make sure your database is compatible
o Have required permissions
o Take a full backup of the VirtualCenter 2.x database
o Back up the VirtualCenter 2.x SSL certificates
o Install the vSphere Client
o vCenter Converter, upgrade
o vCenter Guided Consolidation upgrade
o Upgrade to vCenter Update Manager 4.0.
o Use vCenter Update Manager to upgrade ESX 3.x hosts to ESX 4.0. (or use host update utility)
o Use vCenter Update Manager to upgrade your VMs. vCenter Update Manager ensures that the VMware Tools upgrade and the virtual
hardware upgrade happen in the correct order
o Upgrade your product licenses
vmware vcp 410 > o ESX 2.x hosts cannot be added to clusters.
o Oracle 9i is no longer supported.
o Microsoft SQL Server 2000 is no longer supported.
o To Back Up VirtualCenter 2.x:
o Make a full backup of the VirtualCenter 2.x database

administrative lockout
A global setting that provides password protection for Windows hosts. Administrative lockout restricts users from creating new virtual machines, editing virtual machine configurations, and changing network settings.
alarm
An entity that monitors one or more Passed VCP410 properties of a virtual machine, such as CPU load. Alarms send notifications as directed by the configurable alarm definition.
allocated disk
A type of virtual disk in which all disk space for the virtual machine is allocated at the time the disk is created. This is the default type of virtual disk created by vCenter Server.
API (application programming interface)
A specified set of functions that enables you to access a service programmatically.
append mode
In ESX Server 2.x, a disk mode in which software running in the virtual machine appears to write changes to the disk. Changes are stored in a temporary .REDO file. If a system administrator deletes the redo-log file, the virtual machine returns to the state it was in the last time it was used in persistent mode. See also disk mode.
authorization role
A set of privileges grouped for convenient identification under names such as Administrator.
child
A managed entity grouped by a folder object or another managed entity. See also folder.
clone
(n.) A duplicate of a virtual machine. (v.) To make a copy of a virtual machine. When a clone is created, vCenter Server provides an option for customizing the guest operating system of that virtual machine. Hosted products distinguish between full clones and linked clones. See also full clone, linked clone.
cluster
A server group in the virtual environment. Clusters enable a high-availability solution.
cluster compute resource
An extended compute resource that represents a cluster of hosts available for backing virtual machines. See also compute resource.
compute resource
A managed object that represents either a single host or a cluster of hosts available for backing virtual machines. See also cluster compute resource.
configuration
See virtual machine configuration.
console
See service console, VMware virtual machine console.
current virtual machine
A virtual machine of the latest version supported by the product in use. See also legacy virtual machine.
customization
The process of applying new characteristic values to a virtual machine as it is being deployed from a template or cloned from another existing virtual machine. Customization options include changing the new virtual machine identification and network information.
custom networking
In hosted products, any type of network connection between virtual machines and the host that does not use the default bridged, host-only, or network address translation (NAT) configurations. For instance, different virtual machines can be connected to the host by separate networks or connected to each other and not to the host. Any network topology is possible.
daemon
A UNIX background program that runs unattended, performing services at a specified time or when some condition occurs. Analogous to a service in Windows.
datacenter
A required structure under which hosts and their associated virtual machines are added to the vCenter Server. vCenter Server supports multiple datacenters. A host can be managed under only one datacenter.
datacenter folder
An optional inventory grouping structure contained within the datacenter structure. A vCenter Server supports multiple datacenter folders. Datacenter folders can contain only datacenters and other datacenter folders.
datastore
Virtual representations of combinations of underlying physical storage resources in the datacenter. A datastore is the storage location (for example, a physical disk, a RAID, or a SAN) for virtual machine files.
DHCP (Dynamic Host Configuration Protocol)
A communications protocol that enables dynamic addressing. The software relieves administrators of the task of assigning an IP address to each device that connects to a network.
disabled
A state in which actions and features are deactivated. The feature is turned off by a choice the user makes.
disk arrays
Groups of multiple disk devices that are the typical SAN disk storage device. These arrays vary in design, capacity, performance, and other features.
disk mode
A property of a virtual disk that defines its external behavior (how the virtualization layer treats its data. It is invisible to the guest operating system. Available modes vary by product. See also persistent mode, nonpersistent mode and append mode.
distributed virtual port group
A dvPort group is a port group associated with a DVS. It specifies port configuration options for each member port. A dvPort group defines how a connection is made through the DVS to the network.
DNS (Domain Name System)
An Internet data query service that translates host names into IP addresses. Also called Domain Name Server or Domain Name Service.
dvPort (distributed virtual port)
A port on a DVS that connects to a host’s service console or VMkernel or to a virtual machine’s network adapter.
DVS
See vNetwork Distributed Switch (DVS)
enable
A state in which actions and features are active. The feature is turned on by a choice the user makes.
enumeration
The act of discovering resources available in a virtual machine environment. In particular, discovering all resources of a given type or a list of resources discovered by enumeration.
Ethernet switch
A physical switch that manages network traffic between machines. A switch has multiple ports, each of which can be connected to a machine or to another switch on the network. See also virtual switch.
EULA (end user license agreement)
The software license that details any restrictions placed on users.
event
An action that is of interest to vCenter Server. Each event triggers an event message. Event messages are archived in the vCenter Server database. Messages appear in two locations in the user interface: the Events option in the navigation bar and the Events tab for objects under the Inventory button.
event declaration
Type of event (alert, error, info, warning, or user) and its name, arguments, and message format.< Passed VCP 4 br /> existing partition
A partition on a physical disk. See also physical disk.
fabric
A Fibre Channel network topology in which devices pass data to each other through interconnecting switches. A fabric is used in many SANs. Fabrics are typically divided into zones. Also called switched fabric or Fibre Channel fabric. See also FC (Fibre Channel).
FAT (file allocation table)
See file allocation table (FAT).
fault
A data object containing information about an exception condition encountered by an operation.
FC (Fibre Channel)
An ANSI-standard, gigabit-speed network technology used to build storage area networks and transmit data. Fibre Channel components include HBAs, switches, and cabling.
file
A container for raw data, such as text or an image.
file allocation table (FAT)
An area on a disk that stores information about the location of each piece of every file on the disk and about the location of unusable areas of the disk.
file system cache
A storage mechanism that speeds access to files stored on a disk by caching frequently accessed data. The maximum disk cache for 32-bit operating systems is 512MB; for 64-bit operating systems, the maximum is 1TB. All platforms use file system caches for improved performance.
folder
A managed entity used to group other managed entities. Folder types are determined by the types of child entities they contain. See also child.
FQDN (fully qualified domain name)
The name of a host that includes the host name and the domain name. For example, the FQDN of a host named esx1 in the domain vmware.com is esx1.vmware.com.
full clone
A complete copy of the original virtual machine, including all associated virtual disks. See also linked clone.
full screen switch mode
A display mode in which the virtual machine’s display fills the entire screen. (The user has no access to the VMware Workstation user interface.) The user cannot create, reconfigure, or start virtual machines. A system administrator performs those functions. See also quick switch mode.
full virtual machine backup
Backs up all files that make up the entire virtual machine. These files include disk images, .vmx files, and so on.
Go to snapshot
To restore a snapshot of the active virtual machine. See also revert to snapshot.
GOS (guest operating system)
See guest operating system.
group
A set of users assigned a common set of privileges. A group may contain other groups. See also service console.
growable disk
A type of virtual disk in which the disk space is not preallocated to its full size. The disk files begin small and grow as data is written to the disk.
guest operating system
An operating system that runs inside a virtual machine. See also host operating system.
guest user
An unauthenticated user who can log in to a system with a temporary user name and password. A guest user has restricted access to files and folders and has a set of restricted permissions
handle
A temporary token used by a Web service client to invoke Web service operations that require a reference to an object. Like a file handle, an object handle is a temporary handle that always refers to the same object.
HBA (host bus adapter)
A device that connects one or more peripheral units to a computer and manages data storage and I/O processing (often for Fibre Channel, IDE, or SCSI interfaces). An HBA can be physical (attached to a host) or virtual (part of a virtual machine).
HCL (hardware compatibility list)
The definitive list of hardware that VMware supports.
headless
Describes a program that runs in the background without any interface connected to it. A running virtual machine that has no console connections is running headless.
heartbeat
A signal emitted at regular intervals by softw vcp 410 are to demonstrate that it is still active. The signal emitted by a Level 2 Ethernet transceiver at the end of every packet to show that the collision-detection circuit is still connected.

o vCenter Server instances in a Linked Mode group can be in different domains if the domains have a two-way trust relationship.
o The installer must be run by a domain user who is an administrator on both the machines.
o The vCenter Server installer validates that the machine clocks are not more than 5 minutes apart.
o The instances can run under di VCP-410 questions fferent domain accounts.
o Windows Server 2008 automatically configures the firewall to permit access. Launch firewall.cpl and add an exception for
C:WindowsADAMdsamain.exe
o When you install vCenter Server in Linked Mode, the firewall configuration on any network-based firewalls must be modified.
o Configure Windows RPC ports to generically allow selective ports for machine-to-machine RPC communication.
o vCenter Collector service – uses port 8181 and 8182, by default.
o vCenter Web Server – uses ports 8080 and 8443, by default.
o All product licenses are encapsulated in 25-character license keys that you can manage and monitor from vCenter Server.
o vSphere Licenses – For ESX/ESXi.
o vCenter Server Licenses – For vCenter Server.
o vCenter Server 4.0 does not require a license server to manage ESX 4.0/ESXi 4.0 hosts. However, vCenter Server 4.0 does requires a license
server to manage ESX 3.x/ESXi 3.5 hosts.
o If a vCenter Server license expires, the managed hosts become disconnected.
o If an ESX/ESXi host license expires, the VMs that reside on the host continue to run, but you cannot power on the VMs or reset them.
ESXi Installable and vCenter Server Setup Guide
o When you power on the ESXi host for the first time or after resetting the configuration defaults, the host enters an autoconfiguration phase
during which system network and storage devices are configured with defaults.
o By default, DHCP configures IP and all visible blank internal disks are formatted with VMFS so that virtual machines can be stored on the disks.
o ESXi has an interface called the direct console to:
o Configuring host defaults
o Setting up administrative access
VCP-410 dumps o Troubleshooting
o Minimum hardware configurations supported by ESXi 4.0:
o 64-bit x86 CPUs.
o 2GB RAM minimum
o Supported SATA, SAS or SCSI disks
o The installer reformats and partitions the target disk and installs the ESXi 4.0 boot image.
o ESXi Installable is always installed in evaluation mode (60 days).
o ESXi Installable and ESXi Embedded cannot exist on the same host.
o Booting multiple servers from a single shared ESXi image is not supported.
o If there is no DHCP available during the install, it assigns the link local IP address, which is in the subnet 169.254.x.x/16.
o Direct Console
Action Key
View and change the configuration F2
Change the user interface to high-contrast mode F4
Shut down or restart the host F12
Move the selection between fields Arrow keys
Select a menu item Enter
Toggle a value Spacebar
Confirm sensitive commands, such as resetting configuration defaults F11
Save and exit Enter
Exit without saving Esc
Exit system logs q
o To change the security banner > Advanced Settings window, select Annotations.
o Test Management Network:
o Pings the default gateway
o Pings the primary DNS nameserver
o Pings the secondary DNS nameservPassed VCP-410 er
o Resolves the configured host name
o Restarting the management agents restarts all management agents and services that are installed and running in /etc/init.d on the ESXi host.
Typically, these agents include hostd, ntpd, sfcbd, slpd, wsman, and vobd. The software also restarts the Automated Availability Manager
(AAM) if it is installed.
o Disable the management network is if you want to isolate an ESXi host from an HA and DRS cluster, but you do not want to lose your static IP
and DNS configurations or reboot the host

o ks-first-safe.cfg Installs ESX on the first detected disk and preserves the VMFS datastores on the disk.
o ks-first.cfg Installs ESX on the first detected disk.
o The default root password is mypassword.
o /boot and vmkcore are physical partitions. /, swap, /var/log, and all the optional partitions are stored on a virtual disk called esxconsole-
<system-uuid>/esxconsole.vmdk. The virtual disk is stored in a VMFS volume.
VCP-410 exam o You cannot define the sizes of the /boot, vmkcore, and /vmfs partitions when you use the graphical or text installation modes. You can define
these partition sizes when you do a scripted installation.
o ESX Required Partitions
Mount Point Type Size Location
/boot ext3 1.25GB of free space and includes the /boot and vmkcore
partitions. The /boot partition alone requires
1100MB.
Physical partition
N/A swap 600MB recommended minimum 1600MB maximum. Virtual disk in a VMFS volume
/ ext3 Based on the size of the /usr partition. By default, the
minimum size is 5GB and no /usr partition is defined.
Virtual disk in a VMFS volume
N/A VMFS3 For VMFS volumes hosting esxconsole.vmdk: 1200MB and
an additional 10GB. VMFS2 is supported in read-only
mode to import legacy VMs.
Physical partition.
N/A vmkcore See /boot Physical partition
o ESX Optional Partitions
Mount Point Type Recommended Size Location
/home ext3 512MB Virtual disk in a VMFS volume
/tmp ext3 1024MB Virtual disk
/usr ext3 Missing in PDF Virtual disk
/var/log ext3 2000MB Virtual disk. The graphical and text
installers create this partition by
default.
o vihostupdate command applies software updates to ESX4/ESXi4 hosts and installs and updates ESX/ESXi extensions (use vihostupdate35 on
ESX 3.5/ESXi 3.5 hosts.)
o The esxupdate utility is for ESX only.
o You can use the vihostupdate utility in conjunction with offline bundles or with a depot
o vSphere Databases:
o Microsoft SQL Server 2005 Express – up to 5 hosts and 50 VMs. If the machine has Microsoft SQL Native Client installed, remove it before
installing vCenter Server with the bundled database. If the machine has MSXML Core Services 6.0 installed, remove it before installing
o Microsoft SQL Server 2005 – Windows XP, apply MDAC 2.8 SP1 to the client. Use the SQL Native Client driver (version 9.x) for the client.
Ensure that the machine has a valid ODBC DSN entry. Remove MSXML Core Services 6.0 before
VCP-410 exam questions o Microsoft SQL Server 2008 – Windows XP, apply MDAC 2.8 SP1 to the client. Use the SQL Native Client driver (version 10.x) for the client.
Ensure that the machine has a valid ODBC DSN entry.
o Oracle 10g – If necessary, first apply patch 10.2.0.3 (or later) to the client and server. Then apply patch 5699495 to the client. Ensure that
the machine has a valid ODBC DSN entry.
o Oracle 11g – Ensure that the machine has a valid ODBC DSN entry.
o Even though vCenter Server is supported on 64-bit operating systems, the vCenter Server system must have a 32-bit DSN. This requirement
applies to all supported databases. By default, any DSN created on a 64-bit system is 64 bit. On a 64-bit system use
C:WINDOWSSYSWOW64odbc32.exe.
o vCenter Server must have a computer name that is 15 characters or fewer. The data source name (DSN) and remote database systems can
have names with more than 15 characters.
o To prepare a SQL Server database to work with vCenter Server, you generally need to create a SQL Server database user with database
operator (DBO) rights.
o If you use SQL Server for vCenter Server, do not use the master database.
o When using Microsoft SQL Server 2008 Standard Edition with vCenter Server, do not name the instance MSSQLSERVER.
o The vCenter Server performs a silent installation of vCenter Orchestrator. If you install vCenter Server on an IPv6 operating system, the
vCenter Orchestrator mod VCP-410 study guide ule is not supported.
o The vSphere Host Update Utility is for updating and patching ESXi 4.0 hosts and upgrading ESX 3.x/ESXi 3.5 hosts to ESX 4.0/ESXi 4.0.
o You can join multiple vCenter Server systems to form a Linked Mode group.
o Linked Mode global data includes:
o Connection information (IP and ports)
o Certificates
o Licensing information
o User roles

The evaluation period is 60 days and begins as soon as you power on the ESX machine, even if you start in license mode initially.
o The installer creates three basic partitions: /boot, vmkcore and VMFS. The service console VMDK file contains swap, and /var/log, by default,
and any other partitions that you specify.
o The media depot is a network-accessible location that contains the ESX installation media. You can use HTTP/ HTTPS, FTP, or NFS to access the
depot.
VCP-410 dumps o Scripted installation – you must point to the media depot in the script by including the install command with the nfs or url option.
o Interactive installation – include the askmedia boot option.
o The boot options list appears when you boot the installer and press F2.
o Bootstrap Commands for ESX Installation
Command Description
askmedia Allows you to interactively select the location of the ESX installation media. This option is required if the
image is hosted at an HTTP, FTP, or NFS location.
BOOTIF Accepts the format for the boot network adapter as supplied by PXELINUX.
gateway=<ip address> Sets this network gateway as the default gateway during the install.
ip=<ip address> Specifies a static IP address to be used for downloading the script and the installation media. The IPAPPEND
option is also supported if you PXE boot the installer.
ks=cdrom:/<path> Performs a scripted installation with the script at <path>, which resides on the DVD in the DVD-ROM drive.
ks=file://<path> Performs a scripted installation with the script at <path>, which resides inside the initial ramdisk image.
ks=ftp://<server>/<path>/ Performs a scripted installation with a script located at the given URL.
ks=http://<server>/<path> Performs a scripted installation with a script located at the given URL.
ks=https://<server>/<path> Performs a scripted installation with a script located at the given URL.
ks=nfs://<server>/<path> Performs a scripted installation with the script located at <path> on a given NFS VCP-410 server.
ks=usb Performs a scripted installation with the ks.cfg script in the root directory of the USB flash drive attached to
the host. If multiple flash drives are attached, the installer cycles through each one, mounting and
unmounting them until the file named ks.cfg is found.
ks=UUID:<partition-UUID>:/<path> Performs a scripted installation with a script located on the ext partition with the given UUID.
ksdevice=<device> Same as netdevice
nameserver=<ip address> Specifies a domain name server as the nameserver during the install.
netdevice=<device> Tries to use a network adapter <device> when looking for an installation script and installation media. Specify
as a MAC address (for example, 00:50:56:C0:00:01). If not specified and files need to be retrieved over
the network, the installer defaults to the first discovered network adapter. The IPAPPEND option is also
supported if you PXE boot the installer.
netmask=<subnet mask> Specifies subnet mask for the network interface that downloads the installation media.
noapic Flags the kernel to use the XTPIC instead of the APIC.
text Starts the ESX installer in text mode.
url=<url> Looks for the installation media at the specified URL. When you are PXE booting the installer, the url=
command only works with earlier versions of SYSLINUX. The command does not work with
SYSLINUX/PXELINUX version 3.70 and higher.
vlanid=<vlanid> Configures the VLAN for the network card.
o PXE Boot the ESX Installer:
1. Install TFTP server software that supports PXE booting.
2. Put menu.c32 file in an accessible place
3. Install PXELINUX.
4. Configure the DHCP server.
VCP-410 braindump /> 5. Create the kernel image and ramdisk directory by copying the vmlinuz and initrd.img files from the /isolinux directory on the ESX
installation DVD to a supported location.
6. Create the /tftpboot/pxelinux.cfg directory on your TFTP server.
7. Create a PXE configuration file. PXE configuration file in /tftpboot/pxelinux.cfg
o In an interactive installation, omit the ks= option.
o ESX 3.x supported a hybrid installation. You could supply an incomplete ESX installation script, and the installer prompts you for the missing
parts. ESX 4.0 does not support this.
o Install ESX interactively or by using a script. For interactive installation, you can use graphical mode or text mode.
o The installer erases all content on the selected storage device.
o Installing ESX on a USB device is not supported.
o VMFS2 volumes are not recognized by the ESX 4.0 installer.
o The installation log is /var/log/esx_install.log.
o The installation script can reside in one of the following locations:
o Default installation script
o FTP
o HTTP/HTTPS
o NFS
o USB flash drive
o Local disk
o The installer creates a /root/ks.cfg script, which reflects the choices you made in the interactive installation.
o Installation media contains the following default installation scripts

vCompute – aggregate resources
o vStorage – enables the most efficient use and management of storage
o vNetwork – simplify and enhance networking
o Fault Tolerance – a secondary copy. Actions completed on the primary VM are also applied to the secondary VM. If the primary VM becomes
unavailable, the secondary machine becomes active, providing continual availability.
o Distributed Virtual Switch (D VCP-410 exam questions VS) – spans many hosts reduction of maintenance and increasing network capacity.
o Host Profiles – host configuration management through user-defined configuration policies. Captures the blueprint and monitors compliance.
o Pluggable Storage Array (PSA) – greater array certification flexibility and improved array-optimized performance. A multipath I/O framework.
o Cluster – aggregate computing and memory resources of a group of physical x86 servers sharing the same network and storage arrays.
o Resource pools – partitions of computing and memory resources from a single host or a cluster. can be hierarchical and nested.
o Storage VMotion – enables the migration of VMs from one datastore to another datastore without service interruption
o Fault Tolerance (FT) – uses vLockstep technology, continuous availability by protecting a VM (the Primary VM) with a shadow copy (Secondary
VM) that runs in virtual lockstep on a separate host.
o vNetwork Distributed Switch (dvSwitch) – functions as a single virtual switch across all associated hosts.
o dvPort (distributed virtual port) – a port on a DVS that connects to a host’s service console or VMkernel or to a VM’s network adapter.
o vApp – has the same basic operation as a VM, but can contain multiple VMs or appliances.
o Web Access cannot be used to access a hos VCP-410 study guide t running ESXi 4.0.
o Web Access is turned off by default for ESX hosts.
Getting Started with ESX
o ESX Service Console is held in the esxconsole.vmdk partition.
o vCenter Server uses Microsoft SQL Server 2005 Express for small deployments with up to 5 hosts and 50 VMs.
o If SQL Native Client is already installed, uninstall SQL Native Client before you begin the vCenter Server installation.
o vCenter server must belong to a domain rather than a workgroup. Otherwise it’s not able to discover – using such features as vCenter Guided
Consolidation Service. The computer name cannot be more than 15 characters.
o vCenter Server cannot be an Active Directory domain controller.
o The Domain user account should have the following permissions:
o Member of the Administrators group
o Act as part of the operating system
o Log on as a service
ESX and vCenter server installation guide
o ESX4 will only install and run on servers with 64-bit x86 CPUs. They require a 2GB RAM minimum.
o vCenter Server must have 2 CPUs and 3GB RAM.
o The vCenter Server has a service called VMware VirtualCenter Management Webservices. This service requires 128MB to 1.5GB of additional
memory.
o You can use a 32-bit Windows for up 200 hosts. A 64-bit Windows can have 200-300 hosts.
o The vSphere Client requires the Microsoft .NET 3.0 SP1 Framework.
o vCenter server required firewall ports:
Port Description
80 Redirects requests to HTTPS port 443.
389 LDAP port number for the Directory Services for the vCenter Server group. Needs to bind to port 389, even if you are not joining this
vCenter Server instance to a Linked Mode group.
443 Listen for connections from the vSphere Client.
636 For vCenter Linked Mode, this is the SSL port of the local instance
902 Uses to send data to managed hosts. Managed hosts also send a regular heartbeat over UDP port 902 to the vCenter
902/903 Ports used by vSphere Client to display VM consoles.
8080 Web Services HTTP. Used for the VMware VirtualCenter Management Webservices.
8443 Web Services HTTPS. Used for the VMware VirtualCenter Management Webservices.
VCP-410 questions o If ESX will not use an NTP server, make sure that the server hardware clock is set to UTC in the BIOS (EDIT: As a matter of best practice you
should always set ESX server’s hardware clocks to UTC)
o IPv6 is not supported for ESX installation
o The service console must be installed on a VMFS datastore that is resident on a host's local disk or on a SAN disk that is masked and zoned to
that particular host only.