reiki

Hosts, clusters, and resources pools provide flexible and dynamic ways to organize the aggregated computing and memory resources in the virtual environment and link them back to the underlying physical resources.
A host represents the aggregate computing and memory resources of a physical x86 server. For example, if the physical x86 server has four dual-core CPUs running at 4GHz each and 32GB of system memory, the host has 32GHz of computing power and 32GB of memory available for running virtual machines that are assigned to it.
A cluster acts and can be managed as a si 220 702 ngle entity. It represents the aggregate computing and memory resources of a group of physical x86 servers sharing the same network and storage arrays. For example, if the group contains eight servers with four dual-core CPUs each running at 4GHz and 32GB of memory. The cluster then has and aggregate 256GHz of computing power and 256GB of memory available for running virtual machines.
Resource pools are partitions of computing and memory resources from a single host or a cluster. Resource pools can be hierarchical and nested. You can partition any resource pool into smaller resource pools to further divide and assign resources to different groups or for different purposes.
Figure 4 illustrates the use of resource pools. Three x86 servers with 4GHz computing power and 16GB of memory each are aggregated to form a cluster of 12GHz computing power and 48GB of memory. The Finance Department resource pool reserves 8GHz of computing power and 32GB of memory from the cluster, leaving 4GHz computing power and 16GB of memory reserved for the other virtual machine. From the Finance Department resource pool, the smaller Accounting resource pool reserves 4GHz computing power and 16GB of memory for the virtual machines from the accounting department. That leaves 4GHz of computing power and 16GB of memory for the virtual machine called Payroll.
Figure 4. Hosts, Clusters, and Resource Pools
You can dynamically change resource allocation policies. For example, at year end, the workload on Accounting increases, and which requires an increase in the Accounting resource pool reserve 9L0-403 of 4GHz of power to 6GHz. You can make the change to the resource pool dynamically without shutting down the associated virtual machines.
When reserved resources are not being used by resource pool or virtual machine, they can be shared. In the example, if the 4GHz of resources reserved for the Accounting department are not being used, the Payroll virtual machine can use those gigahertz during its peak time. When Accounting resource demands increase, Payroll dynamically returns them. Even though resources are reserved for different resource pools, they are not wasted their owner does not use them. This capability helps to maximize resource utilization while also ensuring that reservations are met and resource policies enforced.
As demonstrated by the example, resource pools can be nested, organized hierarchically, and dynamically reconfigured so that the IT environment matches the company organization. Individual business units can receive dedicated resources while still exploiting from the efficiency of resource pooling.

QUESTION NO: 457
Resource pools at the same level are called?
A. Parent Pools
B. Root Resource Pools
C. Sibling Pools
D. Child Pools

Answer: C

QUESTION NO: 458
Assuming this is the only virtual machine, and the only resource pool, what is the
maximum amount of memory that could be configured for use by the virtual machine that
is part of the Finance Resource Pool?
A. 57 MB less virtual machine overhead
B. 13375 MB less virtual machine overhead
C. 16384 MB less virtual machine overhead
D. 3009 MB less virtual machine overhead

Answer: C

QUESTION NO: 459
An administrator has deployed a new virtual
machine on an ABC ESX Host, sc-vicuna04.vmeduc.com. Users are complaining of poor
performance on the applicati 9L0-510 on running on the virtual machine. Performance tools display
the results shown in the exhibit.
Which two tasks could you perform to try to improve the user experience (Choose Two)?
A. Remove the limit on the CPU settings of the virtual machine.
B. Add another vCPU to the virtual machine.
C. Migrate the virtual machine to another ESX host.
D. Remove CPU affinity on the Advanced CPU setting of the virtual machine.

Answer: A,B

