<?xml version="1.0" encoding="UTF-8"?>
<cpq_package version="2.0.1.0">
  <filename>CP031628.zip</filename>
  <divisions>
    <division key="6">
      <division_xlate lang="en">Server</division_xlate>
      <division_xlate lang="cn">服务器</division_xlate>
      <division_xlate lang="ja">サーバ</division_xlate>
      <division_xlate lang="ko">서버</division_xlate>
      <division_xlate lang="tw">伺服器</division_xlate>
    </division>
  </divisions>
  <operating_systems>
    <operating_system key="">
      <operating_system_xlate>VMware vSphere 5.5</operating_system_xlate>
    </operating_system>
    <operating_system key="">
      <operating_system_xlate>VMware vSphere 6.0</operating_system_xlate>
    </operating_system>
    <operating_system key="">
      <operating_system_xlate>VMware vSphere 6.5</operating_system_xlate>
    </operating_system>
  </operating_systems>
  <products>
    <product rom="I39"/>
  </products>
  <category key="1200212">
    <category_xlate lang="en">BIOS - System ROM</category_xlate>
    <category_xlate lang="cn">BIOS - 系统 ROM</category_xlate>
    <category_xlate lang="ja">BIOS - システムROM</category_xlate>
    <category_xlate lang="ko">BIOS - 시스템 ROM</category_xlate>
    <category_xlate lang="tw">BIOS ─ 系統 ROM</category_xlate>
  </category>
  <id product="1f1cac7aa6ca4f8f9efe604dd3abf128" version="2ce8d90f89284d6281fabf3cdcca722a"/>
  <name>
    <name_xlate lang="en">Online ROM Flash Component for VMware - HPE Synergy 660 Gen9  (I39) Compute Module</name_xlate>
    <name_xlate lang="cn">Online ROM Flash Component for VMware - HPE Synergy 660 Gen9  (I39) Compute Module</name_xlate>
    <name_xlate lang="ja">VMware用オンラインROMフラッシュコンポーネント - HPE Synergy 660 Gen9 (I39) コンピュートモジュール</name_xlate>
    <name_xlate lang="ko">Online ROM Flash Component for VMware - HPE Synergy 660 Gen9  (I39) Compute Module</name_xlate>
    <name_xlate lang="tw">Online ROM Flash Component for VMware - HPE Synergy 660 Gen9  (I39) Compute Module</name_xlate>
  </name>
  <alt_name>
    <alt_name_xlate lang="en">HPE Synergy 660 Gen9 (I39) Compute Module</alt_name_xlate>
    <alt_name_xlate lang="cn">HPE Synergy 660 Gen9 (I39) Compute Module</alt_name_xlate>
    <alt_name_xlate lang="ja">HPE Synergy 660 Gen9 (I39) コンピュートモジュール</alt_name_xlate>
    <alt_name_xlate lang="ko">HPE Synergy 660 Gen9 (I39) Compute Module</alt_name_xlate>
    <alt_name_xlate lang="tw">HPE Synergy 660 Gen9 (I39) Compute Module</alt_name_xlate>
  </alt_name>
  <version value="2.40_02-17-2017" revision="" type_of_change="0"/>
  <manufacturer_name>
    <manufacturer_name_xlate lang="en">Hewlett Packard Enterprise</manufacturer_name_xlate>
    <manufacturer_name_xlate lang="cn">惠普企业</manufacturer_name_xlate>
    <manufacturer_name_xlate lang="ja">Hewlett Packard Enterprise</manufacturer_name_xlate>
    <manufacturer_name_xlate lang="ko">Hewlett Packard Enterprise</manufacturer_name_xlate>
    <manufacturer_name_xlate lang="tw">Hewlett Packard Enterprise</manufacturer_name_xlate>
  </manufacturer_name>
  <languages langlist="en">
    <languages_xlate lang="en">English (US)</languages_xlate>
    <languages_xlate lang="ja">英語（US）</languages_xlate>
    <languages_xlate lang="ko">영어(미국)</languages_xlate>
    <languages_xlate lang="cn">英语（美国）</languages_xlate>
    <languages_xlate lang="tw">美式英文</languages_xlate>
  </languages>
  <release_date year="2017" month="3" day="8" hour="14" minute="24" second="5"/>
  <description>
    <description_xlate lang="en">
