<?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: Firmware upgrade procedure in Server Clustering</title>
    <link>https://community.hpe.com/t5/server-clustering/firmware-upgrade-procedure/m-p/6949974#M661</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;What is the CMU version ?&lt;/P&gt;&lt;P&gt;Since other firmware versions applied correctly wiith CMU, i think that there is no issue with the way CMU upgrade the firmware. Regarding the ouput of the disk firmware ouput, CMU will directly display the o/p from the update process of firmware component.&lt;/P&gt;&lt;P&gt;Please try to update the disk firmware on that node manually, by installing the rpm. CMU will&amp;nbsp;unpack the rpm and the firmware executable is copied to the selected nodes and executed in parallel&lt;/P&gt;&lt;P&gt;For more information please refer section "Installing and upgrading firmware" in the HPE Insight CMU user guide.&lt;/P&gt;&lt;P&gt;Also, is it a customer cluster ? If yes please let us know the details and also raise an issue with HPE local support center.&lt;/P&gt;</description>
    <pubDate>Tue, 21 Mar 2017 12:34:34 GMT</pubDate>
    <dc:creator>Abhishekc</dc:creator>
    <dc:date>2017-03-21T12:34:34Z</dc:date>
    <item>
      <title>Firmware upgrade procedure</title>
      <link>https://community.hpe.com/t5/server-clustering/firmware-upgrade-procedure/m-p/6949565#M660</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to optimize our firmware update routines and have stumbled into an issue (and a bug).&lt;/P&gt;&lt;P&gt;We have traditionally updated firmware on our cluster nodes by booting them with the Service Pack ISOs, and let the system find the updates needed. This works fine but is quite cumbersome (and slow) to do on many nodes.&lt;/P&gt;&lt;P&gt;Therefore we would like to use CMU instead.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;So I upgraded a single node using the old method, noting the RPMs needed&lt;/LI&gt;&lt;LI&gt;Copy the RPMs to /opt/cmu/firmware/&lt;/LI&gt;&lt;LI&gt;Select node(s) and RPM, and initiate firmware upgrade.&lt;/LI&gt;&lt;LI&gt;Repeat 3 for remaining RPMs&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;This worked fine until I reached the disk firmware&amp;nbsp;upgrade (hp-firmware-hdd-a08f92a4f9-HPGE-1.1.x86_64.rpm), which failed with (from /var/cpq/Component.log):&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;Device Drive 9XF3T2P0 (Generic HBA C610/X99 series chipset 6-Port SATA Controller [AHCI mode] in Slot ATTR_VALUE_SLOT_UNKNOWN) will not be updated because it does not support deferred or immediate flashing online&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The message from CMU was a bit simpler (and essentially wrong):&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;============ Summary ============&lt;BR /&gt;Smart Component Finished&lt;/P&gt;&lt;P&gt;Summary Messages&lt;BR /&gt;================&lt;BR /&gt;Smart Component opted to not flash 1 device&lt;BR /&gt;See log at /var/cpq/Component.log for details&lt;/P&gt;&lt;P&gt;Exit Status: 3&lt;BR /&gt;Update not attempted. All selected devices are either up-to-date or have newer versions installed.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Return code: 3&lt;/P&gt;&lt;P&gt;Installation complete: man mar 20 13:42:58 CET 2017&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;From the ISO update I know that the new firmware is newer (see attached image) and working. So my best guess is that it's not possible to update the disk firmware using CMU?&lt;/P&gt;&lt;P&gt;Can this really be the case, because that would lead me to upgrade the disk firmware in the old way (which can update all firmware automatically at the same time, which I really can't imagine (or trying not to) on a huge cluster with 100s or 1000s of nodes?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Brian Højen-Sørensen&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 11:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/firmware-upgrade-procedure/m-p/6949565#M660</guid>
      <dc:creator>brs</dc:creator>
      <dc:date>2017-03-21T11:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware upgrade procedure</title>
      <link>https://community.hpe.com/t5/server-clustering/firmware-upgrade-procedure/m-p/6949974#M661</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;What is the CMU version ?&lt;/P&gt;&lt;P&gt;Since other firmware versions applied correctly wiith CMU, i think that there is no issue with the way CMU upgrade the firmware. Regarding the ouput of the disk firmware ouput, CMU will directly display the o/p from the update process of firmware component.&lt;/P&gt;&lt;P&gt;Please try to update the disk firmware on that node manually, by installing the rpm. CMU will&amp;nbsp;unpack the rpm and the firmware executable is copied to the selected nodes and executed in parallel&lt;/P&gt;&lt;P&gt;For more information please refer section "Installing and upgrading firmware" in the HPE Insight CMU user guide.&lt;/P&gt;&lt;P&gt;Also, is it a customer cluster ? If yes please let us know the details and also raise an issue with HPE local support center.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Mar 2017 12:34:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/firmware-upgrade-procedure/m-p/6949974#M661</guid>
      <dc:creator>Abhishekc</dc:creator>
      <dc:date>2017-03-21T12:34:34Z</dc:date>
    </item>
  </channel>
</rss>

