grammy

Each vCenter Converter server must be associated with only one vCenter Server.
o You can install vCenter Converter on:
o Windows Server 2000 SP4 with Update Rollup 1
o Windows Server 2003 SP2 (32 bit & 64 bit)
o Windows Server 2003 R2 SP2 (32 bit & 64 bit)
o Windows Server 2008 (32 bit & 64 bit)
o Windows Vista SP1 (32 bit &am 220 702 ; 64 bit)
o Windows XP Professional SP3 (32 bit & 64 bit)
o You can install the vCenter Converter CLI on Linux computers.
o The operating system on which you install vCenter Converter server determines which VMs & third-party images you can import, export, &
reconfigure.
o VMs must be powered off before you import them. You cannot import suspended VMs.
o Ports required by vCenter Converter:
Communication path Port
vCenter Converter server to remote physical machine TCP– 445, 139 UDP– 137, 138
vCenter Converter server to vCenter Server 443
vCenter Converter client to vCenter Converter server 443
Physical machine to vCenter Server 443
Physical machine to ESX/ESXi 902
o You must install the Microsoft Sysprep tools on your vCenter Server machine in the appropriate location: C:Documents & SettingsAll
UsersApplication DataVMwareVMware VCENTERsysprep.
o You can export VMs that vCenter Server manages to managed formats or hosted formats.
o You can download & use the VMware peTool to add storage & network drivers to the boot CD ISO image.
o You can migrate physical & virtual source machines by using the converter-tool executable file & the command-line interface (CLI). This
provides access to functionality without requiring the vSphere Client plug-in. Can run on Windows & Linux computers.
9L0-403 /> o The vCenter Converter installer does not support Linux. You must download the latest version of the Linux installer.
vCenter Orchestrator 4.0 – Installation and Configuration Guide
o vCenter Orchestrator is a development and process-automation platform that provides a library of extensible workflows.
o Orchestrator exposes every operation in the vCenter Server API.
o Three global user roles: Administrators, Developers, and End Users.
o Support for several OS:
o Server 2003 R2, 32bit, 64bit
o Server 2008, 32bit, 64bit
o Supported directory service types:
o Active Directory
o OpenLDAP
o eDirectory
o Sun Java Directory Server
o Supported browsers:
o IE 6.0 and 7.0
o Firefox 3.0.6 or later
o Safari 3.x (experimental)
o The database is separate from the standard vCenter database.
o Microsoft SQL Server 2005 Enterprise (SP2) and x64 and (SP1)
o Microsoft SQL Server 2005 Standard (SP2), (SP1)
o Microsoft SQL Server 2000 Enterprise (SP4)
o Microsoft SQL Server 2000 Standar 9L0-510 d (SP4)
o Oracle 10g Enterprise Release 2 (10.2.0.3.0) x32 and x64
o Orchestrator does not support IPv6 operating systems.
o Orchestrator Configuration Service startup type is set to Manual by default.
o http://<computer_DNS_name_or_IP_address>:8282.
o HTTPS connection through port 8283, you must configure Jetty to use SSL.
o You cannot change the vmware default user name.

