<?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: How to configure basic setup for Brocade 8GB/24C for HP chassis FC switch in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6050797#M63419</link>
    <description>&lt;P&gt;First, they are two &lt;U&gt;different&lt;/U&gt; fabrics (Lets call them "A" and "B"). Neither switch &lt;EM&gt;should&lt;/EM&gt; see each other and you do &lt;U&gt;not&lt;/U&gt; want them connected together. They provide high availability and you can work on one fabric (zone changes, firmware updates) &lt;EM&gt;without&lt;/EM&gt; disturbing the other.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Every device&amp;nbsp;'out there' (servers, storage) has a World Wide Name (&lt;STRONG&gt;WWN&lt;/STRONG&gt;) associated with it. A WWN is like an oversized MAC address. However, every device has at least &lt;EM&gt;two&lt;/EM&gt;: A node or &lt;U&gt;system&lt;/U&gt; WWN that refers to the entire device and one or more &lt;U&gt;port&lt;/U&gt; WWNs (&lt;STRONG&gt;pWWN&lt;/STRONG&gt;) that refer to a specific connector ON that device. A typical server Host Bus Adapter (HBA) has a WWN and a pWWN. HP storage arrays have a WWN and several pWWN depending on make and model.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In the switch's Zone Admin window, if you drill down (double-click) on a (device) WWN, you will see one or more pWWN's below. If you drill down on a pWWN, you may see a comment string set by the device's driver. If you drill down on a switch port, you will see a (device) WWN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: Regardless of how you get to it, the Best Practice is to zone with the port WWNs (pWWN).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You &lt;EM&gt;could&lt;/EM&gt; do all the zoning with the pWWN addresses. You could also browse on the Internet to 15.201.225.10 instead of hp.com, but &lt;U&gt;I&lt;/U&gt; wouldn't. :)&lt;BR /&gt;The switches have the ability to define an &lt;U&gt;ALIAS&lt;/U&gt; for each pWWN. No one wants to remember 64-bit hex numbers! You want this to be something humanly understandable and relatively self-documenting. For example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;SERVER2_SLOT3_A – HBA in PCI slot 3 on Server2 on fabric "A"&lt;/LI&gt;&lt;LI&gt;DATAWAREHOUSE02_SLOT1_A – HBA in PCI slot 1 on Data warehouse server 2 on fabric "A"&lt;/LI&gt;&lt;LI&gt;HQEVA01_CtrlA_FP2_B – FP2 of controller "A" on HQEVA01 on fabric "B"&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;As you go along, periodically remember to save the configuration. Watch the status messages at the bottom as the commit starts and ends.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once aliases are defined, we need a &lt;U&gt;ZONE&lt;/U&gt; for each allowed connection. Best Practice is One initiator (server), One target (storage device)! Again, you want this to be something humanly understandable and relatively self-documenting. Examples:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DATAWAREHOUSE02_HQEVA01_A – Zone from Datawarehouse02 to HQEVA01 on fabric "A". Consists of the aliases DATAWAREHOUSE02_SLOT1_A, HQEVA01_CtrlA_FP1_A, HQEVA01_CtrlB_FP1_A.&lt;/LI&gt;&lt;LI&gt;DATAWAREHOUSE02_TAPE02_B – Zone from Datawarehouse02 to Tape drive library 2 on fabric "B". Consists of the aliases DATAWAREHOUSE02_SLOT2_B and TAPE02_B.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;NOTE: An alias can&amp;nbsp;be in more than one zone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again, periodically remember to save the configuration.&lt;/P&gt;&lt;P&gt;Finally&amp;nbsp; you are ready to make a &lt;U&gt;ZONE CONFIG&lt;/U&gt;. This is a name like "Fabric_A". Add all your zones to it. Save the configuration and you're finally ready to ENABLE the configuration. Watch the status messages at the bottom!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: Once a zone configuration is enabled, only those devices within zones can 'talk' to the other devices within their zone. Any device &lt;EM&gt;not&lt;/EM&gt; in a zone is just out of luck.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now repeat the process on the other switch (Fabric_B). You should wind up with two configurations, Fabric A and B that are logically similar but with different pWWNs and minor changes in alias and zone names.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For a &lt;U&gt;lot&lt;/U&gt; more information, see the &lt;A target="_blank" href="http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&amp;amp;locale=en_US&amp;amp;docIndexId=179911&amp;amp;taskId=101&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=406734"&gt;HP SAN Design Reference Guide&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;-----------&lt;/P&gt;&lt;P&gt;If my post was useful, click on my KUDOS! "White Star" !&lt;/P&gt;</description>
    <pubDate>Fri, 03 May 2013 14:42:31 GMT</pubDate>
    <dc:creator>Sheldon Smith</dc:creator>
    <dc:date>2013-05-03T14:42:31Z</dc:date>
    <item>
      <title>How to configure basic setup for Brocade 8GB/24C for HP chassis FC switch</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6049439#M63412</link>
      <description>&lt;DIV&gt;&lt;P&gt;&lt;FONT size="2"&gt;Hi All,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;I am novice when it comes to setting up Brocade FC Switches, well any FC switches, so please excuse the silly questions.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;I have 2 x 8GB/24C Brocade FC switches for HP C7000 Chassis and need to configure them to connect to aHP FC SAN.&amp;nbsp; If anyone has a guide on how to set these 2 as a pair and document that shows how to complete a basic setup with zoning to a SAN and Blade connectivity I would be grateful.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;I have completed the following on both:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Upgraded the firmware to 7.1.0b&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Set correct date/time/timezone&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;SetIP config&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Set different Domain IDs&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;Set the same Fabric name&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;It seems that neither switch can see each other, so any help would be gre&lt;/FONT&gt;at&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 02 May 2013 15:08:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6049439#M63412</guid>
      <dc:creator>soulman</dc:creator>
      <dc:date>2013-05-02T15:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure basic setup for Brocade 8GB/24C for HP chassis FC switch</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6049637#M63415</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you really want the switches in the same fabric (most people do not want this) - you need to connect them with a cable.&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2013 18:30:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6049637#M63415</guid>
      <dc:creator>Johan Guldmyr</dc:creator>
      <dc:date>2013-05-02T18:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure basic setup for Brocade 8GB/24C for HP chassis FC switch</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6049677#M63416</link>
      <description>&lt;P&gt;It will be easier to manage if you set different domain IDs.&lt;BR /&gt;&lt;BR /&gt;Each switch will be a certain SAN, so the switches won't see each other.&lt;BR /&gt;&lt;BR /&gt;For basic zoning you will create aliases for the connected devices, create zones and put them all together in a current config.&lt;BR /&gt;&lt;BR /&gt;E.g. a zone consists of an initiator server HBA an a target storage port.&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2013 19:51:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6049677#M63416</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2013-05-02T19:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to configure basic setup for Brocade 8GB/24C for HP chassis FC switch</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6050797#M63419</link>
      <description>&lt;P&gt;First, they are two &lt;U&gt;different&lt;/U&gt; fabrics (Lets call them "A" and "B"). Neither switch &lt;EM&gt;should&lt;/EM&gt; see each other and you do &lt;U&gt;not&lt;/U&gt; want them connected together. They provide high availability and you can work on one fabric (zone changes, firmware updates) &lt;EM&gt;without&lt;/EM&gt; disturbing the other.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Every device&amp;nbsp;'out there' (servers, storage) has a World Wide Name (&lt;STRONG&gt;WWN&lt;/STRONG&gt;) associated with it. A WWN is like an oversized MAC address. However, every device has at least &lt;EM&gt;two&lt;/EM&gt;: A node or &lt;U&gt;system&lt;/U&gt; WWN that refers to the entire device and one or more &lt;U&gt;port&lt;/U&gt; WWNs (&lt;STRONG&gt;pWWN&lt;/STRONG&gt;) that refer to a specific connector ON that device. A typical server Host Bus Adapter (HBA) has a WWN and a pWWN. HP storage arrays have a WWN and several pWWN depending on make and model.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In the switch's Zone Admin window, if you drill down (double-click) on a (device) WWN, you will see one or more pWWN's below. If you drill down on a pWWN, you may see a comment string set by the device's driver. If you drill down on a switch port, you will see a (device) WWN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: Regardless of how you get to it, the Best Practice is to zone with the port WWNs (pWWN).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You &lt;EM&gt;could&lt;/EM&gt; do all the zoning with the pWWN addresses. You could also browse on the Internet to 15.201.225.10 instead of hp.com, but &lt;U&gt;I&lt;/U&gt; wouldn't. :)&lt;BR /&gt;The switches have the ability to define an &lt;U&gt;ALIAS&lt;/U&gt; for each pWWN. No one wants to remember 64-bit hex numbers! You want this to be something humanly understandable and relatively self-documenting. For example:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;SERVER2_SLOT3_A – HBA in PCI slot 3 on Server2 on fabric "A"&lt;/LI&gt;&lt;LI&gt;DATAWAREHOUSE02_SLOT1_A – HBA in PCI slot 1 on Data warehouse server 2 on fabric "A"&lt;/LI&gt;&lt;LI&gt;HQEVA01_CtrlA_FP2_B – FP2 of controller "A" on HQEVA01 on fabric "B"&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;As you go along, periodically remember to save the configuration. Watch the status messages at the bottom as the commit starts and ends.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once aliases are defined, we need a &lt;U&gt;ZONE&lt;/U&gt; for each allowed connection. Best Practice is One initiator (server), One target (storage device)! Again, you want this to be something humanly understandable and relatively self-documenting. Examples:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;DATAWAREHOUSE02_HQEVA01_A – Zone from Datawarehouse02 to HQEVA01 on fabric "A". Consists of the aliases DATAWAREHOUSE02_SLOT1_A, HQEVA01_CtrlA_FP1_A, HQEVA01_CtrlB_FP1_A.&lt;/LI&gt;&lt;LI&gt;DATAWAREHOUSE02_TAPE02_B – Zone from Datawarehouse02 to Tape drive library 2 on fabric "B". Consists of the aliases DATAWAREHOUSE02_SLOT2_B and TAPE02_B.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;NOTE: An alias can&amp;nbsp;be in more than one zone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again, periodically remember to save the configuration.&lt;/P&gt;&lt;P&gt;Finally&amp;nbsp; you are ready to make a &lt;U&gt;ZONE CONFIG&lt;/U&gt;. This is a name like "Fabric_A". Add all your zones to it. Save the configuration and you're finally ready to ENABLE the configuration. Watch the status messages at the bottom!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: Once a zone configuration is enabled, only those devices within zones can 'talk' to the other devices within their zone. Any device &lt;EM&gt;not&lt;/EM&gt; in a zone is just out of luck.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now repeat the process on the other switch (Fabric_B). You should wind up with two configurations, Fabric A and B that are logically similar but with different pWWNs and minor changes in alias and zone names.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For a &lt;U&gt;lot&lt;/U&gt; more information, see the &lt;A target="_blank" href="http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&amp;amp;locale=en_US&amp;amp;docIndexId=179911&amp;amp;taskId=101&amp;amp;prodTypeId=12169&amp;amp;prodSeriesId=406734"&gt;HP SAN Design Reference Guide&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;-----------&lt;/P&gt;&lt;P&gt;If my post was useful, click on my KUDOS! "White Star" !&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2013 14:42:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/how-to-configure-basic-setup-for-brocade-8gb-24c-for-hp-chassis/m-p/6050797#M63419</guid>
      <dc:creator>Sheldon Smith</dc:creator>
      <dc:date>2013-05-03T14:42:31Z</dc:date>
    </item>
  </channel>
</rss>

