VCP DCV 6
-Insufficient spare capacity on available hosts
– vSphere HA attempted to restart the virtual machine but encountered a fatal error each time it tried.
– Your cluster’s shared storage is Virtual SAN and one of the virtual machine’s files has become inaccessible due to the occurrence of more than the specified number of host failures.
– Restart actually succeeded.
2. The default PSP for all devices claimed by VMW_SATP_ALUA is VMW_PSP_MRU.
2. Independent Hardware iSCSI adapters require vmkernel networking.
– Re-add and enable vMotion for each affected USB device
2. The virtual machine object is inaccessible or orphaned
– Moving the virtual machine will violate an affinity rule.
– Virtual machine has a local device mounted.
• VM Name = APP005
• ID = 00512 Which command
would successfully power off the virtual machine?
2. Always store with the VM
ESXi hosts have self-signed SSL certificates by default.
2. The disk is a CD-ROM/ISO file
■ Cluster Services (VMware Distributed Resource Scheduler) – all metrics
■ CPU – cpuentitlement, totalmhz, usage (average), usagemhz
■ Disk – capacity, maxTotalLatency, provisioned, unshared, usage (average), used
■ Memory – consumed, mementitlement, overhead, swapinRate, swapoutRate, swapused, totalmb, usage (average), vmmemctl (balloon)
■ Network – usage (average), IPv6
■ System – heartbeat, uptime
■ Virtual Machine Operations – numChangeDS, numChangeHost, numChangeHostDS
– Use for long-term performance monitoring when device statistics are not required.
– Level 1 is the default Collection Level for all Collection Intervals.
■ Level 1 metrics
■ CPU – idle, reservedCapacity
■ Disk – All metrics, excluding numberRead and numberWrite.
■ Memory – All metrics, excluding memUsed and maximum and minimum rollup values.
■ Virtual Machine Operations – All metrics
– Use for long-term performance monitoring when device statistics are not required but you want to monitor more than the basic statistics.
■ Level 1 and Level 2 metrics
■ Metrics for all counters, excluding minimum and maximum rollup values.
■ Device metrics
– Use for short-term performance monitoring after encountering problems or when device statistics are required.
– Because of the large quantity of troubleshooting data retrieved and recorded, use level 3 for the shortest time period (Day or Week collection interval).
– All metrics supported by the vCenter Server, including minimum and maximum rollup values.
■When the system searches the SATP rules to locate a SATP for a given device, it searches the driver rules first. If there is no match, the vendor/model rules are searched, and finally the transport rules are searched. If no match occurs, NMP selects a default SATP for the device.
■If VMW_SATP_ALUA is assigned to a specific storage device, but the device is not ALUA-aware, no claim rule match occurs for this device. The device is claimed by the default SATP based on the device’s transport type.
■The default PSP for all devices claimed by VMW_SATP_ALUA is VMW_PSP_MRU. The VMW_PSP_MRU selects an active/optimized path as reported by the VMW_SATP_ALUA, or an active/unoptimized path if there is no active/optimized path. This path is used until a better path is available (MRU). For example, if the VMW_PSP_MRU is currently using an active/unoptimized path and an active/optimized path becomes available, the VMW_PSP_MRU will switch the current path to the active/optimized one.
■While VMW_PSP_MRU is typically selected for ALUA arrays by default, certain ALUA storage arrays need to use VMW_PSP_FIXED. To check whether your storage array requires VMW_PSP_FIXED, see the VMware Compatibility Guide or contact your storage vendor. When using VMW_PSP_FIXED with ALUA arrays, unless you explicitly specify a preferred path, the ESXi host selects the most optimal working path and designates it as the default preferred path. If the host selected path becomes unavailable, the host selects an alternative available path. However, if you explicitly designate the preferred path, it will remain preferred no matter what its status is.
■By default, the PSA claim rule 101 masks Dell array pseudo devices. Do not delete this rule, unless you want to unmask these devices.
SATPs allow load balancing across multiple paths, intelligent path selection, and over troubled conditions such as “chatter”, when passed rapidly fail back and forth between controllers.
2. Monitor the health of the physical I/O channels or paths
3. Report any changes in the state of the paths up the stack
4. Perform actions required to fail over storage between controllers on the array
VMW_SATP_DEFAULT_AA — Generic for active/active arrays
VMW_SATP_DEFAULT_AP — Generic for active/passive arrays
VMW_SATP_ALUA — Asymmetric Logical Unit Access-compliant arrays
VMW_SATP_SVC — IBM SVC-based systems (SVC, V7000, Actifio)
VMW_SATP_CX — EMC/Dell CLARiiON and Celerra (also VMW_SATP_ALUA_CX)
VMW_SATP_SYMM — EMC Symmetrix DMX-3/DMX-4/VMAX, Invista
VMW_SATP_INV — EMC Invista and VPLEX
VMW_SATP_EQL — Dell EqualLogic systems
2. VM-Host Affinity – Individual virtual machines
– Affinity Rule: Specifies that the members of a selected virtual machine DRS group can or must run on the members of a specific host DRS group.
– Anti-affinity rule: Specifies that the members of a selected virtual machine DRS group cannot run on the members of a specific host DRS group.
2. Upgrade the host to the latest BIOS.
identifies which virtual machines need to be restarted.
– Monitoring the power state of all protected virtual machines. If one virtual machine fails, the master
host ensures that it is restarted. Using a local placement engine, the master host also determines where
the restart should be done.
– Managing the lists of cluster hosts and protected virtual machines.
– Acting as vCenter Server management interface to the cluster and reporting the cluster health state
Get access to
Guarantee No Hidden