<?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 Confirmation on possable PID issue. in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930217#M23663</link>
    <description>Hello&lt;BR /&gt;&lt;BR /&gt;If i add a new switch to an existing Fabric with a differnent PID no - existing PID 0 , new PID 1 - will it cause the fabric to segment and disconnect servers from storage units ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
    <pubDate>Mon, 22 Jan 2007 07:07:07 GMT</pubDate>
    <dc:creator>Dave Thomson</dc:creator>
    <dc:date>2007-01-22T07:07:07Z</dc:date>
    <item>
      <title>Confirmation on possable PID issue.</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930217#M23663</link>
      <description>Hello&lt;BR /&gt;&lt;BR /&gt;If i add a new switch to an existing Fabric with a differnent PID no - existing PID 0 , new PID 1 - will it cause the fabric to segment and disconnect servers from storage units ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 22 Jan 2007 07:07:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930217#M23663</guid>
      <dc:creator>Dave Thomson</dc:creator>
      <dc:date>2007-01-22T07:07:07Z</dc:date>
    </item>
    <item>
      <title>Re: Confirmation on possable PID issue.</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930218#M23664</link>
      <description>The new switch will not join the existing fabric.</description>
      <pubDate>Mon, 22 Jan 2007 08:04:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930218#M23664</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-01-22T08:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: Confirmation on possable PID issue.</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930219#M23665</link>
      <description>Thanks Ewu, but would it cause the existing fabric to disconnect current servers from storage.&lt;BR /&gt;&lt;BR /&gt;I connected a switch to my fabric - different PID. I only expected it to not join to the fabric. But i had servers disconnecting from the storage devices. Device ID's have been set accordingly.&lt;BR /&gt;&lt;BR /&gt;Would the differnt PID do this, or might i have another issue. I cannot retest it with a new PID. New switches are PID1,2 Current fabric is PID 0. I have to first change the current fabric to 1, this will take 3 weeks.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 22 Jan 2007 08:16:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930219#M23665</guid>
      <dc:creator>Dave Thomson</dc:creator>
      <dc:date>2007-01-22T08:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: Confirmation on possable PID issue.</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930220#M23666</link>
      <description>Just to make sure:&lt;BR /&gt;we are talking about the "Core-PID" setting, right?&lt;BR /&gt;&lt;BR /&gt;I have never tried it out myself, but from reading the documentation, value 2 should be compatible with value 0. It makes sure that the   area byte wraps around on switches with many ports.</description>
      <pubDate>Mon, 22 Jan 2007 14:07:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930220#M23666</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2007-01-22T14:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: Confirmation on possable PID issue.</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930221#M23667</link>
      <description>a switch with a pid of 0 won't communicate with a switch with a PID of 1.  The PID 1 will segment itself.  I went thru this same issue about 18months ago when we were adding directors to our fabric and had Brocade 2800 switches in our fabric.  First had to go to a PID of 2 (kind of an interop).  Brocade has a script on their website that will change the PID format on multiple switches at once to ease the downtime.</description>
      <pubDate>Tue, 23 Jan 2007 08:51:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930221#M23667</guid>
      <dc:creator>Jim Paulsen</dc:creator>
      <dc:date>2007-01-23T08:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: Confirmation on possable PID issue.</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930222#M23668</link>
      <description>Thanks.&lt;BR /&gt;&lt;BR /&gt;We are replacing 2 Brocade 2800's with new switchs. It makes more sence to change the current PID on the remaing switches to 1 instead of 0 so we dont have this issue again.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;</description>
      <pubDate>Wed, 24 Jan 2007 01:33:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/confirmation-on-possable-pid-issue/m-p/3930222#M23668</guid>
      <dc:creator>Dave Thomson</dc:creator>
      <dc:date>2007-01-24T01:33:23Z</dc:date>
    </item>
  </channel>
</rss>

