<?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: Firmware Updates - Best Practices in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516167#M7788</link>
    <description>There is also a document available&lt;BR /&gt;&lt;BR /&gt;HP BladeSystem ProLiant firmware management best practices General overview&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01857420/c01857420.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01857420/c01857420.pdf&lt;/A&gt;</description>
    <pubDate>Mon, 19 Oct 2009 05:38:20 GMT</pubDate>
    <dc:creator>JKytsi</dc:creator>
    <dc:date>2009-10-19T05:38:20Z</dc:date>
    <item>
      <title>Firmware Updates - Best Practices</title>
      <link>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516165#M7786</link>
      <description>Hello All &amp;amp; Greetings.&lt;BR /&gt;&lt;BR /&gt;I am working ona  bunch of HP c7000 class Enclosures and various blades - but mostly BL460cG1 &amp;amp; BL460cG6. I would like to know the 'Best Practices' to do the following:&lt;BR /&gt;&lt;BR /&gt;1. Upgrading the OA, Virtual Connect firmware in a production environment.&lt;BR /&gt;2. Upgrading the various firmware for the bladeservers (iLO, Power, etc.)&lt;BR /&gt;&lt;BR /&gt;Thanks, &lt;BR /&gt;Kishan</description>
      <pubDate>Mon, 19 Oct 2009 00:39:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516165#M7786</guid>
      <dc:creator>kishanb</dc:creator>
      <dc:date>2009-10-19T00:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware Updates - Best Practices</title>
      <link>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516166#M7787</link>
      <description>Hi Kishan,&lt;BR /&gt;&lt;BR /&gt;Please see the c-class bladesystem firmware compatibility matrix: &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18004.www1.hp.com/products/blades/components/c-class-compmatrix.html" target="_blank"&gt;http://h18004.www1.hp.com/products/blades/components/c-class-compmatrix.html&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;First check your blade BIOS/firmware levels, update if necessary. This may require blade reboots&lt;BR /&gt;&lt;BR /&gt;From Best practices guide:&lt;BR /&gt;&lt;BR /&gt;Offline Updates&lt;BR /&gt;The following instructions can be used to update the firmware on an individual server using the HP Firmware Maintenance CD &lt;BR /&gt;&lt;BR /&gt;1) Download the HP Firmware Maintenance CD from the HP website. Links to the latest versions are posted on the BladeSystem Compatibility Chart web pages and can be accessed through the &lt;A href="http://www.hp.com/go/bladesystemupdates" target="_blank"&gt;http://www.hp.com/go/bladesystemupdates&lt;/A&gt; URL. The file will be called firmware-&lt;VERSION&gt;.zip. &lt;BR /&gt;&lt;BR /&gt;2) To extract the ISO image, open Windows Explorer and double-click on the ZIP file and copy the ISO image to a directory on a USB key or network hard drive. For Linux users, simply unzip the ZIP file using theÂ "unzip firmware-&lt;VERSION&gt;.zip"Â command. &lt;BR /&gt;&lt;BR /&gt;3) The easiest way to update a server blade using the HP Firmware Maintenance CD ISO image is to place it on a USB key and insert it into the USB port on the front of the C3000 enclosure or on the rear of the C7000 enclosure.&lt;BR /&gt;&lt;BR /&gt;4) Browse to the HP BladeSystem Onboard Administrator web interface and login using the OA administrator credentials.&lt;BR /&gt;&lt;BR /&gt;5) Click on "Device Bays"Â  to pull up a summary of all blades in the enclosure&lt;BR /&gt;&lt;BR /&gt;6) Check the box beside each blade that needs to be updated&lt;BR /&gt;&lt;BR /&gt;7) Click the "DVD" tab and select the "Connect to FW*.iso" option in the pull down menu where the "*"Â  signifies the version, date, and pass number of the HP Firmware Maintenance CD ISO file that was extracted in step #2.&lt;BR /&gt;&lt;BR /&gt;8) Check the box beside each blade that needs to be updated again if they are deselected during the DVD connection step.&lt;BR /&gt;&lt;BR /&gt;9) Select the "Virtual Power" tab and select the "Momentary Press"Â  option. After confirming the popup for power change on the blade(s), the blades should power down if they were already powered on or power on if they had already been powered off. In the event they are powered off by step 9, repeat this step again to power the blade(s) on.&lt;BR /&gt;&lt;BR /&gt;10) Use the remote console to browse into each blade and drive the installation process by following the steps as outlined in the "Using HP Smart Update Manager (HP SUM) in GUI mode". Some screens such as the "Source Selection"Â and "Select Installation Hosts"Â  will not be displayed in offline mode.&lt;BR /&gt;&lt;BR /&gt;NOTE: The iLO firmware must be deselected if the Firmware CD is being executed in offline mode to prevent errors that could occur when the iLO Firmware is updated and the iLO virtual media and remote console is reset. It is best to update the iLO firmware online first using the HP BladeSystem Firmware Update Bundles, then use the HP Firmware Maintenance CD in offline mode to flash offline-only firmware such as the QLogic, Brocade and Emulex FC HBA firmware.&lt;BR /&gt;&lt;BR /&gt;NOTE: Please use the HP BladeSystem Firmware Deployment Tool for an automated way to perform these steps. The HP BladeSystem Firmware Deployment Tool also does not have the issue with iLO Firmware updates disconnecting the media since the FDT copies all the files from the iLO Virtual Media to a RAM drive on each server before initiating the firmware update process.&lt;BR /&gt;&lt;BR /&gt;NOTE: Reboot the server once the firmware updates have completed successfully to activate all the software.&lt;BR /&gt;&lt;BR /&gt;NOTE: In some rare instances, the Firmware Maintenance CD may not boot with some 3rd party external Fiber Channel storage attached. In the event this occurs, it may be necessary to disconnect the external storage for the duration of the update process and reconnect it afterwards.&lt;BR /&gt;&lt;BR /&gt;NOTE: As an alternative, the HP Firmware Maintenance CD can be burned to a physical CD and placed in an external CD/DVD drive connected to the SUV (Serial-USB-Video) cable for the individual blade that needs to be updated. &lt;BR /&gt;&lt;/VERSION&gt;&lt;/VERSION&gt;</description>
      <pubDate>Mon, 19 Oct 2009 01:30:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516166#M7787</guid>
      <dc:creator>Viveki</dc:creator>
      <dc:date>2009-10-19T01:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware Updates - Best Practices</title>
      <link>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516167#M7788</link>
      <description>There is also a document available&lt;BR /&gt;&lt;BR /&gt;HP BladeSystem ProLiant firmware management best practices General overview&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01857420/c01857420.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01857420/c01857420.pdf&lt;/A&gt;</description>
      <pubDate>Mon, 19 Oct 2009 05:38:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516167#M7788</guid>
      <dc:creator>JKytsi</dc:creator>
      <dc:date>2009-10-19T05:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware Updates - Best Practices</title>
      <link>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516168#M7789</link>
      <description>The compatibility matrix is a good idea but poorly executed. Until only a few days ago there was no mention of OA versions 2.52 and 2.60, instead it showed 2.41 and 2.51. At the same time HP support was recommending to us to upgrade our enclosures to the latest version 2.60 when we experienced an issue, otherwise they refused to support us at all.&lt;BR /&gt;&lt;BR /&gt;Now that the matrix shows OA versions 2.52 and 2.60, the download page shows the HP BladeSystem Online Firmware Bundle for Windows/Linux version 1.60 which only support 2.52!&lt;BR /&gt;&lt;BR /&gt;Come on HP...if you're going to create tools like this then please keep them up to date and in sync with your releases. Otherwise don't withhold support from your customers.</description>
      <pubDate>Tue, 20 Oct 2009 06:14:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516168#M7789</guid>
      <dc:creator>8i5</dc:creator>
      <dc:date>2009-10-20T06:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: Firmware Updates - Best Practices</title>
      <link>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516169#M7790</link>
      <description>I agree. HP - make it right. It says in the compatibility matrix that if you want to run 2.52 or 2.60 - you should run iLO 1.79.&lt;BR /&gt;&lt;BR /&gt;But in the HP BladeSystem Online Firmware Bundle for Windows 1.60 - iLO 1.78 is included.&lt;BR /&gt;&lt;BR /&gt;I wonder if we could stick to the normal Firmware CD (now 8.60) and HP PSP (now 8.30) so we can have the same update process for all our ProLiants, no matter if it's blade or rack.&lt;BR /&gt;&lt;BR /&gt;HP, comments on this?</description>
      <pubDate>Wed, 28 Oct 2009 14:08:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/firmware-updates-best-practices/m-p/4516169#M7790</guid>
      <dc:creator>Jonas Back_2</dc:creator>
      <dc:date>2009-10-28T14:08:24Z</dc:date>
    </item>
  </channel>
</rss>