high-latency network in which Update Manager & the hosts are at different locations might take a few hours because the upgrade file is
copied from the Update Manager server repository to the host before the upgrade.
o When you upgrade a host, no third-party management agents or software applications are migrated to the ESX 4. 220 701 0/ESXi 4.0 host.
o In the ESX 3.5 patch remediation process, cumulative rollups & updates are considered patches. If a rollup contains two patches installed on
the host, the state of the host is noncompliant against the rollup until the rollup itself is installed on the host.
o In the ESX 4.0 patch remediation process, Update Manager operates with vSphere Installation Bundles (*.vib files). A bundle is the smallest
installable unit on an ESX 4.x host. A bulletin defines a specific fix for a host, a rollup that aggregates previous fixes, or an update release.
When a host is compliant with all bundles in a bulletin, it is compliant with the vSphere bulletin that contains the bundles.
o Before the ESX host upgrade remediation, Update Manager runs a script on the host to check whether the host can be upgraded. If the host
can be upgraded, Update Manager copies the ISO file to the host. The ISO file contains the bits that are to be installed as well as a Linux kernel
& ramdisk, which serve as the installer environment. The host reboots into the installer, & the installer creates a service console virtual disk
(VMDK) to install the packages into the console VMDK. The host is rebooted, upgraded to ESX 4.0, & reconnected to the vCenter system. If the
upgrade fails, you can roll back to the previous version.
o For ESXi hosts, updates are all-inclusive.
o The ESXi image on the host maintains two copies. The first copy is in the active boot & the second one is the standby boot.
o The active boot contains the patched image & the standby boot contains the previous version of the ESXi host image.
o Take snapshots of templates before remediation, especially if the templates are sealed.
o After a template is started & remediated, the registry keys are restored, & the machine is shut down, returning the template to its sealed
state.
o Staging patches for ESX/ESXi hosts allows you to download the patches from the Update Manager server to the ESX/ESXi hosts, without
applying the patches immediately.
o Staging patches does not require that the hosts enter maintenance mode.
o Update Manager stores data about events. You can review this event data to gather information about operations that are in progress or that
have finished.
o Because of limitations in the ZIP utility used by the Update Manager, the cumulative log file size cannot exceed 2GB, although the script seems
to complete successfully.
o To generate Update Manager log files, exclude the generation of the vCenter logs using the vumsupport. wsf script file:
o C:Program FilesVMwareInfrastructureUpdate Managercscript vum-support.wsf /n
o When you upgrade an ESXi host with less than 10MB of free space in its /tmp directory, although Update Manager indicates that the
remediation process completes successf 220 702 ully, the ESXi host is not upgraded.
vCenter Converter Administration Guide
o vCenter Converter does not support creating thin-provisioned target disks on ESX/ESXi 4.0.
o vCenter Converter Components:
o vCenter Converter server
o vCenter Converter CLI
o vCenter Converter agent
o vCenter Converter client
o vCenter Converter Boot CD
o When you import a physical system, vCenter Converter uses cloning & system reconfiguration steps.
o When you hot clone dual-boot systems, you can clone only the default operating system to which the boot.ini file points.
o You can clone remotely, as long as it is running & accessible to the network. With local cloning, vCenter Converter runs on the source machine
to perform the migration.
o During hot cloning, the machine you are cloning experiences no downtime.
o Disk-based cloning for cold cloning & importing existing VMs. Supports all basic & dynamic disks.
o Volume-based cloning for hot & cold cloning & for importing existing VMs. All volumes in the destination VM are basic volumes, performed at
the file level or block level, depending on your size selections.
o Only master boot record (MBR) disks are supported. GUID partition table (GPT) disks are not supported.
o Hot cloning supports all types of source volumes that Windows recognizes.
o You cannot schedule reconfiguration tasks.
o Converter can restore VCB images of any guest operating system type on an ESX/ESXi host that vCenter Server manages. However, only disks
are preserved. It does not preserve certain hardware backup information from the original image, but rather substitutes default settings.
o You can schedule an unlimited number of physical-to-virtual recurring tasks & specify how the existing VMs are to be retained.For recurring
tasks, the vCenter Converter agent must be 220 702 installed permanently on the source machine.
o You can keep multiple VMs as backups to an existing machine
o VM names have an 80-character limit. VMware recommends a maximum of 60 characters because the time stamp might make the name
exceed the limit.
o Applications might not work if they depend on specific characteristics of the underlying hardware

Patch
o Patch baseline can be either dynamic or fixed.
o You can create baseline groups that contain both patch & upgrade baselines.
o Update Manager settings:
640 802 Dumps o When to check for updated patch information.
o When to scan or remediate.
o How to handle pre-remediation snapshots of VMs.
o How to handle failures to put hosts in maintenance mode.
o How to handle rebooting virtual appliances after remediation.
o Hardware Requirements:
o 2 or more logical cores
o 2GB RAM if Update Manager & vCenter are on different machines
o 4GB RAM if Update Manager & vCenter are on the same machine
o Supported Database Formats
o SQL Server 2005 SP1 (Use SQL Native Client driver for the client)
o SQL Server 2005 Express (Use SQL Native Client driver for the client)
o SQL 2008
o Oracle 10g Release 1 (10.1.0.2)
o Oracle 10g Release 2 (10.2.0.3)
o Oracle 11g Release 1 (11.1.0.6.0)
o It is not recommended to install Update Manager & vCenter on a VM that is managed by the same vCenter system. Upon scanning &
remediating, the VM on which Update Manager & vCenter are installed can reboot & the whole deployment system will shut down.
o If Update Manager does not have access to the Internet, install the Update Manager Download Service (UMDS) to download patches.
o You can export downloaded patches to a specific location that serves as a shared repository for Update Manager: C:Program
FilesVMwareInfrastructureUpdate Managervmware-umds --export –dest <repository_path>
o To set up a download of all available updates: vmware-umds --set-config --enable-host 1 --enable-win 1 --enable-lin 1
o Download the selected patches: vmware-umds --download.
o The Update Manager Web server listens on 9084 TCP & 9087 TCP. The Update Manager SOAP server listens on 8084 TCP.
o To obtain metadata for the patches, Update Manager must be able to connect to https://www.vmware.com & https://xml.shavlik.com, &
requires outbound ports 80 & 443.
o Update Manager connects to vCenter on port 80.
o ESX/ESXi hosts connect to the Update Manager Web server listening on HTTP port 9084 for host patch downloads.
o Update Manager connects to ESX/ESXi hosts on port 902 for pushing the VM patches & host upgrade files.
o The Update Manager Client plug-in connects to the Update Manager SOAP server listening on port 8084. It also connects to the Update
Manager Web server on HTTP port 9087 for uploading 640-802 the host upgrade files
o Update Manager 4.0 supports Internet Protocol version 6 (IPv6) environment for scanning & remediating ESX/ESXi 4.0 hosts. For VM
scanning & remediation IPv6 is not supported.
o If you have ESX 3.X hosts in your inventory & the Update Manager is installed on a computer with IPv6, the scan & remediation operations on
the hosts fail.
o You can configure Update Manager to take snapshots of VMs before applying patches & Upgrades. You can choose to keep these snapshots
indefinitely or for a fixed period of time.
o Configure how Update Manager responds to failure to put hosts in Maintenance Mode:
o Fail
o Retry
o Power Off VMs & Retry
o Suspend VMs & Retry
o Smart rebooting selectively reboots the virtual appliances & VMs in the vApp to maintain startup dependencies & possibly reboots the
appliances that are not remediated. Smart rebooting is enabled by default
o Update Manager includes four default dynamic patch baselines & four upgrade baselines. You cannot edit or delete default baselines.
o Critical VM Patches
o Non-Critical VM Patches
o Critical Host Patches
o Non-Critical Host Patches
640 802 braindumps o VMware Tools Upgrade to Match Host
o VM Hardware Upgrade to Match Host
o VA Upgrade to Latest
o VA Upgrade to Latest Critical
o Compliance status is displayed based on permissions.
o For ESX/ESXi hosts in a cluster, the remediation process is sequential.
o For multiple clusters under a datacenter, the remediation processes run in parallel

