<?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 SUT Install in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/sut-install/m-p/7099125#M25464</link>
    <description>&lt;P&gt;I have a Oneview (OV) system that is running 5.00.01. I am trying to utilize OV "profiles" to apply SPP to my BL460c Gen 10 blades. I have done this process before many times successfully. I am using the SUT drivers (2.5.5) at the OS level to upgrade my HP driver set. When I run "SUT /Deploy" or "SUT /DeployReboot" on a Windows 2016 server, I keep getting "NO action needed, firmware deployment request and ILo task queue both are empty".&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if I run a SUT /STATUS, it tells me I need several updates that are based on the baseline I selected in OV. I am getting these same messages on multiple servers of various Gens. I get the yellow OV status of "&lt;SPAN&gt;One or more firmware components are inconsistent with the specified firmware baseline.".&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;Any help would be great!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks Scott&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Aug 2020 21:41:36 GMT</pubDate>
    <dc:creator>Scott Caryer</dc:creator>
    <dc:date>2020-08-24T21:41:36Z</dc:date>
    <item>
      <title>SUT Install</title>
      <link>https://community.hpe.com/t5/bladesystem-general/sut-install/m-p/7099125#M25464</link>
      <description>&lt;P&gt;I have a Oneview (OV) system that is running 5.00.01. I am trying to utilize OV "profiles" to apply SPP to my BL460c Gen 10 blades. I have done this process before many times successfully. I am using the SUT drivers (2.5.5) at the OS level to upgrade my HP driver set. When I run "SUT /Deploy" or "SUT /DeployReboot" on a Windows 2016 server, I keep getting "NO action needed, firmware deployment request and ILo task queue both are empty".&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, if I run a SUT /STATUS, it tells me I need several updates that are based on the baseline I selected in OV. I am getting these same messages on multiple servers of various Gens. I get the yellow OV status of "&lt;SPAN&gt;One or more firmware components are inconsistent with the specified firmware baseline.".&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;Any help would be great!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks Scott&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Aug 2020 21:41:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/sut-install/m-p/7099125#M25464</guid>
      <dc:creator>Scott Caryer</dc:creator>
      <dc:date>2020-08-24T21:41:36Z</dc:date>
    </item>
    <item>
      <title>Re: SUT Install</title>
      <link>https://community.hpe.com/t5/bladesystem-general/sut-install/m-p/7099402#M25465</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;Scott,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;After you install iSUT, the default mode of iSUT is set to OnDemand mode. During every SPP upgrade, iSUT self-upgrades itself if the version of iSUT found in SPP is higher. During self-upgrade, iSUT configurations such as mode are retained. You can change the iSUT mode to an auto mode after a&amp;nbsp;successful iSUT installation. To do so, use the following command:&lt;/P&gt;&lt;P&gt;sut –set mode=&amp;lt;OnDemand/AutoStage/AutoDeploy/AutoDeployReboot&amp;gt;&lt;/P&gt;&lt;P&gt;Will you please try by change the sut mode to AutoDeployReboot using below command.&lt;/P&gt;&lt;P&gt;sut –set mode=AutoDeployReboot&lt;/P&gt;</description>
      <pubDate>Wed, 26 Aug 2020 12:43:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/sut-install/m-p/7099402#M25465</guid>
      <dc:creator>AmRa</dc:creator>
      <dc:date>2020-08-26T12:43:09Z</dc:date>
    </item>
  </channel>
</rss>