<![CDATA[This component provides updated system firmware that can be installed directly on supported Operating Systems. Additionally, when used in conjunction with Smart Update Manager (SUM) and Insight Control for VMware vCenter, this Component allows the user to update firmware on remote servers from a central location. This remote deployment capability eliminates the need for the user to be physically present at the server in order to perform a firmware update.]]>
</description_xlate>
    <description_xlate lang="cn">
<![CDATA[This component provides updated system firmware that can be installed directly on supported Operating Systems. Additionally, when used in conjunction with Smart Update Manager (SUM) and Insight Control for VMware vCenter, this Component allows the user to update firmware on remote servers from a central location. This remote deployment capability eliminates the need for the user to be physically present at the server in order to perform a firmware update.]]>
</description_xlate>
    <description_xlate lang="ja">
<![CDATA[This component provides updated system firmware that can be installed directly on supported Operating Systems. Additionally, when used in conjunction with Smart Update Manager (SUM) and Insight Control for VMware vCenter, this Component allows the user to update firmware on remote servers from a central location. This remote deployment capability eliminates the need for the user to be physically present at the server in order to perform a firmware update.]]>
</description_xlate>
    <description_xlate lang="ko">
<![CDATA[This component provides updated system firmware that can be installed directly on supported Operating Systems. Additionally, when used in conjunction with Smart Update Manager (SUM) and Insight Control for VMware vCenter, this Component allows the user to update firmware on remote servers from a central location. This remote deployment capability eliminates the need for the user to be physically present at the server in order to perform a firmware update.]]>
</description_xlate>
    <description_xlate lang="tw">
<![CDATA[This component provides updated system firmware that can be installed directly on supported Operating Systems. Additionally, when used in conjunction with Smart Update Manager (SUM) and Insight Control for VMware vCenter, this Component allows the user to update firmware on remote servers from a central location. This remote deployment capability eliminates the need for the user to be physically present at the server in order to perform a firmware update.]]>
</description_xlate>
  </description>
  <prerequisite_notes>
    <prerequisite_notes_xlate lang="en">
      <prerequisite_notes_xlate_part>
<![CDATA[<p>This component requires that the following HPE&nbsp; drivers be loaded before the component can run.<br />
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;HPE ProLiant iLO 3/4 Channel Interface Driver&rdquo; (CHIF) must be installed and running.<br />
The minimum iLO version for ESXi 5.5, ESXi 6.0&nbsp;and ESXi 6.5 is 1.4.<br />
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &ldquo;Compaq ROM Utility Driver&rdquo; (CRU) must be installed and running<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.</p>

<p>Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools.&nbsp; The drivers are also available from the OS specific &ldquo;HPE Agentless Management Service Offline Bundle&rdquo;&nbsp; for VMware vSphere 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>
]]>
</prerequisite_notes_xlate_part>
    </prerequisite_notes_xlate>
    <prerequisite_notes_xlate lang="cn">
      <prerequisite_notes_xlate_part>
<![CDATA[<p>This component requires that the following HPE&nbsp; drivers be loaded before the component can run.<br />
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;HPE ProLiant iLO 3/4 Channel Interface Driver&rdquo; (CHIF) must be installed and running.<br />
The minimum iLO version for ESXi 5.5, ESXi 6.0&nbsp;and ESXi 6.5 is 1.4.<br />
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &ldquo;Compaq ROM Utility Driver&rdquo; (CRU) must be installed and running<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.</p>

<p>Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools.&nbsp; The drivers are also available from the OS specific &ldquo;HPE Agentless Management Service Offline Bundle&rdquo;&nbsp; for VMware vSphere 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>
]]>
</prerequisite_notes_xlate_part>
    </prerequisite_notes_xlate>
    <prerequisite_notes_xlate lang="ja">
      <prerequisite_notes_xlate_part>
