<?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 Find-HPiLO bug, for non HPE hardware in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/find-hpilo-bug-for-non-hpe-hardware/m-p/6976008#M7913</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I'm seeing an odd behaviour for the&amp;nbsp;&lt;STRONG&gt;Find-HPiLO&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;cmdlet (&lt;STRONG&gt;v. 1.4.0.2&lt;/STRONG&gt;). When trying to find all remote servers, in a big&amp;nbsp;infrastructure that mixes both HPE and Dell/Lenovo servers, if I execute:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;$ilo = Find-HPiLO 10.10.1-254.40 -Timeout 1000&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I obtain duplicate rows (with same SPN/UUID and SerialNumber of a previously found HP server), when a non-HPE hardware seats at the .40 IP address of a&amp;nbsp;remote subnet.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems the cmdlet still generates an (incorrect) output object, caching a previously found server data.&lt;/P&gt;
&lt;P&gt;Has anybody seen the same beahviour ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;BR /&gt;Claudio&lt;/P&gt;</description>
    <pubDate>Mon, 28 Aug 2017 15:30:00 GMT</pubDate>
    <dc:creator>Ciprandi</dc:creator>
    <dc:date>2017-08-28T15:30:00Z</dc:date>
    <item>
      <title>Find-HPiLO bug, for non HPE hardware</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/find-hpilo-bug-for-non-hpe-hardware/m-p/6976008#M7913</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I'm seeing an odd behaviour for the&amp;nbsp;&lt;STRONG&gt;Find-HPiLO&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;cmdlet (&lt;STRONG&gt;v. 1.4.0.2&lt;/STRONG&gt;). When trying to find all remote servers, in a big&amp;nbsp;infrastructure that mixes both HPE and Dell/Lenovo servers, if I execute:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT face="courier new,courier"&gt;$ilo = Find-HPiLO 10.10.1-254.40 -Timeout 1000&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I obtain duplicate rows (with same SPN/UUID and SerialNumber of a previously found HP server), when a non-HPE hardware seats at the .40 IP address of a&amp;nbsp;remote subnet.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems the cmdlet still generates an (incorrect) output object, caching a previously found server data.&lt;/P&gt;
&lt;P&gt;Has anybody seen the same beahviour ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;BR /&gt;Claudio&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2017 15:30:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/find-hpilo-bug-for-non-hpe-hardware/m-p/6976008#M7913</guid>
      <dc:creator>Ciprandi</dc:creator>
      <dc:date>2017-08-28T15:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: Find-HPiLO bug, for non HPE hardware</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/find-hpilo-bug-for-non-hpe-hardware/m-p/6976389#M7918</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;This is a known issue and fix will be available in the next release i.e., iLO 1.5..0.0 version which will be available probably next week or so on the HPE web.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Gokul&lt;/P&gt;&lt;P&gt;HPE PowerShell Expert Team&lt;/P&gt;</description>
      <pubDate>Tue, 12 Sep 2017 17:24:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/find-hpilo-bug-for-non-hpe-hardware/m-p/6976389#M7918</guid>
      <dc:creator>GokulKS</dc:creator>
      <dc:date>2017-09-12T17:24:11Z</dc:date>
    </item>
  </channel>
</rss>

