2V0-622 · Question #213
Refer to the Exhibit. The Exhibit shows the status of vmhba32 and vmhba33 as Unbound. What is a likely reason for this status?
The correct answer is A. The host bus adapter is not associated with a vmknic. Software iSCSI HBAs show an 'Unbound' status when they have not been associated with a VMkernel (vmknic) network adapter, which is required for iSCSI traffic to flow.
Question
Refer to the Exhibit. The Exhibit shows the status of vmhba32 and vmhba33 as Unbound. What is a likely reason for this status?
Exhibit
Options
- AThe host bus adapter is not associated with a vmknic.
- BThe Dynamic Target Discovery was not configured.
- CThe Static Target Discovery was not configured.
- DThe host bus adapter is not associated with a vmnic.
How the community answered
(37 responses)- A81% (30)
- B11% (4)
- C3% (1)
- D5% (2)
Why each option
Software iSCSI HBAs show an 'Unbound' status when they have not been associated with a VMkernel (vmknic) network adapter, which is required for iSCSI traffic to flow.
Software iSCSI initiators (vmhba32, vmhba33) depend on VMkernel ports to send and receive iSCSI traffic; without a bound vmknic, the HBA has no network interface through which to communicate with iSCSI targets, and vSphere reports the state as Unbound. Port binding must be configured explicitly in the iSCSI adapter's Network Port Binding section.
Dynamic Target Discovery (Send Targets) is a method for the initiator to query an iSCSI target for available LUNs; its absence would result in no discovered targets, not an Unbound HBA status.
Static Target Discovery requires manually specifying target IP addresses; failure to configure it also results in missing targets, not the Unbound status shown for the HBA itself.
vmnic refers to a physical Ethernet NIC used for standard or distributed vSwitch uplinks; iSCSI software HBAs bind to VMkernel adapters (vmknic), not directly to physical vmnics.
Concept tested: Software iSCSI HBA port binding to VMkernel adapter
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-B3E7B855-4E9A-4F07-BB44-F57D0014F450.html
Topics
Community Discussion
No community discussion yet for this question.