<![CDATA[<p>This component requires that the following HPE&nbsp; drivers be loaded before the component can run.<br />
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;HPE ProLiant iLO 3/4 Channel Interface Driver&rdquo; (CHIF) must be installed and running.<br />
The minimum iLO version for ESXi 5.5, ESXi 6.0&nbsp;and ESXi 6.5 is 1.4.<br />
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &ldquo;Compaq ROM Utility Driver&rdquo; (CRU) must be installed and running<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.</p>

<p>Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools.&nbsp; The drivers are also available from the OS specific &ldquo;HPE Agentless Management Service Offline Bundle&rdquo;&nbsp; for VMware vSphere 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>
]]>
</prerequisite_notes_xlate_part>
    </prerequisite_notes_xlate>
    <prerequisite_notes_xlate lang="ko">
      <prerequisite_notes_xlate_part>
<![CDATA[<p>This component requires that the following HPE&nbsp; drivers be loaded before the component can run.<br />
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;HPE ProLiant iLO 3/4 Channel Interface Driver&rdquo; (CHIF) must be installed and running.<br />
The minimum iLO version for ESXi 5.5, ESXi 6.0&nbsp;and ESXi 6.5 is 1.4.<br />
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &ldquo;Compaq ROM Utility Driver&rdquo; (CRU) must be installed and running<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.</p>

<p>Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools.&nbsp; The drivers are also available from the OS specific &ldquo;HPE Agentless Management Service Offline Bundle&rdquo;&nbsp; for VMware vSphere 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>
]]>
</prerequisite_notes_xlate_part>
    </prerequisite_notes_xlate>
    <prerequisite_notes_xlate lang="tw">
      <prerequisite_notes_xlate_part>
<![CDATA[<p>This component requires that the following HPE&nbsp; drivers be loaded before the component can run.<br />
1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;HPE ProLiant iLO 3/4 Channel Interface Driver&rdquo; (CHIF) must be installed and running.<br />
The minimum iLO version for ESXi 5.5, ESXi 6.0&nbsp;and ESXi 6.5 is 1.4.<br />
2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &ldquo;Compaq ROM Utility Driver&rdquo; (CRU) must be installed and running<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.</p>

<p>Both drivers are integrated into the HPE VMware Custom Image which also contains other HPE advanced management tools.&nbsp; The drivers are also available from the OS specific &ldquo;HPE Agentless Management Service Offline Bundle&rdquo;&nbsp; for VMware vSphere 6.5, 6.0, and 5.5 on vibsdepot.hpe.com.</p>

<p>&nbsp;</p>

<p>&nbsp;</p>

<p>&nbsp;</p>
]]>
</prerequisite_notes_xlate_part>
    </prerequisite_notes_xlate>
  </prerequisite_notes>
  <installation_notes>
    <installation_notes_xlate lang="en">
      <installation_notes_xlate_part>
<![CDATA[<p>IMPORTANT: This component requires that the CRU driver be loaded before the component can run.<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.<br />
<br />
<br />
<strong>Offline:</strong></p>

<ul>
	<li>SPP Offline mode boots a special Linux OS environment, thus the Linux Components are used, not the VMware Components</li>
</ul>

<p><br />
<strong>Remote Online, if the component is supported by SUM but is not yet part of an SPP:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>Download the appropriate SPP</li>
	<li>Add the component to the SPP</li>
	<li>Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated</li>
	<li>Run SUM</li>
	<li>Add the ESXi host to be updated as a remote target/node</li>
	<li>Enter IP or DNS address of the ESXi host to be updated</li>
	<li>Enter the ESXi host credentials (root or administrator username and password)</li>
	<li>For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.</li>
	<li>Follow&nbsp;Smart Update Manager Steps to complete the firmware update</li>
	<li>Refer to the SPP documentation for detailed instructions at:&nbsp; <a href="http://www.hp.com/go/spp">www.hpe.com/go/spp</a><br />
	&nbsp;</li>
</ul>

<p><strong><strong>To update firmware from VMware ESXi operating system on target server:</strong> </strong></p>

<ul>
	<li>Enable Tech Support Mode on the ESXi host</li>
	<li>Login as root. (You must be root in order to apply the update)</li>
	<li>Place the Component ( CPxxxxxx.zip) in a temporary directory</li>
	<li>From the same directory, unzip the Component:<br />
	unzip CPxxxxxx.zip</li>
	<li>To perform the standalone installation, execute the command:<br />
	CPxxxxxx.vmexe</li>
	<li>Follow the directions given by the Component</li>
	<li>Logout</li>
	<li>Disable Tech Support Mode on the ESXi host</li>
	<li>Reboot your system for the firmware update to take effect</li>
</ul>
]]>
</installation_notes_xlate_part>
    </installation_notes_xlate>
    <installation_notes_xlate lang="cn">
      <installation_notes_xlate_part>
