SG0-001 · Question #344
Node A is a member of SAN Zone 1 and SAN Zone 2. Node B is a member of SAN Zone 2. Node B has just been replaced and the storage administrator is troubleshooting connectivity issues between Node A and
The correct answer is D. Zone configuration may need to be updated with the new port WWN.. After replacing Node B, connectivity issues with Node A suggest that the SAN zone configuration, which relies on unique hardware identifiers, needs updating.
Question
Node A is a member of SAN Zone 1 and SAN Zone 2. Node B is a member of SAN Zone 2. Node B has just been replaced and the storage administrator is troubleshooting connectivity issues between Node A and Node B. Which of the following is the MOST likely cause of the issue?
Options
- ANodes cannot be a member of multiple zones.
- BNode B is an unauthorized host cabled to the wrong SAN switch.
- CZone configuration is causing undesired Registered State Change Notification events.
- DZone configuration may need to be updated with the new port WWN.
How the community answered
(30 responses)- A17% (5)
- B3% (1)
- C7% (2)
- D73% (22)
Why each option
After replacing Node B, connectivity issues with Node A suggest that the SAN zone configuration, which relies on unique hardware identifiers, needs updating.
Nodes can indeed be members of multiple SAN zones, which is a common and flexible configuration in Fibre Channel environments.
While possible, a physical misconnection or unauthorized host is less likely to be the primary cause of connectivity issues immediately after a hardware replacement than an outdated zone configuration referencing the old hardware's WWN.
Registered State Change Notifications (RSCNs) inform devices of changes in the fabric, but an issue with zone configuration not including a new WWN is a more direct and likely cause of initial connectivity failure than undesired RSCN events themselves.
Fibre Channel zones are typically configured using the unique World Wide Names (WWNs) of the Host Bus Adapter (HBA) ports. When Node B is replaced, its new HBA will have a different WWN than the old one. The existing SAN zone configuration, which still references the old WWN, will therefore not include the new Node B, preventing it from communicating with Node A.
Concept tested: Fibre Channel zoning and WWN updates
Source: https://www.cisco.com/c/en/us/support/docs/storage-networking/mds-9000-series-multilayer-san-switches/44585-soft-hard-zone.html
Topics
Community Discussion
No community discussion yet for this question.