Testking VCP-410
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 controls whether memory pages 220 702 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:
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 9L0-403 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. 9L0-510 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 conservative 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.
VCP-410 Test Questions
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 220 701 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 from 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 220 702 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 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 220 701 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.
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 VCP-410 Exam
Perform a rescan each time you make one of the following changes:
o Create new LUNs on a SAN.
o Change the path masking on a host.
o Reconnect a cable.
o Make a change to a host in a cluster.
o Change CHAP settings or add new discovery addresses.
o If you notice unsatisfactory performance for your software iSCSI LUNs, you can change their 640 802 Dumps maximum queue depth by using the vicfgmodule
command.
o The iscsi_max_lun_queue parameter is used to set the maximum outstanding commands, or queue depth, for each LUN accessed through the
software iSCSI adapter. The default is 32, and the valid range is 1 to 255.
o Setting the queue depth higher than the default can decrease the total number of LUNs supported.
Appendix A - iSCSI SAN Configuration Checklist
o Set the following Advanced Settings for the ESX/ESXi host:
o Set Disk.UseLunReset to 1
o Set Disk.UseDeviceReset to 0
Appendix B - VMware vSphere Command-Line Interface
o The resxtop command provides a detailed look at ESX/ESXi resource use in real time.
o The vicfg-iscsi command allows you to configure software or hardware iSCSI on ESX/ESXi hosts, set up CHAP parameters, and set up
iSCSI networking.
o Use the vicfg-mpath command to view information about storage devices, paths, and multipathing plugins.
o Use the esxcli corestorage claimrule command to manage claim rules. Claim rules determine which multipathing module should
claim paths to a particular device and manage the device.
o The vmkping command allows you to verify the VMkernel networking configuration.
Appendix C - Managing Storage Paths and Multipathing Plugins (Same as Appendix B in the Fibre Channel SAN Configuration Guide)
Resource Management Guide
o The need for resource management arises from the over-commitment of resources.
o Resources include CPU, memory, power, storage, and network resources.
o The guide focuses primarily on CPU and memory. Power resource consumption can also be reduced with the Distributed Power Management
(DPM) feature.
o ESX/ESXi manages network bandwidth and disk resources on a per-host basis, using network traffic shaping and a 640-802 proportional share
mechanism, respectively.
o Shares specify the relative priority or importance of a virtual machine (or resource pool).
o Shares are typically specified as High, Normal, or Low and these values specify share values with a 4:2:1 ratio. (or can set Custom value)
o A reservation specifies the guaranteed minimum allocation for a virtual machine.
o The reservation is expressed in concrete units (megahertz or megabytes).
o Reservation defaults to 0.
o Limit specifies an upper bound for CPU or memory resources that can be allocated to a virtual machine. It never gets more than this.
o A limit is expressed in concrete units (megahertz or megabytes).
o CPU and memory limit default is unlimited.
o Using limits can be beneficial if you want to manage user expectations, but might waste idle resources.
o Expandable Reservation defines whether reservations are considered during admission control.
o Overhead Reservation is the amount of the “Reserved Capacity” field that is being reserved for virtualization overhead.
o Worst Case Allocation is the amount of (CPU or memory) resource that is allocated to the virtual machine based on user-configured resource
allocation policies (for example, reservation, shares and limit), and with the assumption that all virtual machines in the cluster consume their
full amount of allocated resources.
o Admission Control - If enough unreserved CPU and memory are available, or if there is no reservation, the virtual machine is powered on.
Otherwise, an Insufficient Resources warning appears.
o ESX/ESXi cannot enable hyperthreading on a system with more than 32 physical cores, because ESX/ESXi has a logical limit of 64 CPUs.
o Hyperthreaded Core Sharing Modes:
o Any - can freely share cores with other 640 802 braindumps virtual CPUs.
o None - each virtual CPU should always get a whole core to itself, with the other logical CPU on that core being placed into the halted
state.
o Internal - cannot share cores with vCPUs from other virtual machines. Can share cores with the other virtual CPUs from the same virtual
machine. Only for SMP virtual machines.
o For the best performance, when you use manual affinity settings, include at least one additional physical CPU in the affinity setting to allow at
least one of the virtual machine's threads to be scheduled at the same time as its virtual CPUs.
o Dynamic Voltage and Frequency Scaling (DVFS) - You can configure your hosts to dynamically switch CPU frequencies based on workload
demands.
VCP-410 Dumps
On ESXi, it is not possible to rescan a single storage adapter.
o You can modify the Disk.MaxLUN parameter to improve LUN discovery speed.
o You cannot discover LUNs with a LUN ID number that is greater than 255.
o You can disable the default sparse LUN support to decrease the time ESX/ESXi needs to scan for LUNs.
o The sparse LUN support enables the VMkernel to perform uninterrupted LUN scanning when a storage system presents LUNs with
nonsequential LUN numbering.
o NPIV enables a single FC HBA port to vcp 4 register several unique WWNs with the fabric, each of which can be assigned to an individual virtual
machine.
o The virtual machine’s configuration file (.vmx) is updated to include a WWN pair (consisting of a World Wide Port Name and a World Wide
Node Name).
o If NPIV is enabled, four WWN pairs (WWPN & WWNN) are specified for each virtual machine at creation time. All physical paths must be
zoned to the virtual machine.
o NPIV can only be used for virtual machines with RDM disks. Physical HBAs, must have access to all LUNs that are to be accessed by virtual
machines running on that host.
o By default, the host performs a periodic path evaluation every 5 minutes causing any unclaimed paths to be claimed by the appropriate MPP.
o Make sure read/write caching is enabled.
o Dynamic load balancing is not currently supported with ESX/ESXi.
o Path thrashing only occurs on active-passive arrays
Appendix A – Multipathing Checklist
Appendix B – Managing Storage Paths and Multipathing Plugins
o Claim rules indicate which multipathing plugin, the NMP (Native MP) or any third-party MPP, manages a given physical path.
o List claim rules esxcli corestorage claimrule list
o To list all multipathing modules: vicfg-mpath --server --list-plugins
o List all VMware SATPs: esxcli nmp satp list
o List all storage devices: esxcli nmp device list
iSCSI SAN Configuration Guide
o There is no mention of requiring a Service Console connection for iSCSI anymore.
o Virtual SCSI controllers - BusLogic Parallel, LSI Logic Parallel, LSI Logic SAS, and VMware Paravirtual.
o iSCSI Name identifies a particular iSCSI vmware vcp 4 element. The iSCSI name can use either IQN or EUI format.
o IQN (iSCSI qualified name) - can be up to 255 characters long and has the following format: iqn.yyyy-mm.naming-authority:unique_name
o EUI (extended unique identifier) - takes the form eui.<16 hex digits>
o iSCSI aliases - not unique, and are intended to be just a friendly name to associate with the node.
o You must enable your software iSCSI initiator so that ESX can use it to access iSCSI storage.
o Dynamic Discovery - Also known as Send Targets discovery responds by supplying a list of available targets to the initiator. The names and IP
addresses of these targets appear on the Static Discovery tab. If you remove a static target added by dynamic discovery, the target might be
returned to the list the next time a rescan happens, the HBA is reset, or the host is rebooted.
o Static Discovery - The initiator does not have to perform any discovery.
o Dynamic discovery obtains a list of accessible targets from the iSCSI storage system, while static discovery can only try to access one particular
target by target name.
o You cannot change the IP address, DNS name, or port number of an existing Send Targets server. To make changes, delete the existing server
and add a new one.
o To protect the integrity of iSCSI headers and data, the iSCSI protocol defines error correction methods known as header digests and data
digests. Both parameters are disabled by default, but you can enable them.
o Check the end-to-end, noncryptographic data integrity beyond the integrity checks that other networking layers provide.
o Enabling header and data digests does require additional processing for both the initiator and the target. Intel Nehalem processors offload
the iSCSI digest calculations.
o Use the esxcli command to connect the VMkernel ports to the software iSCSI initiator.
o Jumbo Frames up to 9kB (9000 Bytes) are supported.
o You cannot change the IP address, DNS name, iSCSI target name, or port number of an existing target. To make changes, remove the existing
target and add a new one.
o iSCSI requires that all devices on the network implement Challenge Handshake Authentication Protocol (CHAP), 640 802 which verifies the legitimacy
of initiators that access targets on the network. (EDIT - I don’t think its “required”)
o ESX/ESXi supports one-way CHAP for both hardware and software iSCSI, and mutual CHAP for software iSCSI only.
o For software iSCSI only, you can set one-way CHAP and mutual CHAP for each initiator or at the target level.
o Hardware iSCSI supports CHAP only at the initiator level.
o For software iSCSI, the CHAP name should not exceed 511 and the CHAP secret 255 alphanumeric characters.
o For hardware iSCSI, the CHAP name should not exceed 255 and the CHAP secret 100 alphanumeric characters.
o Boot from a SAN - ensure that the LUN is presented to the ESX system as LUN 0. The host can also boot from LUN 255.
VCP-410 Real Exam Questions
Appendix A – ESX Technical Support Commands
Command Purpose
esxcfg-advcfg advanced options
esxcfg-auth Configures authentication
esxcfg-boot bootstrap settings
esxcfg-dumppart Configures a diagnostic vcp-410 partition
esxcfg-firewall service console firewall ports
esxcfg-info Information about the state of the service console, VMkernel, various subsystems in the virtual network, and
storage resource hardware.
esxcfg-init Internal initialization routines. Used for the bootstrap process you should not use it under any circumstances.
esxcfg-module Sets driver parameters and modifies which drivers are loaded during startup.
esxcfg-mpath multipath settings for your Fibre Channel or iSCSI disks.
esxcfg-nas Manages NFS mounts
esxcfg-nics physical network adapters
esxcfg-resgrp resource group settings
esxcfg-route default VMkernel gateway route
esxcfg-swiscsi software iSCSI software adapter.
esxcfg-upgrade Upgrades from ESX Server 2.x to ESX.
esxcfg- scsidevs Prints a map of VMkernel storage devices to service console devices.
esxcfg-vmknic VMkernel TCP/IP settings for VMotion, NAS, and iSCSI.
esxcfg-vswif service console network settings.
esxcfg-vswitch virtual machine network settings.
Appendix B – Linux Commands Used with ESX
Appendix C – Using vmkfstools
o vmkfstools utility is used to create and manipulate virtual disks, file systems, logical volumes, and vmware vcp 410 physical storage devices.
Fibre Channel SAN Configuration Guide
o Zones define which HBAs can connect to which SPs.
o Zoning is similar to LUN masking, which is commonly used for permission management. Usually, LUN masking is performed at the SP or server
level.
o WWPN (World Wide Port Name) is a globally unique identifier for a port.
o Port ID (or port address) enables routing. FC switches assign the port ID when the device logs in to the fabric.
o When N-Port ID Virtualization (NPIV) is used, a single FC HBA port (N-port) can register with the fabric by using several WWPNs.
o active-active - access to the LUNs simultaneously through all the storage ports that are available, without significant performance degradation.
o active-passive - one port is actively providing access to a given LUN. The other ports act as backup
o Disk shares are relevant only within a given ESX/ESXi host.
o Virtual machine I/O might be delayed for up to sixty seconds while path failover takes place. I/O delays might be longer on active-passive
arrays.
o On virtual machines running Microsoft Windows, increase the value of the SCSI TimeoutValue parameter to 60.
o Only one VMFS volume per LUN.
o Unless you are using diskless servers, do not set up the diagnostic partition on a SAN LUN.
o ESX/ESXi does not support FC connected tape devices.
o You cannot use virtual machine logical-volume manager software to mirror virtual disks. Dynamic disks on a Microsoft Windows virtual
machine are an exception, but require special configuration.
o You should not mix FC HBAs from different vendors in a single server.
o Use a dedicated SCSI adapter for any tape drives that you are connecting to an ESX/ESXi system.
o You should not use boot from SAN in the following situations:
o If you are using Microsoft Cluster Service.
o If I/O contention might occur between the service console and VMkernel.
o Proper LUN masking is critical in boot from SAN mode.
o Runtime Name - the name of the first path to the device. Created by the host. Is not a reliable vmware vcp 410 identifier for the device, and is not persistent.
o vmhba#:C#:T#:L#, where:
o vmhba# is the name of the storage adapter
o C# is the storage channel number.
o T# is the target number.
o L# is the LUN number
o If a target has only one LUN, the LUN number is always zero (0).
Testking VCP-410
vSphere supports a maximum of eight simultaneous VMotion, cloning, deployment, or Storage VMotion accesses to a single VMFS3
datastore, and a maximum of four simultaneous VMotion, cloning, deployment, or Storage VMotion accesses to a single NFS or VMFS2
datastore. A migration with VMotion involves one access to the datastore. A migration with Storage VMotion Passed VCP410
involves one access to the
source datastore and one access to the destination datastore
o Disks are converted from thin to thick format or thick to thin format only when they are copied from one datastore to another. If you choose
to leave a disk in its original location, the disk format is not converted.
o Thin or thick provisioned – not available for RDMs in physical compatibility mode. If you select this option for a virtual compatibility mode
RDM, the RDM is converted to a virtual disk. RDMs converted to virtual disks cannot be converted back to RDMs.
o You can run the storage vmotion command in either interactive or noninteractive mode.
o Interactive mode, type svmotion --interactive.
o Noninteractive mode: svmotion [Standard CLI options] --datacenter= --vm ‘:’ [--disks ‘:, :]’
o A snapshot captures the entire state of the VM at the time you take the snapshot. This includes:
o Memory state – The contents of the VM’s memory.
o Settings state – The VM settings.
o Disk state – The state of all the VM’s virtual disks.
o Snapshots of raw disks, RDM physical mode disks, and independent disks are not supported.
o Change Disk Mode to independent to Exclude Virtual Disks from Snapshots
o Persistent – Disks in persistent mode behave like conventional disks on your physical computer. All data written to a disk in persistent mode
are written permanently to the disk.
o Nonpersistent – Changes are discarded when you power off or reset the VM. Nonpersistent mode enables you to restart the VM with a virtual
disk in the same state every time. Changes to the disk are actually written to and read from a redo log file that is deleted when you power off
or reset.
o Snapshots:
o Delete – commits the snapshot data to Passed VCP 4
the parent and removes the selected snapshot.
o Delete All – commits all the immediate snapshots before the You are here current state to the base disk and removesall existing
snapshots for that VM.
o Revert to Snapshot – a shortcut to the parent snapshot of “You are here”.
o If you use Active Directory groups for permissions, make sure that they are security groups and not distribution groups.
o Users who are currently logged in and are removed from the domain retain their vSphere permissions only until the next validation period (the
default is every 24 hours).
o A role is a predefined set of privileges. Privileges define basic individual rights required to perform actions and read properties. When you
assign a user or group permissions, you pair the user or group with a role and associate that pairing with an inventory object.
o Default roles:
o System roles – System roles are permanent. You cannot edit the privileges associated with these roles.
o Sample roles – VMware provides sample roles for convenience as guidelines and suggestions. You can modify or remove these roles.
o You can also create completely new roles.
o All roles permit the user to schedule tasks by default. Users can schedule only tasks they have permission to perform at the time the tasks are
created.
o Default roles:
Role Role Type Description of User Capabilities
No Access system Cannot view or change the assigned object. available in ESX/ESXi and vCenter Server.
Read Only system View the state and details about the object. available on ESX/ESXi and vCenter
Server.
Administrator system All privileges for all objects. available in ESX/ESXi and vCenter Server.
Virtual Machine
Power User
sample allow the user to interact with vcp 410 and make hardware changes to VMs, as well as
perform snapshot operations. available only on vCenter Server.
Virtual Machine User sample allow the user to interact with a VM’s console, insert media, and perform power
operations. available only on vCenter Server.
Resource Pool
Administrator
sample allow the user to create child resource pools and modify the configuration of the
children, but not to modify the resource configuration of the pool or cluster on which
the role was granted. Also allows the user to grant permissions to child resource
pools, and assign VMs to the parent or child resource pools. available only on
vCenter Server.
VMware Consolidated
Backup User
sample used by the VMware Consolidated Backup product and should not be modified.
available only on vCenter Server.
Datastore Consumer sample allow the user to consume space on the datastores on which this role is granted.
available only on vCenter Server.
Network Consumer sample allow the user to assign VMs or hosts to networks available only on vCenter Server.
VCP-410 Test Questions
After you upgrade all of your hosts to ESX4/ESXi4, you can optionally uninstall your license server and remove the license server configuration
from vCenter Server.
o For ESXi, the vSphere Host Update Utility does not support roll back.
o You can remove the ESX 4.0 boot option from the ESX bootloader menu and perform a complete roll back to ESX 3.x. Any changes made to
the ESX 4.0 service console are lost after the rollback.
o Any changes made to VMs will persist after the rollback.
o If you upgraded the VM hardware, VCP-410 questions the VMs will not work after you perform the ESX rollback. To avoid this situation, take a snapshot of
the VM before you upgrade the VM hardware.
o Run the rollback-to-esx3 command – reconfigures the bootloader.
o Reboot the server.
o After the host boots into ESX 3.x, delete the ESX 4.0 service console VMDK folder from the VMFS datastore.
o Each time you update an ESXi host, a copy of the ESXi build is saved on your host.
o ESXi permits only one level of rollback.
o When you manually boot into the standby build instead of the current boot build, an irreversible rollback occurs.
o When the page that displays the current boot build appears, press Shift+r to select the standby build.
o Do not use vmware-vmupgrade.exe to upgrade VMs.
o Some VMs that you create on ESX4 hosts are supported on ESX 3.x/ESXi 3.5 hosts. If you create a VM on ESX4 and select the typical path, the
virtual hardware version is version 7. Virtual machines with virtual hardware version 7 are not supported on ESX 3.x/ESXi 3.5 hosts. Select the
custom path and select virtual hardware version 4
o If you create VMs that use paravirtualization (VMI) or an enhanced networking device (vmxnet), VMotion is not supported. In this case, you
can only move the VM to the ESX 3.x host if the VM is powered off.
o On Windows guest operating systems, you must reboot the VM a total of three times when you upgrade VMware Tools and the virtual
hardware:
1. Power on the VM.
2. Upgrade VMware Tools.
3. Reboot the VM at the end of the VMware Tools upgrade.
4. Power off the VM.
5. Upgrade the virtual Hardware.
6. Power on VCP-410 dumps the VM.
7. The Windows operating system detects new devices and prompts you to reboot the VM.
8. Reboot the VM to make the devices work properly.
o During the virtual hardware upgrade, the VM must be shut down for all guest operating systems.
o When you upgrade from virtual hardware version 3 to version 7, the upgrade is irreversible, even if you take a VM backup or snapshot before
performing the upgrade. 4 to version 7 the upgrade is reversible if you take a VM backup or snapshot
o Tools for installing updates and patches to ESX/ESXi hosts:
o Host Update Utility – graphical utility for ESXi only.
o Update Manager – for ESX and ESXi,
o vihostupdate – command-line utility for ESX and ESXi.
o esxupdate – command-line utility for ESX only.
o If the Host Update Utility does not meet the needs of your environment, you can customize the application the settings.config XML file,
located in %PROGRAMFILES%\VMware\Infrastructure\VIUpdate 4.0
o Run vihostupdate on ESX 4.0/ESXi 4.0 hosts. Run vihostupdate35 on ESX 3.5/ESXi 3.5 hosts.
o The esxupdate utility is supported as well. It is for ESX only.
o The vihostupdate command works with bulletins.
o You can use the vihostupdate utility in conjunction with offline bundles or with a depot.
o To Passed VCP-410 get the build number of an ESX4 host: # vmware –l (from KB 1001179).
vSphere Basic System Administration
o VMware modules (plugins) include:
o Update Manager
o Converter Enterprise
o vShield Zones – an application-aware firewall built for vCenter Server integration. It inspects client-server communications and intervirtual-
machine communication to provide detailed traffic analytics and application-aware firewall partitioning.
o Orchestrator – a workflow engine that enables you to create and execute automated workflows.
o Data Recovery – a disk-based backup and recovery solution. Enable centralized and efficient management of backup jobs and includes
data de-duplication.
o Tomcat Web server is installed as part of the vCenter Server installation. The components that require Tomcat are:
o Linked Mode
o CIM/Hardware Status tab
VMware VCP-410 Exam
Back up the VirtualCenter 2.x SSL certificates. %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter or
%ALLUSERSPROFILE%\VMware\VMware 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 copy 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 VCP-410 exam 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, VCP-410 exam questions exported VMs, and .iso files.
o Backup the ESXi Host Configuration: vicfg-cfgbackup --server --portnumber --
protocol --username username --password -s
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 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 VCP-410 study guide 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
VCP-410 Dumps
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 different domain accounts.
o Windows Server 2008 automatically configures the firewall to permit access. Launch firewall.cpl and add an exception for
C:\Windows\ADAM\dsamain.exe
o When you install vCenter Server in Linked Mode, the firewall VCP-410 exam questions 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 VCP-410 study guide 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
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 VCP-410 questions DNS nameserver
o Pings the secondary DNS nameserver
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.
VCP-410 Real Exam Questions
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-
/esxconsole.vmdk. The virtual disk is stored in a VMFS volume.
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 VCP-410 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. VCP-410 braindump 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
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:\WINDOWS\SYSWOW64\odbc32.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 VCP-410 exam 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 module 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
|
Despre mine
Links
Categorii
Postari recente
Testking VCP-410
VCP-410 Test Questions
VMware VCP-410 Exam
VCP-410 Dumps
VCP-410 Real Exam Questions
Prieteni
|