<![CDATA[<p>IMPORTANT: This component requires that the CRU driver be loaded before the component can run.<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.<br />
<br />
<br />
<strong>Offline:</strong></p>

<ul>
	<li>SPP Offline mode boots a special Linux OS environment, thus the Linux Components are used, not the VMware Components</li>
</ul>

<p><br />
<strong>Remote Online, if the component is supported by SUM but is not yet part of an SPP:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>Download the appropriate SPP</li>
	<li>Add the component to the SPP</li>
	<li>Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated</li>
	<li>Run SUM</li>
	<li>Add the ESXi host to be updated as a remote target/node</li>
	<li>Enter IP or DNS address of the ESXi host to be updated</li>
	<li>Enter the ESXi host credentials (root or administrator username and password)</li>
	<li>For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.</li>
	<li>Follow&nbsp;Smart Update Manager Steps to complete the firmware update</li>
	<li>Refer to the SPP documentation for detailed instructions at:&nbsp; <a href="http://www.hp.com/go/spp">www.hpe.com/go/spp</a><br />
	&nbsp;</li>
</ul>

<p><strong><strong>To update firmware from VMware ESXi operating system on target server:</strong> </strong></p>

<ul>
	<li>Enable Tech Support Mode on the ESXi host</li>
	<li>Login as root. (You must be root in order to apply the update)</li>
	<li>Place the Component ( CPxxxxxx.zip) in a temporary directory</li>
	<li>From the same directory, unzip the Component:<br />
	unzip CPxxxxxx.zip</li>
	<li>To perform the standalone installation, execute the command:<br />
	CPxxxxxx.vmexe</li>
	<li>Follow the directions given by the Component</li>
	<li>Logout</li>
	<li>Disable Tech Support Mode on the ESXi host</li>
	<li>Reboot your system for the firmware update to take effect</li>
</ul>
]]>
</installation_notes_xlate_part>
    </installation_notes_xlate>
    <installation_notes_xlate lang="ja">
      <installation_notes_xlate_part>
<![CDATA[<p>IMPORTANT: This component requires that the CRU driver be loaded before the component can run.<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.<br />
<br />
<br />
<strong>Offline:</strong></p>

<ul>
	<li>SPP Offline mode boots a special Linux OS environment, thus the Linux Components are used, not the VMware Components</li>
</ul>

<p><br />
<strong>Remote Online, if the component is supported by SUM but is not yet part of an SPP:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>Download the appropriate SPP</li>
	<li>Add the component to the SPP</li>
	<li>Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated</li>
	<li>Run SUM</li>
	<li>Add the ESXi host to be updated as a remote target/node</li>
	<li>Enter IP or DNS address of the ESXi host to be updated</li>
	<li>Enter the ESXi host credentials (root or administrator username and password)</li>
	<li>For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.</li>
	<li>Follow&nbsp;Smart Update Manager Steps to complete the firmware update</li>
	<li>Refer to the SPP documentation for detailed instructions at:&nbsp; <a href="http://www.hp.com/go/spp">www.hpe.com/go/spp</a><br />
	&nbsp;</li>
</ul>

<p><strong><strong>To update firmware from VMware ESXi operating system on target server:</strong> </strong></p>

<ul>
	<li>Enable Tech Support Mode on the ESXi host</li>
	<li>Login as root. (You must be root in order to apply the update)</li>
	<li>Place the Component ( CPxxxxxx.zip) in a temporary directory</li>
	<li>From the same directory, unzip the Component:<br />
	unzip CPxxxxxx.zip</li>
	<li>To perform the standalone installation, execute the command:<br />
	CPxxxxxx.vmexe</li>
	<li>Follow the directions given by the Component</li>
	<li>Logout</li>
	<li>Disable Tech Support Mode on the ESXi host</li>
	<li>Reboot your system for the firmware update to take effect</li>
</ul>
]]>
</installation_notes_xlate_part>
    </installation_notes_xlate>
    <installation_notes_xlate lang="ko">
      <installation_notes_xlate_part>
