<?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 Synergy secure boot authentication alert in HPE Synergy</title>
    <link>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243549#M2318</link>
    <description>&lt;P&gt;This turned out to be a known issue that HPE support needed to clear down the 'locked' alert manually&lt;/P&gt;</description>
    <pubDate>Fri, 23 May 2025 07:59:56 GMT</pubDate>
    <dc:creator>jlangmead</dc:creator>
    <dc:date>2025-05-23T07:59:56Z</dc:date>
    <item>
      <title>HPE Synergy secure boot authentication alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243293#M2313</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I'm in the process of updating OneView on a pair of composer2's and have recieved a composer critical alert stating that "OneView detected a Secure Boot authentication failure on this appliance". I've seen this on previous updates and it's always cleared itself - however on this occasion it hasn't. The version of OneView the composer is currently running is 8.60.02.&lt;/P&gt;&lt;P&gt;Both the composers successfully completed the update and rejoined the cluster without error. They show up as fully synched and work ok. I tested a failover between the composers with completed without error.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My feeling is that this is a false alert and may clear over time - but I monitored it for two hours but it still remains. Has anyone seen this before?&lt;/P&gt;&lt;P&gt;I have logged a support call with HPE but thought I's post here also.&lt;/P&gt;&lt;P&gt;many thanks in advance&lt;/P&gt;&lt;P&gt;J&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 May 2025 00:21:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243293#M2313</guid>
      <dc:creator>jlangmead</dc:creator>
      <dc:date>2025-05-25T00:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: HPE Synergy secure boot authentication alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243532#M2317</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;1. Please select Remove standby from OneView -&amp;gt; Settings -&amp;gt; Appliance&amp;nbsp;, which factory resets composer.&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;2. remove and insert of composer&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P dir="auto" style="margin: 0;"&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 02:18:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243532#M2317</guid>
      <dc:creator>support_s</dc:creator>
      <dc:date>2025-05-23T02:18:24Z</dc:date>
    </item>
    <item>
      <title>Re: HPE Synergy secure boot authentication alert</title>
      <link>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243549#M2318</link>
      <description>&lt;P&gt;This turned out to be a known issue that HPE support needed to clear down the 'locked' alert manually&lt;/P&gt;</description>
      <pubDate>Fri, 23 May 2025 07:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-synergy/hpe-synergy-secure-boot-authentication-alert/m-p/7243549#M2318</guid>
      <dc:creator>jlangmead</dc:creator>
      <dc:date>2025-05-23T07:59:56Z</dc:date>
    </item>
  </channel>
</rss>

