<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic FCIP Replication performance problems in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709376#M2655</link>
    <description>I'm looking for some light in this CA installation:&lt;BR /&gt;
&lt;BR /&gt;
EVA3000 - VCS 3028&lt;BR /&gt;
EVA4000 - XCS 5031&lt;BR /&gt;
Two independent fiber links (dedicated to CA) with bulk electronic in it, that delivers 30-75 Mbits/sec. Length is less than 10 Km.&lt;BR /&gt;
2 + 2 SR2122 with only FCIP protocol, dedicated to CA.&lt;BR /&gt;
&lt;BR /&gt;
In the performance test phase we use Command View to manage CA activity. No SRM installed.&lt;BR /&gt;
&lt;BR /&gt;
Ping letency for 2KBytes packets are 4 ms (round trip). FTP bandwith is over 8MB/sec average. We measure this using two hosts that use this line.&lt;BR /&gt;
&lt;BR /&gt;
Using the performance estimator we should have arround 100-115 I/Os sec (block=16KB) and trip latency of 2ms and low line usage.&lt;BR /&gt;
&lt;BR /&gt;
Now the reality ... very sad data:&lt;BR /&gt;
- Full Copy  of one single copy set in one DR group takes for ever ... 0,6 MB/sec. Using EVAperf drt we get latency of more than 1000 ms.&lt;BR /&gt;
&lt;BR /&gt;
- Host I/O (iometer) of 16KB (full writes) gives arround 2 I/Os/sec&lt;BR /&gt;
&lt;BR /&gt;
During the test there are no other significant load on the EVA3000 and NO load at all on the EVA4000. The line is dedicated to CA all the time.&lt;BR /&gt;
&lt;BR /&gt;
The obvious answer is that the problem is the line speed. Said that, way the ping &amp;amp; ftp numbers are good and the CA are so bad ??&lt;BR /&gt;
Have you had similar experience in other FCIP replications ??&lt;BR /&gt;
&lt;BR /&gt;
Any help or experience sharing will be appreciated.</description>
    <pubDate>Thu, 19 Oct 2006 08:37:32 GMT</pubDate>
    <dc:creator>BR711326</dc:creator>
    <dc:date>2006-10-19T08:37:32Z</dc:date>
    <item>
      <title>FCIP Replication performance problems</title>
      <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709376#M2655</link>
      <description>I'm looking for some light in this CA installation:&lt;BR /&gt;
