The switch Interoperability test was performed per the Fibre Channel Methodologies for Interconnect (FC-MI) Technical Report version 1.92 which describes common methodologies for facilitating interoperability in a heterogeneous switch SAN environment.
The MDS family is SANmark 3001and 3002 qualified.
IBM Supports MDS InterOp Mode-1 (FC-MI standard), Mode-2 (Brocade PID=0), Mode-3 (Brocade PID=1), and Mode-4 (McDATA native). Please refer to the following IBM document for more information:
Note All Cisco data center switches including MDS and Nexus platforms are interoperable among each other at all code levels released on Cisco web site. If there is any feature specific code level recommendation for a release, we publish the information in Release Notes and product configuration guides.
Note If a desired combination of a Cisco NX-OS software version and a Brocade or McData switch does not appear in this section, submit a Cisco Configuration Request (CCR) to have the combination validated before deploying that combination. Click here to download the CCR form.
Note Interoperability between a Cisco MDS 9000 or Cisco Nexus 5000 switch and a Brocade switch is based on the software version that is running on each switch. Interoperability is not based on the model number of the switch. The model numbers of the switches are provided in the table below for reference.
Table 3-1 Switch Interoperability Matrix, MDS 9000 Series
Cisco MDS OS Version
MDS InterOp Mode
HP Blade Chassis with Brocade 4Gb SAN Switches (Brocade model 4024)
Table 3-2 Switch Interoperability Matrix, Cisco Nexus 5000 Series
2.Cisco MDS interop mode 1 supports connectivity of Cisco MDS 9000 Family switches to other Fibre Channel vendor switches per the FC-MI standard document.
3.Cisco MDS interop mode 2 supports nondisruptive connectivity to Brocade Silkworm 2800 and 3800 switches family with Core-PID set to 0.
4.Cisco MDS InterOp mode 3 supports nondisruptive connectivity of all Brocade Silkworm switches including 3900 and 12000 switch family with Core-PID set to 1. We recommend using Cisco Fabric Manager for all MDS interop mode types with Brocade for zone administration. In MDS InterOp mode 3 and Brocade Native, Host attached to Brocade does not receive RSCN after zoneset activation/de-activation and can not discover LUNs immediately. Zoneset activation includes, a new zoneset activation and modification of existing zoneset and reactivation. Zoneset may be a regular zoneset or IVR zoneset. This issue is seen on all major Brocade releases 5.3.x; 6.1.0d, 6.x.
5.Zoning changes cannot be activated from Brocade switch. Work around is to use MDS switches to activate zoning changes. Brocade switches cannot see IVR enabled devices if NAT is enabled
6.In an IVR NAT enabled configuration, use persistence FCID with Area’s value of 64 or less for MDS connected devices. This will ensure that the Brocade nameserver will discover the devices. In addition, RDI mode must be configured.
7.Cisco SAN-OS 3.2(1a) is supported on Brocade switches running 5.3.0 only.
8.MDS interop mode 4 supports native connectivity to McDATA switches, and is supported for migration purposes. McDATA software security features such as Fabric Binding are not supported in this mode and must be disabled.
IBM eServer Bladecenter Interoperability Matrix
Table 3-4 MDS Interoperability with IBM eServer Bladecenter12