nerdexam
Cisco

300-625 · Question #15

Refer to the exhibit. A storage network engineer gets remote access to two Cisco MDS 9000 Series Switches with an ISL trunk and receives several log messages. Which set of actions resolve the…

The correct answer is A. 1. Add :11:11:11:11:11:11:11:13 pwwn in zone Server11 and activate Zoneset10-A on MDS-A. Option A is correct because it takes the minimum necessary action: adding the missing PWWN (:11:11:11:11:11:11:11:13) to the existing zone Server11 and re-activating the zoneset on MDS-A. When a zoneset is activated on one switch in the fabric, Cisco MDS automatically…

MDS Troubleshooting

Question

Refer to the exhibit. A storage network engineer gets remote access to two Cisco MDS 9000 Series Switches with an ISL trunk and receives several log messages. Which set of actions resolve the problem while least affecting service?

Exhibit

300-625 question #15 exhibit

Options

  • A
    1. Add :11:11:11:11:11:11:11:13 pwwn in zone Server11 and activate Zoneset10-A on MDS-A.
  • B
    1. Deactivate zone set Zoneset10-A on MDS-A.
  • C
    1. Add :11:11:11:11:11:11:11:13 pwwn in zone Server11 and activate Zoneset10-A on MDS-A.
  • D
    1. Explicitly import zone set Zoneset10-A on MDS-B using the zoneset import interface import

How the community answered

(26 responses)
  • A
    46% (12)
  • B
    15% (4)
  • C
    12% (3)
  • D
    27% (7)

Explanation

Option A is correct because it takes the minimum necessary action: adding the missing PWWN (:11:11:11:11:11:11:11:13) to the existing zone Server11 and re-activating the zoneset on MDS-A. When a zoneset is activated on one switch in the fabric, Cisco MDS automatically propagates the updated zone database to peer switches (like MDS-B) over the ISL - no manual intervention on the second switch is needed, and existing zoned traffic remains uninterrupted.

Option B is wrong because simply deactivating the zoneset on MDS-A tears down all active storage paths in that zoneset - this is the most disruptive action possible and doesn't fix anything by itself. Option C is wrong because it likely includes an unnecessary additional step (such as deactivating the zoneset first or reconfiguring MDS-B) that introduces extra disruption beyond what A requires. Option D is wrong because zoneset import pulls a peer switch's active zoneset into the local database - it doesn't resolve a missing PWWN, and the correct workflow is to make changes on MDS-A and activate outward, not import from MDS-B.

Memory tip: In Cisco MDS zoning, think "Add then Activate" - always make the smallest zone database change needed and activate on the managing switch; the fabric handles propagation automatically. If you see "deactivate" or "import from peer" as the first step, that's usually the wrong answer.

Topics

#Fibre Channel Zoning#MDS Switch Configuration#Port World Wide Names#ISL Connectivity

Community Discussion

No community discussion yet for this question.

Full 300-625 Practice