The iSCSI initiator relies on being able to get MAC address changes from certain types of storage. If you are using ESX iSCSI and have iSCSI
storage, set the MAC Address Changes option to Accept.
o A legitimate need for more than one adapter to have the same MAC address, is if you are using Microsoft Network Load Balancing in unicast
mode. When NLB is used in t 220 701 he standard multicast mode, adapters do not share MAC addresses.
o ESX uses the Pluggable Authentication Modules (PAM) structure for authentication. The PAM configuration in /etc/pam.d/vmware-authd, ESX
uses /etc/passwd authentication, but you can configure ESX to use another distributed authentication mechanism.
o CIM transactions also use ticket-based authentication in connecting with the vmware-hostd process.
o Management functions with username/password > vmware-hostd > Service Console
o VM console with ticket > vmkauthd > vm in VMkernel
o vicfg commands do not perform an access check.
o The vpxuser is used for vCenter Server permissions.
o The root user and vpxuser permissions are the only users not assigned the No Access role by default.
o ESX supports SSL v3 and TLS v1.
o All network traffic is encrypted as long as:
o Did not change the Web proxy service to allow unencrypted traffic for the port.
o Service console firewall is configured for medium or high security.
o The default location for your certificate is /etc/vmware/ssl/ on the ESX host. The certificate consists of two files: the certificate itself (rui.crt)
and the private-key file (rui.key).
o The ESX host generates certificates the first time the system is started.
o Each time you restart the vmware-hostd process, the mgmt-vmware script searches for existing certificate files (rui.crt and rui.key). If it cannot
find them, it generates new certificate files.
o SSL timeout settings are set in /etc/vmware/hostd/config.xml.
o Do not set up certificates using passphrases.
o For certificates in a location other than the default location, set the location in /etc/vmware/hostd/proxy.xml.
o If you are performing activities that require root privileges, log in to the service console as a recognized user and acquire root privileges
through the sudo command, which provides e 220 702 nhanced security compared to the su command.
o The service console firewall is configured to block all incoming and outgoing traffic, except for ports 22, 123, 427, 443, 902, 5989, 5988, pings
(ICMP) and communication with DHCP and DNS (UDP only) clients.
o Medium security - All incoming traffic is blocked, except on the default ports and any ports you specifically open. Outgoing traffic is not
blocked.
o Low security - There are no blocks on either incoming or outgoing traffic. This setting is equivalent to removing the firewall.
o Password aging restrictions are enabled for user logins by default.
o Maximum days - By default, passwords are set to never expire.
o Minimum days - The default is 0, meaning that the users can change their passwords any time.
o Warning time - The default is seven days.
o To change this for hosts use esxcfg-auth. Change for users use the command chage.
o By default, ESX uses the pam_cracklib.so plug-in. There is no restrictions on the root password, but the defaults for non-root users is:
o minimum password length is nine
o password length algorithm allows shorter passwords if the user enters a mix of character classes. M – CC = E where the Character Classes
are upper, lower, digits and other.
o retries is set to three
o The pam_passwdqc.so provides a greater number of options for fine-tuning password strength and performs password strength tests for all
users, including the root user.
o setuid allows an application to temporarily change the permissions of the user running the application.
o setgid changes the permissions of the group running the application.
o Default setuid applications: crontab, pam_timestamp_check, passwd, ping, pwdb_chkpwd, ssh-keysign, su, sudo, unix_chkpwd, vmkload_app,
vmware-authd, vmware-vmx. Default setgid Applications: wall, lockfile.
o Virtual Machine Recommendations:
o Install Antivirus Software
220 701 o Disable Copy and Paste Operations Between the Guest Operating System and Remote Console
o Removing Unnecessary Hardware Devices
o Limiting Guest Operating System Writes to Host Memory
o Configuring Logging Levels for the Guest Operating System
o Host profiles eliminates per-host, configuration and maintain configuration consistency and correctness across the datacenter.
o Only supported for VMware vSphere 4.0 hosts.
o Host Profiles are only available when the appropriate licensing is in place.
o You can export a profile to a file that is in the VMware profile format (.vpf).