<![CDATA[<p>IMPORTANT: This component requires that the CRU driver be loaded before the component can run.<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.<br />
<br />
<br />
<strong>Offline:</strong></p>

<ul>
	<li>SPP Offline mode boots a special Linux OS environment, thus the Linux Components are used, not the VMware Components</li>
</ul>

<p><br />
<strong>Remote Online, if the component is supported by SUM but is not yet part of an SPP:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>Download the appropriate SPP</li>
	<li>Add the component to the SPP</li>
	<li>Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated</li>
	<li>Run SUM</li>
	<li>Add the ESXi host to be updated as a remote target/node</li>
	<li>Enter IP or DNS address of the ESXi host to be updated</li>
	<li>Enter the ESXi host credentials (root or administrator username and password)</li>
	<li>For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.</li>
	<li>Follow&nbsp;Smart Update Manager Steps to complete the firmware update</li>
	<li>Refer to the SPP documentation for detailed instructions at:&nbsp; <a href="http://www.hp.com/go/spp">www.hpe.com/go/spp</a><br />
	&nbsp;</li>
</ul>

<p><strong><strong>To update firmware from VMware ESXi operating system on target server:</strong> </strong></p>

<ul>
	<li>Enable Tech Support Mode on the ESXi host</li>
	<li>Login as root. (You must be root in order to apply the update)</li>
	<li>Place the Component ( CPxxxxxx.zip) in a temporary directory</li>
	<li>From the same directory, unzip the Component:<br />
	unzip CPxxxxxx.zip</li>
	<li>To perform the standalone installation, execute the command:<br />
	CPxxxxxx.vmexe</li>
	<li>Follow the directions given by the Component</li>
	<li>Logout</li>
	<li>Disable Tech Support Mode on the ESXi host</li>
	<li>Reboot your system for the firmware update to take effect</li>
</ul>
]]>
</installation_notes_xlate_part>
    </installation_notes_xlate>
    <installation_notes_xlate lang="tw">
      <installation_notes_xlate_part>
<![CDATA[<p>IMPORTANT: This component requires that the CRU driver be loaded before the component can run.<br />
The minimum CRU version for 5.5 is 5.5.4.1.<br />
The minimum CRU version for 6.0 is 6.0.8.<br />
The minimum CRU version for 6.5 is 6.5.8.<br />
<br />
<br />
<strong>Offline:</strong></p>

<ul>
	<li>SPP Offline mode boots a special Linux OS environment, thus the Linux Components are used, not the VMware Components</li>
</ul>

<p><br />
<strong>Remote Online, if the component is supported by SUM but is not yet part of an SPP:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>Download the appropriate SPP</li>
	<li>Add the component to the SPP</li>
	<li>Mount the SPP on a remote server running Windows or Linux that has a network connection to the ESXi host to be updated</li>
	<li>Run SUM</li>
	<li>Add the ESXi host to be updated as a remote target/node</li>
	<li>Enter IP or DNS address of the ESXi host to be updated</li>
	<li>Enter the ESXi host credentials (root or administrator username and password)</li>
	<li>For SUM 6.0 and newer, select both the Additional Package with the added component and the SPP Baseline on the node Inventory page.</li>
	<li>Follow&nbsp;Smart Update Manager Steps to complete the firmware update</li>
	<li>Refer to the SPP documentation for detailed instructions at:&nbsp; <a href="http://www.hp.com/go/spp">www.hpe.com/go/spp</a><br />
	&nbsp;</li>
</ul>

<p><strong><strong>To update firmware from VMware ESXi operating system on target server:</strong> </strong></p>

<ul>
	<li>Enable Tech Support Mode on the ESXi host</li>
	<li>Login as root. (You must be root in order to apply the update)</li>
	<li>Place the Component ( CPxxxxxx.zip) in a temporary directory</li>
	<li>From the same directory, unzip the Component:<br />
	unzip CPxxxxxx.zip</li>
	<li>To perform the standalone installation, execute the command:<br />
	CPxxxxxx.vmexe</li>
	<li>Follow the directions given by the Component</li>
	<li>Logout</li>
	<li>Disable Tech Support Mode on the ESXi host</li>
	<li>Reboot your system for the firmware update to take effect</li>
</ul>
]]>
</installation_notes_xlate_part>
    </installation_notes_xlate>
  </installation_notes>
  <availability_notes/>
  <documentation_notes/>
  <revision_history>
    <revision>
      <version value="2.40_02-17-2017" revision="" type_of_change="0"/>
      <revision_enhancements_xlate lang="en">
        <revision_enhancements_xlate_part>
