<?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: Principal switch election in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442814#M10231</link>
    <description>Rene,&lt;BR /&gt;&lt;BR /&gt;The default behavor of the switches in the fabric is that the switch with the lowest WWN will become principal.&lt;BR /&gt;&lt;BR /&gt;Starting at FabricOS versions 4.1.0 and 3.1.0, a fabricPrincipal option was added to set a prefered Principal switch for the fabric.&lt;BR /&gt;&lt;BR /&gt;When this option is set, the switch with the lowest WWN of the switches that have the option set will become the principal.&lt;BR /&gt;&lt;BR /&gt;Note, when setting this option, a new principal is not elected until there is a fabric reconfiguration.  This usually happens when a switch joins or leaves the fabric.  (The switchDisable and switchEnable commands can cause this to happen as well as a switch reboot.)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Typically, it is not a problem that the Director is not the principal.&lt;BR /&gt;&lt;BR /&gt;If the director is a core switch in the SAN, then it might be preferable to have it as the principal.  This is especially true in a larger fabric with many edge switches.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Bill</description>
    <pubDate>Thu, 16 Dec 2004 10:01:13 GMT</pubDate>
    <dc:creator>Bill Rothanburg</dc:creator>
    <dc:date>2004-12-16T10:01:13Z</dc:date>
    <item>
      <title>Principal switch election</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442811#M10228</link>
      <description>We currently use a SAN that consists of 2 fabrics. In this SAN I am a the moment busy with replacing the current switches in both fabrics with a 2/128 Director switch and a 2/16 switch for each fabric.&lt;BR /&gt;&lt;BR /&gt;Some time ago I connected the 2 Directors to the existing fabrics so I can do the migration in phases. Both Directors are subordinate switches in the fabric, because the 1Gbit switches in the existing fabrics already were the principal.&lt;BR /&gt;&lt;BR /&gt;Before disabling the 1Gbit switch the configuration of each fabric was:&lt;BR /&gt;1 2/128 Director switch --&amp;gt; subordinate&lt;BR /&gt;1 2/16-EL switch        --&amp;gt; subordinate&lt;BR /&gt;1 2/16 switch           --&amp;gt; subordinate&lt;BR /&gt;1 1/16 switch           --&amp;gt; principal&lt;BR /&gt;&lt;BR /&gt;When I disabled the 1Gbit switch the Director did not become the principal, but the 2/16 switch became the principal. This is not what I expected, I assumed the Director would become the principal switch, because it is the largest switch in the fabric. &lt;BR /&gt;&lt;BR /&gt;How is the principal switch in a fabric being elected? I know it is normally the switch that is first turned on in the fabric, but how does it work in an existing fabric when the principal leaves the fabric?&lt;BR /&gt;&lt;BR /&gt;How can I force the 2/128 Director to be the principal switch? &lt;BR /&gt;&lt;BR /&gt;Is it a problem that the Director is not the principal?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Dec 2004 03:40:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442811#M10228</guid>
      <dc:creator>Rene Heeres</dc:creator>
      <dc:date>2004-12-14T03:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: Principal switch election</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442812#M10229</link>
      <description>Rene:&lt;BR /&gt;&lt;BR /&gt;"...but how does it work in an existing fabric when the principal leaves the fabric?"&lt;BR /&gt;&lt;BR /&gt;Can you show us a diagram of how your switches are interconnected to each other?  I think that the order would be the same as the boot order...  since the 1/16 was the principal and the 2/16 was possibly already in place with the 2/128 being added afterwards, the 2/16 would be "next in line".  I do not know if this is the case or if there is any logic behind the scenes that helps selects which becomes the principal.&lt;BR /&gt;&lt;BR /&gt;"How can I force the 2/128 Director to be the principal switch? "&lt;BR /&gt;&lt;BR /&gt;If you reboot both the 2/16 and the 2/16el, the director should become the principal.  Not the best way since you will disrupt production, but if done off hours....&lt;BR /&gt;&lt;BR /&gt;Another way would be to shutdown everything then reboot in a specific order... the 2/128 first, then the 2/18 then the 2/18el then your storage....then tape devices...then servers.&lt;BR /&gt;&lt;BR /&gt;"Is it a problem that the Director is not the principal?"&lt;BR /&gt;&lt;BR /&gt; I do not see a problem with any switch being subordinate or principal unless you WANT to see a particular switch as the principal. Some environments are like that. ;o)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Tue, 14 Dec 2004 09:56:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442812#M10229</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2004-12-14T09:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Principal switch election</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442813#M10230</link>
      <description>Steven, &lt;BR /&gt;&lt;BR /&gt;Thank you for your reply. I have included a sheet with the current configuration of one fabric (both are configured the same).&lt;BR /&gt;&lt;BR /&gt;Rebooting the other switches is not a good option because this would mean downtime for some servers connected to the fabric. We have a number of systems that have only one connection to the SAN, this is due to an explosive grow in servers connected to the SAN and a shortage of fiber uplinks to the Directors. This is also why we have placed a 2/16 switch in a rack with blade servers (switch12).&lt;BR /&gt;&lt;BR /&gt;I prefer the Directors being the principal switches in the fabric, because they are the Core switches in our SAN. Eventually they will become the principal anyway, but I am just wondering if it is possible to force them to become the principal.&lt;BR /&gt;&lt;BR /&gt;I'm interested in how the election of the principal switch in a fabric works, is there any information about that?</description>
      <pubDate>Tue, 14 Dec 2004 10:55:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442813#M10230</guid>
      <dc:creator>Rene Heeres</dc:creator>
      <dc:date>2004-12-14T10:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: Principal switch election</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442814#M10231</link>
      <description>Rene,&lt;BR /&gt;&lt;BR /&gt;The default behavor of the switches in the fabric is that the switch with the lowest WWN will become principal.&lt;BR /&gt;&lt;BR /&gt;Starting at FabricOS versions 4.1.0 and 3.1.0, a fabricPrincipal option was added to set a prefered Principal switch for the fabric.&lt;BR /&gt;&lt;BR /&gt;When this option is set, the switch with the lowest WWN of the switches that have the option set will become the principal.&lt;BR /&gt;&lt;BR /&gt;Note, when setting this option, a new principal is not elected until there is a fabric reconfiguration.  This usually happens when a switch joins or leaves the fabric.  (The switchDisable and switchEnable commands can cause this to happen as well as a switch reboot.)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Typically, it is not a problem that the Director is not the principal.&lt;BR /&gt;&lt;BR /&gt;If the director is a core switch in the SAN, then it might be preferable to have it as the principal.  This is especially true in a larger fabric with many edge switches.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Bill</description>
      <pubDate>Thu, 16 Dec 2004 10:01:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442814#M10231</guid>
      <dc:creator>Bill Rothanburg</dc:creator>
      <dc:date>2004-12-16T10:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: Principal switch election</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442815#M10232</link>
      <description>Bill, &lt;BR /&gt;&lt;BR /&gt;I checked the WWID's and the switch with the lowest WWID indeed is the principal!!&lt;BR /&gt;&lt;BR /&gt;I believe the correct name for the setting is: fabric.principalSwSelMode.  Can I modify this parameter on a running switch or do I have to disable the switch to change this parameter?</description>
      <pubDate>Fri, 17 Dec 2004 07:22:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/principal-switch-election/m-p/3442815#M10232</guid>
      <dc:creator>Rene Heeres</dc:creator>
      <dc:date>2004-12-17T07:22:57Z</dc:date>
    </item>
  </channel>
</rss>