Key contents of the metadata in the mapping file include the location of the mapped device (name resolution), the locking state of the
mapped device, permissions, and so on.
o You cannot perform vMotion or Storage vMotion between datastores when NPIV is enabled.
640 802 Dumps h a firewall. It also mitigates risks using other methods:
o Only services essential to managing its functions.
o By default, installed with a high-security setting. All outbound ports are closed.
o By default, all ports not specifically required for management access to the service console are closed.
o By default, weak ciphers are disabled and all communications from clients are secured by SSL. Default certificates created on ESX use
SHA-1 with RSA encryption as the signature algorithm.
o The Tomcat Web service, has been modified to run only those functions required.
o VMware monitors all security alerts (for the RHEL5 distribution and 3rd party software).
o Insecure services such as FTP and Telnet are not installed.
o The number of applications that use a setuid or setgid flag is minimized.
o ESX can automate whether services start based on the status of firewall ports, but this only applies to service settings configured through the
vSphere Client or applications created with the vSphere Web services SDK. Doesn’t apply to changes made with the esxcfg-firewall utility or
configuration files in /etc/init.d/.
Port Purpose Interface Traffic type
22 SSH Server Service Console Incoming TCP
80 HTTP access and WS-Management Service Console Incoming TCP
123 NTP Client Service Console Outgoing UDP
427 The CIM client SLPv2 to find CIM servers. Service Console Incoming and
outgoing UDP
443 HTTPS access - vmware-hostd
vCenter Server access to ESX hosts
Client access to vCenter Server and ESX hosts
WS-Management
Client access to vSphere Update Manager
Converter access to vCenter Server
Web Access to vCenter Server and ESX hosts
Service Console Incoming TCP
640-802 902 Host access to other hosts for migration and provisioning
Authentication traffic for ESX (xinetd/vmware-authd)
Client access to virtual machine consoles (UDP) Status update (heartbeat)
connection from ESX to vCenter Server
Service Console Incoming TCP,
outgoing UDP
903 Remote console traffic from VI client & Web Access (xinetd/vmware-authd-mks) Service Console Incoming TCP
2049 Transactions from NFS storage devices VMkernel Incoming and
outgoing TCP
2050-2250 Between ESX hosts for HA and EMC Autostart Manager Service Console Outgoing TCP,
incoming and
outgoing UDP
3260 Transactions to iSCSI storage devices VMkernel &
Service Console
Outgoing UDP
5900-5964 RFB protocol, which is used by management tools such as VNC Service Console Incoming and
outgoing TCP
5989 CIM XML transactions over HTTPS Service Console Incoming and
outgoing TCP
8000 VMotion requests VMkernel Incoming and
outgoing TCP
8042-8045 Between ESX hosts for HA and EMC Autostart Manager Service Console Outgoing TCP,
incoming and
outgoing UDP
8100, 8200 Between ESX hosts for Fault Tolerance Service Console Outgoing TCP,
incoming and
640 802 braindumps outgoing UDP
PLUS installed management agents and supported services such as NFS.
o Create a separate VLAN for communication with the service console.
o Configure network access for connections with the service console through a single virtual switch and one or more uplink ports.

Mware vSphere virtualizes the entire IT infrastructure including servers, storage, and networks.
VMware vSphere aggregates these resources and presents a uniform set of elements in the virtual environment. With VMware vSphere, you can manage IT resources like a shared utility an vcp 4 d dynamically provision resources to different business units and projects.
Figure 3 shows the key elements in virtual datacenter.
Figure 3. Virtual Datacenter Architecture
You can use vSphere to view, configure, and manage these key elements. These elements include:
■

Computing and memory resources called hosts, clusters, and resource pools
■

Storage resources called datastores
■

Networking resources called networks
■

Virtual machines
A host is the virtual representation of the computing and memory resources of a physical machine running ESX/ESXi. When one or more physical machines are grouped together to work and be managed as a whole, the aggregate computing and memory resources form a cluster. Machines can be dynamically added or removed from a cluster. Computing and memory resources from hosts and clusters can be finely partitioned into a hierarchy of resource pools.
Datastores are virtual representations of combinations of underlying physical storage resources in the datacenter. These physical storage resources can come from the following:
vmware vcp 4 ■

Local SCSI, SAS, or SATA disks of the server
■

Fibre Channel SAN disk arrays
■

iSCSI SAN disk arrays
■

Network Attached Storage (NAS) arrays
Networks in the virtual environment connect virtual machines to one another and to the physical network outside of the virtual datacenter.
Virtual machines are designated to a particular host, cluster or resource pool, and a datastore when they are created. After they are powered-on, virtual machines consume resources dynamically as the workload increases or give back resources dynamically as the workload decreases.
Provisioning of virtual machines is much faster and easier than physical machines. New virtual machines can be created in seconds. When a virtual machine is provisioned, the appropriate operating system and applications can be installed unaltered on the virtual machine to handle a particular workload just as though they were being installed on a physical machine. A virtual machine can even be provisioned with the operating system and applications already installed and configured.
Resources get provisioned to virtual machines b 640 802 ased on the policies set by the system administrator who owns the resources. The policies can reserve a set of resources for a particular virtual machine to guarantee its performance. The policies can also prioritize and set a variable portion of the total resources to each virtual machine. A virtual machine is prevented from being powered-on and consuming resources if doing so violates the resource allocation policies. For more information on resource and power management, see the Resource Management Guide.

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

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

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

Each computing server can have multiple Ethernet network interface cards (NICs) to provide high bandwidth and reliable networking to the entire VMware vSphere datacenter.
vCenter Server

