<?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: SAN Switch replacement in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864177#M3563</link>
    <description>Is this switch in a fabric? Is it redundant? If you added the switch to the fabric, you could add a new port alias to the zone and move the cable. There would be minimal downtime for the host. Later remove the old port. etc etc.</description>
    <pubDate>Thu, 08 Nov 2007 08:36:42 GMT</pubDate>
    <dc:creator>James Muell</dc:creator>
    <dc:date>2007-11-08T08:36:42Z</dc:date>
    <item>
      <title>SAN Switch replacement</title>
      <link>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864175#M3561</link>
      <description>Hi&lt;BR /&gt;
I need to replace a B series SAN Switch 4/16 with a B series SAN switch 4/64. While researching the use of uploading and downloading config files I discovered a recommendation not to use config files from different models of switches. Would anyone know of any documentation or whitpapers detailing the best procedure to perform this migration.&lt;BR /&gt;
&lt;BR /&gt;
tia&lt;BR /&gt;
&lt;BR /&gt;
Ian</description>
      <pubDate>Wed, 07 Nov 2007 03:53:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864175#M3561</guid>
      <dc:creator>Icoaty</dc:creator>
      <dc:date>2007-11-07T03:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: SAN Switch replacement</title>
      <link>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864176#M3562</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;How much do you have configured on the switch? is it mainly zoneing stuff you want to bring across?&lt;BR /&gt;&lt;BR /&gt;I take it your're also trying to keep downtime to a minimum.&lt;BR /&gt;&lt;BR /&gt;I can think of a couple of ways you can get around this:&lt;BR /&gt;&lt;BR /&gt;Export the config from the old and the new switches - then copy the parts that you want to bring across into the exported config from the new switch (i'd make a copy first) and re-import it.&lt;BR /&gt;&lt;BR /&gt;OR&lt;BR /&gt;&lt;BR /&gt;Depending on your licences on the switches, connect the new switch to your existing fabric. You should then be able to setup the Zone's and/or have them migrate into this switch. Save the config and then swap in the new switch.</description>
      <pubDate>Thu, 08 Nov 2007 05:06:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864176#M3562</guid>
      <dc:creator>Chris Rosan</dc:creator>
      <dc:date>2007-11-08T05:06:05Z</dc:date>
    </item>
    <item>
      <title>Re: SAN Switch replacement</title>
      <link>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864177#M3563</link>
      <description>Is this switch in a fabric? Is it redundant? If you added the switch to the fabric, you could add a new port alias to the zone and move the cable. There would be minimal downtime for the host. Later remove the old port. etc etc.</description>
      <pubDate>Thu, 08 Nov 2007 08:36:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/san-switch-replacement/m-p/864177#M3563</guid>
      <dc:creator>James Muell</dc:creator>
      <dc:date>2007-11-08T08:36:42Z</dc:date>
    </item>
  </channel>
</rss>

