<?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: use of Redundant ROM in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853171#M56317</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Many ProLiant servers ship with redundant ROM capabilities. Redundant ROM is a failover mechanism wherein the original ROM can be kept as backup in case of network failure during ROM upgrade.&lt;BR /&gt;&lt;BR /&gt;To access the redundant ROM manually:&lt;BR /&gt;1. Remove power to the server. &lt;BR /&gt;2. Set the system maintenance switch positions 1, 5, and 6 to ON. &lt;BR /&gt;3. Power up the server. &lt;BR /&gt;4. After the server emits two beeps, power down the server. &lt;BR /&gt;5. Reset the system maintenance switch positions 1, 5, and 6 to OFF &lt;BR /&gt;</description>
    <pubDate>Wed, 30 Aug 2006 06:32:04 GMT</pubDate>
    <dc:creator>KiranKumar_2</dc:creator>
    <dc:date>2006-08-30T06:32:04Z</dc:date>
    <item>
      <title>use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853170#M56316</link>
      <description>hi&lt;BR /&gt;how system can boot from Redundant ROM ?(in a proliant server)</description>
      <pubDate>Wed, 30 Aug 2006 06:24:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853170#M56316</guid>
      <dc:creator>hamidhp</dc:creator>
      <dc:date>2006-08-30T06:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853171#M56317</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Many ProLiant servers ship with redundant ROM capabilities. Redundant ROM is a failover mechanism wherein the original ROM can be kept as backup in case of network failure during ROM upgrade.&lt;BR /&gt;&lt;BR /&gt;To access the redundant ROM manually:&lt;BR /&gt;1. Remove power to the server. &lt;BR /&gt;2. Set the system maintenance switch positions 1, 5, and 6 to ON. &lt;BR /&gt;3. Power up the server. &lt;BR /&gt;4. After the server emits two beeps, power down the server. &lt;BR /&gt;5. Reset the system maintenance switch positions 1, 5, and 6 to OFF &lt;BR /&gt;</description>
      <pubDate>Wed, 30 Aug 2006 06:32:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853171#M56317</guid>
      <dc:creator>KiranKumar_2</dc:creator>
      <dc:date>2006-08-30T06:32:04Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853172#M56318</link>
      <description>dear Hamidhp,&lt;BR /&gt;&lt;BR /&gt;Please explain, the exact type of the server. If you want it generally, its always explained in the Maintenance and Service guide of the server. Like at ML370 G3:&lt;BR /&gt;&lt;BR /&gt;ROMPaq Disaster Recovery Mode&lt;BR /&gt;&lt;BR /&gt;A corrupted system ROM requires that you recreate the ROM BIOS by flashing the ROM.&lt;BR /&gt;This operation can be accomplished only when the system is in disaster recovery (emergency&lt;BR /&gt;repair boot) mode. If both sides of the redundant ROM are corrupted, the system&lt;BR /&gt;automatically enters the disaster recovery mode and the server emits three extended beeps.&lt;BR /&gt;&lt;BR /&gt;To perform ROMPaq disaster recovery:&lt;BR /&gt;&lt;BR /&gt;1. After hearing the three beeps, insert a ROMPaq diskette with the latest system ROM&lt;BR /&gt;from SmartStart.&lt;BR /&gt;IMPORTANT: The ROMPaq flashes both sides of the redundant ROM. This process may take up&lt;BR /&gt;to ten minutes.&lt;BR /&gt;2. Wait until the server emits three rising beeps, indicating the completion of the ROM flash&lt;BR /&gt;process.&lt;BR /&gt;3. Restart the system.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;Attila</description>
      <pubDate>Wed, 30 Aug 2006 06:36:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853172#M56318</guid>
      <dc:creator>Attila Szabó</dc:creator>
      <dc:date>2006-08-30T06:36:33Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853173#M56319</link>
      <description>Sorry, i misunderstand you. Ki Ku wrote the good mode, how to boot from redundant ROM. (you can use the other methot only if both image corrupted) That method not explained in Maintenance and Service guide, its in Server User guide.&lt;BR /&gt;gl,&lt;BR /&gt;Attila</description>
      <pubDate>Wed, 30 Aug 2006 06:49:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853173#M56319</guid>
      <dc:creator>Attila Szabó</dc:creator>
      <dc:date>2006-08-30T06:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853174#M56320</link>
      <description>Hi&lt;BR /&gt;i Set the system maintenance switch positions 1, 5, and 6 to ON and power&lt;BR /&gt;up the server but server emits extended beeps&lt;BR /&gt;do you know what is meaning of this beeps.&lt;BR /&gt;myb server is proliant dl380 G4</description>
      <pubDate>Sat, 02 Sep 2006 01:44:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853174#M56320</guid>
      <dc:creator>hamidhp</dc:creator>
      <dc:date>2006-09-02T01:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853175#M56321</link>
      <description>There is a maintenance and service guide for that server (&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&amp;amp;prodSeriesId=397634&amp;amp;targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00687567%2Fc00687567.pdf)" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&amp;amp;prodSeriesId=397634&amp;amp;targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00687567%2Fc00687567.pdf)&lt;/A&gt;&lt;BR /&gt;In that documentation, there is no section about beep codes, but there is a section about error LEDs, take of the top of the server, and check the error LEDs.&lt;BR /&gt;&lt;BR /&gt;there is another guide: The server user guide (&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&amp;amp;prodSeriesId=397634&amp;amp;targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00218203%2Fc00218203.pdf)" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&amp;amp;prodSeriesId=397634&amp;amp;targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00218203%2Fc00218203.pdf)&lt;/A&gt;&lt;BR /&gt;In this document, you can find a section: "Access to redundant ROM settings"&lt;BR /&gt;In there, there is a full explain, what you need to do, and what you will hear.&lt;BR /&gt;Please, can you explain, what is the real situation, what happened, and why you need the redundant ROM?&lt;BR /&gt;There is a last file, which can be useful:&lt;BR /&gt;Proliant Servers Troubleshooting Guide (&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&amp;amp;prodSeriesId=397634&amp;amp;targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00300504%2Fc00300504.pdf)" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/CoreRedirect.jsp?redirectReason=DocIndexPDF&amp;amp;prodSeriesId=397634&amp;amp;targetPage=http%3A%2F%2Fh20000.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00300504%2Fc00300504.pdf)&lt;/A&gt;&lt;BR /&gt;In this file, there is a chapter about beep codes (page 92), but a common rule, the longer beep is biger problem.&lt;BR /&gt;regards,&lt;BR /&gt;Attila</description>
      <pubDate>Sat, 02 Sep 2006 19:51:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853175#M56321</guid>
      <dc:creator>Attila Szabó</dc:creator>
      <dc:date>2006-09-02T19:51:12Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853176#M56322</link>
      <description>dear attila &lt;BR /&gt;my server ia a proliant DL380 G4&lt;BR /&gt;after a power shock the screen became black&lt;BR /&gt;and server doesn't have any activity&lt;BR /&gt;when we turn on the server only the fans work with high speed.&lt;BR /&gt;the link of documents in your text are corrupted can you give me new link.&lt;BR /&gt;thank you&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Sep 2006 02:04:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853176#M56322</guid>
      <dc:creator>hamidhp</dc:creator>
      <dc:date>2006-09-04T02:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: use of Redundant ROM</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853177#M56323</link>
      <description>Sorry for the links, I just copied them from the browser :)&lt;BR /&gt;So you an find all documents related for your server here:&lt;BR /&gt;HP ProLiant DL380 G4 Server series - Manuals&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lt;/A&gt;〈=en&amp;amp;cc=us&amp;amp;docIndexId=179911&amp;amp;taskId=101&amp;amp;prodTypeId=15351&amp;amp;prodSeriesId=397634&lt;BR /&gt;On that page, just CTRL+F to the document names:&lt;BR /&gt;- ProLiant DL380 Generation 4 Server Maintenance and Service Guide &lt;BR /&gt;- ProLiant Servers Troubleshooting Guide &lt;BR /&gt;- ProLiant DL380 Generation 4 Server User Guide &lt;BR /&gt;If somehow the link doesnt work, go to &lt;A href="http://www.hp.com" target="_blank"&gt;www.hp.com&lt;/A&gt; , click to "Support and Troubleshooting", type "DL380 G4" - enter, click to "HP ProLiant DL380 G4 Rack Server (311143-xx1)", and click to Manuals (guides, supplements, addendums, etc).&lt;BR /&gt;This must help. But i think your problem is not a ROM problem, it looks like a hardware error. The error LEDs on front panel become red or yellow? Look around on motherboard, when the server is running, mabye there will some error LEDs will also (there are many orange LEDs in one row, thats the RAID controller LEDs, most of them not related to errors).&lt;BR /&gt;Greets,&lt;BR /&gt;Attila</description>
      <pubDate>Mon, 04 Sep 2006 02:24:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/use-of-redundant-rom/m-p/3853177#M56323</guid>
      <dc:creator>Attila Szabó</dc:creator>
      <dc:date>2006-09-04T02:24:03Z</dc:date>
    </item>
  </channel>
</rss>