ESX4 Patch Management Guide
o Bulletin - grouping of one or more VIBs (vSphere Installation Bundle).
o Depot - logical grouping of VIBs – online.
o Offline Bundle zip - archive that encapsulates VIBs.
o Patch - bulletin that groups one or m vcp 4 ore VIBs together to address a particular issue or enhancement.
o Roll-up - collection of patches that is grouped for ease of download and deployment.
o Update - periodic release of an ESX image.
o VIB - single software package.
o A record of each installed bulletin is written to the /etc/vmware/esxupdate
o Four basic modes of esxupdate:
o Inspection mode
o esxupdate query - display a list of bulletins installed.
o esxupdate info - display information on the contents of one or more bulletins.
o Scan mode - determines which bulletins are applicable.
o Test mode - go through all installation operations without installing.
o Update mode - installs bulletins.
o The installation process is recorded in the esxupdate.log file. By default, this file is located in the /var/log/vmware directory.
o esxupdate never reboots your host.
Optional vSphere Products and Modules
vCenter Update Manager Administration Guide
o Update Manager can:
o Scan for compliance & apply updates for guests, appliances, & hosts.
o Directly upgrade hosts, VM hardware, VMware Tools, & virtual appliances.
o Update third-party software on hosts.
o Update Manager requires network connectivity with vCenter. Each installation of the Update Manager must be associated (registered) with a
single vCenter instance
o The Update Manager Client has two main views, Administrator's view & Compliance view.
o Administrator's view you can:
o Configure the Update Manager settings
vmware vcp 4 > o Create & manage baselines & baseline groups
o View Update Manager events
o Review the patch repository & add or remove patches from a baseline
o Compliance view you can:
o View compliance & scan results for each selected inventory object
o Attach & detach baselines & baseline groups from a selected inventory object
o Scan a selected inventory object
o Stage patches for hosts
o Remediate a selected inventory object
o The Update Manager process begins by downloading information about a set of security patches. One or more of these patches are
aggregated to form a baseline. Multiple baselines can be added to a baseline group. A baseline group is a composite object that consists of a
set of non-conflicting baselines. You can use baseline groups to combine different types of baselines & then scan & remediate an inventory
object against all of them as a whole. If a baseline group contains both upgrade & patch baselines, the upgrade executes first.
o A collection of VMs, virtual appliances, & ESX/ESXi hosts or individual inventory objects can be scanned for compliance with a baseline or a
baseline group & later remediated (updated). You can initiate these processes manually or through scheduled tasks.
o You can configure the Update Manager server to download patches either from the Internet or from a shared repository.
o Types of scan:
o Patch scan – ESX 3.0.3 & later, ESX 3i version 3.5 & later, VMs running Windows or Linux.
o Host upgrade scan – ESX 3.0.0 & later & ESX 3i version 3.5 & later.
o VMware Tools scan –Windows or Linux.
o VM hardware upgrade scan.
o Virtual appliance upgrade scan –VMware Stud 640 802 io registered Red Hat, Ubuntu, SUSE, & CentOS Linux virtual appliances.
o Staging patches for ESX/ESXi 4.0 hosts allows you to download the patches from the Update Manager server to the ESX/ESXi hosts without
applying the patches immediately.
o Remediation applies patches & upgrades after a scan is complete.
o Baselines can be:
o Upgrade

