An administrator has recently upgraded from vSphere 6.0 to 6.5, and can no longer see the software iSCSI
named vmhba33.
Which could be the reason for this?
A.
The upgrade has changed the vmhba name.
B.
vSphere 6.5 automates iSCSI configurations.
C.
vSphere 6.5 no longer supports software iSCSI.
D.
The upgrade has deleted the vmhba.
Explanation:
In vSphere 6.5, the name assigned to the iSCSI software adapter is different from the earlier releases. After you
upgrade to the vSphere 6.5 release, the name of the existing software iSCSI adapter, vmhbaXX, changes.
https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-esxi-vcenter-server-65-releasenotes.html#storageissues
I say A.
Source: https://docs.vmware.com/en/VMware-vSphere/6.5/rn/vsphere-esxi-vcenter-server-65-release-notes.html#storageissues
iSCSI Issues
In vSphere 6.5, the name assigned to the iSCSI software adapter is different from the earlier releases
After you upgrade to the vSphere 6.5 release, the name of the existing software iSCSI adapter, vmhbaXX, changes. This change affects any scripts that use hard-coded values for the name of the adapter. Because VMware does not guarantee that the adapter name remains the same across releases, you should not hard code the name in the scripts. The name change does not affect the behavior of the iSCSI software adapter.
Workaround: None.