The principal switch on a Fibre Channel network fails to assign requested domain to a subordinate switch. What are two reasons? (Choose two.)

Question

Options

• ACisco Fabric Services distribution is not enabled on the switch.
• BThe fabric is locked.
• CThe requested domain is outside the allowed list.
• DThe persistent FC ID feature is not enabled.
• EAn existing switch already has the requested domain assigned.

• A
  2% (1)
• B
  4% (2)
• C
  82% (37)
• D
  11% (5)

Explanation

In Fibre Channel, the principal switch assigns domain IDs to subordinate switches during fabric initialization. A request fails if the domain ID isn't in the principal switch's allowed domain ID list (C) - each fabric can be configured to permit only specific domain IDs, so any request outside that range is rejected. It also fails if another switch in the fabric already holds that domain ID (E) - domain IDs must be unique across the fabric, so a duplicate assignment is simply denied.

Why the distractors are wrong:

• A (CFS not enabled): Cisco Fabric Services handles configuration distribution (like zoning), not domain ID assignment - these are separate mechanisms.
• B (fabric locked): A fabric lock prevents CFS configuration changes from being distributed, not domain ID assignment during fabric bring-up.
• D (persistent FC ID not enabled): Persistent FC IDs relate to end-device N_Port ID assignment stability across reconnections, not switch domain ID assignment.

Memory tip: Think of domain ID assignment like reserving a seat number - the seat must be on the approved seating chart (allowed list = C) and not already taken by someone else (duplicate = E). Locks and services are about configuring the fabric, not joining it.

No community discussion yet for this question.