<?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 Thermal Status Degraded - warning email in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169166#M51228</link>
    <description>We received a warning e-mail from SIM (v5.2) regarding a thermal status degradation on a server (as a result of an A/C failure).&lt;BR /&gt;&lt;BR /&gt;Is there anyway to make the e-mail display what the recorded temperature was along with the threshold it exceeded?</description>
    <pubDate>Sun, 12 Apr 2009 13:03:48 GMT</pubDate>
    <dc:creator>Nat Sacks</dc:creator>
    <dc:date>2009-04-12T13:03:48Z</dc:date>
    <item>
      <title>Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169166#M51228</link>
      <description>We received a warning e-mail from SIM (v5.2) regarding a thermal status degradation on a server (as a result of an A/C failure).&lt;BR /&gt;&lt;BR /&gt;Is there anyway to make the e-mail display what the recorded temperature was along with the threshold it exceeded?</description>
      <pubDate>Sun, 12 Apr 2009 13:03:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169166#M51228</guid>
      <dc:creator>Nat Sacks</dc:creator>
      <dc:date>2009-04-12T13:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169167#M51229</link>
      <description>That would be meaningless.  The important datum is that it was exceeded.</description>
      <pubDate>Sun, 12 Apr 2009 15:07:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169167#M51229</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2009-04-12T15:07:56Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169168#M51230</link>
      <description>Due respect David, that isn't a valid answer to my question. ;)&lt;BR /&gt;&lt;BR /&gt;As it goes, it is not meaningless.  the level of the threshold breach might determine a course of corrective action.</description>
      <pubDate>Sun, 12 Apr 2009 15:25:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169168#M51230</guid>
      <dc:creator>Nat Sacks</dc:creator>
      <dc:date>2009-04-12T15:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169169#M51231</link>
      <description>There are from 3 to 32 sensors for temperature in ProLiant servers, all with individually set thresholds based on model and the component being protected.  Depending on the model of server and the sensor tripped, you could have results anywhere from 30C to 105C.  The value itself is meaningless, only the fact that it tripped.</description>
      <pubDate>Sun, 12 Apr 2009 20:03:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169169#M51231</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2009-04-12T20:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169170#M51232</link>
      <description>David&lt;BR /&gt;I understand that there are many sensors that provide temperature readings.  However, knowing the extent of the breach might affect how my team choose to react and, based on a recent experience I therefore deem these alerts to be meaningful.&lt;BR /&gt;&lt;BR /&gt;All I wish to know is if it is possible to change the content of the alert e-mail to include which threshold was breached and to what extent?&lt;BR /&gt;&lt;BR /&gt;I appreciate that you've taken the time to reply but you haven't provided me with an answer to my question.</description>
      <pubDate>Mon, 13 Apr 2009 05:43:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169170#M51232</guid>
      <dc:creator>Nat Sacks</dc:creator>
      <dc:date>2009-04-13T05:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169171#M51233</link>
      <description>That implies that you could infer something from that data, and you can't.  The event should trigger one action:  investigate.  The only other thing that possibly could help would be this event in conjunction with another event--such as fan failure, and then you would know the problem is in the system.  If you were to receive thermal degraded from multiple systems, that might tell you where to investigate--from multiple systems in a rack, maybe a row airflow problem, insufficient airflow in the rack door, or wraparound air.  From systems throughout the computer room--check the environment.  Regardless, the event should tell you to investigate.&lt;BR /&gt;&lt;BR /&gt;And no, the contents of the event are not user-modifiable.</description>
      <pubDate>Mon, 13 Apr 2009 13:48:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169171#M51233</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2009-04-13T13:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169172#M51234</link>
      <description>thanks for the answer :)</description>
      <pubDate>Mon, 13 Apr 2009 14:02:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169172#M51234</guid>
      <dc:creator>Nat Sacks</dc:creator>
      <dc:date>2009-04-13T14:02:47Z</dc:date>
    </item>
    <item>
      <title>Re: Thermal Status Degraded - warning email</title>
      <link>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169173#M51235</link>
      <description>solved!  :o)</description>
      <pubDate>Fri, 19 Feb 2010 15:40:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/thermal-status-degraded-warning-email/m-p/5169173#M51235</guid>
      <dc:creator>Nat Sacks</dc:creator>
      <dc:date>2010-02-19T15:40:54Z</dc:date>
    </item>
  </channel>
</rss>

