HP AE370A HP StorageWorks Fabric OS 6.x administrator guide (5697-0015, May 20 - Page 246

The Fibre Channel routing feature for M-EOS interoperability is not a licensed feature. Table 59 Brocade-McDATA M-EOSn interoperability compatibility matrix1 Fabric OS Versions of M-EOSn (i10k) 9.2.0 9.6.2 v5.3.0 Yes No 6.0 No Yes 1. Both Open and McDATA Fabric modes are supported. Connected SANs provide additional functionality not possible with segregated SANs. Some of these functions are as follows: • Island consolidation-Uses the Fabric OS 6.0 FC router to connect isolated M-EOS and Brocade Fabrics and share devices. • Backup consolidation-Consolidates backup solutions across Brocade and M-EOS fabrics. • Manageable large-scale storage network-Uses the Fabric OS 6.0 FC router to localize traffic while connecting devices in the metaSAN. This provides a large number of fabrics with a large number of devices. • Sharing across an FCIP link-Shares devices between Brocade and M-EOS fabrics over a campus Ethernet or over long-distance IP links beyond 1000 km. • Sharing across a long-distance FC link-Shares devices between Brocade fabrics over long-distance FC links as far as 300 km. • LUN sharing-Uses your high-end RAID array connected to an Intrepid series to share targets with an HP fabric; just connect one Intrepid series port to an FC router EX_Port and the one EX_Port to the HP fabric. • LSAN zone database binding-Increases FCR scalability to support more FCR switches in the backbone and support more devices in the metaSAN. The connectivity limitations of a metaSAN containing Brocade and M-EOS fabrics are defined by the scalability of each individual fabric. See the HP StorageWorks SAN Design reference guide for the latest scalability support information: http://www.hp.com/go/sandesignguide Refer to the M-EOS fabric documentation for scalability considerations. McDATA Mi10K interoperability When an EX_Port is connected to a M-EOS edge fabric, the front domain ID must be within a range the edge M-Series switch can understand. Valid values are: • McDATA Native mode: 1 - 31 • McDATA Open mode: 97 - 127 The default front domain ID assigned to the EX_Port remains at 160 when it is created. However when connected to the Mi10K, a daemon sends a request domain ID (RDI) command that must be within the valid range M-EOS understands. When an RDI command is sent to an Mi10k switch with a valid domain ID defined by standards and is not within the range an Mi10k switch understands, the RDI request is rejected. This behavior of the i10k is different from other M-Series switches. If you set a front domain ID that is not within the valid range M-EOS understands, then in Fibre Channel routing, a daemon internally requests a valid domain ID that M-EOS understands. Unless you change the front domain ID, there is no impact. The behavior with the non-Mi10k switches displays the regular switch when configured. When the Mi10k is connected, it shows the switch name in format "McDATA: format". First the daemon requests the switch name and when this request is rejected by the Mi10K edge switch with the reason of command not supported, the daemon will try an ELS command request node identification 246 Using the FC-FC routing service