VMware 3V0-22.21 Actual Free Exam Questions & Community Discussion
A vSphere administrator has deployed a new server. The VM will have a workload which is prodApp1 to the following specifications:
* The VM should never have any memory contention while powered on. even if the host that it resides
* Configure the virtual machine for high latency sensitivity.
* The VM should never have any memory contention while powered on. even if the host that it resides
* Configure the virtual machine for high latency sensitivity.
Correct Answer: A
Vote an answer
You have been asked to create a new datastore for the Production cluster; however, the ESXi host esxi02a is not able to add the datastore. Your storage team has determined that there is nothing incorrect with the storage presentation.
Troubleshoot why host esxi02a is not able to create the datastore. Add the datastore to the host once the proper configuration has been applied, and then reboot the host!
Use the following information to complete this task;
* ESXi host: esxi02a
* Datastore Name: new_datastore
* Datastore target: iSCSI Target
* Datastore LUN: 4
* Reboot the host
Troubleshoot why host esxi02a is not able to create the datastore. Add the datastore to the host once the proper configuration has been applied, and then reboot the host!
Use the following information to complete this task;
* ESXi host: esxi02a
* Datastore Name: new_datastore
* Datastore target: iSCSI Target
* Datastore LUN: 4
* Reboot the host
Correct Answer:
Cannot create a new datastore from vCenter Server or directly from the vSphere Client Creating a new datastore fails The Add Storage Wizard reports the error: An error occurred during host configuration. Call "HostDatastoreSystem.QueryVmfsDatastoreCreateOptions" for object "ha-datastoresystem" on ESXi "xxx.xxx.xxx.xx" failed. An internal error occurred in the vsphere client.
Cause
This issue may occur if:
The size of the LUN is more than 2TB - 512 bytes. The maximum LUN size in vSphere 4 is 2TB - 512 bytes. For more information on this limitation, see Troubleshooting a LUN that is extended in size past the 2TB/2047GB limit (1004230).
The LUN being presented was used as an RDM earlier and does not have a valid partition table.
The LUN being presented was used as a disk device on an other operating system and does not have a valid partition table.
The LUN contains a GPT partition that cannot be removed.
Resolution
To prevent this issue:
Ensure that the LUN size is less than 2TB - 512 bytes or 2047GB. If the LUN is larger then 2TB - 512 bytes, delete it from your Storage Array and recreate it with a size less than the 2TB - 512 bytes limit.
If the disk was used by another operating system in the past (I.E.: it was an RDM, or Linux, FreeBSD, or other filesystem) or contains a GPT partition, you must delete the partition information.For more information
Cause
This issue may occur if:
The size of the LUN is more than 2TB - 512 bytes. The maximum LUN size in vSphere 4 is 2TB - 512 bytes. For more information on this limitation, see Troubleshooting a LUN that is extended in size past the 2TB/2047GB limit (1004230).
The LUN being presented was used as an RDM earlier and does not have a valid partition table.
The LUN being presented was used as a disk device on an other operating system and does not have a valid partition table.
The LUN contains a GPT partition that cannot be removed.
Resolution
To prevent this issue:
Ensure that the LUN size is less than 2TB - 512 bytes or 2047GB. If the LUN is larger then 2TB - 512 bytes, delete it from your Storage Array and recreate it with a size less than the 2TB - 512 bytes limit.
If the disk was used by another operating system in the past (I.E.: it was an RDM, or Linux, FreeBSD, or other filesystem) or contains a GPT partition, you must delete the partition information.For more information
0
0
0
10