vCenter Server provides a single point of control to the datacenter. It provides essential datacenter services such as access control, performance monitoring, and configuration. It unifies the resources from the individual computing servers to be shared among virtual machines in the entire datacenter. It does this by managing the assignment of virtual machines to the computing servers and the assignment of resources to the virtual machines within a given computing server based on the policies that the system administrator sets.
Computing servers continue to function even in t vmware vcp 410 he unlikely event that vCenter Server becomes unreachable (for example, if the network is severed). They can be managed separately and continue to run the virtual machines assigned to them based on the resource assignmen vmware vcp 410 t that was last set. After connection to vCenter Server is restored, it can manage the datacenter as a whole again.
Management clients

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Use local SATA storage, internal and external, in unshared mode only.
o Some SAS storage systems can offer shared access
o You can have up to 256 VMFS datastores per system, with a minimum volume size of 1.2GB.
o Grow the existing datastore extent if the storage device where your datastore resides has free space. You can grow the VCP-410 questions extent up to 2 TB.
o You can connect up to 32 hosts to a single VMFS volume. (EDIT: Maximums document says 64)
o Perform a rescan each time you:
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 Do not rescan when a path is unavailable.
o To rescan adapters on all hosts managed by vCenter by right-clicking a datacenter, cluster, or folder and selecting Rescan for Datastores.
o ESX does not support the delegate user functionality that enables access to NFS volumes using non-root credentials
o Disk format on a NAS device is dictated by the NFS server, typically a thin format that requires on-demand space allocation.
o When your host accesses a virtual machine disk file on an NFS-based datastore, a .lck-XXX lock file is generated to prevent other hosts from
accessing this file.
o If the underlying NFS volume, is read-only, make sure that the volume is exported as a read-only share by the NFS server, or configure it as a
read-only on the ESX host.
o A diagnostic partition cannot be located on an iSCSI LUN accessed through a software iSCSI initiator.
o You can query and scan the host’s diagnostic partition using the vicfg-dumppart -l command
o You can group datastores into folders.
o You can unmount:
o NFS datastores
o VMFS datastore copies mounted without resignaturing
o You can have up to 32 extents.
VCP-410 dumps o You can grow an extent in an existing VMFS datastore. Only extents with free space immediately after them are expandable.
o If a shared datastore has powered on virtual machines and becomes 100% full, you can increase the datastore's capacity only from the host,
with which the powered on virtual machines are registered.
o You can mount a VMFS datastore only if it does not collide with an already mounted VMFS datastore that has the same UUID (signature).
o When resignaturing a VMFS copy, ESX assigns a new UUID and a new label to the copy, and mounts the copy as a datastore distinct from the
original.
o The default format of the new label assigned to the datastore is snap-<snapID>-<oldLabel>, where <snapID> is an integer and <oldLabel> is the
label of the original datastore.
o Datastore resignaturing is irreversible.
o A spanned datastore can be resignatured only if all its extents are online.
o Pluggable Storage Architecture (PSA) is an open modular framework that coordinates the simultaneous operation of multiple multipathing
plugins (MPPs). The VMkernel multipathing plugin that ESX provides by default is the VMware Native Multipathing Plugin (NMP). Two types of
NMP subplugins, Storage Array Type Plugins (SATPs), and Path Selection Plugins (PSPs).
o The VMware NMP supports all storage arrays listed on the VMware storage HCL and provides a default path selection algorithm based on the
array type.
o ESX offers an SATP for every type of array that VMware supports.
o By default, the VMware NMP supports the following PSPs:
o Most Recently Used (MRU)
o Fixed - with active-passive arrays that have a Fixed path policy, path thrashing might be a problem.
o Round Robin (RR) - Uses a path selection algorithm that rotates through all available paths enabling load balancing across the paths.
o Claim rules defined in the /etc/vmware/esx.conf file, the host determines which multipathing plugin (MPP) should claim the paths.
o By default, the host performs a periodic path evaluation every 5 minutes.
o Active multiple working paths currently used for transferring data are marked as Active (I/O). In ESX 3.5 or earlier, the term active means the
only path that the host is using to issue I/O to a LUN.
o Standby path is operational and can be used for I/O if active paths fail.
o If you created a virtual disk in the thin format, you can later inflate it to its full size.
o RDM offers several benefits. User-Friendly Persistent Names, Dynamic Name Resolution, Distributed File Locking, File Permissions, File System
Operations, Snapshots, vMotion, SAN Management Agents and N-Port ID Virtualization(NPIV).
Passed VCP-410 o Certain limitations exist when you use RDMs:
o Not available for block devices or certain RAID devices.
o Available with VMFS-2 and VMFS-3 volumes only.
o No snapshots in physical compatibility mode.
o No partition mapping. It requires a whole LUN.

