<?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: Errors after swapping disk paths in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7239#M1582</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Changing the source path while the partner is down is supported. Not while a node is up but during takeover is on. If you change while online a a cp event occurs organ core dump since the label has the source port on it. But During a cf takeover the down node can be recabeled and should be checked in maintenance mode for paths. On giveback all supported since the change was offline on that node. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from my iPhone 4S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Jul 2012 14:45:41 GMT</pubDate>
    <dc:creator>scottgelb</dc:creator>
    <dc:date>2012-07-16T14:45:41Z</dc:date>
    <item>
      <title>Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7207#M1566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Recently we tracked down an issue where our MPHA for some of our shelves was not done per best practices (on a 3000 series, 0a &amp;amp; 0b, 0c &amp;amp; 0d share an ASIC and shouldn't be connected to the same stack).&amp;nbsp; After talking with support, we performed a takeover, and then on the down filer we swapped the cables for ports 0a and 0c.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the filer came back up, we noticed these errors (which are still persisting).&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. I see periodic messages saying "DBG: ses_incorporate_path(): Enclosure Logical Identifier Mismatch."&amp;nbsp; These are always in big clusters when they happen (12 messages or so).&lt;/P&gt;&lt;P&gt;2. If I run sysconfig -a now, I see the following at the end of some adapter lists:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Shelf 1: ESH4&amp;nbsp; Firmware rev. ESH A: 14&amp;nbsp; ESH B: 14&lt;/P&gt;&lt;P&gt;shelf: XX:XX:XX:XX:XX:XX:XX:XX channel 2b not found!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Shelf 2: ESH4&amp;nbsp; Firmware rev. ESH A: 14&amp;nbsp; ESH B: 14&lt;/P&gt;&lt;P&gt;shelf: XX:XX:XX:XX:XX:XX:XX:XX channel 2b not found!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Shelf 3: ESH4&amp;nbsp; Firmware rev. ESH A: 14&amp;nbsp; ESH B: 14&lt;/P&gt;&lt;P&gt;shelf: XX:XX:XX:XX:XX:XX:XX:XX channel 2b not found!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Shelf 4: ESH4&amp;nbsp; Firmware rev. ESH A: 14&amp;nbsp; ESH B: 14&lt;/P&gt;&lt;P&gt;shelf: XX:XX:XX:XX:XX:XX:XX:XX channel 2b not found!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Shelf 5: ESH4&amp;nbsp; Firmware rev. ESH A: 14&amp;nbsp; ESH B: 14&lt;/P&gt;&lt;P&gt;shelf: XX:XX:XX:XX:XX:XX:XX:XX channel 2b not found!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Shelf 6: ESH4&amp;nbsp; Firmware rev. ESH A: 14&amp;nbsp; ESH B: 14&lt;/P&gt;&lt;P&gt;shelf: XX:XX:XX:XX:XX:XX:XX:XX channel 2b not found!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can we correct this issue?&amp;nbsp; As far as I can tell, the disk pathing shown is correct (MPHA issue is good) and the data is still available.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:22:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7207#M1566</guid>
      <dc:creator>JCASON</dc:creator>
      <dc:date>2025-06-05T06:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7212#M1569</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;I have seen this when the MPHA paths go up and down the same path. Even though MPHA if you check cable paths, are the 2 paths up and down the same top of bottom modules?&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:23:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7212#M1569</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-07-16T14:23:41Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7216#M1571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Also supprt or your netapp NetApp or var se can run a config advisor (wiregauge) and check all pathing to confirm the issue. &lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:25:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7216#M1571</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-07-16T14:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7221#M1574</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the reply Scott.&amp;nbsp; I double checked and that isn't the case here.&amp;nbsp; We are Afiler_in-&amp;gt;Bfiler_out or vice versa in all cases.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:38:00 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7221#M1574</guid>
      <dc:creator>JCASON</dc:creator>
      <dc:date>2012-07-16T14:38:00Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7226#M1577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;last time i checked recabeling a mpha system online wasnt supported. if you do so, you need to properly reboot (or takeover/giveback) BOTH systems to properly clean up the disk inventory on both machines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;usualy we offline maschines to recable them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:39:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7226#M1577</guid>
      <dc:creator>thomas_glodde</dc:creator>
      <dc:date>2012-07-16T14:39:43Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7234#M1580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are any of the shelf to shelf cables crossed? Probably not but worth checking. If cabled ok it is likely a power cycle of the controller will fix it but support will help   Likely maintenance mode boot to check each node taken over.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from my iPhone 4S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:42:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7234#M1580</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-07-16T14:42:41Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7239#M1582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Changing the source path while the partner is down is supported. Not while a node is up but during takeover is on. If you change while online a a cp event occurs organ core dump since the label has the source port on it. But During a cf takeover the down node can be recabeled and should be checked in maintenance mode for paths. On giveback all supported since the change was offline on that node. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from my iPhone 4S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:45:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7239#M1582</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-07-16T14:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7247#M1583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&lt;P&gt;Darn autocorrect. Ha&lt;/P&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 14:47:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7247#M1583</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-07-16T14:47:45Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7250#M1585</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We resolved this, but were required to take the entire system down fully (both heads and all shelves) and bring them back up.&amp;nbsp; Support still claims that you can change pathing during takeover, but it didn't work for us.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 19:26:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7250#M1585</guid>
      <dc:creator>JCASON</dc:creator>
      <dc:date>2012-07-16T19:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: Errors after swapping disk paths</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7254#M1587</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen some weird anomalies that have only been cleared by a power cycle.. one recently where one path of mpha brought down both paths when connected to a ds14 fc loop... so one node wouldn't come up.&amp;nbsp; A power cycle of both nodes cleared it.&amp;nbsp; All cabling was correct.&amp;nbsp; 99% of the time all good but this is the 1% of frustration... seems a bit better with SAS technology now instead of FCAL on older shelves.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jul 2012 19:33:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Errors-after-swapping-disk-paths/m-p/7254#M1587</guid>
      <dc:creator>scottgelb</dc:creator>
      <dc:date>2012-07-16T19:33:46Z</dc:date>
    </item>
  </channel>
</rss>

