<?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: storage takeover in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455564#M10079</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can get the event log from that day and check if there is any information about the reboot.&lt;/P&gt;</description>
    <pubDate>Wed, 02 Oct 2024 06:36:08 GMT</pubDate>
    <dc:creator>Gmox</dc:creator>
    <dc:date>2024-10-02T06:36:08Z</dc:date>
    <item>
      <title>storage takeover</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455457#M10073</link>
      <description>&lt;P&gt;When I used node show to check the storage, I found that the "uptime" of a node was 67 days, because the auto-giveback of this storage was on, which means that this storage was taken over, restarted and returned 67 days ago.&lt;BR /&gt;No alarm related to him is found in the EMERGENCY,ALERT,ERROR file currently stored&lt;BR /&gt;What can I do to find out what went wrong on the day of storage?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2024 16:04:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455457#M10073</guid>
      <dc:creator>weiliu</dc:creator>
      <dc:date>2024-09-27T16:04:12Z</dc:date>
    </item>
    <item>
      <title>Re: storage takeover</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455564#M10079</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can get the event log from that day and check if there is any information about the reboot.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2024 06:36:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455564#M10079</guid>
      <dc:creator>Gmox</dc:creator>
      <dc:date>2024-10-02T06:36:08Z</dc:date>
    </item>
    <item>
      <title>Re: storage takeover</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455582#M10083</link>
      <description>&lt;P&gt;Hello Weiliu,&lt;BR /&gt;&lt;BR /&gt;Gmox is right, you need to download the SP/BMC logs from your cluster and manually check the events logs&lt;BR /&gt;(IPMI).&lt;BR /&gt;&lt;BR /&gt;Depending on your platform you will need to run different commands. Please check the below KBs&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_logs_to_collect_for_a_down_system_with_a_Service_Processor" target="_blank"&gt;https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_logs_to_collect_for_a_down_system_with_a_Service_Processor&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_logs_to_collect_for_a_down_system_with_a_BMC" target="_blank"&gt;https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/What_logs_to_collect_for_a_down_system_with_a_BMC&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If there was a reboot, it will certainly be there.&lt;BR /&gt;It will also give clubs on the RCA root cause&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Oct 2024 06:19:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/storage-takeover/m-p/455582#M10083</guid>
      <dc:creator>darr613</dc:creator>
      <dc:date>2024-10-03T06:19:31Z</dc:date>
    </item>
  </channel>
</rss>