<![CDATA[Updated the system thermal logic to support the latest adapters.<p>Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options.]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="cn">
        <revision_enhancements_xlate_part>
<![CDATA[Updated the system thermal logic to support the latest adapters.<p>Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options.]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="ja">
        <revision_enhancements_xlate_part>
<![CDATA[Updated the system thermal logic to support the latest adapters.<p>Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options.]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="ko">
        <revision_enhancements_xlate_part>
<![CDATA[Updated the system thermal logic to support the latest adapters.<p>Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options.]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="tw">
        <revision_enhancements_xlate_part>
<![CDATA[Updated the system thermal logic to support the latest adapters.<p>Updated the HP RESTful API HPE BIOS Attribute Registry resources to match the latest BIOS/Platform Configuration options.]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_fixes_xlate lang="en">
        <revision_fixes_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Problems Fixed:</B></P>Addressed an issue where the system may become unresponsive during system boot when a third party USB 3.0 XHCI adapter card is installed in the server.<p>Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy.  The iLO GUI will now report the DIMM's status as degraded.<p>Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.<p>Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.<P><B>Known Issues:</B></P>None]]>
</revision_fixes_xlate_part>
      </revision_fixes_xlate>
      <revision_fixes_xlate lang="cn">
        <revision_fixes_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Problems Fixed:</B></P>Addressed an issue where the system may become unresponsive during system boot when a third party USB 3.0 XHCI adapter card is installed in the server.<p>Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy.  The iLO GUI will now report the DIMM's status as degraded.<p>Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.<p>Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.<P><B>Known Issues:</B></P>None]]>
</revision_fixes_xlate_part>
      </revision_fixes_xlate>
      <revision_fixes_xlate lang="ja">
        <revision_fixes_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Problems Fixed:</B></P>Addressed an issue where the system may become unresponsive during system boot when a third party USB 3.0 XHCI adapter card is installed in the server.<p>Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy.  The iLO GUI will now report the DIMM's status as degraded.<p>Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.<p>Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.<P><B>Known Issues:</B></P>None]]>
</revision_fixes_xlate_part>
      </revision_fixes_xlate>
      <revision_fixes_xlate lang="ko">
        <revision_fixes_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Problems Fixed:</B></P>Addressed an issue where the system may become unresponsive during system boot when a third party USB 3.0 XHCI adapter card is installed in the server.<p>Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy.  The iLO GUI will now report the DIMM's status as degraded.<p>Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.<p>Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.<P><B>Known Issues:</B></P>None]]>
</revision_fixes_xlate_part>
      </revision_fixes_xlate>
      <revision_fixes_xlate lang="tw">
        <revision_fixes_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Problems Fixed:</B></P>Addressed an issue where the system may become unresponsive during system boot when a third party USB 3.0 XHCI adapter card is installed in the server.<p>Addressed an issue where the system may properly indicate that a DIMM has experienced a high rate of corrected memory errors in the Integrated Management Log (IML), but the DIMM's status may incorrectly be reported in the iLO GUI as healthy.  The iLO GUI will now report the DIMM's status as degraded.<p>Addressed an issue where the system may become unresponsive during system boot when a USB-based UPS is attached to the server USB ports. This issue only impacted a system when configured for legacy boot mode.<p>Addressed an issue where the system may not properly report and log errors to the Integrated Management Log (IML) detected on the optional HPE Dual SD Card option. This issue only impacted logging when the system performed a warm reset.<P><B>Known Issues:</B></P>None]]>
</revision_fixes_xlate_part>
      </revision_fixes_xlate>
    </revision>
    <revision>
      <version value="2.20_09-08-2016" revision="" type_of_change="1"/>
      <revision_enhancements_xlate lang="en">
        <revision_enhancements_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Enhancements/New Features:</B></P>This is the initial version of the firmware.<P><B>Known Issues:</B></P>None]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="cn">
        <revision_enhancements_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Enhancements/New Features:</B></P>This is the initial version of the firmware.<P><B>Known Issues:</B></P>None]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="ja">
        <revision_enhancements_xlate_part>
<![CDATA[<P><B>重要な注意：</B></P>なし<P><B>ファームウェアの依存関係:</B></P>なし<P><B>改善点/新しい機能：</B></P>これは、このファームウェアでの最初のバージョンです。<P><B>既知の問題点：</B></P>なし]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="ko">
        <revision_enhancements_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Enhancements/New Features:</B></P>This is the initial version of the firmware.<P><B>Known Issues:</B></P>None]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
      <revision_enhancements_xlate lang="tw">
        <revision_enhancements_xlate_part>
<![CDATA[<P><B>Important Notes:</B></P>None<P><B>Firmware Dependencies:</B></P>None<P><B>Enhancements/New Features:</B></P>This is the initial version of the firmware.<P><B>Known Issues:</B></P>None]]>
</revision_enhancements_xlate_part>
      </revision_enhancements_xlate>
    </revision>
  </revision_history>
  <sw_keys>
    <sw_keys_and>
      <sw_key name="I39">
        <sw_key_expectedpath>firmware:system</sw_key_expectedpath>
      </sw_key>
    </sw_keys_and>
  </sw_keys>
  <prerequisites>
    <supported_operating_systems>
      <supported_operating_system platform="vmware_esx_server" major="5" minor="5" sr="OEM" name="VMware vSphere 5.5"/>
      <supported_operating_system platform="vmware_esx_server" major="6" minor="5" sr="OEM" name="VMware vSphere 6.5"/>
      <supported_operating_system platform="vmware_esx_server" major="6" minor="0" sr="OEM" name="VMware vSphere 6.0"/>
    </supported_operating_systems>
    <supported_devices/>
    <required_diskspace size_kb="5000"/>
  </prerequisites>
  <installation>
    <install>
      <install_caps silent="no" needuseracct="no"/>
      <command></command>
      <command_params></command_params>
      <reboot_required value="yes"/>
      <reboot_details value="Required">
        <reboot_details_xlate lang="en">Reboot is required after installation for updates to take effect and hardware stability to be maintained.</reboot_details_xlate>
        <reboot_details_xlate lang="cn">安装之后必须重启才能使更新生效并保持硬件稳定性。</reboot_details_xlate>
        <reboot_details_xlate lang="ja">アップデートの効果とハードウェアの安定を得るために、インストール後の再起動は必要です。</reboot_details_xlate>
        <reboot_details_xlate lang="ko">업데이트가 적용되고 하드웨어 안정성이 유지되려면 설치 후 재부팅해야 합니다.</reboot_details_xlate>
        <reboot_details_xlate lang="tw">安裝後必須重新啟動，更新才會生效，並維持硬體穩定。</reboot_details_xlate>
      </reboot_details>
      <per_device_install_time_seconds>0</per_device_install_time_seconds>
    </install>
    <uninstall>
      <uninstall_caps silent="no"/>
      <command></command>
      <command_params></command_params>
      <reboot_required value="no"/>
    </uninstall>
  </installation>
</cpq_package>
