VMware 2V0-621 - Questions & Answers

Revert the access permissions of the service.xml file to the read-only default by running the command:

# chmod 444 /etc/vmware/firewall/service.xml
Refresh the firewall rules for the changes to take effect by running the command:

# esxcli network firewall refresh

or

# localcli network firewall refresh

References:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008226

Clone a Virtual Machine in the vSphere Client

Cloning a virtual machine creates a duplicate of the virtual machine with the same configuration and installed software as the original. Optionally, you can customize the guest operating system of the clone to change the virtual machine name, network settings, and other properties. This prevents conflicts that can occur if a virtual machine and a clone with identical guest operating system settings are deployed simultaneously.

Prerequisites

You must be connected to vCenter Server in order to clone a virtual machine. You cannot clone virtual machines if you connect directly to an ESXi host.

References:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%
2FGUID-5C504B67-CDB3-42FC-8B3B-737201A725DD.html

ESXi 4.x, 5.x and 6.0

To power on a virtual machine from the command line:
1. List the inventory ID of the virtual machine with the command:

vim-cmd vmsvc/getallvms |grep <vm name>

Note: The first column of the output shows the vmid.
2. Check the power state of the virtual machine with the command:

vim-cmd vmsvc/power.getstate <vmid>

3. Power-on the virtual machine with the command:

vim-cmd vmsvc/power.on <vmid>

References:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1038043

The .nvram file. This small file contains the BIOS that is used when the VM boots. It is similar to a physical server that has a BIOS chip that lets you set hardware configuration options. A VM also has a virtual BIOS that is contained in the NVRAM file. The BIOS can be accessed when a VM first starts up by pressing the F2 key. Whatever changes are made to the hardware configuration of the VM are then saved in the NVRAM file. This file is in binary format and if deleted it will be automatically re-created when a VM is powered on.

References:
http://searchvmware.techtarget.com/tip/Understanding-the-files-that-make-up-a-VMware-virtual-machine

Whenever a user tries to connect to a higher version of the ESXI host, the user will be prompted to upgrade to the higher version to escape the compatibility issues.

Port: 902 (Default)
Purpose:
Host access to other hosts for migration and provisioning Authentication traffic for ESXi and remote console traffic (xinetd/vmware-authd) vSphere Client access to virtual machine consoles (UDP) Status update (heartbeat) connection from ESXi to vCenter Server Traffic Type Incoming and outgoing TCP, outgoing UDP

References:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc_50%
2FGUID-ECEA77F5-D38E-4339-9B06-FF9B78E94B68.html

When an ESXi 5.1 / 5.5 host is managed by vCenter Server 5.1 and 5.5, two components are installed, each with its own logs:
1. /var/log/vpxa.log: vCenter Server vpxa agent logs, including communication with vCenter Server and the Host Management hostd agent.
2. /var/log/fdm.log: vSphere High Availability logs, produced by the fdm service. For more information, see the vSphere HA Security section of the vSphere Availability Guide.

References:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032076

Cause
This issue is occurs if the allocated JVM maximum memory heap is too low for the VMware Inventory service, VMware Profile-Driven Storage service, or VMware VirtualCenter Web Management service.
Several core vCenter Server services use individual configuration files (wrapper.conf) to determine the JVM maximum heap size that each service can use. The VMware Inventory service, VMware Profile-
Driven Storage service, and VMware VirtualCenter Web Management service rely on the JVM maximum memory heap configured in their individual wrapper.conf file and play a critical role in the functionality of vCenter Server. Note: If vCenter Server 5.5 has recently been updated beyond 5.5 U2, see Upgrading VMware vCenter Server 5.5 to 5.5 U2 or later reduces the JVM maximum memory heap size (2114669).
Resolution
This is a known issue affecting vCenter Server 5.x.
To resolve this issue, manually set the inventory size.
To change the JVM maximum memory heap size for a Windows installed vCenter Server 5.x, see, see Configuring Tomcat server settings in VMware vCenter Server 5.1 and 5.5 (2021302).
To manually set the inventory size in vCenter Server Appliance 5.x:
1. Log in to vCenter Server Appliance administration interface (VAMI) URL:

https://vCenter_Server_FQDN\IP:5480
2. Click the Services tab.
3. Change the Inventory Size to Medium or Large, depending on your environment.

Note: The system memory may need to be increased when changing this setting. For more information on environment sizing, see theConfigure Inventory Size for the VMware vCenter Server Appliance section of the Configuring Hosts and vCenter Server guide.
4. Restart the VMware Profile-Driven Storage Service and VMware Inventory Service. For more information, see Stopping, starting, or restarting vCenter Server Appliance services (2054085).

References:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2126282