How to configure iscsi target parameters to allow max resiliance
Felipe Gutierrez
felipe at usto.re
Wed May 6 08:28:38 PDT 2015
Formatted message: <a href="http://www.t10.org/cgi-bin/ac.pl?t=r&f=r1505138_f.htm">HTML-formatted message</a>
ok, thanks anyway.
On Wed, May 6, 2015 at 12:20 PM, Black, David <david.black at emc.com> wrote:
> This is not a support forum - please pursue questions about
> implementation
>
> behavior in support forums for the appropriate implementation.
>
>
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA 01748
> +1 (508) 293-7953 FAX: +1 (508) 293-7786
> david.black at emc.com Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>
>
>
> *From:* owner-t10 at t10.org [mailto:owner-t10 at t10.org] *On Behalf Of *Felipe
> Gutierrez
> *Sent:* Wednesday, May 06, 2015 10:56 AM
> *To:* t10 at t10.org
> *Subject:* How to configure iscsi target parameters to allow max
> resiliance
>
>
>
> Hi, I am experiencing a lot of broken pipe on my iscsi target when I try
> to create a virtual machine form vmware on it. The design is like this:
>
>
>
> vmware -> NFS -> iscsi initiator -> iscsi target
>
>
>
> Ok, I know I am using two protocols (NFS and iSCSI), and I am not doing a
> simple copy of files, that by the way work with nfs. I am installing a VM.
>
>
>
> I wounder to know about the parameters at
> https://www.ietf.org/rfc/rfc3720.txt which I should increase to make it
> ok.
>
>
>
> 12.2. MaxConnections
>
> 12.12. MaxRecvDataSegmentLength
>
> 12.13. MaxBurstLength
>
> 12.14. FirstBurstLength
>
> 12.15. DefaultTime2Wait
>
> 12.16. DefaultTime2Retain
>
> 12.17. MaxOutstandingR2T
>
>
>
> thanks,
>
> Felipe
>
>
More information about the T10
mailing list