<?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: Server Operational (6026) Message within each planned reboot in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558330#M39844</link>
    <description>And if that doesn't resolve it, something probably got cooked in the overheat (I'm assuming overheating as opposed to too cold).&lt;BR /&gt;&lt;BR /&gt;Overheats can be nasty.  I said in reponse to someone else's post I've seen servers survive 'em with no ill effects and I've had to completely replace servers after an overheat-triggered shutdown.  Depends on what (if anything) got cooked.</description>
    <pubDate>Wed, 06 Jan 2010 03:39:25 GMT</pubDate>
    <dc:creator>Ken Krubsack</dc:creator>
    <dc:date>2010-01-06T03:39:25Z</dc:date>
    <item>
      <title>Server Operational (6026) Message within each planned reboot</title>
      <link>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558328#M39842</link>
      <description>Hello!&lt;BR /&gt;One of our servers (DL 380G5) generates a message in the hp sim events log: "Server Operational (6026) - The server is operational again. The server has previously been shutdown due to a thermal anomaly on the server and has just become operational again.".&lt;BR /&gt;&lt;BR /&gt;We had a thermal shutdown weeks before, since this event we get this message after each reboot.&lt;BR /&gt;&lt;BR /&gt;All logs are cleared, Ilo2 was resetted. What else can we do?&lt;BR /&gt;&lt;BR /&gt;Thank you!&lt;BR /&gt;Kind regards,&lt;BR /&gt;Oliver</description>
      <pubDate>Tue, 05 Jan 2010 08:09:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558328#M39842</guid>
      <dc:creator>Gerspacher</dc:creator>
      <dc:date>2010-01-05T08:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: Server Operational (6026) Message within each planned reboot</title>
      <link>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558329#M39843</link>
      <description>I've had this with blades before after a thermal shutdown.  Only way to clear was to actually remove all power from the server.  See if that fixes it.</description>
      <pubDate>Tue, 05 Jan 2010 12:26:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558329#M39843</guid>
      <dc:creator>James Kennedy_4</dc:creator>
      <dc:date>2010-01-05T12:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: Server Operational (6026) Message within each planned reboot</title>
      <link>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558330#M39844</link>
      <description>And if that doesn't resolve it, something probably got cooked in the overheat (I'm assuming overheating as opposed to too cold).&lt;BR /&gt;&lt;BR /&gt;Overheats can be nasty.  I said in reponse to someone else's post I've seen servers survive 'em with no ill effects and I've had to completely replace servers after an overheat-triggered shutdown.  Depends on what (if anything) got cooked.</description>
      <pubDate>Wed, 06 Jan 2010 03:39:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558330#M39844</guid>
      <dc:creator>Ken Krubsack</dc:creator>
      <dc:date>2010-01-06T03:39:25Z</dc:date>
    </item>
    <item>
      <title>Re: Server Operational (6026) Message within each planned reboot</title>
      <link>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558331#M39845</link>
      <description>Hello!&lt;BR /&gt;&lt;BR /&gt;Sorry, but the shutdown of the server was not the solution. the server were unpolugged for about 1 minute, but we even get the error message 6026.&lt;BR /&gt;&lt;BR /&gt;I have also updated the insight agent to version 8.30, but noch success.&lt;BR /&gt;&lt;BR /&gt;Restarting the server always generates the message 6026!&lt;BR /&gt;&lt;BR /&gt;It is interesting, that the message does not appear in any of the server logs (IML, ilo), but it is shown in the hp sim console. So i think it must be a snmp trap send by the agent.&lt;BR /&gt;&lt;BR /&gt;Any other idea?&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Fri, 08 Jan 2010 09:00:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558331#M39845</guid>
      <dc:creator>Gerspacher</dc:creator>
      <dc:date>2010-01-08T09:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: Server Operational (6026) Message within each planned reboot</title>
      <link>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558332#M39846</link>
      <description>Hello once again!&lt;BR /&gt;&lt;BR /&gt;Updating the agent to version 8.30 was not the solution, but only at first look. Doing a reboot was the solution, after this reboot i got no more error messages.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help!&lt;BR /&gt;&lt;BR /&gt;kind regards,&lt;BR /&gt;Oliver&lt;BR /&gt;</description>
      <pubDate>Mon, 11 Jan 2010 09:35:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/server-operational-6026-message-within-each-planned-reboot/m-p/4558332#M39846</guid>
      <dc:creator>Gerspacher</dc:creator>
      <dc:date>2010-01-11T09:35:49Z</dc:date>
    </item>
  </channel>
</rss>

