MENU
Refer to the exhibit.
Refer to the exhibit. A SAN engineer must enforce the port security configuration database in Fibre Channel fabric that uses Cisco MDS 9000 Switches. Port security is enabled on the VSAN to which the port belongs. However, the rogue host can still log in to the fabric. Which Cisco MDS command resolves the issue?
The correct answer is Option A. Cisco MDS and Nexus SAN troubleshooting is driven by fabric state: the host and target must be in the correct VSAN, must complete FLOGI/PLOGI where applicable, and must be permitted by active zoning, fcdomain, FSPF, NPV/NPIV, or port-security policy. This question focuses on MDS, VSAN, port security, so the selected action fixes the dependency that prevents the initiator, target, or inter-switch link from becoming usable. Cisco documentation emphasizes checking VSAN membership, active zonesets, correct port mode, fabric binding, device-alias consistency, and the relevant FC databases before changing unrelated server settings. The distractors either target a different database, use the wrong port role, or would not cause the observed Fibre Channel state to change. After the fix, the engineer should confirm the interface state, FLOGI database, name-server entries, zoneset activation, and successful initiator-to-target reachability with tools such as fcping or fabric show commands.