nerdexam
CompTIA

CV0-003 · Question #48

Host A and B can both access LUNs one to ten in a single SAN LUN 11 has been created and Host A can access it but Host B cannot. Which of the following will likely be the cause of this issue?

The correct answer is B. Incorrect HBA WWPN. SAN LUN masking uses the HBA World Wide Port Name (WWPN) as the host identifier, so an incorrect WWPN for Host B in the zoning or masking configuration of LUN 11 would selectively block only that host from the new LUN.

Troubleshooting

Question

Host A and B can both access LUNs one to ten in a single SAN LUN 11 has been created and Host A can access it but Host B cannot. Which of the following will likely be the cause of this issue?

Options

  • AFaulty fiber HBA
  • BIncorrect HBA WWPN
  • CIncorrect HBA software version
  • DDefective HBA

How the community answered

(35 responses)
  • A
    14% (5)
  • B
    74% (26)
  • C
    3% (1)
  • D
    9% (3)

Why each option

SAN LUN masking uses the HBA World Wide Port Name (WWPN) as the host identifier, so an incorrect WWPN for Host B in the zoning or masking configuration of LUN 11 would selectively block only that host from the new LUN.

AFaulty fiber HBA

A faulty fiber HBA would disrupt all SAN connectivity for Host B across every LUN, not selectively block a single newly provisioned LUN.

BIncorrect HBA WWPNCorrect

In a SAN fabric, LUN masking and zoning use each host's HBA WWPN to control which hosts are permitted to see which LUNs. If Host B's WWPN is missing or incorrectly entered in the access control configuration for LUN 11, the SAN will deny Host B access to that LUN while still allowing Host A. Because Host B retains full access to LUNs 1-10, the HBA hardware itself is confirmed working, and the problem is isolated to a misconfigured WWPN entry for the newly created LUN.

CIncorrect HBA software version

An incorrect HBA software or driver version would cause broad compatibility or connectivity issues affecting all LUNs, not a targeted failure limited to LUN 11.

DDefective HBA

A defective HBA would result in complete SAN access failure for Host B on all LUNs, not a selective inaccessibility to one newly created LUN.

Concept tested: SAN LUN masking and HBA WWPN zoning configuration

Source: https://docs.netapp.com/us-en/ontap/san-admin/lun-masking-concept.html

Topics

#SAN zoning#LUN masking#HBA WWPN#Fibre Channel

Community Discussion

No community discussion yet for this question.

Full CV0-003 Practice