o vSphere CLI commands:
Command ESXi 4 ESX 4 VC 4 CLI “esxcfg”
prefix available
Description
esxcli yes yes no Manage pluggable storage architecture (PSA) & native multipathing (NMP).
resxtop yes yes yes Monitors i vcp-410 real time how ESX hosts use resources. Runs in interactive or
batch mode. This command is supported only on Linux.
svmotion no no yes Moves a VM’s configuration file & optionally its disks while the VM is
running. Must run against a vCenter Server system.
vicfg-advcfg yes yes yes esxcfg-advcfg Performs advanced configuration including enabling & disabling CIM
providers. Use this command as instructed by VMware.
vicfg-cfgbackup yes no no esxcfg-cfgbackup Backs up the configuration data of an ESXi system & restores previously
saved configuration data.
vicfg-dns yes yes yes esxcfg-dns Specifies an ESX/ESXi host’s DNS (Domain Name Server) configuration.
vicfg-dumppart yes yes yes esxcfg-dumppart Manages diagnostic partitions.
vicfg-iscsi yes yes yes Manages iSCSI storage.
vicfg-module yes yes yes esxcfg-module Enables VMkernel options. Use this command with the options listed in this
document, or as instructed by VMware.
vicfg-mpath yes yes yes esxcfg-mpath Configures storage arrays.
vicfg-mpath35 no no no Configures storage arrays for ESX/ESXi 3.5 hosts.
vicfg-nas yes yes yes esxcfg-nas Manages NAS file systems
vicfg-nics yes yes yes esxcfg-nics Manages the ESX/ESXi host’s physical NICs.
vicfg-ntp yes yes yes esxcfg-ntp Specifies the NTP (Network Time Protocol) server.
vicfg-rescan yes yes yes esxcfg-rescan Rescans the storage configuration.
vicfg-route yes yes yes esxcfg-route Manipulates the ESX/ESXi host’s route entry
vicfg-scsidevs yes yes yes esxcfg-scsidevs Finds available LUNs.
vicfg-snmp yes yes no esxcfg-snmp Manages the Simple Network Management Protocol (SNMP) agent.
vicfg-syslog yes no yes esxcfg-syslog Specifies the syslog server & the port to connect to that server for ESXi
vmware vcp 410 hosts.
vicfg-user yes yes no Creates, modifies, deletes, & lists local direct access users & groups of users.
vicfg-vmknic yes yes yes esxcfg-vmknic Adds, deletes, & modifies virtual network adapters (VMkernel NICs).
vicfg-volume yes yes yes Supports resignaturing a VMFS snapshot volume & mounting & unmounting
the snapshot volume.
vicfg-vswitch yes yes yes esxcfg-vswitch Adds or removes virtual switches or modifies virtual switch settings.
vifs yes yes no Performs file system operations such as retrieving & uploading files on the
remote server.
vihostupdate yes yes no Manages updates of ESX/ESXi hosts
vihostupdate35 no no no Manages updates of ESX/ESXi 3.5 hosts
vmkfstools yes yes no Creates & manipulates virtual disks, file systems, logical volumes, & physical
storage devices on an ESX/ESXi host.
vmware-cmd yes yes yes Performs VM operations remotely. This includes, for example, creating a
snapshot, powering the VM on or off & getting information about the VM.
o The rest of the booklet is a detailed description of each command in this table. Similar information can also be found in the command’s
corresponding man pages.
License Server Configuration for vCenter Server vmware vcp 410 4.0 – ESX 3.x licensing
o Using vCenter Server 4.0 to manage ESX 3.x/ESXi 3.5 hosts, you have several options:
o A single license server for vCenter Server 4.0 and the ESX 3.x/ESXi 3.5 hosts.
o One license server for vCenter Server 4.0, and use another license server for the ESX 3.x/ESXi 3.5 hosts.
o A license server for vCenter Server 4.0, and use host-based licensing for the ESX 3.x/ESXi 3.5 hosts.
o Do not use a license server. Upgrade all of your hosts to ESX 4.0/ESXi 4.0

o Optimize for performance – Acknowledges changes to the virtual disk immediately, but saves them at a later time.
o VMI currently supports only 32-bit guests.
Additional Resources
Setup for Failover Clustering and Microsoft Cluster Service
o Support for Windows Server 2003 SP2,Passed VCP410 2000 SP4, or 2008.
o Only two-node clustering.
Storage Type Cluster in a Box Cluster Across Boxes Standby Host
(n+1)
Virtual disks Yes (recommended) No No
Non-pass-through RDM (virtual compatibility mode) Yes Yes No
Pass-through RDM (physical compatibility mode) No Yes (recommended) Yes
o Clusters across physical machines with non-pass-through RDM is supported only for clustering with Windows 2000 Server or Windows Server
2003. It is not supported for clustering with Windows Server 2008.
o Not supported:
o Clustering on iSCSI or NFS disks.
o Clustered virtual machines as part of VMware clusters (DRS or HA).
o MSCS in conjunction with VMware Fault Tolerance.
o Migration with VMotion.
o N-Port ID Virtualization (NPIV)
o With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
o You must use hardware version 7 with ESX4.
o You can put the boot disk of a virtual machine on a SAN-based VMFS volume.
o Clustered continuous replication (CCR) environment for Microsoft Exchange - Use physical compatibility mode RDMs.
o For boot disks - Select “Support clustering features such as Fault Tolerance” to create a disk in eagerzeroedthick format.
o SCSI Controller Type:
o Windows 2000 and 2003 - Server LSI Logic Parallel (download from the LSI web site).
o Windows 2008 - LSI Logic SAS
o Cluster across boxes:
o Shared storage must be on an FC SPassed VCP 4 AN.
o RDM in physical compatibility (pass-through) or virtual compatibility (non-pass-through) mode. VMware recommends physical
compatibility mode. The cluster cannot use virtual disks for shared storage.
o Failover clustering with Windows Server 2008 is not supported with virtual compatibility mode
o Standby Host (n+1): Use only a single physical path from the host to the storage arrays.
vSphere Command-Line Interface Installation and Reference Guide
o vSphere CLI commands run on top of the vSphere SDK for Perl.
o You can install a vSphere CLI package on either Linux or Microsoft Windows, or deploy the vSphere Management Assistant (vMA).
o If you establish a vCenter Server system as a target server, you can execute most vSphere CLI commands against all ESX/ESXi systems it
manages without additional authentication.
o You can use vSphere CLI commands interactively or in scripts.
o The installation script for the vSphere CLI is supported on:
o Red Hat Enterprise Linux (RHEL) 5.2 (64 bit)
o Red Hat Enterprise Linux (RHEL) 5.2 (32 bit)
o SUSE Enterprise Server 10 SP1 32 bit
o Ubuntu 8.04 32 bit
o vSphere CLI is supported on:
o Windows XP SP2 32 bit
o Windows XP SP2 64 bit
o Windows Vista Enterprise SP1 32 bit
o Windows Vista Enterprise SP1 6 vcp 410 4 bit
o If you set up a vCenter Server system as a target server, you can specify any of the ESX/ESXi hosts that vCenter Server system manages using
the --vihost option.
o VMware recommends that you use the vSphere CLI commands with the vicfg prefix. Commands with the esxcfg prefix are available mainly for
compatibility reasons & might become obsolete

