<?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: Powering down a failed controller in ONTAP Hardware</title>
    <link>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148326#M9459</link>
    <description>What is the reason to power it off? It is not required for replacement. I am not sure what "safe" means in this case. It should not affect another node in the same chassis if that was the question.</description>
    <pubDate>Wed, 08 May 2019 10:50:53 GMT</pubDate>
    <dc:creator>aborzenkov</dc:creator>
    <dc:date>2019-05-08T10:50:53Z</dc:date>
    <item>
      <title>Powering down a failed controller</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148325#M9458</link>
      <description>&lt;P&gt;Hello all!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have a V6220 single-chassis dual-controller filer (controllers are named Filer-A and Filer-B). Some time ago Filer-A had a hardware failure (maybe voltage regulators but I'm not 100% sure), was taken over by Filer-B, rebooted by watchdog, but didn't came up. Now it's in zombie state, dead by fact but still powered on. Whole system works through alive Filer-B.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is it safe to issue "system power off" command from Filer-A Service Processor CLI? Sorry for such a stupid question, but I'm not an expert in storage and we have a very mission-critical database on this system.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 12:34:05 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148325#M9458</guid>
      <dc:creator>strider78</dc:creator>
      <dc:date>2025-06-04T12:34:05Z</dc:date>
    </item>
    <item>
      <title>Re: Powering down a failed controller</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148326#M9459</link>
      <description>What is the reason to power it off? It is not required for replacement. I am not sure what "safe" means in this case. It should not affect another node in the same chassis if that was the question.</description>
      <pubDate>Wed, 08 May 2019 10:50:53 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148326#M9459</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2019-05-08T10:50:53Z</dc:date>
    </item>
    <item>
      <title>Re: Powering down a failed controller</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148327#M9460</link>
      <description>&lt;P&gt;The reason is simple, it's a last resort, I hope that power cycle may heal it. Yes, I wanted to make sure that powering it off won't harm a working filer. Thank you very much for an answer.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 11:05:54 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148327#M9460</guid>
      <dc:creator>strider78</dc:creator>
      <dc:date>2019-05-08T11:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: Powering down a failed controller</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148331#M9461</link>
      <description>&lt;P&gt;HEllo,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think your system is in Wauting for give back or maybe&amp;nbsp;@loader prompt&lt;/P&gt;
&lt;P&gt;Can you type before :&lt;/P&gt;
&lt;P&gt;system console&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And check the state of your controler&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anf on your survival controler, wath is the result of&lt;/P&gt;
&lt;P&gt;cf status&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 12:12:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148331#M9461</guid>
      <dc:creator>cedric_renauld</dc:creator>
      <dc:date>2019-05-08T12:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: Powering down a failed controller</title>
      <link>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148352#M9463</link>
      <description>&lt;P&gt;Filer-A was dead completely, "system console" showed nothing, "cf status" on a survived Filer-B showed only that it has taken over a partner. Interconnect link was down too.&lt;/P&gt;
&lt;P&gt;Then I issued "system power off" on a dead filer's SP. Powered it on after 5 minutes.&lt;/P&gt;
&lt;P&gt;Bingo!&lt;/P&gt;
&lt;P&gt;All hardware (voltage) issues were auto-deasserted, ONTAP booted normally and now is ready for a giveback.&lt;/P&gt;
&lt;P&gt;Now I'm sure that my system was hit by a 500 days uptime bug. Upgraded my SP's firmware to latest compatible version.&lt;/P&gt;
&lt;P&gt;Thanks all for help.&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 17:42:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Hardware/Powering-down-a-failed-controller/m-p/148352#M9463</guid>
      <dc:creator>strider78</dc:creator>
      <dc:date>2019-05-08T17:42:56Z</dc:date>
    </item>
  </channel>
</rss>

