I got asked an interesting question over the weekend regarding the use of DS8000 Metro Mirror and FCIP distance extension technology. It seems an IBM competitor had told a client that their sync
hron ous repl icat ion technology worked over an FCIP link, but that IBM DS8000 Metro Mirror did not. My first reaction was that FCIP is clearly going to have more latency than a WDM/CWDM based solution, but there is no technical reason why an FCIP link would not work. So to confirm, I checked the last published Interop Matrix for DS8000 found here: It confirmed my thinking when on page 9, I checked out Table 3 which clearly shows a number of FCIP extenders all happily supported by DS8000 Metro Mirror. I then checked the Brocade matrix found here: Amusingly it lists IBM Metro Mirror and the other vendors solution listed as supported with the same list of FCIP extenders. Finally I found a really nice white paper which rather proved the point: http://www.thebrainhouse.ch/gse/doku/65_GSE/Performance_of_Metro_Mirror_over_Distance_WP100824_20060908.pdf This white paper tested Metro Mirror over distance using.... (wait for it) FCIP to simulate distance. I also found an IBM internal whitepaper about a client who did DS8000 Metro Mirror over 830kms with a Cienna CN2000. So... myth busted....
The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
Anthony's Blog: Using System Storage - An Aussie Storage Blog
Matching: fcip X