VMware HA Attributes:
Attribute Description
das.isolationaddress[...} Address to ping to determine if a host is isolated from the network. If not specified, the default
gateway of the console network is used. Can specify multiple isolation addresses (up to 10).
das.usedefaultisolationaddress Specifies whether or not this default is used (true|false).
VCP-410 questions das.failuredetectiontime Failure detection time for host monitoring. The default is 15000 milliseconds
das.failuredetectioninterval Heartbeat interval among VMware HA hosts. Default is 1000 milliseconds.
das.defaultfailoverhost The host that VMware HA tries to fail virtual machines over to.
das.isolationShutdownTimeout Time the system waits for a VM to shut down before powering it off. Default is 300 seconds.
das.slotMemInMB The maximum bound on the memory slot size.
das.slotCpuInMHz The maximum bound on the CPU slot size.
das.vmMemoryMinMB Memory resource value assigned to a VM if it’s not specified or zero. Default is 0 MB.
das.vmCpuMinMHz Default CPU resource value assigned to a VM if it’s not specified or zero. Default is 256MHz.
das.iostatsInterval I/O stats interval for VM monitoring sensitivity. Default is 120 (seconds).
o If you change the value of any of the following advanced attributes, you must disable and then re-enable VMware HA before your changes
take effect.
o das.isolationaddress[...]
o das.usedefaultisolationaddress
o das.failuredetectiontime
o das.failuredetectioninterval
o das.isolationShutdownTimeout
o On ESX hosts, HA communications travel over service console networks.
o On ESXi hosts, HA communications travel over VMkernel networks.
o HA needs and automatically opens the following firewall ports:
o Incoming port: TCP/UDP 8042-8045
o Outgoing port: TCP/UDP 2050-2250
o VMware Fault Tolerance provides continuous availability for virtual machines by creating and maintaining a Secondary VM that is identical to,
and continuously available to repla VCP-410 dumps ce, the Primary VM in the event of a failover situation.
o A fault tolerant VM and its secondary copy are not allowed to run on the same host. Fault Tolerance uses anti-affinity rules.
o Fault Tolerance prerequisites:
o VMware HA must be enabled on the cluster. Host Monitoring should also be enabled.
o Host certificate checking must be enabled for all hosts.
o Each host must have a VMotion and a Fault Tolerance Logging NIC configured.
o Hosts must have the same version and patch level.
o Hosts must have processors from the FT-compatible processor group.
o Hosts must have Hardware Virtualization (HV) enabled in the BIOS.
o Virtual machines must be stored in virtual RDM or VM disk (VMDK) files that are thick provisioned with the Cluster Features option.
o Virtual machines must be running on one of the supported guest operating systems.
o Not supported for fault tolerant virtual machines.
o Snapshots.
o Storage VMotion
o DRS features
o SMP virtual machines
o Physical RDMs
o Paravirtualized guests
o NPIV
o NIC passthrough
o EPT/RVI
o You should have no more than four fault tolerant virtual machines (primaries or secondaries) on any single host.
o The recommendation is that you use a maximum of 16 virtual disks per fault tolerant virtual machine.
Appendix – Fault Tolerance Error Messages
vSphere Web Access Administrator’s Guide
o Supported Operating Systems:
o Windows 2003 SP1, XP Pro SP3, XP Home SP2, 2000 SP4
o Linux with standard libraries, but requiring GTK+ 2.
o Supported browsers:
o IE 6, 7 or later
o Firefox 2, 3.0 or later
Passed VCP-410 o The console webAccess service is now vmware-webAccess
o The Alarms tab is available only when you use vSphere Web Access to connect to vCenter Server.
o You can view the assigned tasks for a virtual machine, but you cannot assign tasks using Web Access.
o New disk policy (not available option from vSphere Client)
o Optimize for safety – Saves all changes to the virtual disk before notifying the system

