What might cause the upgrade to be unsuccessful?

An administrator is upgrading an ESXi 3.5 host to ESXi 5.x with an intermediate upgrade to 4.0
using Update Manager. The host has a single Intel Xeon processor, 4GB of RAM, and a VMFS
datastore on a private, SAN-attached LUN. What might cause the upgrade to be unsuccessful?

An administrator is upgrading an ESXi 3.5 host to ESXi 5.x with an intermediate upgrade to 4.0
using Update Manager. The host has a single Intel Xeon processor, 4GB of RAM, and a VMFS
datastore on a private, SAN-attached LUN. What might cause the upgrade to be unsuccessful?

A.
The ESXi host has 4GB RAM.

B.
The ESXi host has one processor.

C.
ESXi 3.5 is not supported for upgrade.

D.
Update Manager cannot upgrade a previously upgraded host.

Explanation:
http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-AA106086-E10D-456EB0B9-340D3D1462C3.html

Show Hint

Leave a Reply 1

Your email address will not be published. Required fields are marked *

Gary

Gary

The answer should be D based on the link below:

http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc_50%2FGUID-AA106086-E10D-456E-
B0B9-340D3D1462C3.html

You cannot use Update Manager to upgrade a host to ESXi 5.0 if the host was previously upgraded from ESX 3.x to ESX 4.x. Such hosts do not have sufficient free space in the /boot partition to support the Update Manager upgrade process. This problem also affects some 4.x ESX hosts, even if they were not previously upgraded from ESX 3.x. Hosts must have more than 350MB of free space in the /boot partition to support the Update Manager upgrade process. If the host that you are upgrading does not have more than 350MB of free space in the /boot partition, use a scripted or interactive upgrade instead.

Reply