2V0-622D · Question #79
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?
The correct answer is A. The upgrade has changed the vmhba name.. After a vSphere 6.0-to-6.5 upgrade, software iSCSI adapter names can change because vSphere 6.5 uses a revised naming scheme for storage adapters.
Question
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?
Options
- AThe upgrade has changed the vmhba name.
- BvSphere 6.5 automates iSCSI configurations.
- CvSphere 6.5 no longer supports software iSCSI.
- DThe upgrade has deleted the vmhba.
How the community answered
(34 responses)- A76% (26)
- B9% (3)
- C12% (4)
- D3% (1)
Why each option
After a vSphere 6.0-to-6.5 upgrade, software iSCSI adapter names can change because vSphere 6.5 uses a revised naming scheme for storage adapters.
vSphere 6.5 changed the way software iSCSI adapter identifiers are assigned, so an adapter previously named vmhba33 may receive a new vmhba number post-upgrade. The adapter still exists and functions normally - only its name has changed as a result of the new naming convention.
vSphere 6.5 does not fully automate iSCSI configuration; administrators must still manually configure software iSCSI adapters and perform port binding.
vSphere 6.5 fully supports software iSCSI; no support was removed in this version.
The upgrade process does not delete existing storage adapters; the adapter is present but was renamed by the new naming scheme.
Concept tested: vSphere 6.5 storage adapter naming changes after upgrade
Source: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.storage.doc/GUID-overview.html
Topics
Community Discussion
No community discussion yet for this question.