01/08/2010

VCP-410 Real Exam Questions

o Performance charts o WebAccess o vCenter Storage Monitoring/Storage Views tab o vCenter Service Status o When a server is connected to other vCenter Server systems using Linked Mode, you can connect to that vCenter Server system and view and vcp 4 manage the inventories of all the vCenter Server systems that are linked. o Linked Mode uses Microsoft Active Directory Application Mode (ADAM) to store and synchronize data. o The following requirements apply to each vCenter Server system that is a member of a Linked Mode group: o DNS must be operational. o Can be in different domains if the domains have a two-way trust relationship. o When adding a vCenter instance to a Linked Mode group, the installer must be run by a domain user who is an administrator on both the machines. o Must have network time synchronization. The installer validates that the machine clocks are not more than 5 minutes apart. o The roles defined on each vCenter Server system in a linked mode group are replicated to the other systems in the group. o Troubleshooting: o Conflicts can occur, when you clone a vCenter Server instance that is running in a VM and you do not use sysprep or a similar utility to ensure that the cloned vCenter Server instance has a globally unique identifier (GUID). o The DNS name of the machine must match with the actual machine name. o Joining a Linked Mode group: 1. Verify that the vCenter Server domain name matches the machine name. 2. Update the URLs to make them compatible with the new domain name and machine name (if required). 3. Join the vCenter Server system to a Linked Mode group. o When you are logged in to a vCenter Server system that is part of a connected group, you can monitor the health of services running on each server in the group. o Client uses ports 80 and 443 to communicate with vCenter Server and ESX/ESXi hosts. These ports cannot be changed. o The SNMP traps sent by vCenter Server are defined in VMWARE-VC-EVENT-MIB.mib o ESX/ESXi includes an SNMP agent embedded in hostd that can both send traps and receive polling requests such as GET requests. This agent is vmware vcp 4 referred to as the embedded SNMP agent. Versions of ESX prior to ESX 4.0 included a Net-SNMP-based agent. You can continue to use this Net-SNMPbased agent in ESX 4.0 with MIBs supplied by your hardware vendor and other third-party management applications. However, to use the VMware MIB files, you must use the embedded SNMP agent. By default, the embedded SNMP agent is disabled. To enable it, use the vSphere CLI command vicfg-snmp. o Both the embedded SNMP agent and the Net-SNMP-based agent available in the ESX service console listen on UDP port 161 by default. If you enable both of these agents for polling on an ESX host, you must change the port used by at least one of them. o Can use SNMP to monitor guest operating systems or applications running in VMs. Do not install agents in the VM that are intended to monitor physical hardware. o VMware MIB Files MIB File Description VMWARE-ROOT-MIB.mib Contains VMware’s enterprise OID and top level OID assignments. VMWARE-AGENTCAP-MIB.mib Defines the capabilities of the VMware agents by product versions. VMWARE-ENV-MIB.mib Defines variables and trap types used to report on the state of physical hardware components of the host computer. VMWARE-OBSOLETE-MIB.mib Defines OIDs that have been made obsolete to maintain backward compatibility with earlier versions of ESX/ESXi. Includes variables formerly defined in the files VMWARE-TRAPS-MIB.mib and VMWARE-VMKERNEL-MIB.mib. VMWARE-PRODUCTS-MIB.mib Defines OIDs to uniquely identify each SNMP agent on each VMware platform by name, version, and build platform. VMWARE-RESOURCES-MIB.mib Defines variables used to report information on resource usage of the VMkernel, including physical memory, CPU, and disk utilization. 640 802 VMWARE-SYSTEM-MIB.mib The VMWARE-SYSTEM-MIB.mib file is obsolete. Use the SNMPv2-MIB to obtain information from sysDescr.0 and sysObjec ID.0. VMWARE-TC-MIB.mib Defines common textual conventions used by VMware MIB files. VMWARE-VC-EVENTS-MIB.mib Defines traps sent by vCenter Server. Load this file if you use vCenter Server to send traps. VMWARE-VMINFO-MIB.mib Defines variables for reporting information about VMs, including VM traps.
Jan 8, 2010 1:17:21 PM

The comments to this entry are closed.

NEXT POST
VCP-410 Test Questions o 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 vcp-410 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, the VMs will not work...
PREVIOUS POST
VMware VCP-410 Exam Main Documentation Set Introduction to VMware vSphere o vCompute – aggregate resources o vStorage – enables the most efficient use and management of storage o vNetwork – simplify and enhance networking o Fault Tolerance – a secondary copy. Actions completed on the primary VM are also applied to the secondary VM. If the primary VM becomes 640 802 Dumps unavailable, the secondary machine becomes active, providing continual availability. o Distributed Virtual Switch (DVS) – spans many hosts reduction of maintenance and increasing network capacity. o Host Profiles – host configuration management through user-defined configuration policies. Captures the blueprint and monitors...