<?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: fabric segemented: incompatibility in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507037#M40648</link>
    <description>Fixed it by changing the PID to 1, to match the existing 4/16 switch.</description>
    <pubDate>Fri, 02 Oct 2009 17:49:39 GMT</pubDate>
    <dc:creator>JeffWardlaw</dc:creator>
    <dc:date>2009-10-02T17:49:39Z</dc:date>
    <item>
      <title>fabric segemented: incompatibility</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507035#M40646</link>
      <description>I'm trying to connect an older 2/8 switch to our existing 4/16. However, I get an error: :port 9, incompatible flow control parameters".&lt;BR /&gt;&lt;BR /&gt;I've opened up a case with HP, but not ecstatic with the vagueness of the replies I'm getting.&lt;BR /&gt;&lt;BR /&gt;I've tried this in multiple ports on the 2/8 switch, and get the same error.&lt;BR /&gt;&lt;BR /&gt;One of the things I've come across is that this may be cause by having different domain ids on the switches. However, all 4 of my existing switches in my two fabrics have different DIDs: 1-4. I've manually set the 2/8 to domain id 5.&lt;BR /&gt;&lt;BR /&gt;Question: Are the switches in a fabric supposed to share a single domain id?&lt;BR /&gt;&lt;BR /&gt;Any other hints?&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;Jeff</description>
      <pubDate>Fri, 02 Oct 2009 13:57:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507035#M40646</guid>
      <dc:creator>JeffWardlaw</dc:creator>
      <dc:date>2009-10-02T13:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: fabric segemented: incompatibility</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507036#M40647</link>
      <description>Hi Jeff,&lt;BR /&gt;&lt;BR /&gt;No.  All switches in a fabric must have a different domain ID...&lt;BR /&gt;&lt;BR /&gt;Have you tried fixing the port speed on both switches to match ?&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;&lt;BR /&gt;Rob</description>
      <pubDate>Fri, 02 Oct 2009 17:08:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507036#M40647</guid>
      <dc:creator>Rob Leadbeater</dc:creator>
      <dc:date>2009-10-02T17:08:43Z</dc:date>
    </item>
    <item>
      <title>Re: fabric segemented: incompatibility</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507037#M40648</link>
      <description>Fixed it by changing the PID to 1, to match the existing 4/16 switch.</description>
      <pubDate>Fri, 02 Oct 2009 17:49:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/fabric-segemented-incompatibility/m-p/4507037#M40648</guid>
      <dc:creator>JeffWardlaw</dc:creator>
      <dc:date>2009-10-02T17:49:39Z</dc:date>
    </item>
  </channel>
</rss>

