<?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 CPLD firmware update on composer2 in HPE Synergy</title>
    <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168877#M1043</link>
    <description>&lt;P&gt;Trying to get back dead composer2, which couldn't be powered on.&lt;/P&gt;&lt;P&gt;All the sympthoms are loking as described here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=a00121316en_us&amp;amp;docLocale=en_US" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=a00121316en_us&amp;amp;docLocale=en_US&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Current OneView version was 6.50, so i decided to update via OneView.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The appliance state displays "Not connected to standby", so i used the "Remove standby" option as suggested and then uploaded&amp;nbsp;HPE_Synergy_Composer2_CPLD_Firmware_Z7550-97383.bin&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Update was successful, but only on active composer. The other composer was not updated, even in activity log i can't see nothing about it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;At this moment, i have two composers, all of them has ip addresses, i can login at each of them thru ilo, but can't power on the second one. I even couldn't confirm it was updated to CPLD&amp;nbsp;&lt;SPAN&gt;version 0x12(A), because it has no power.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In the maintenance console i can only see the active composer, that is already updated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When i'm tryig to reach maintenance console of the second composer, putty, as expected, can't connect to it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Moreover, we have two independent synergy domains, in the second domain both two composers are dead. I planned to physically move those composers to the freame of the first domain and try to update and resore it there, but until i'm figured out how to proper restore standby composer in this domain, im' stuck.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any suggestions?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jun 2022 08:15:17 GMT</pubDate>
    <dc:creator>dehpe2022</dc:creator>
    <dc:date>2022-06-22T08:15:17Z</dc:date>
    <item>
      <title>CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168877#M1043</link>
      <description>&lt;P&gt;Trying to get back dead composer2, which couldn't be powered on.&lt;/P&gt;&lt;P&gt;All the sympthoms are loking as described here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=a00121316en_us&amp;amp;docLocale=en_US" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=a00121316en_us&amp;amp;docLocale=en_US&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Current OneView version was 6.50, so i decided to update via OneView.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The appliance state displays "Not connected to standby", so i used the "Remove standby" option as suggested and then uploaded&amp;nbsp;HPE_Synergy_Composer2_CPLD_Firmware_Z7550-97383.bin&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Update was successful, but only on active composer. The other composer was not updated, even in activity log i can't see nothing about it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;At this moment, i have two composers, all of them has ip addresses, i can login at each of them thru ilo, but can't power on the second one. I even couldn't confirm it was updated to CPLD&amp;nbsp;&lt;SPAN&gt;version 0x12(A), because it has no power.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In the maintenance console i can only see the active composer, that is already updated.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When i'm tryig to reach maintenance console of the second composer, putty, as expected, can't connect to it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Moreover, we have two independent synergy domains, in the second domain both two composers are dead. I planned to physically move those composers to the freame of the first domain and try to update and resore it there, but until i'm figured out how to proper restore standby composer in this domain, im' stuck.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any suggestions?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 08:15:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168877#M1043</guid>
      <dc:creator>dehpe2022</dc:creator>
      <dc:date>2022-06-22T08:15:17Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168879#M1044</link>
      <description>&lt;P&gt;Running the CPLD fix ( &lt;A href="https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_1d4a2ae5ea394f9ab843c724ca" target="_blank"&gt;https://support.hpe.com/hpesc/public/swd/detail?swItemId=MTX_1d4a2ae5ea394f9ab843c724ca&lt;/A&gt; ) on the Active Composer2 should reach out to all Composer2 iLO it can talk to in the ring and should have updated anyone that matches.&amp;nbsp; So moving the other two dead ones into the ring with the working active composer should also work.&lt;/P&gt;&lt;P&gt;The fix is supposed to RESET the dead composer2's iLO on the standby.&amp;nbsp;&amp;nbsp;After running again, I would reseat the formerly dead standby just in case it decides to come alive after the update (maybe the reset didn't work?)&lt;/P&gt;&lt;P&gt;Glad the active updated-- but if the standby did not, you'll need to engage support to figure out why.&amp;nbsp; It doesn't hurt to run it again.. ..and it's good that you verified you can login to the iLO.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 15:33:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168879#M1044</guid>
      <dc:creator>DanCernese</dc:creator>
      <dc:date>2022-06-21T15:33:25Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168903#M1046</link>
      <description>&lt;P&gt;After removing and installing back the second composer, i have the same results i.e. NOTHING. I suppose a consequence of the fact that it couldn't power on,&amp;nbsp;therefore its ILO was unable to detect actual CPLD version. Repeated update didn't help, saying 'already updated' for the first composer and even not mentioning the second one.&lt;/P&gt;&lt;P&gt;Comparing this issue with CPLD problem on the computing units itselves, i've tried to update CPLD through ILO. After some searching i've downloaded&amp;nbsp;firmware-synergy_composer2_cpld-12-1.1.x86_64.rpm and planned to use it, but..... Firmware update page is unavailable, saying somthing like insufficient rights. 'iloadm' user (created by me in OneView) doesn't have it. Besides my user i've got 'administrator' and '_OneViewAdmin' but i have no passwords for them.&lt;/P&gt;&lt;P&gt;Computing unit CPLD issue was resolved by resetting ILO, which, as i remember, helps with power-on and subsequently firmware update. But in my case i can't reset composer ilo due to insufficient rights. Anyway, after removing composer from slot and putting it back in, ilo was resetted, isn't it?&lt;/P&gt;&lt;P&gt;Or, alternatively, i've uploadeded .rpm and .compsig to repository, created custom SPP but how to apply SPP to composer? Is it possible?&lt;/P&gt;&lt;P&gt;At this moment i can't engage support, so i have to resolve this issue by myself, so i'm searching any ideas that would help&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 19:54:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168903#M1046</guid>
      <dc:creator>dehpe2022</dc:creator>
      <dc:date>2022-06-21T19:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168904#M1047</link>
      <description>&lt;P&gt;Try as you might, there is no alternative path.&amp;nbsp; Only the methods documented in the advisory will work.&amp;nbsp; There are no others.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 20:00:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168904#M1047</guid>
      <dc:creator>DanCernese</dc:creator>
      <dc:date>2022-06-21T20:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168906#M1048</link>
      <description>&lt;P&gt;OK, tomorrow i will try to remove dead composer from the second domain and put it in this system with operating appliance. Hope something changes and second composer will be updated&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 20:11:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168906#M1048</guid>
      <dc:creator>dehpe2022</dc:creator>
      <dc:date>2022-06-21T20:11:44Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168908#M1049</link>
      <description>&lt;P&gt;Don't forget there is also the local USB method &lt;STRONG&gt;if the maintenance console responds&lt;/STRONG&gt; and you can login.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 21:06:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168908#M1049</guid>
      <dc:creator>DanCernese</dc:creator>
      <dc:date>2022-06-21T21:06:55Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168984#M1050</link>
      <description>&lt;P&gt;Results of the day:&lt;/P&gt;&lt;P&gt;Another dead composer moved to this frame can't power on.&lt;/P&gt;&lt;P&gt;CPLD update through OneView didn't update this composer either.&lt;/P&gt;&lt;P&gt;Just for fun, i've placed two dead composers in second frame (working composer are situated in the first frame),&lt;/P&gt;&lt;P&gt;assigned completely new IP addresses for both of them and started update with&amp;nbsp;HPE_Synergy_Composer2_CPLD_Firmware_Z7550-97383.bin again. For the active composer it says 'already applied' for the rest two of them nothing jappens. Absolutely. As far as i remember, one of them flashed green by Power LED for half a minute, which i suppose was power cycling or ILO reset, and no sign of life again.&lt;/P&gt;&lt;P&gt;I suppose, the main problem is inability to power on to help ILO determine current version of CPLD firmware. Maybe because e-fuse is stuck in off position.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Next try will be resetting of e-fuse with oneview console, or clear composer NVRAM with dip switches inside it (but comparing with proliant, it has two block of switches and i'm not sure that the second 12-switch panel is the same as in DL servers)&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://s1.hostingkartinok.com/uploads/images/2022/06/626f32fd66ef3d80b528c7fbb42de25d.jpg" border="0" alt="appliance DIP switches" width="1600" height="900" /&gt;&lt;/P&gt;&lt;P&gt;BTW, all dead composers are still easily accessible via ILO&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 18:18:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168984#M1050</guid>
      <dc:creator>dehpe2022</dc:creator>
      <dc:date>2022-06-22T18:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168989#M1051</link>
      <description>&lt;P&gt;Do NOT play with the Composer's switches.&amp;nbsp; If you clear NVRAM, you will not be able to reimage them among other things.. ..and they may never boot again without support help.&amp;nbsp; [edit] It may even completely forget what kind of appliance it is.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 19:09:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168989#M1051</guid>
      <dc:creator>DanCernese</dc:creator>
      <dc:date>2022-06-22T19:09:05Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168990#M1052</link>
      <description>&lt;P&gt;Is there anything interesting in the log file found from&lt;/P&gt;&lt;P&gt;Settings &amp;gt; Appliance =&amp;gt; Actions =&amp;gt; Download fixme installation details&lt;/P&gt;&lt;P&gt;Can you download an AHS log from one of the dead composers, maybe the one that flashed the power LED?&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jun 2022 19:12:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7168990#M1052</guid>
      <dc:creator>DanCernese</dc:creator>
      <dc:date>2022-06-22T19:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: CPLD firmware update on composer2</title>
      <link>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7174247#M1111</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Any updates on this topic, it will be intereted for us, did you resolve the issue?&lt;BR /&gt;I've checked some shell scripts inside the firmware bin file, and seems that getting the current level of CPLD firmware is prerequisite in order to continue with main part of the upgrade process. Another prerequisites are getting ILO IP and credentials, but seems they are valid in your case.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2022 18:50:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/cpld-firmware-update-on-composer2/m-p/7174247#M1111</guid>
      <dc:creator>CSKA</dc:creator>
      <dc:date>2022-09-19T18:50:19Z</dc:date>
    </item>
  </channel>
</rss>

