<?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 Identify all servers in need of firmware update in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/identify-all-servers-in-need-of-firmware-update/m-p/4458883#M92339</link>
    <description>I am looking for a software package that would allow me to search a network segment for all HP servers that require firmware (and possibly other) updates.  Primarily the servers are Proliant DLs but other models will possibly exist.</description>
    <pubDate>Mon, 13 Jul 2009 19:36:28 GMT</pubDate>
    <dc:creator>twenty12</dc:creator>
    <dc:date>2009-07-13T19:36:28Z</dc:date>
    <item>
      <title>Identify all servers in need of firmware update</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/identify-all-servers-in-need-of-firmware-update/m-p/4458883#M92339</link>
      <description>I am looking for a software package that would allow me to search a network segment for all HP servers that require firmware (and possibly other) updates.  Primarily the servers are Proliant DLs but other models will possibly exist.</description>
      <pubDate>Mon, 13 Jul 2009 19:36:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/identify-all-servers-in-need-of-firmware-update/m-p/4458883#M92339</guid>
      <dc:creator>twenty12</dc:creator>
      <dc:date>2009-07-13T19:36:28Z</dc:date>
    </item>
    <item>
      <title>Re: Identify all servers in need of firmware update</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/identify-all-servers-in-need-of-firmware-update/m-p/4458884#M92340</link>
      <description>What you should so is install HP SIM on a server and then add the server name (dns alias is best) to the SNMPTrap destination then any server will report when it has a critical update.&lt;BR /&gt;&lt;BR /&gt;This could be anything from Software to firmware, which all should be kept at the same levels, and since you have to reboot for a firmware update, you should update the rest at the same time.</description>
      <pubDate>Tue, 14 Jul 2009 01:10:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/identify-all-servers-in-need-of-firmware-update/m-p/4458884#M92340</guid>
      <dc:creator>Graeme Bray</dc:creator>
      <dc:date>2009-07-14T01:10:52Z</dc:date>
    </item>
  </channel>
</rss>

