<?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: Triggered reboot on Procurve Switches in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206513#M29249</link>
    <description>Thanks for replying,&lt;BR /&gt;&lt;BR /&gt;Yes there is an event log msg for the temp. &lt;BR /&gt;can you please tell me how to configure this excatly :)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Islam Hassan</description>
    <pubDate>Wed, 04 Nov 2009 07:12:35 GMT</pubDate>
    <dc:creator>Shadow13</dc:creator>
    <dc:date>2009-11-04T07:12:35Z</dc:date>
    <item>
      <title>Triggered reboot on Procurve Switches</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206511#M29247</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Is there anyway to make the switch reboot automatically if the temperature exceeds the threshold ??</description>
      <pubDate>Wed, 28 Oct 2009 13:35:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206511#M29247</guid>
      <dc:creator>Shadow13</dc:creator>
      <dc:date>2009-10-28T13:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered reboot on Procurve Switches</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206512#M29248</link>
      <description>Is there a SNMP trap for the over-temperature event? If so you could use something to monitor for that trap and then issue a reboot (also via SNMP).</description>
      <pubDate>Thu, 29 Oct 2009 08:08:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206512#M29248</guid>
      <dc:creator>Mohammed Faiz</dc:creator>
      <dc:date>2009-10-29T08:08:34Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered reboot on Procurve Switches</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206513#M29249</link>
      <description>Thanks for replying,&lt;BR /&gt;&lt;BR /&gt;Yes there is an event log msg for the temp. &lt;BR /&gt;can you please tell me how to configure this excatly :)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Islam Hassan</description>
      <pubDate>Wed, 04 Nov 2009 07:12:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206513#M29249</guid>
      <dc:creator>Shadow13</dc:creator>
      <dc:date>2009-11-04T07:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered reboot on Procurve Switches</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206514#M29250</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm not sure whether all event log messages generate SNMP traps, I can't find any documents that reference what traps are generated for what SNMP communities.&lt;BR /&gt;First you need to specify a trap receiver on the switch:&lt;BR /&gt;&lt;BR /&gt;snmp-server host *SNMP_server_IP* all public&lt;BR /&gt;&lt;BR /&gt;Then you'd need to set an action on whatever SNMP software you're running (we have SNMPc) based on the over-temperature event.&lt;BR /&gt;The MIB for performing a reset of the switch is 'hpicfReset' which when set to a value of 2 causes a switch reset.</description>
      <pubDate>Wed, 04 Nov 2009 10:38:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206514#M29250</guid>
      <dc:creator>Mohammed Faiz</dc:creator>
      <dc:date>2009-11-04T10:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered reboot on Procurve Switches</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206515#M29251</link>
      <description>yes it is possible with PCM+ policy</description>
      <pubDate>Wed, 04 Nov 2009 14:36:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206515#M29251</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2009-11-04T14:36:20Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered reboot on Procurve Switches</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206516#M29252</link>
      <description>I already knew about the PCM+ Policy but i just wanted to double check.&lt;BR /&gt;&lt;BR /&gt;Thanks alot</description>
      <pubDate>Wed, 04 Nov 2009 14:48:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/triggered-reboot-on-procurve-switches/m-p/5206516#M29252</guid>
      <dc:creator>Shadow13</dc:creator>
      <dc:date>2009-11-04T14:48:18Z</dc:date>
    </item>
  </channel>
</rss>

