<?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: IML log how to mark repaired? in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6208407#M19231</link>
    <description>&lt;P&gt;This has been an irritation for me as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The capability to&amp;nbsp;mark events as repaired in the IML was apparently a new feature introduced with the ILO3's (HP types please correct me if I'm wrong on that).&amp;nbsp; Blades (and towers and rackmounts, for that matter)&amp;nbsp;before the G7's all had ILO2's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ILO2's (and earlier) you had to clear the IML entirely, and frankly, sometimes I like to have the history.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2013 13:01:16 GMT</pubDate>
    <dc:creator>Ken Krubsack</dc:creator>
    <dc:date>2013-09-18T13:01:16Z</dc:date>
    <item>
      <title>IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6208129#M19229</link>
      <description>&lt;P&gt;I have c7000 Blade Enclosure and some BL460cG1 and BL460cG6 blade servers.&lt;BR /&gt;Servers&amp;nbsp;have ESX 4 installed without HP Management Agents on them.&lt;/P&gt;&lt;P&gt;Looking through ILO on IML log of server I found some errors showing predictive failure of drives. I replaced drives that were in predictive failure state and they are now OK. The problem is that failures in log are not marked repaired.&lt;/P&gt;&lt;P&gt;I'm trying to mark some items repaired but only thing that I can do is go to ILO web management and clear whole IML log. Does anyone knows how to mark all entries repaired insted of cleaning IML log?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2013 08:05:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6208129#M19229</guid>
      <dc:creator>Alien_ri</dc:creator>
      <dc:date>2013-09-18T08:05:40Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6208407#M19231</link>
      <description>&lt;P&gt;This has been an irritation for me as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The capability to&amp;nbsp;mark events as repaired in the IML was apparently a new feature introduced with the ILO3's (HP types please correct me if I'm wrong on that).&amp;nbsp; Blades (and towers and rackmounts, for that matter)&amp;nbsp;before the G7's all had ILO2's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ILO2's (and earlier) you had to clear the IML entirely, and frankly, sometimes I like to have the history.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2013 13:01:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6208407#M19231</guid>
      <dc:creator>Ken Krubsack</dc:creator>
      <dc:date>2013-09-18T13:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6209671#M19234</link>
      <description>&lt;P&gt;I checked on one of my BL460cG7 servers that has ILO3.&lt;BR /&gt;Same situation. Unable to mark as read.&lt;BR /&gt;But on BL460cGen8 that has ILO4, &amp;nbsp;I was able to mark some items as read.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Seems like it's by design. ;)&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2013 11:48:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6209671#M19234</guid>
      <dc:creator>Alien_ri</dc:creator>
      <dc:date>2013-09-19T11:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6209701#M19235</link>
      <description>&lt;P&gt;Alien_ri,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On a G7 (ILO3) I should think you should be able to mark IML events repaired.&amp;nbsp; I can on every ILO3 we have (and that's in the hundreds).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check the rights you assigned the user you're logging in as and verify the firmware level of the ILO3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ken&lt;/P&gt;</description>
      <pubDate>Thu, 19 Sep 2013 12:14:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6209701#M19235</guid>
      <dc:creator>Ken Krubsack</dc:creator>
      <dc:date>2013-09-19T12:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6512982#M19556</link>
      <description>&lt;P&gt;It is possible to mark a IML entry as repaired from the host OS with hplog/hpasmcli like so&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;# show log entry numbers
hplog -v

# mark entry number as repaired
hpasmcli -s "REPAIR IML 30"&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Tested on a Linux server with iLO2.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jun 2014 22:35:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/6512982#M19556</guid>
      <dc:creator>Michael Leu</dc:creator>
      <dc:date>2014-06-17T22:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7009274#M21210</link>
      <description>&lt;P&gt;Now we have ILO5 and Gen10. Hp-health and hpasmcli are not supported anymore.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are back to the problem on how to set ILO IML logs to repaired from CLI.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone had any luck with it on HP Gen10 servers?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 13:37:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7009274#M21210</guid>
      <dc:creator>GregCabaj</dc:creator>
      <dc:date>2018-06-19T13:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7009309#M21211</link>
      <description>&lt;P&gt;From another customer inquiry, I had a discussion with the tools group about not being able&amp;nbsp;to do this from a CLI tool anymore.&amp;nbsp; They are now aware of the issue and looking to add this capability into the RESTful tool in the future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 19:56:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7009309#M21211</guid>
      <dc:creator>Jimmy Vance</dc:creator>
      <dc:date>2018-06-19T19:56:28Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7048767#M21664</link>
      <description>&lt;P&gt;Use RestFull api with powershell:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;Param(
    $server,
    $username,
    $password
)

#Check if Rest Ilo tools are installed
if (Test-Path "C:\Program Files\Hewlett Packard Enterprise\RESTful Interface Tool\ilorest.exe") {

Write-Host "************* Start checking server $server *************" -ForegroundColor DarkBlue -BackgroundColor Green
#check if Temp folder Exists, if not create the folder.
if (-not (Test-Path "C:\temp")) {New-Item -Path "c:\" -Name "temp" -ItemType "directory"}
#get the IML log from the ilo and place it in the temp folder
cd "C:\Program Files\Hewlett Packard Enterprise\RESTful Interface Tool"
.\ilorest.exe serverlogs --selectlog=IML --url $server -u $username -p $password -f C:\temp\IML_Log.txt
#get the content of the log and covert it into an powershell object
$entrysjson = get-content C:\temp\IML_Log.txt
$entrys = ConvertFrom-Json -InputObject $entrysjson
#process each log entry seperatly
foreach ($entry in $entrys) {
#ignore if log entry is repaired or repair option does not apply.
#if ignore rule does not apply, report server and message information
if ($entry.Oem.Hpe.Repaired -notlike $null -and $entry.Oem.Hpe.Repaired -notlike "True")
{#reset the IML log entry
.\ilorest.exe serverlogs --selectlog=IML -r $entry.Id
Write-host "Marked Repaired for server: $server Entry: "$entry.Message}
}}&lt;/PRE&gt;</description>
      <pubDate>Tue, 04 Jun 2019 08:56:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7048767#M21664</guid>
      <dc:creator>Ziglar</dc:creator>
      <dc:date>2019-06-04T08:56:51Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7087625#M22156</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i´m on the same subject, i tried the IML Log Repair Command in PS &amp;amp; iLORest CMD : &lt;FONT&gt;&lt;STRONG&gt;iLOrest &amp;gt; serverlogs --selectlog=IML -r 36&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;...and it failes with : &lt;STRONG&gt;"&lt;FONT&gt;iLO response with code [400]: An unknown property is in the request body"&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Why? I cant see the issue... can some one help me out...&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arthur&lt;/P&gt;</description>
      <pubDate>Mon, 11 May 2020 10:22:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7087625#M22156</guid>
      <dc:creator>Arthur_</dc:creator>
      <dc:date>2020-05-11T10:22:53Z</dc:date>
    </item>
    <item>
      <title>Re: IML log how to mark repaired?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7088893#M22177</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You can try the below customer advisory, If you are facing the issue with ILO5.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Advisory: HPE Integrated Lights-Out 5 (iLO 5) - iLOrest il clone Command Does Not Load all Settings on iLO 5 Firmware Version 1.40 (or Later)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=emr_na-a00066421en_us" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=emr_na-a00066421en_us&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;If you feel this was helpful please click the&lt;/STRONG&gt;&amp;nbsp;&lt;STRONG&gt;KUDOS!&amp;nbsp;&lt;/STRONG&gt;&lt;STRONG&gt;thumb below!&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2020 03:58:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/iml-log-how-to-mark-repaired/m-p/7088893#M22177</guid>
      <dc:creator>SanjeevGoyal</dc:creator>
      <dc:date>2020-05-23T03:58:11Z</dc:date>
    </item>
  </channel>
</rss>

