<?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: p-class enclosure problems in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174281#M32466</link>
    <description>are u discovering server ip's and iLO ips both of pclass servers?</description>
    <pubDate>Sat, 05 Apr 2008 08:43:26 GMT</pubDate>
    <dc:creator>Change_happens</dc:creator>
    <dc:date>2008-04-05T08:43:26Z</dc:date>
    <item>
      <title>p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174280#M32465</link>
      <description>HP sim shows the enclosure, but won't populate it with any blades. Rack and blade firmware are all at current levels. All ILOs have been discovered. Oddly enough, all the blades, except one, used to show up in the enclosure. But, for other reasons, I deleted all discovered systems and started over. Everything was re-discovered ok, except for the p-class enclosure. It was discovered, but shows health status as unknown, and is empty. The c-class and blades therein came back fine. Not sure what I missed on the p-class? I deleted it several times and rediscovered,but same result each time.</description>
      <pubDate>Fri, 04 Apr 2008 16:41:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174280#M32465</guid>
      <dc:creator>Joel Coulson</dc:creator>
      <dc:date>2008-04-04T16:41:49Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174281#M32466</link>
      <description>are u discovering server ip's and iLO ips both of pclass servers?</description>
      <pubDate>Sat, 05 Apr 2008 08:43:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174281#M32466</guid>
      <dc:creator>Change_happens</dc:creator>
      <dc:date>2008-04-05T08:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174282#M32467</link>
      <description>I'm discovering the ILO IPs and currently only two of the blade server IPs. Previously, I discovered only the ILO range. When it was working, discovering only the ILO range popluated the enclosure. HP sim knew there was stuff there, but without discovering the server IPs, it didn't know anything about them except blade model and stuff it could get from the ILO. No clue why it won't populate now based on just the ILO IPs as it did before.</description>
      <pubDate>Mon, 07 Apr 2008 11:01:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174282#M32467</guid>
      <dc:creator>Joel Coulson</dc:creator>
      <dc:date>2008-04-07T11:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174283#M32468</link>
      <description>ur iLO's are association with ur servers after discovering blade IPs?</description>
      <pubDate>Mon, 07 Apr 2008 12:43:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174283#M32468</guid>
      <dc:creator>Change_happens</dc:creator>
      <dc:date>2008-04-07T12:43:15Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174284#M32469</link>
      <description>a) Did you checked "Discover server when its Mp is discovered" option in "Discovery settings" in discovery page. This will create logical blades and associate it with its MP when the MP is discovered.&lt;BR /&gt;b) Make sure iLO gives a proper xml reply http://iloIP/xmldata?ietm=all&lt;BR /&gt;c)Now when you discover the server with its IP address, SIM would associate it with the iLO depending on its serial number thats obtained from SNMP support on the server, so make sure SNMP settings are enabled on the managed node [SNMP service is running , and "Accepts SNMP packets from all hosts" is enabled].&lt;BR /&gt;d) Make sure the server has a unique UUID configured .&lt;BR /&gt;e) Make sure the server UUID matches with that returned from iLO XML query.&lt;BR /&gt;&lt;BR /&gt;Hope this will solve your problem.&lt;BR /&gt;Thanks&lt;BR /&gt;Deepak</description>
      <pubDate>Mon, 07 Apr 2008 15:32:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174284#M32469</guid>
      <dc:creator>V Deepak Kumar</dc:creator>
      <dc:date>2008-04-07T15:32:19Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174285#M32470</link>
      <description>maybe we are getting to the root of the problem. Of 12 blades, only 5 have a UUID listed in the ILO server status page. I was unable to get any xml replies. No errors, just IE cannot display the webpage. Sounds like I have some work to do. Where should I start.</description>
      <pubDate>Mon, 07 Apr 2008 16:48:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174285#M32470</guid>
      <dc:creator>Joel Coulson</dc:creator>
      <dc:date>2008-04-07T16:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174286#M32471</link>
      <description>See if iLO has got old firmware? upgrade to latest and check reply. &lt;BR /&gt;If they still didn't show the UUID this may happen ur server dont have that then u have to set it manually by going into BIOS just make sure uniqueness.&lt;BR /&gt;&lt;BR /&gt;I am sure by upgrading to iLO will solve ur issue it looks old or corrupted f/w of iLO.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Ajay</description>
      <pubDate>Tue, 08 Apr 2008 04:44:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174286#M32471</guid>
      <dc:creator>Change_happens</dc:creator>
      <dc:date>2008-04-08T04:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174287#M32472</link>
      <description>The attached doc has the details on setting UUID on server and enable XML replies on the ILO. Hope this helps.&lt;BR /&gt;Thanks&lt;BR /&gt;Deepak</description>
      <pubDate>Wed, 09 Apr 2008 08:33:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174287#M32472</guid>
      <dc:creator>V Deepak Kumar</dc:creator>
      <dc:date>2008-04-09T08:33:38Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174288#M32473</link>
      <description>I tried to narrow the scope to see if I can pinpoint the issue. Reinstalled SIM and created new DB. discovered only the leftmost ILO and its associated server, with same result:&lt;BR /&gt;&lt;BR /&gt;BL25p firmware 1.91&lt;BR /&gt;P-class enclosure firmware 2.40&lt;BR /&gt;Has UUID and does get xml reply&lt;BR /&gt;&lt;BR /&gt;still I get only the attached.</description>
      <pubDate>Wed, 09 Apr 2008 16:41:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174288#M32473</guid>
      <dc:creator>Joel Coulson</dc:creator>
      <dc:date>2008-04-09T16:41:12Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174289#M32474</link>
      <description>Ok,&lt;BR /&gt;1) Is the ILO associated with the server?&lt;BR /&gt;2) Is the server associated with the enclosure?&lt;BR /&gt;3) Once the server is associated with the iLO, for a server to comeup in picture its solt number [You can check that in system page , association section of server]. Slot information is picked from SNMP support on the server. So make sure &lt;BR /&gt;a) SNMP service is running on the server. and make sure the server setting "Accept SNMP packets from all hosts" is enabled.&lt;BR /&gt;b) SNMP community string is public&lt;BR /&gt;c) Servers have latest PSP versions&lt;BR /&gt;Slot information is picked from OID : 1.3.6.1.4.1.232.22.2.4.1.1.1.8&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;Thanks&lt;BR /&gt;Deepak</description>
      <pubDate>Thu, 10 Apr 2008 07:42:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174289#M32474</guid>
      <dc:creator>V Deepak Kumar</dc:creator>
      <dc:date>2008-04-10T07:42:24Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174290#M32475</link>
      <description>Did the solution worked?&lt;BR /&gt;Thanks&lt;BR /&gt;Deepak</description>
      <pubDate>Fri, 11 Apr 2008 13:20:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174290#M32475</guid>
      <dc:creator>V Deepak Kumar</dc:creator>
      <dc:date>2008-04-11T13:20:55Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174291#M32476</link>
      <description>Hi Joel,&lt;BR /&gt;&lt;BR /&gt;Did you discover the ILO with the option "Discover the Server when its Integrated Lights out is discovered"?&lt;BR /&gt;&lt;BR /&gt;The Status is empty/disabled, because the physical server(IP's) are not discovered or properly associated to the enclosure.&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Apr 2008 10:51:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174291#M32476</guid>
      <dc:creator>asc_3</dc:creator>
      <dc:date>2008-04-17T10:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174292#M32477</link>
      <description>sorry, was out on vacation. I do have the option check to automatically discover server when ilo discovered. I've deleted and rediscovered many times. Lastly, I've deleted everything and discovered only 1 ilo in the enclosure. SIM sees the enclosure, knows its a P-class. However, it does not see a Rack. the rack only shows up if I discover something in the c-class enclosure, which shares the rack with the p-class. should sim be able to detect the rack with my discovery of just one ILO? I do see a rack name in the xml reply if the discovered ILO.</description>
      <pubDate>Tue, 22 Apr 2008 17:48:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174292#M32477</guid>
      <dc:creator>Joel Coulson</dc:creator>
      <dc:date>2008-04-22T17:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174293#M32478</link>
      <description>I should have noticed this earlier, but enclosure2 is unnamed and has no serial number (see attached), which is probably why sim is not seeing it. To rememdy this, I ssh'd into the ilo and tried to put serial numbers with SET ENCLOSURE SERIAL_NUMBER "&lt;SERIAL&gt;" command, got the following errors. I attempted to put in a 10-digit number per the instructions. Here is a example of what happens. I've tried various formats&lt;BR /&gt;&lt;BR /&gt;hpiLO-&amp;gt; SET ENCLOSURE SERIAL_NUMBER 9872345098&lt;BR /&gt;status=2&lt;BR /&gt;status_tag=COMMAND PROCESSING FAILED&lt;BR /&gt;error_tag=COMMAND ERROR-UNSPECIFIED&lt;BR /&gt;Invalid target.&lt;BR /&gt;&lt;/SERIAL&gt;</description>
      <pubDate>Wed, 23 Apr 2008 11:53:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174293#M32478</guid>
      <dc:creator>Joel Coulson</dc:creator>
      <dc:date>2008-04-23T11:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: p-class enclosure problems</title>
      <link>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174294#M32479</link>
      <description>set /map1/blade/rack/enclosure(N)/ser=9872345098&lt;BR /&gt;&lt;BR /&gt;Should work!</description>
      <pubDate>Fri, 16 May 2008 13:03:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/p-class-enclosure-problems/m-p/4174294#M32479</guid>
      <dc:creator>Change_happens</dc:creator>
      <dc:date>2008-05-16T13:03:33Z</dc:date>
    </item>
  </channel>
</rss>

