Implementing and Managing Cisco MDS Switches
Domain 1 covers the work you do on a Cisco MDS 9000 switch itself: initial bring-up, NX-OS CLI conventions, VSAN and interface provisioning, administrative access, licensing, upgrades and health checks. Exam items often describe a switch that is reachable but not passing traffic, or a new switch joining an existing SAN.
Bring-up and management
- Use the setup script or CLI to set the mgmt0 address, default gateway, hostname, admin credentials, NTP and AAA. Separate management traffic from in-band VSAN traffic.
- Verify feature licenses before enabling features; configure roles and rule-based RBAC, SNMP, syslog and Call Home.
- Save with copy running-config startup-config; verify with show running-config, show interface, show vsan, show fcdomain and show logging.
VSAN and port rules
- A VSAN is an independent fabric instance. Create it, then explicitly assign interfaces; creation alone assigns nothing.
- Choose the port mode to match the neighbor: F for a host/target N port, FL for loop, E for an ISL, TE for a trunking ISL, NP for an NPV uplink, SD for SPAN destination.
- For trunking ISLs, set the allowed VSAN list on both ends. A mismatch keeps the link from carrying that VSAN.
- Domain IDs must be unique inside a VSAN. FC IDs use domain/area/port; principal switch election prefers configured principal priority and then the lowest switch WWN.
Worked example
A new MDS connects to a core switch. The ISL shows up, but hosts in VSAN 20 cannot log in. Check the physical port: it is TE, but the trunk allowed list contains only VSAN 10. The core has VSAN 20 configured, but the edge ISL never carries it. Add VSAN 20 to the allowed list on both switches, verify with show interface trunk vsan, then confirm FLOGI and name-server entries. The reasoning: an up E/TE port does not imply every VSAN is carried; trunk allowance is a separate gate.
Traps
- Assuming a VSAN exists on a port because the VSAN was created.
- Setting a domain ID in the wrong VSAN, or duplicating one.
- Treating mgmt0 as an in-band FC path.
- Forgetting to save or to distribute consistent trunk and VSAN settings.