SG0-001 · Question #475
When zoning an FC or FCoE device, which of the following identifiers would BEST be used to define the zone members?
The correct answer is D. World Wide Port Names. World Wide Port Names (WWPNs) are the best identifiers for defining zone members in FC or FCoE fabrics because they uniquely identify individual ports, ensuring precise control over which specific device ports can communicate.
Question
When zoning an FC or FCoE device, which of the following identifiers would BEST be used to define the zone members?
Options
- AWorld Wide Node Names
- BSCSI GUID
- CInitiator-Target UUID
- DWorld Wide Port Names
How the community answered
(65 responses)- A6% (4)
- B2% (1)
- C3% (2)
- D89% (58)
Why each option
World Wide Port Names (WWPNs) are the best identifiers for defining zone members in FC or FCoE fabrics because they uniquely identify individual ports, ensuring precise control over which specific device ports can communicate.
World Wide Node Names (WWNNs) identify the entire device (node) rather than specific ports, which is less granular and can lead to unintended access if a node has multiple ports that should be isolated.
SCSI GUIDs are logical identifiers for SCSI devices or LUNs, not for fabric ports, and are not used for zoning purposes in FC/FCoE fabrics.
Initiator-Target UUIDs are not standard identifiers used for zoning FC or FCoE fabric members; zoning typically relies on WWNs.
World Wide Port Names (WWPNs) are the best identifiers for zoning because they uniquely identify each individual Fibre Channel or FCoE port on an HBA or storage array, allowing for granular control over connectivity at the port level. Using WWPNs ensures that zoning policies are applied to specific physical connections, making configurations stable even if devices move within the fabric, provided their WWPNs remain consistent.
Concept tested: Fibre Channel zoning identifiers
Source: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/4_1/configuration/guides/zoning/zoning_4_1/zoning_overview.html
Topics
Community Discussion
No community discussion yet for this question.