o MAC Address Changes - the guest OS changes the MAC address of the adapter to anything other than what is in the .vmx
o Forged Transmits - Outbound frames with a source MAC address that is different from the one set on the adapter are dropped.
o Traffic shaping
o Traffic shaping policy is defined by three characteristics: average bandwidth, peak bandwidth, and burst size.VCP-410 exam r /> o ESX shapes outbound network traffic on vSwitches and both inbound and outbound traffic on a vNetwork Distributed Switch.
o Peak bandwidth cannot be less than the specified average bandwidth.
o NIC Teaming (Load balancing and failover)
o Load Balancing
1. Route based on the originating port ID — Choose an uplink based on the virtual port where the traffic entered the virtual
switch.
2. Route based on ip hash — Choose an uplink based on a hash of the source and destination IP addresses of each packet.
3. Route based on source MAC hash — Choose an uplink based on a hash of the source Ethernet.
4. Use explicit failover order — Always use the highest order uplink from the list of Active adapters which passes failover
detection criteria.
o IP-based teaming requires that the physical switch be configured with etherchannel. For all other options, etherchannel should
be disabled.
o Incoming traffic is controlled by the load balancing policy on the physical switch
o Network failover detection
o Link Status only
o Beacon probing - Do not use beacon probing with IP-hash load balancing.
o Notify Switches - a notification is sent out over the network to update the lookup tables on physical switches. In almost all cases, this
process is desirable for the lowest latency of failover occurrences and migrations with VMotion. Do not use this option when the
virtual machines using the port group are using Microsoft Network Load Balancing in unicast mode.
o Failback - determines how a physical adapter is returned to active duty after recovering from a failure. If failback is set to Yes
(default), the adapter is returned to active duty immediately upon recovery.
o Failover Order
1. Active Uplinks
2. Standby Uplinks
3. Unused Uplinks
o When using IP-hash load balancing, do not configure standby uplinks.
o VLAN - The VLAN policy allows virtual networks to join physical VLANs - vNetwork Distributed Switch only (dvPorts).
o Port blocking policies - vNetwork Distributed Switch only (dvPorts).
o VMware uses the Organizationally Unique Identifier (OUI) 00:50:56 for manually generated addresses. You must set them in a virtual
machine’s configuration file: ethernet<number>.addressType="static"
o Jumbo frames must be enabled at the host level using the command-line interface to configure the MTU size for each vSwitch.
o TCP Segmentation Offload (TSO) is enabled VCP-410 exam questions on the VMkernel interface by default, but must be enabled at the virtual machine level.
o To enable TSO at the virtual machine level, you must replace the existing vmxnet or flexible virtual network adapters with enhanced vmxnet
virtual network adapters. This might result in a change in the MAC address of the virtual network adapter.
o To check whether TSO is enabled on a particular VMkernel networking interface use the esxcfg-vmknic -l command. The list shows
each TSO-enabled VMkernel interface with TSO MSS set to 65535.
o If TSO is not enabled for a particular VMkernel interface, the only way to enable it is to delete the VMkernel interface and recreate the
interface.
o Jumbo frames up to 9kB (9000 bytes) are supported.
o Use the vicfg-vswitch -m <MTU> <vSwitch> command to set the MTU size for the vSwitch.
o Enabling jumbo frame support on a virtual machine requires an enhanced vmxnet adapter for that virtual machine.
o NetQueue in ESX takes advantage of the capability of some network adapters to deliver network traffic to the system in multiple receive
queues that can be processed separately. This allows processing to be scaled to multiple CPUs, improving receive-side networking
performance.
o NetQueue is enabled by default.
o ESX supports a direct PCI device connection for virtual machines running on Intel Nehalem platforms. Each virtual machine can connect to up
to 2 passthrough devices.
o The following features are unavailable for virtual machines configured with VMDirectPath:
VCP-410 study guide o VMotion
o Hot adding and removing of virtual devices
o Suspend and resume
o Record and replay
o Fault tolerance
o High availability
o DRS (limited availability; the virtual machine can be part of a cluster, but cannot migrate across hosts)
o Software-initiated iSCSI is not available over 10GigE network adapters in ESX.