Periodically (every two seconds by default), the system examines the loads of the various nodes and determines if it should rebalance the load
by moving a virtual machine from one node to another.
o Transparent page sharing has also been optimized for use on NUMA systems.
o The VMkernel.Boot.sharePerNode option VCP-410 exam controls whether memory pages can be shared (de-duplicated) only within a single NUMA node or
across multiple NUMA nodes. It is turned on by default.
o If you turn off the option, identical pages can be shared across different NUMA nodes. In memory-constrained environments, such as VMware
View this could be very beneficial.
o The systems that offer a NUMA platform include AMD CPUs or the IBM Enterprise X-Architecture.
o You must manually select the boxes for all processors in the NUMA node. CPU affinity is specified on a per-processor, not on a per-node, basis.
o Specify nodes to be used for future memory allocations only if you have also specified CPU affinity.
Appendix A - Performance Monitoring Utilities: resxtop and esxtop
o The esxtop utility reads its default configuration from .esxtop4rc.
o Do not edit the .esxtop4rc file. Instead, select the fields and the order in a running esxtop process, make changes, and save this file using
the W interactive command.
Appendix B – Advanced attributes
vSphere Availability Guide
o The first five hosts added to the cluster are designated as primary hosts, and all subsequent hosts are designated as secondary hosts. The
primary hosts maintain and replicate all cluster state and are used to initiate failover actions. If a primary host is removed from the cluster,
VMware HA promotes another host to primary status.
o One of the primary hosts is also designated as the active primary host and its responsibilities include:
o Deciding where to restart virtual machines.
o Keeping track of failed restart attempts.
o Determining when it is appropriate to keep trying to restart a virtual machine.
o If the active primary host fails, another primary host replaces it.
o If a host stops receiving heartbeats from all other hosts in the cluster for more than 12 seconds, it attempts to ping its isolation addresses. If
this also fails, the host declares itself as isolated from the network.
o Three types of admission control:
VCP-410 exam questions /> o Host
o Resource pool
o HA
o Only VMware HA admission control can be disabled.
o Slot size is a logical representation of the memory and CPU resources that satisfy the requirements for any powered-on virtual machine in the
cluster.
o The maximum Configured Failover Capacity that you can set is four.
o If your cluster contains any virtual machines that have much larger reservations than the others, they will distort slot size calculation. To avoid
this, you can specify an upper bound for the CPU or memory component of the slot size by using the das.slotCpuInMHz or das.slotMemInMB
advanced attributes, respectively.
o You can configure VMware HA to perform admission control by reserving a specific percentage of cluster resources for recovery from host
failures.
o You can configure VMware HA to designate a specific host as the failover host.
o To ensure that spare capacity is available on the failover host, you are prevented from powering on virtual machines or using VMotion to
migrate virtual machines to the failover host.
o When choosing an admission control policy, you should consider a number of factors:
o Avoiding Resource Fragmentation - The Host Failures Cluster Tolerates policy avoids resource fragmentation by defining a slot as the
maximum virtual machine reservation. The Percentage of Cluster Resources policy does not address the problem of resource
fragmentation. With the Specify a Failover Host policy, resources are not fragmented because a single host is reserved for failover.
o Flexibility of Failover Resource Reservation - The Host Failures Cluster Tolerates policy allows you to set the failover level from one to four
hosts. The Percentage of Cluster Resources policy allows you to designate up to 50% of cluster resources for failover. The Specify a
Failover Host policy only allows you to specify a single failover host.
o Heterogeneity of Cluster - In a heterogeneous cluster, the Host Failures Cluster Tolerates policy can be too conservati VCP-410 study guide ve because it only
considers the largest virtual machine reservations when defining slot size and assumes the largest hosts fail when computing the Current
Failover Capacity. The other two admission control policies are not affected by cluster heterogeneity

The VMware vSphere storage architecture consists of layers of abstraction that hide and manage the complexity and differences among physical storage subsystems.
This storage architecture is shown in Figure 10.
Figure 10. Storage Architecture
To the applications and guest operating systems inside each virtual machine, the storage subsystem appears a VCP-410 dumps s a virtual SCSI controller connected to one or more virtual SCSI disks as shown in Figure 10. These controllers are the only types of SCSI controllers that a virtual machine can see and access, and include BusLogic Parallel, LSI Logic Parallel, LSI Logic SAS, and VMware Paravirtual.
The virtual SCSI disks are provisioned from datastore elements in the datacenter. A datastore is like a storage appliance that delivers storage space for virtual machines across multiple physical hosts.
The datastore abstraction is a model that assigns storage space to virtual machines while insulating the guest from the complexity of the underlying physical storage technology. The guest virtual machine is not exposed to Fibre Channel SAN, iSCSI SAN, direct attached storage, and NAS.
Each virtual machine is stored as a set of files in a directory in the datastore. The disk storage associated with each virtual guest is a set of files within the guest's directory. You can operate on the guest disk storage as an ordinary file. It can be copies, moved, or backed up. New virtual disks can be added to a virtual machine without powering it down. In that case, a virtual disk file (.vmdk) is created in VMFS to provide new storage for the added virtual disk or an existing virtual disk file is associated with a virtual machine.
Each datastore is a physical VMFS volume on a storage device. NAS datastores are an NFS volume with VMFS characteristics. Datastores can span multiple physical storage subsystems. As shown in Figure 10, a single VMFS volume can contain one or more LUNs from a local SCSI disk array on a physical host, a Fibre Channel SAN disk farm, or iSCSI SAN disk farm. New LUNs added to any of the physical storage subsystems are detected and made available to all existing or new datastores. Storage capacity on a previously created datastore can be extended without powering down physical hosts or storage subsystems. If any of the LUNs within a VMFS volume fails or becomes unavailable, only virtual machines that touch that LUN are affected VCP-410 . An exception is the LUN that has the first extent of the spanned volume. All other virtual machines with virtual disks residing in other LUNs continue to function as normal.
VMFS is a clustered file system that leverages shared storage to allow multiple physical hosts to read and write to the same storage simultaneously. VMFS provides on-disk locking to ensure that the same virtual machine is not powered on by multiple servers at the same time. If a physical host fails, the on-disk lock for each virtual machine is released so that virtual machines can be restarted on other physical hosts.
VMFS also features failure consistency and recovery mechanisms, such as distributed journaling, a failure-consistent virtual machine I/O path, and machine state snapshots. These mechanisms can aid quick identification of the cause and recovery from virtual machine, physical host, and storage subsystem failures.
VMFS also supports raw device mapping (RDM). RDM provides a mechanism for a virtual machine to have direct access to a LUN on the physical storage subsystem (Fibre Channel or iSCSI only). RDM is useful for supporting two typical types of applications:
■

