[c-nsp] FCoE or FCIP over MPLS possible?

[Charles Sprickman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 19, 2014, at 8:48 AM, Mark Tinka wrote:

> On Wednesday, March 19, 2014 01:39:06 PM Youssef Bengelloun-
> Zahr wrote:
> 
>> We have been working on the same problem but with a
>> different vendor.
>> 
>> So far, no real clues on how to transport reliably FCoE
>> over WAN (MPLS in our case).
>> 
>> I'm interested in any feedbacks you guys might have.
> 
> We looked at this back in 2009. Basically, it was a no-go 
> then. You could only reliably transport FCIP or iSCSI 
> because that can run in asynchronous mode.
> 
> FCoE or FC required DWDM infrastructure over short spans.

Also, no matter what you use, be aware of how the delay will affect
any applications running on top of your storage.  If you have the
"PostgreSQL Performance" book (awesome if you even dabble in PGSQL,
BTW), there is an excellent explanation of how disk latency will
affect your IOPS in the real world.

Plug some crazy latency numbers into this thing to get an idea of
what the delay on a long WAN link might do to your DB throughput:

http://www.wmarow.com/strcalc/

The parameter that you want to play with is probably the "average
I/O service time (ms)" field.

Charles

> 
> Of course, that was 2009. We were a transport service 
> provider, not a data centre player. So I haven't looked at 
> this since.
> 
> Mark.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJTKfCxAAoJEMfwH0dqLIp2hRkIAJ5qRd0Amw2XYolEYim62NIy
gMwG0j0pMNpdMtN2x8VX9cpfl6mGZnjKqvF2n3y55cVNZgpaMYr248nyQfQuGT7T
McV7fj8Nx2kcwCn3WGAQxlT7O46REkNcCVpF5hgLEIO8Sgqwnoj2xqKqiP1Dqp/4
zPt3l10rFggGchdmp8yP5RwGIww/vcXNBa/4hCR5ditINTg7kiN2fejgnDOkzIP9
CYTR0MViUaP8Y8AAVnHVP5FEnURe8bwgyY1oORiDhyf3pn7s5pEL4g7dpnNdwavn
50zbgYm0rv7cODt3ZvqnIL86S7QqfnfHog875Ihmif3rEl8EuodKNuEAmf35SEs=
=SEOf
-----END PGP SIGNATURE-----