<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:black;
position:relative;
top:0pt;
mso-text-raise:0pt;
letter-spacing:0pt;
mso-number-form:default;
mso-number-spacing:default;
mso-stylistic-set:0;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.vote-count-post
{mso-style-name:vote-count-post;}
span.comment-copy
{mso-style-name:comment-copy;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
font-variant:normal !important;
color:windowtext;
text-transform:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
font-variant:normal !important;
color:windowtext;
text-transform:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-IN" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Hi Malcolm,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Thank! That’s a very good point. I’ve almost forgot that we should prefer cross failover configuration, rather than the individual failover.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">So, using the same connection type is we should prefer (to cover failover + load distribution).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><i><span lang="EN-US" style="color:#2E74B5">--<o:p></o:p></span></i></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#2E74B5">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#2E74B5">Jeevan.<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Cowe, Malcolm J [mailto:malcolm.j.cowe@intel.com]
<br>
<b>Sent:</b> 15 March 2016 15:24<br>
<b>To:</b> Jeevan Behara Patnaik (GIS) <jeevan.patnaik@wipro.com>; lustre-discuss@lists.lustre.org<br>
<b>Subject:</b> RE: [lustre-discuss] Lustre failover configuration - Need help in selecting storage<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB">One of the reasons to use the same connection type for the IO path to the storage is to ensure consistency in performance regardless of which server the storage is mounted on. However, there is another reason for using
a symmetrical IO path: Lustre systems are designed to distribute the IO workload across multiple servers in parallel, maximising the available throughput across the network and the disk IO and each server delivering the same level of performance.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">The servers are usually configured into building blocks of paired clusters for HA (that is, 2 servers attached to one or more shared DAS arrays). The storage is split into multiple LUNs, with half of the LUNs presented
to one server, half to the other server in the pair. This means that each server is able to transact IO, each server has the same performance characteristics and there are no idle or passive servers. Maximum utilisation and consistent performance across the
all the servers in the network.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">For example, if you have 2 OSS servers (oss1, oss2) connected to a 60 disk tray split into 6 RAID 6 (8+2) LUNs, then 3 LUNs would be primary targets on oss1, 3 on oss2, and you’d allow the LUNs to migrate on failover.
This way, each of the servers is active on the network, maximising the available throughput performance of the file system. Similarly, the MGT and MDT are commonly paired into an metadata server pair.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">If you create an imbalance in the performance of each IO path, then the 2<sup>nd</sup> server is going to end up as a passive node only, rather than being another server to scale out the bandwidth.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I’ve attached some example diagrams (apologies to the list for the additional 120KB or so – not sure the list will accept it actually :) ), that highlights at a very high level a fairly well used pattern for the metadata
and OSS servers for HA. Just pictures, but enough to get an idea of what Lustre is about. Where costs are a concern, one can also investigate use of JBODs, although they add their own complexity with regard to storage management (identifying failed disks,
etc.). ZFS is gaining popularity as a storage platform but has its own challenges as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#0071C5">Malcolm Cowe<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial",sans-serif">High Performance Data Division<o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial",sans-serif">Intel Corporation</span></b><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial",sans-serif"> |
<span style="color:#0071C5"><a href="http://www.intel.com">www.intel.com</a></span><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><a name="_____replyseparator"></a><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
<a href="mailto:jeevan.patnaik@wipro.com">jeevan.patnaik@wipro.com</a> [<a href="mailto:jeevan.patnaik@wipro.com">mailto:jeevan.patnaik@wipro.com</a>]
<br>
<b>Sent:</b> Tuesday, March 15, 2016 6:18 PM<br>
<b>To:</b> <a href="mailto:bevans@cray.com">bevans@cray.com</a>; <a href="mailto:lustre-discuss@lists.lustre.org">
lustre-discuss@lists.lustre.org</a>; Cowe, Malcolm J<br>
<b>Subject:</b> RE: [lustre-discuss] Lustre failover configuration - Need help in selecting storage<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-fareast-language:EN-US">Thanks Ben and Malcolm,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-fareast-language:EN-US">Yes, now I have an idea what to do. I thought multiport DAS that could share a single storage on two servers is hard to find. Also, if there is any cost concern, we can
still use one directly attached Primary node and Network attached Failover node.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><i><span lang="EN-US" style="color:#2E74B5">--<o:p></o:p></span></i></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:#2E74B5">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:#2E74B5">Jeevan.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Cowe, Malcolm J [<a href="mailto:malcolm.j.cowe@intel.com">mailto:malcolm.j.cowe@intel.com</a>]
<br>
<b>Sent:</b> 15 March 2016 01:58<br>
<b>To:</b> Jeevan Behara Patnaik (GIS) <<a href="mailto:jeevan.patnaik@wipro.com">jeevan.patnaik@wipro.com</a>>;
<a href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a><br>
<b>Subject:</b> RE: [lustre-discuss] Lustre failover configuration - Need help in selecting storage<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB">Why not use a multi-ported direct attached storage (DAS) enclosure? Performance is retained and configuration is straightforward. There are a number of such enclosures available from a range
of vendors, many of whom have solutions that have been qualified with Lustre.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#0071C5">Malcolm Cowe<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial",sans-serif">High Performance Data Division<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial",sans-serif">Intel Corporation</span></b><span lang="EN-US" style="font-size:8.0pt;font-family:"Arial",sans-serif"> |
<span style="color:#0071C5"><a href="http://www.intel.com">www.intel.com</a></span><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:#2E74B5"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Ben Evans [<a href="mailto:bevans@cray.com">mailto:bevans@cray.com</a>]
<br>
<b>Sent:</b> 14 March 2016 19:15<br>
<b>To:</b> Jeevan Behara Patnaik (GIS) <<a href="mailto:jeevan.patnaik@wipro.com">jeevan.patnaik@wipro.com</a>>;
<a href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a><br>
<b>Subject:</b> Re: [lustre-discuss] Lustre failover configuration - Need help in selecting storage<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black">You'll only go as fast as your slowest piece.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black">With that in mind, First figure out what sorts of bandwidth you can actually get across your chosen network type (per server). That will dictate how fast you want your
storage to be. Benchmark it, make sure you can get the I/O over the wire that you think you can for that one server.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black">Next, find a disk system that can deliver that speed for you (you'll be able to get some of the info, but you'll want to benchmark that as well, with different RAID configurations,
settings, etc.). You may want to overprovision storage speed, since you probably won't be getting ideal throughput numbers.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black">As to redundancy, there are a number of direct-attach systems that allow you to connect two servers to the same set of disks. You don't need (or really want) anything
fancy like a SAN.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black">Given the cost/performance ratios, you might also experiment with a few smaller OSTs made up of SSDs, or using something like flashcache on the MDT(s).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black">-Ben Evans<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">lustre-discuss <<a href="mailto:lustre-discuss-bounces@lists.lustre.org">lustre-discuss-bounces@lists.lustre.org</a>> on behalf of "<a href="mailto:jeevan.patnaik@wipro.com">jeevan.patnaik@wipro.com</a>" <<a href="mailto:jeevan.patnaik@wipro.com">jeevan.patnaik@wipro.com</a>><br>
<b>Date: </b>Monday, March 14, 2016 at 8:36 AM<br>
<b>To: </b>"<a href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a>" <<a href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a>><br>
<b>Subject: </b>[lustre-discuss] Lustre failover configuration - Need help in selecting storage<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="624" style="width:468.0pt;margin-left:36.0pt;background:white;border-collapse:collapse">
<tbody>
<tr>
<td width="19" valign="top" style="width:14.05pt;padding:0cm 11.25pt 0cm 0cm"></td>
<td width="605" valign="top" style="width:453.95pt;padding:0cm 0cm 0cm 0cm">
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">We need storage specifically for HPC Lustre failover setup, where it is must that two servers should share same block level storage to have failover configuration.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">With very limited knowledge on hardware, I have the below understanding:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:6.0pt;margin-left:22.5pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">NAS can be used for shared storage, but there will be bottleneck for speed due to intermediate network.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:6.0pt;margin-left:22.5pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">SAN can be used, but it is costly to implement the solution and not really needed for Storage of 50-100TB.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:6.0pt;margin-left:22.5pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">If at all we find multiple iscsi ports to the storage enclosure, the storage can be used only by splitting i.e., works as two storage devices and the same storage can't be used
by both the<br>
systems. (And one thing to remind here, in the lustre setup, both the servers would be only attached, but only one will be used (not sure, how it is possible, again need to check on this).</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:22.5pt;text-indent:-18.0pt"><span style="font-size:10.0pt;font-family:Symbol">·</span><span style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">Having two virtual machines may be how we can do it. But, then, it is not really helpful for the purpose of failover, as the physical machine would be only one.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">But, while posting the question, I am thinking, maybe we can compromise on speed in NAS, if we try having one directly attached server (primary) and the other attached via network (failover),
so we face slowness only when the primary stops working.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">As I posted the similar question on Server Fault:
<a href="http://serverfault.com/questions/763569/is-it-possible-to-have-a-directly-attached-shared-storage-accessed-at-block-lev">
http://serverfault.com/questions/763569/is-it-possible-to-have-a-directly-attached-shared-storage-accessed-at-block-lev</a>, I have got the following response:</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#222426;border:none windowtext 1.0pt;padding:0cm"><br>
<span class="comment-copy">“Have you actually attempted to set up a proof of concept, or at least looked through the</span><span class="apple-converted-space"> </span><span class="comment-copy"><a href="http://doc.lustre.org/lustre_manual.xhtml"><span style="color:#005999">documentation</span></a>?
Lustre really doesn't care very much how you connect to the underlying storage, so you can do whatever gets you the bandwidth you need.”</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span class="comment-copy"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#222426;border:none windowtext 1.0pt;padding:0cm">So, is it true that we don’t need to worry about bandwidth of the storage server?</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span class="comment-copy"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#222426;border:none windowtext 1.0pt;padding:0cm">I mean, for example: the communication as I understood is as follows:</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">Client
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> MGS (Ethernet)</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">MGS
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> MGT (Direct/ISCSI)
</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">MGS
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> MDS (Ethernet/Internal
Communication)</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">MDS
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> MDT (Direct/ISCSI/Ethernet)</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">MDS
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> OSS (Ethernet)</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">OSS
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> OST (Direct/ISCSI/Ethernet)
</span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt;text-indent:-18.0pt">
<span style="font-size:10.0pt;font-family:Wingdings">è</span><span style="font-size:7.0pt">
</span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm">OST
</span></span><span class="comment-copy"><span style="font-size:10.0pt;font-family:Wingdings;border:none windowtext 1.0pt;padding:0cm">ßà</span></span><span class="comment-copy"><span style="font-size:10.0pt;border:none windowtext 1.0pt;padding:0cm"> Client
(Ethernet) </span></span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426">Does it mean that, the performance won’t be affected at any stage, if iscsi is replaced by Ethernet or by using limited bandwidth?
</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="19" valign="top" style="width:14.05pt;padding:0cm 11.25pt 0cm 0cm">
<p class="MsoNormal" align="center" style="text-align:center;line-height:12.7pt">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#222426"> </span><o:p></o:p></p>
</td>
<td width="605" valign="top" style="width:453.95pt;padding:0cm 0cm 0cm 0cm">
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:#222426"> </span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black"><img border="0" width="79" height="79" style="width:.8229in;height:.8229in" id="_x0000_i1025" src="cid:image001.jpg@01D17ED0.CD65E740" alt="WNC_Logo"></span><b><span lang="EN-US" style="color:#2E74B5">--</span></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="font-size:10.0pt;color:#2E74B5">Thanks and Regards,</span></b><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><b><span lang="EN-US" style="color:#C45911">Jeevan Patnaik B</span></b><span lang="EN-US" style="color:#2E74B5">|
</span><span lang="EN-US" style="color:#BF8F00">Project Engineer</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:#002060">Nokia IT - HEE Platform</span><span lang="EN-US" style="color:#2E74B5"> |
</span><span lang="EN-US" style="color:#2F5496">WIPRO Technologies - Hyderabad</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:#7F7F7F">Mob: +91-9000607181| Off: +91-4030970347.</span><span lang="EN-US" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US" style="font-size:10.5pt;color:black">The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain
proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING:
Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
<a href="http://www.wipro.com">www.wipro.com</a> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s)
and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
<a href="http://www.wipro.com">www.wipro.com</a> <o:p></o:p></span></p>
</div>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should
not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments
for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
</body>
</html>