SAN snapshot or other layered applications that run in the virtual machines. RDM better enables scalable backup offloading systems using features inherent to the SAN.
■

Microsoft Clustering Services (MSCS) spanning physical hosts and using virtual-to-virtual clusters as well as physical-to-virtual clusters. Cluster data and quorum disks must be configured as RDMs rather than files on a shared VMFS.
Figure 11. Raw Device Mapping
VCP-410 braindump An RDM is a symbolic link from a VMFS volume to a raw LUN. The mapping makes LUNs appear as files in a VMFS volume. The mapping file, not the raw LUN, is referenced in the virtual machine configuration.
When a LUN is opened for access, the mapping file is read to obtain the reference to the raw LUN. Thereafter, reads and writes go directly to the raw LUN rather than going through the mapping file.

ESX/ESXi uses at least 50MB of system memory for the VMkernel. This is not configurable. It depends on the number and type of PCI devices.
An ESXi host uses additional system memory for management agents.
o The service console typically uses 272MB.
o Memory activity is monitored to estimate the working set sizes for a default period of 60 seconds.
o ESX/ESXi charges more for idle memory than for memory that is in use. This is done to help prevent virtual machines from hoarding idle
memory.
o Hosts can reclaim memory fr VCP-410 exam questions om virtual machines using:
o Memory balloon driver (vmmemctl) - collaborates with the server to reclaim pages that are considered least valuable by the guest
operating system. Closely matches the behavior of a native system under similar memory constraints. Causes the guest to use its own
native memory management algorithms. You must configure the guest operating system with sufficient swap space.
o Swap Files - hosts use swapping to forcibly reclaim memory from a virtual machine when the vmmemctl driver is not available or is not
responsive. You must reserve swap space for any unreserved virtual machine memory (the difference between the reservation and the
configured memory size) on per-virtual machine swap files.
o If you are overcommitting memory, to support the intra-guest swapping induced by ballooning, ensure that your guest operating systems also
have sufficient swap space. This guest-level swap space must be greater than or equal to the difference between the virtual machine’s
configured memory size and its Reservation.
o Many workloads present opportunities for sharing memory across virtual machines.
o To determine the effectiveness of memory sharing use resxtop or esxtop to observe the actual savings. The PSHARE field of the interactive
mode in the Memory page.
o You measure guest physical memory using the Memory Granted metric (for a virtual machine) or Memory Shared (for an ESX/ESXi host). To
measure machine memory, however, use Memory Consumed (for a virtual machine) or Memory Shared Common (for an ESX/ESXi host).
o The VMkernel maps guest physical memory to machine memory.
o Multiple regions of guest physical memory might be mapped to the same region of machine memory (in the case of memory sharing) or
specific regions of guest physical memory might not be mapped to machine memory (when the VMkernel swaps out or balloons guest physical
memory)
o Resource Pool Hierarchy can have Parents, Children, and Siblings.
o Resource Pool Admission Control - Before you power on a virtual machine or create a resource pool, check the CPU Unreserved and Memory
Unreserved fields in the resource pool’s Resource Allocation tab to determine whether sufficient resources are available.
o A group power on will power on multiple virtual machines at the same time.
o VMotion does not support raw disks or migration of applications clustered using Microsoft Cluster Service (MSCS).
o Other VMware products or features, such as VMware vApp and VMware Fault Tolerance, might override the automation levels of virtual
machines in a DRS cluster.
o An affinity rule specifies that two or more virtual VCP-410 study guide machines be placed on the same host. An anti-affinity DRS rule is limited to two virtual
machines,
o If two rules conflict, the older one will take precedence, and the newer rule is disabled.
o Disabled rules are ignored. DRS gives higher precedence to preventing violations of anti-affinity rules than violations of affinity rules.
o When a host machine is placed in standby mode, it is powered off.
o Hosts are placed in standby mode by the VMware DPM feature
o A cluster becomes overcommitted (yellow) when the cluster does not have the capacity to support all resources reserved by the child resource
pools. Typically this happens when cluster capacity is suddenly reduced.
o A cluster enabled for DRS becomes invalid (red) when the tree is no longer internally consistent, that is, resource constraints are not observed.
o VMware DPM can use one of three power management protocols
o IPMI - Intelligent Platform Management Interface
o iLO - Hewlett-Packard Integrated Lights-Out
o WOL - Wake-On-LAN
o If a host supports multiple protocols, they are used in the following order: IPMI, iLO, WOL.
o The VMotion NIC on each host must support WOL to use that protocol.
o The DRS threshold and the VMware DPM threshold are essentially independent. You can differentiate the aggressiveness of the migration and
host-power-state recommendations.
o Verify that DPM is functioning properly by viewing each host’s Last Time Exited Standby information.
o The most serious potential error you face when using VMware DPM is the failure of a host to exit standby mode when its capacity is needed
by the DRS cluster. Use the preconfigured Exit Standby Error alarm for this error.
o DRS Recommendations have 5 levels (1-5). Priority 1, the highest, indicates a mandatory move because of a host entering maintenance or
standby mode or DRS rule violations. Other priority ratings denote how much the recommendation would improve the cluster’s performance;
o Prior to ESX/ESXi 4.0, recommendations received a star rating (1 to 5 stars) instead of a priority level.
o Non-Uniform Memory Access (NUMA) systems are advanced server platforms with more than one system bus.
VCP-410 questions o Some virtual machines are not managed by the ESX/ESXi NUMA scheduler: if you manually set the processor affinity for a virtual machine, or
virtual machines that have more virtual processors than the number of physical processor cores available on a single hardware node.
o When a virtual machine is powered on, ESX/ESXi assigns it a home node. This is initially assigned to home nodes in a round robin fashion