&lt;BR /&gt;
EVA3000 - VCS 3028&lt;BR /&gt;
EVA4000 - XCS 5031&lt;BR /&gt;
Two independent fiber links (dedicated to CA) with bulk electronic in it, that delivers 30-75 Mbits/sec. Length is less than 10 Km.&lt;BR /&gt;
2 + 2 SR2122 with only FCIP protocol, dedicated to CA.&lt;BR /&gt;
&lt;BR /&gt;
In the performance test phase we use Command View to manage CA activity. No SRM installed.&lt;BR /&gt;
&lt;BR /&gt;
Ping letency for 2KBytes packets are 4 ms (round trip). FTP bandwith is over 8MB/sec average. We measure this using two hosts that use this line.&lt;BR /&gt;
&lt;BR /&gt;
Using the performance estimator we should have arround 100-115 I/Os sec (block=16KB) and trip latency of 2ms and low line usage.&lt;BR /&gt;
&lt;BR /&gt;
Now the reality ... very sad data:&lt;BR /&gt;
- Full Copy  of one single copy set in one DR group takes for ever ... 0,6 MB/sec. Using EVAperf drt we get latency of more than 1000 ms.&lt;BR /&gt;
&lt;BR /&gt;
- Host I/O (iometer) of 16KB (full writes) gives arround 2 I/Os/sec&lt;BR /&gt;
&lt;BR /&gt;
During the test there are no other significant load on the EVA3000 and NO load at all on the EVA4000. The line is dedicated to CA all the time.&lt;BR /&gt;
&lt;BR /&gt;
The obvious answer is that the problem is the line speed. Said that, way the ping &amp;amp; ftp numbers are good and the CA are so bad ??&lt;BR /&gt;
Have you had similar experience in other FCIP replications ??&lt;BR /&gt;
&lt;BR /&gt;
Any help or experience sharing will be appreciated.</description>
      <pubDate>Thu, 19 Oct 2006 08:37:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709376#M2655</guid>
      <dc:creator>BR711326</dc:creator>
      <dc:date>2006-10-19T08:37:32Z</dc:date>
    </item>
    <item>
      <title>Re: FCIP Replication performance problems</title>
      <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709377#M2656</link>
      <description>How are you converting FC to IP on Brocade MPR's, if so make sure you have exchange trunking  turned off.</description>
      <pubDate>Thu, 19 Oct 2006 16:57:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709377#M2656</guid>
      <dc:creator>eis1953</dc:creator>
      <dc:date>2006-10-19T16:57:18Z</dc:date>
    </item>
    <item>
      <title>Re: FCIP Replication performance problems</title>
      <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709378#M2657</link>
      <description>The FC - TCPIP gateway is the SR2122 from HP (actually is an old Cisco NS54xx).&lt;BR /&gt;We don't use the Brocade MPR.&lt;BR /&gt;The switches are SAN switch 2/16 &amp;amp; 2/16V.</description>
      <pubDate>Fri, 20 Oct 2006 01:25:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709378#M2657</guid>
      <dc:creator>BR711326</dc:creator>
      <dc:date>2006-10-20T01:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: FCIP Replication performance problems</title>
      <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709379#M2658</link>
      <description>The solution:&lt;BR /&gt;&lt;BR /&gt;Reading the SR2122 Getting Started Guide&lt;BR /&gt;P/N=AA-RTE1G-TE&lt;BR /&gt;page 62 ...&lt;BR /&gt;regarding the parameter "useBport"&lt;BR /&gt;you can see:&lt;BR /&gt;&lt;BR /&gt;Use Fibre Channel (FC) B_port connectivity. This configuration option applies&lt;BR /&gt;to all FCIP connection types. By default, the useBport setting is enabled.&lt;BR /&gt;However, the setting is dependent on the Fibre Channel switches and switch&lt;BR /&gt;firmware in use:&lt;BR /&gt;â &amp;nbsp; B-series&lt;BR /&gt;â   useBport disabled (B-series FW 3.2.x or 4.4.x or later)&lt;BR /&gt;â   useBport enabled (other B-series switch FW)&lt;BR /&gt;â &amp;nbsp; C-series - useBport disabled (MDS FW v2.01b or later)&lt;BR /&gt;â &amp;nbsp; M-series - useBport enabled&lt;BR /&gt;&lt;BR /&gt;My switches versions are 5.1.x &amp;amp; 3.2.x so I have to disable useBport.&lt;BR /&gt;&lt;BR /&gt;After that I get 250 I/O/sec doing iometer on a replicated disk and arround 4MB/sec bandwidth.&lt;BR /&gt;&lt;BR /&gt;So, take care with this parameters !!</description>
      <pubDate>Fri, 20 Oct 2006 01:34:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709379#M2658</guid>
      <dc:creator>BR711326</dc:creator>
      <dc:date>2006-10-20T01:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: FCIP Replication performance problems</title>
      <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709380#M2659</link>
      <description>Same installation, new problems:&lt;BR /&gt;From time to time (once or twice per week) we got communications problems between the SR's.&lt;BR /&gt;Link drop and after few second/minutes link come up again.&lt;BR /&gt;We have two lines, 4 SR2122-2 for FCIP.&lt;BR /&gt;In one of our lines, as soon as the line comes up, we can see automatic FLOGI from the SR and the CA activity resumes.&lt;BR /&gt;In the other line, when the link comes up, nothing happend.--&amp;gt; connection down for ever.&lt;BR /&gt;&lt;BR /&gt;To fix that, I need to disable/enable the FC switch port where the SR is, in this way the SR logs in again to the fabric.&lt;BR /&gt;&lt;BR /&gt;As far as I can see, all the elements in the two lines are similar. Way then this big difference reaction?&lt;BR /&gt;Where can I start debugging this ?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;antonio</description>
      <pubDate>Tue, 17 Apr 2007 16:44:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709380#M2659</guid>
      <dc:creator>BR711326</dc:creator>
      <dc:date>2007-04-17T16:44:38Z</dc:date>
    </item>
    <item>
      <title>Re: FCIP Replication performance problems</title>
      <link>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709381#M2660</link>
      <description>Try this,  It was just released&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18006.www1.hp.com/products/storageworks/fcipd_gateway/index.html?jumpid=reg_R1002_USEN" target="_blank" rel="nofollow"&gt;http://h18006.www1.hp.com/products/storageworks/fcipd_gateway/index.html?jumpid=reg_R1002_USEN&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Shaun</description>
      <pubDate>Mon, 28 May 2007 19:31:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/fcip-replication-performance-problems/m-p/709381#M2660</guid>
      <dc:creator>Shaun Walsh</dc:creator>
      <dc:date>2007-05-28T19:31:01Z</dc:date>
    </item>
  </channel>
</rss>

