<?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 Re: Zoning design in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330425#M35167</link>
    <description>Hi,&lt;BR /&gt;zoning is giving us the IO isolation (e.g. host/storage from host/tape) and security even to the small environment, &lt;BR /&gt;you could see the Brocade guide to&lt;BR /&gt;understanding zoning:&lt;BR /&gt;&lt;A href="http://www.brocadekorea.com/download/resource/53_0000213_01.pdf" target="_blank"&gt;http://www.brocadekorea.com/download/resource/53_0000213_01.pdf&lt;/A&gt;</description>
    <pubDate>Wed, 31 Dec 2008 08:31:04 GMT</pubDate>
    <dc:creator>IBaltay</dc:creator>
    <dc:date>2008-12-31T08:31:04Z</dc:date>
    <item>
      <title>Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330423#M35165</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;In what case the zoning needed to implement? Is it when there is multi connection out from MSA ?Let say if i only got 1 fiber out from MSA 1000;2 server with each 2 Fiber Channel connect to SAN switch, do i still need to do the zoning configuration on SAN switch ?&lt;BR /&gt;&lt;BR /&gt;Thank you for those helpers here :)&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2008 06:14:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330423#M35165</guid>
      <dc:creator>lim meng kiat</dc:creator>
      <dc:date>2008-12-31T06:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330424#M35166</link>
      <description>&lt;!--!*#--&gt;Hi Lim, &lt;BR /&gt;&lt;BR /&gt;Implementation of zone is highly recommended on any SAN switch. ( Though few SAN switch is it mandatory for it to work). &lt;BR /&gt;hence to answer you queries, &lt;BR /&gt;Almost in every case zoning should be implemented. &lt;BR /&gt;Yes, zoning configuration is highly recommended on the scenario that you have explained. &lt;BR /&gt;The best way to zone is to have one initiator and multiple targets to be part of one zone. hence in you scenario you need 2 zones, one for each host on each of your switches.&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2008 08:24:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330424#M35166</guid>
      <dc:creator>Shrivastava Nitin</dc:creator>
      <dc:date>2008-12-31T08:24:25Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330425#M35167</link>
      <description>Hi,&lt;BR /&gt;zoning is giving us the IO isolation (e.g. host/storage from host/tape) and security even to the small environment, &lt;BR /&gt;you could see the Brocade guide to&lt;BR /&gt;understanding zoning:&lt;BR /&gt;&lt;A href="http://www.brocadekorea.com/download/resource/53_0000213_01.pdf" target="_blank"&gt;http://www.brocadekorea.com/download/resource/53_0000213_01.pdf&lt;/A&gt;</description>
      <pubDate>Wed, 31 Dec 2008 08:31:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330425#M35167</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2008-12-31T08:31:04Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330426#M35168</link>
      <description>Refer below link for zoning . Zoning is very improtant while you have tape libraries / different OS in the the fabric. It basically to stop interference between different devices / hosts. &lt;BR /&gt;&lt;BR /&gt;Its always recommended to create seperate zones for tape libraries / different OS's. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf?jumpid=reg_R1002_USEN" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00403562/c00403562.pdf?jumpid=reg_R1002_USEN&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2008 08:37:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330426#M35168</guid>
      <dc:creator>Dileep..</dc:creator>
      <dc:date>2008-12-31T08:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330427#M35169</link>
      <description>Thank for all the reply here...&lt;BR /&gt;My problem is :&lt;BR /&gt;- 1 Brocade SAN switch&lt;BR /&gt;- 1 MSA 1000 FC&lt;BR /&gt;- 2 old server 2003 performing clustering&lt;BR /&gt;- 2 new server 2008 performing clustering&lt;BR /&gt;- create old zone for 2 old server &amp;amp; MSA 1000FC&lt;BR /&gt;- create new zone for 2 new server &amp;amp; MSA 1000FC&lt;BR /&gt;&lt;BR /&gt;Is it my design is validate? I refer to Brocade engineer &amp;amp; according to them this is even configuration on SAN design since only 1 FC from MSA 1000.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 02 Jan 2009 01:51:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330427#M35169</guid>
      <dc:creator>lim meng kiat</dc:creator>
      <dc:date>2009-01-02T01:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330428#M35170</link>
      <description>Whatever you mentioned is not the the best practice. &lt;BR /&gt;&lt;BR /&gt;I would recommend to create zone for each Server/ HBA. &lt;BR /&gt;&lt;BR /&gt;Example :&lt;BR /&gt;1)If you have 2 HBA on first server , then create two seperate zones for each HBA and add MSA1000 to that. Like wise do it for second server. So each server will have 2 zones.&lt;BR /&gt;&lt;BR /&gt;2) If you have single HBA on servers then create seperate zone for each server then add MSA1000 to that.  Each server will single zone. &lt;BR /&gt;&lt;BR /&gt;Basically create seperate zone for each Initiator (HBA). &lt;BR /&gt;&lt;BR /&gt;Hops this will clarify your confusion.</description>
      <pubDate>Fri, 02 Jan 2009 06:30:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330428#M35170</guid>
      <dc:creator>Dileep..</dc:creator>
      <dc:date>2009-01-02T06:30:38Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330429#M35171</link>
      <description>the server with 2 HBA is for fail over purpose. if 1 create 2 zone for both HBA , will it get problem for it ?</description>
      <pubDate>Fri, 02 Jan 2009 07:00:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330429#M35171</guid>
      <dc:creator>lim meng kiat</dc:creator>
      <dc:date>2009-01-02T07:00:54Z</dc:date>
    </item>
    <item>
      <title>Re: Zoning design</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330430#M35172</link>
      <description>Adding multiple HBA to single zone is not recommended. its the very basic zoning style by Operating System. &lt;BR /&gt;&lt;BR /&gt;You may create as below &lt;BR /&gt;&lt;BR /&gt;Serve1_HBA1,MSA1000    &amp;gt;&amp;gt; Zone1 &lt;BR /&gt;Serve1_HBA2,MSA1000    &amp;gt;&amp;gt; Zone2&lt;BR /&gt;&lt;BR /&gt;Serve2_HBA1,MSA1000    &amp;gt;&amp;gt; Zone3&lt;BR /&gt;Serve2_HBA2,MSA1000    &amp;gt;&amp;gt; Zone4&lt;BR /&gt;&lt;BR /&gt;Rgds</description>
      <pubDate>Fri, 02 Jan 2009 07:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/zoning-design/m-p/4330430#M35172</guid>
      <dc:creator>Dileep..</dc:creator>
      <dc:date>2009-01-02T07:58:42Z</dc:date>
    </item>
  </channel>
</rss>