VMware vSphere has a set of virtual networking elements that lets you network the virtual machines in the data center like a physical environment.
Figure 8. Networking with vNetwork Standard Switches
Figure 8 shows the relationship between the networks inside and outside the virtual environment for vVCP-410 Switches. The virtual environment provides networking elements similar to the physical world. They are virtual network interface cards (vNIC), vNetwork Standard Switches (vSwitch), vNetwork Distributed Switches (dvSwitch), and port groups. dvSwitch networking is shown in Figure 9.
Like a physical machine, each virtual machine has one or more vNICs. The guest operating system and application programs communicate with a vNIC through either a commonly available device driver or a VMware device driver optimized for the virtual environment. In either case, communication in the guest operating system occurs just as it would with a physical device. Outside the virtual machine, the vNIC has its own MAC address and one or more IP addresses, and responds to the standard Ethernet protocol as would a physical NIC. An outside agent does not detect that it is communicating with a virtual machine.
A virtual switch works like a layer 2 physical switch. Each server has its own virtual switches. On one side of the virtual switch are port groups that connect to virtual machines. On the other side are uplink connections to physical Ethernet adapters on the server where the virtual switch resides. Virtual machines connect to the outside world through the physical Ethernet adapters that are connected to the virtual switch uplinks.
A virtual switch can connect its uplinks to more than one physical Ethernet adapter to enable NIC teaming. With NIC teaming, two or more physical adapters can be used to share the traffic load or provide passive failover in the event of a physical adapter hardware failure or a network outage. For information on NIC teaming, see the ESX Configuration Guide or ESXi Configuration Guide.
A vNetwork Distributed Switch (dvSwitch) functions as a single virtual switch across all associated hosts. This allows virtual machines to maintain consistent network configuration as they migrate across multiple hosts. Like a vSwitch, each dvSwitch is a network hub that virtual machines can use. A vSwitch can route traffic internally between virtual machines or link to an external network by connecting to physical Ethernet adapters. Each vSwitch can also have one or more dvPort groups assigned to it. dvPort groups aggregate multiple ports under a common configuration and provide a stable anchor point for virtual machines connecting to labeled networks.
Figure 9. Networking with vNetwork Distributed Switches
Port group is a unique concept in the virtual environment. A port group is a mechanism for setting policies that govern the network connected to it. A vSwitch can have multiple port groups. Instead of connecting to a particular port on the vSwitch, a virtual machine connects its vNIC to a port group. All virtual machines that connect to the same port group VCP-410 braindump belong to the same network inside the virtual environment even if they are on different physical servers.
You can configure port groups to enforce policies that provide enhanced networking security, network segmentation, better performance, high availability, and traffic management.
Layer 2 security options

Enforces what vNICs attached to a port group in a virtual machine can do by controlling capabilities for a promiscuous mode, MAC address changes, or forged transmissions.
VLAN support

Integrates virtual networks with physical network VLANs.
Private VLAN

Allows use of VLAN IDs within a private network without having to worry about duplicating VLAN IDs across a wider network.
Traffic shaping

Defines QOS policies for average and peak band VCP-410 exam width, and traffic burst size. You set policies to improve traffic management.
NIC teaming

Sets the NIC teaming policies for an individual port group or network to share traffic load or provide failover in case of hardware failure.

• Principal
• Archives
• Albums
• Liens

«	Août 2010					»
Lu	Ma	Me	Je	Ve	Sa	Di
						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30	31

• VCP-410 Dumps
• VCP-410 Real Exam Questions
• Testking VCP-410
• VCP-410 Test Questions
• VMware VCP-410 Exam
• VCP-410 Dumps
• Testking VCP-410
• VCP-410 Test Questions
• VMware VCP-410 Exam
• VCP-410 Dumps

• Général [11]

• RSS 0.90
• RSS 1.0
• RSS 2.0