4. Assign each physical NIC to a port group and a vSwitch.
5. Use separate physical NICs to handle the different traffic streams, such as network packets generated by VMs, iSCSI protocols, VMotion
tasks, and service console activities.
6. Ensure that the physical NIC capacity is large enough to handle the network traffic on that vSwitch. If the capacity is not enough, consider
using a high-bandwidth physical NIC (10Gbps) or moving some VMs to a vSwitch with a lighter load or to a n VCP-410 dumps ew vSwitch.
7. If packets are being dropped at the vSwitch port, increase the virtual network driver ring buffers where applicable.
8. Verify that the reported speed and duplex settings for the physical NIC match the hardware expectations and that the hardware is
configured to run at its maximum capability. For example, verify that NICs with 1Gbps are not reset to 100Mbps because they are
connected to an older switch.
9. Verify that all NICs are running in full duplex mode. Hardware connectivity issues might result in a NIC resetting itself to a lower speed or
half duplex mode.
10. Use vNICs that are TSO-capable, and verify that TSO-Jumbo Frames are enabled where possible.
o Tasks represent system activities that do not complete immediately, such as migrating a VM.
o If you are logged in to a vCenter Server system that is part of a Connected Group, a column in the task list displays the name of the vCenter
Server system on which the task was performed.
Appendix A – Defined privileges
Appendix B – Installing the MS sysprep tools
Appendix C – Performance metrics
ESX Configuration Guide
o A vNetwork Distributed Switch acts as a single vSwitch across all associated hosts on a datacenter. This allows virtual machines to maintain
consistent network configuration as they migrate across multiple hosts. A dvPort is a port on a vNetwork Distributed Switch.
o The VMkernel TCP/IP networking stack supports iSCSI, NFS, and VMotion. Virtual machines run their own systems’ TCP/IP stacks and connect
to the VMkernel at the Ethernet level through virtual switches.
o TCP Segmentation Offload (TSO), allows a TCP/IP stack to emit very large frames (up to 64KB) even though the maximum transmission unit
(MTU) of the interface is smaller. The network adapter then separates the large frame into MTU-sized frames and prepends an adjusted copy
of the initial TCP/IP headers.
o The default number of logical ports for a vSwitch is 56.
o Each uplink adapter associated with a vSwitch uses one port.
o You can create a maximum of 127 vSwitches on a single host. (EDIT the current Maximums PDF says 248)
o Maximum of 512 port groups on a single host.
o For a port group to reach port groups located on other VLANs, the VLAN ID must be set to 4095. If you enter 4095, the port group can see
traffic on any VLAN while leaving the VLAN tags intact.
o VLAN ID is a number between 1 and 4094.
o ESX supports only NFS version 3 over TCP/IP.
o You can create a maximum of 16 ser VCP-410 vice console ports in ESX.
o CDP advertisements typically occur once a minute.
o dvPort group properties include:
o Port Binding - when ports are assigned to virtual machines connected to this dvPort group.
o Static binding - to assign a port to a virtual machine when the virtual machine is connected to the dvPort group.
o Dynamic binding - to assign a port to a virtual machine the first time the virtual machine powers on after it is connected to the
dvPort group.
o Ephemeral - for no port binding.
o Whether to allow live port moving.
o Config reset at disconnect to discard per-port configurations when a dvPort is disconnected from a virtual machine.
o Binding on host allowed to specify that when vCenter Server is down, ESX can assign a dvPort to a virtual machine.
o Port name format to provide a template for assigning names to the dvPorts in this group.
o Private VLANs are used to solve VLAN ID limitations.
o A private VLAN is identified by its primary VLAN ID. A primary VLAN ID can have multiple secondary VLAN IDs associated with it. Primary
VLANs are Promiscuous, so that ports on a private VLAN can communicate with ports configured as the primary VLAN. Ports on a secondary
VLAN can be either:
o Isolated - communicating only with promiscuous ports
o Community - communicating with both promiscuous ports and other ports on the same secondary VLAN.
o Only one VMotion and IP storage port group for each ESX host.
o You can enable or disable IPv6 support on the host.
o The following networking policies can be applie VCP-410 braindump d:
o Security
o Promiscuous Mode - In non-promiscuous mode, a guest adapter listens only to traffic forwarded to own MAC address. In
promiscuous mode, it can listen to all the frames. By default, guest adapters are set to non-promiscuous mode.

