<?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: HPE MSA 2040 SAN Disk Failure Notification in MSA Storage</title>
    <link>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7055851#M13009</link>
    <description>&lt;P&gt;DerrickAng ,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand.&amp;nbsp;&lt;BR /&gt;Please try MC restart and it should work.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;However , HPE advices to upgrade to the latest firmware as and when available.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We have 7 versions released after :&amp;nbsp;&lt;SPAN&gt;GL210R004&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Since , this array is on old firmware level. You might have to follow upgrade path to get to the latest version :&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;GL210R004 to&amp;nbsp;&amp;nbsp;GL220P010&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Link : GL220P010&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_1a23df52ec684b349672119f2f" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_1a23df52ec684b349672119f2f&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GL220P010 to GL225R003&lt;/P&gt;&lt;P&gt;Link : GL225R003&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_ae8ea19036ea4353b6b87800dc#tab-history" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_ae8ea19036ea4353b6b87800dc#tab-history&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GL225R003 to GL225P002-02&lt;/P&gt;&lt;P&gt;Link : GL225P002-02&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_963950744579459aae30fc9690#tab-history" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_963950744579459aae30fc9690#tab-history&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since we are on older version ,&amp;nbsp; I suggest performing this activity during low IOPS/ downtime.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I am an HPE Employee&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jul 2019 16:11:00 GMT</pubDate>
    <dc:creator>Navaneetha1</dc:creator>
    <dc:date>2019-07-19T16:11:00Z</dc:date>
    <item>
      <title>HPE MSA 2040 SAN Disk Failure Notification</title>
      <link>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7055767#M13006</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi. Recently there is a disk failure but NMS did not pick it up.&amp;nbsp; Running on version GL210R004. Upgrade to current version is able to address the problem? Thanks.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 02:52:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7055767#M13006</guid>
      <dc:creator>DerrickAng</dc:creator>
      <dc:date>2019-07-19T02:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: HPE MSA 2040 SAN Disk Failure Notification</title>
      <link>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7055851#M13009</link>
      <description>&lt;P&gt;DerrickAng ,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand.&amp;nbsp;&lt;BR /&gt;Please try MC restart and it should work.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;However , HPE advices to upgrade to the latest firmware as and when available.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We have 7 versions released after :&amp;nbsp;&lt;SPAN&gt;GL210R004&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Since , this array is on old firmware level. You might have to follow upgrade path to get to the latest version :&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;GL210R004 to&amp;nbsp;&amp;nbsp;GL220P010&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Link : GL220P010&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_1a23df52ec684b349672119f2f" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_1a23df52ec684b349672119f2f&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GL220P010 to GL225R003&lt;/P&gt;&lt;P&gt;Link : GL225R003&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_ae8ea19036ea4353b6b87800dc#tab-history" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_ae8ea19036ea4353b6b87800dc#tab-history&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;GL225R003 to GL225P002-02&lt;/P&gt;&lt;P&gt;Link : GL225P002-02&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_963950744579459aae30fc9690#tab-history" target="_blank"&gt;https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_963950744579459aae30fc9690#tab-history&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Since we are on older version ,&amp;nbsp; I suggest performing this activity during low IOPS/ downtime.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;I am an HPE Employee&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2019 16:11:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7055851#M13009</guid>
      <dc:creator>Navaneetha1</dc:creator>
      <dc:date>2019-07-19T16:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: HPE MSA 2040 SAN Disk Failure Notification</title>
      <link>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7056107#M13015</link>
      <description>&lt;P&gt;Thank you. By the way, notification alert priotity should not be critical but fall under error for disk failure? Can I check operation will not be very much affected during upgrade when doing it in production?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 01:10:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7056107#M13015</guid>
      <dc:creator>DerrickAng</dc:creator>
      <dc:date>2019-07-23T01:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: HPE MSA 2040 SAN Disk Failure Notification</title>
      <link>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7056127#M13016</link>
      <description>&lt;P&gt;There is one known issue I remember regarding drive failure but not getting detected as an alert but this issue was fixed in GL220R005&lt;/P&gt;&lt;P&gt;"&lt;SPAN&gt;Event 8 Unknown Reason Drive failure does not create 314 event.&lt;/SPAN&gt;"&lt;/P&gt;&lt;P&gt;You can search the below link with the above content,&lt;/P&gt;&lt;P&gt;&lt;A href="https://downloads.hpe.com/pub/softlib2/software1/pubsw-linux/p1158764188/v119515/764118-404_RN_MSA_GL220.html" target="_blank"&gt;https://downloads.hpe.com/pub/softlib2/software1/pubsw-linux/p1158764188/v119515/764118-404_RN_MSA_GL220.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;So yes it's always recommended to keep the system up to date in terms of firmware for all components of the system.&lt;/P&gt;&lt;P&gt;Coming to other query, I always recommend to do the firmware update in off-pick hours or in maintenance window in order to avaoid any unknown situation. Theoritically it's possible to do the firmware update anytime but in your case as system is running with old firmware so it's always suggested to do the firmware update in maintenance window. You should also check if you have other drive enclosure attached and any IO module needs update. Also you should check if drive require update as well. So all can be done together in single maintenance window.&lt;/P&gt;&lt;P&gt;Keep in mind that you need to fix the failed hardware issue first and then only you should go for firmware update.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;BR /&gt;Regards&lt;BR /&gt;&lt;FONT color="#0000FF"&gt;&lt;STRONG&gt;Subhajit&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I am an HPE employee&lt;/P&gt;&lt;P&gt;If you feel this was helpful please click the &lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;KUDOS!&lt;/STRONG&gt;&lt;/FONT&gt; thumb below!&lt;/P&gt;&lt;P&gt;***************************************************************************&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 07:00:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7056127#M13016</guid>
      <dc:creator>SUBHAJIT KHANBARMAN_1</dc:creator>
      <dc:date>2019-07-23T07:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: HPE MSA 2040 SAN Disk Failure Notification</title>
      <link>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7056183#M13017</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;There was more than one error message reporting issue fixed between GL200 and GL225. As mentioned previously, you will have to hop the array from GL200 -&amp;gt; GL220 -&amp;gt; GL225. You can perform upgrades while online but as a recommendation you should try to do this during a period of low host I/O.&lt;/P&gt;&lt;P&gt;It is recommended to set your alerts (email and/or) SNMP to a WARNING level. This allows you to be reactive to issues that are happening rather than react to a failure. WARNING level alerts you to possible issues before they become a failure.&lt;/P&gt;&lt;P&gt;Cheers,&lt;BR /&gt;Shawn&lt;/P&gt;&lt;P&gt;I work for Hewlett Packard Enterprise. The comments in this post are my own and do not represent an official reply from HPE. No warranty or guarantees of any kind are expressed in my reply.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 14:30:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/msa-storage/hpe-msa-2040-san-disk-failure-notification/m-p/7056183#M13017</guid>
      <dc:creator>Shawn_K</dc:creator>
      <dc:date>2019-07-23T14:30:00Z</dc:date>
    </item>
  </channel>
</rss>

