What are three possible causes of service profile association failure due to iSCSI configuration issue? (Choose three )

Question

Options

• AWrong WWNN
• BiSCSI Target out of configured range of services
• CInappropriate network configuration
• DImproperly assigned iSCSI Class of Service
• EMisconfigured iSCSI parameters
• FMisconfigured LUN. LUN masking

• A
  17% (6)
• B
  75% (27)
• D
  6% (2)
• F
  3% (1)

Explanation

When a UCS service profile fails to associate due to iSCSI misconfiguration, the root causes typically fall into connectivity, reachability, and parameter correctness. B is correct because if the iSCSI target address or port falls outside the configured service range, the initiator simply cannot reach the target, blocking association. C is correct because iSCSI depends entirely on proper TCP/IP networking - wrong VLANs, missing IP gateways, or MTU mismatches will break connectivity before association can complete. E is correct because iSCSI-specific parameters (initiator IQN, target IQN, CHAP credentials, boot target settings) must exactly match what the storage array expects; any mismatch causes the login sequence to fail.

Why the distractors are wrong: A (Wrong WWNN) is a Fibre Channel concept - iSCSI uses IQNs, not WWNNs, so this is a deliberate FC/iSCSI terminology trap. D (iSCSI Class of Service) is an FCoE/FC QoS concept; standard iSCSI over TCP/IP does not use CoS as an association prerequisite. F (LUN masking) occurs after the iSCSI session is already established - it affects what storage is visible, not whether the profile can associate in the first place.

Memory tip: Think "RNP" - Reachability (target in range), Network (proper IP config), Parameters (iSCSI settings). If any of these three are broken, association fails. Eliminate anything that smells like Fibre Channel (WWNN, CoS) or post-connection storage access (LUN masking).

No community discussion yet for this question.