By default, statistics are stored in the vCenter Server database for one year. You can increase this to three years.
o You cannot view datastore metrics in the advanced charts. They are only available in the overview charts.
o CPU Performance Enhancement Advice
1. Verify that VMware Tools is installed on every VM on the host.
2. Compare the CPU usage value of a VM with the CPU usage of other VMs on the host or in the resource p VCP-410 exam questions ool. The stacked bar chart on the
host's Virtual Machine view shows the CPU usage for all VMs on the host.
3. Determine whether the high ready time for the VM resulted from its CPU usage time reaching the CPU limit setting. If so, increase the
CPU limit on the VM.
4. Increase the CPU shares to give the VM more opportunities to run. The total ready time on the host might remain at the same level if the
host system is constrained by CPU. If the host ready time doesn't decrease, set the CPU reservations for high-priority VMs to guarantee
that they receive the required CPU cycles.
5. Increase the amount of memory allocated to the VM. This decreases disk and or network activity for applications that cache. This might
lower disk I/O and reduce the need for the ESX/ESXi host to virtualize the hardware. Virtual machines with smaller resource allocations
generally accumulate more CPU ready time.
6. Reduce the number of virtual CPUs on a VM to only the number required to execute the workload. For example, a single-threaded
application on a four-way VM only benefits from a single vCPU. But the hypervisor's maintenance of the three idle vCPUs takes CPU cycles
that could be used for other work.
7. If the host is not already in a DRS cluster, add it to one. If the host is in a DRS cluster, increase the number of hosts and migrate one or
more VMs onto the new host.
8. Upgrade the physical CPUs or cores on the host if necessary.
9. Use the newest version of ESX/ESXi, and enable CPU-saving features such as TCP Segmentation Offload, large memory pages, and jumbo
frames.
o Memory Performance Enhancement Advice
1. Verify that VMware Tools is installed on each VM. The balloon driver is installed with VMware Tools and is critical to performance.
2. Verify that the balloon driver is enabled. The VMkernel regularly reclaims unused VM memory by ballooning and swapping. Generally,
this does not impact VM performance.
3. Reduce the memory space on the VM, and correct the cache size if it is too large. This frees up memory for other VMs.
4. If the memory reservation of the VM is set to a value much higher than its active memory, decrease the reservation setting so that the
VMkernel can reclaim the idle memory for other VMs on the host.
5. Migrate one or more VMs to a host in a DRS cluster.
6. Add physical memory to the host.
o Disk I/O Performance Enhancement Advice
1. Increase the VM memory. This should allow for more operating system caching, which can reduce I/O activity. Note that this may require
you to also increase the host memory. Increasing memory might reduce the need to store data because databases can utilize system
memory to cache data and avoid disk access. To verify that VMs have adequate memory, check swap statistics in the guest operating
system. Increase the guest memory, but not to an extent that leads to excessive host memory swapping. Install VMware Tools so that
memory ballooning can occur.
2. Defragment the file systems on all guests.
3. Disable antivirus on-demand scans on VCP-410 study guide the VMDK and VMEM (backup of the VM’s paging file) files.
4. Use the vendor's array tools to determine the array performance statistics. When too many servers simultaneously access common
elements on an array, the disks might have trouble keeping up. Consider array-side improvements to increase throughput.
5. Use Storage VMotion to migrate I/O-intensive VMs across multiple ESX/ESXi hosts.
6. Balance the disk load across all physical resources available. Spread heavily used storage across LUNs that are accessed by different
adapters. Use separate queues for each adapter to improve disk efficiency.
7. Configure the HBAs and RAID controllers for optimal use. Verify that the queue depths and cache settings on the RAID controllers are
adequate. If not, increase the number of outstanding disk requests for the VM by adjusting the Disk.SchedNumReqOutstanding
parameter. For more information, see the Fibre Channel SAN Configuration Guide.
8. For resource-intensive VMs, separate the VM's physical disk drive from the drive with the system page file. This alleviates disk spindle
contention during periods of high use.
9. On systems with sizable RAM, disable memory trimming by adding the line MemTrimRate=0 to the VM's .VMX file.
10. If the combined disk I/O is higher than a single HBA capacity, use multipathing or multiple links.
11. For ESXi hosts, create virtual disks as preallocated. When you create a virtual disk for a guest operating system, select Allocate all disk
space now. The performance degradation associated with reassigning additional disk space does not occur, and the disk is less likely to
become fragmented.
12. Use the most current ESX/ESXi host hardware.
o Networking Performance Enhancement Advice
1. Verify that VMware Tools is installed on ea VCP-410 questions ch VM.
2. If possible, use vmxnet3 NIC drivers, which are available with VMware Tools. They are optimized for high performance.
3. If VMs running on the same ESX/ESXi host communicate with each other, connect them to the same vSwitch to avoid the cost of
transferring packets over the physical network.

If you create or edit a role on a vCenter Server system that is part of a connected group in Linked Mode, the changes you make are propagated
to all other vCenter Server systems in the group. Assignments of roles to specific users and objects are not shared across linked vCenter Server
systems.
o Permissions grant users the right to pVCP-410 erform the activities specified by the role on the object to which the role is assigned
o By default, all users who are members of the Windows Administrators group on the vCenter Server system have the same access rights as any
user assigned to the Administrator role on all objects.
o Propagation is set per permission, not universally applied. Permissions defined for a child object always override those propagated from
parent objects.
o You cannot set permissions directly on a vNetwork Distributed Switches. To set permissions for a vNetwork Distributed Switch and its
associated dvPort Groups, set permissions on a parent object, such a folder or datacenter, and select the option to propagate these
permissions to child objects.
o If no permission is defined for the user on that object, the user is assigned the union of privileges assigned to the groups for that object.
o If a permission is defined for the user on that object, the user's permission takes precedence over all group permissions
o Reports are updated every 30 minutes.
o Map views are updated every 30 minutes
o Alarms are notifications that occur in response to selected events, conditions, and states that occur with objects in the inventory.
o Alarms are composed of a trigger and an action.
o Alarms have two types of triggers: condition/state triggers, and event triggers.
o Condition or State Triggers Monitor the current condition or state of VMs, hosts, and datastores.
o Event Triggers Monitors events that occur in response to operations occuring with any managed object in the inventory, the vCenter Server
system, or the license server.
o Condition and state triggers use one of the following operator sets to monitor an object:
o Is equal to and Is not equal to
o Is above and Is below
o Event triggers use arguments, operators, and values to monitor operations that occur in the vServer System.
VCP-410 braindump o Alarm actions are operations that occur in response to triggered alarms.
o The default VMware alarms do not have actions associated with them. You must manually associate actions with the default alarms.
o You can disable an alarm action from occurring without disabling the alarm itself.
o You disable alarm actions for a selected inventory object.
o When you disable the alarm actions for an object, they continue to occur on child objects.
o When you disable alarm actions, all actions on all alarms for the object are disabled. You cannot disable a subset of alarm actions.
o The SNMP agent included with vCenter Server can be used to send traps when alarms are triggered on a vCenter Server.
o Alarm reporting can further restrict when a condition or state alarm trigger occurs by adding a tolerance range and a trigger frequency to the
trigger configuration.
o The tolerance range specifies a percentage above or below the configured threshold point, after which the alarm triggers or clears.
o Condition threshold + Tolerance Range = Trigger alarm
o The trigger frequency is the time period during which a triggered alarm action is not reported again. By default, the trigger frequency for the
default VMware alarms is set to 5 minutes.
o Statistical data consists of CPU, memory, disk, network, system, and VM operations metrics.
o Collection intervals determine the time period during which statistics are aggregated and rolled up, and the length of time the statistics are
archived in the vCenter database. By default, vCenter Server has four collection intervals: Day, Week, Month, and Year.
o Real-time statistics are not stored in the database. They are stored in a flat file on ESX/ESXi hosts and in memory on the vCenter Server
systems
o Real-time statistics are collected directly on an ESX/ESXi host every 20 seconds (60 seconds for ESX Server 2.x hosts).
o On ESX hosts, the statistics are kept for one hour, after which 180 data points (15 -20 second samples) will have been collected.
o On ESXi hosts, the statistics are kept for 30 minutes, after which 90 data points will have been collected.
o Collection Intervals:
Collected frequency Retention
5 Minutes 1 Day
30 Minutes 1 Week
2 Hours 1 Month
1 Day 1 Year
o You can change the frequency at which statistic queries occur, the length of time statistical data is stored in the vCenter Server database, and
the amount of statistical data collected.
VCP-410 exam o Not all attributes are configurable for each collection interval.
o You can assign a collection level of 1- 4 to each collection interval, with level 4 having the largest number of counters.
o By default, all collection intervals use collection level 1.
o Generally, you need to use only collection levels 1 and 2 for performance monitoring and analysis