<?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: AD Authentication for RILOE/iLO in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975266#M6163</link>
    <description>There is an iLO Best Practices whitepaper linked below.  You can get to this page from &lt;A href="http://www.hp.com/servers/lights-out" target="_blank"&gt;www.hp.com/servers/lights-out&lt;/A&gt; then Support then Manuals&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lt;/A&gt;〈=en&amp;amp;cc=us&amp;amp;docIndexId=179111&amp;amp;taskId=101&amp;amp;prodTypeId=18964&amp;amp;prodSeriesId=397989&lt;BR /&gt;&lt;BR /&gt;Specifically, within the whitepaper, your concern is discussed on page 23:&lt;BR /&gt;&lt;BR /&gt;Setting up the directory server:&lt;BR /&gt;The directory server field can be configured with a DNS name or an IP address. The DNS name can be the DNS name of a single server or the DNS name of a domain. This field can be configured with multiple IP addresses or DNS names separated with a comma or space.</description>
    <pubDate>Fri, 05 May 2006 09:28:07 GMT</pubDate>
    <dc:creator>acartes</dc:creator>
    <dc:date>2006-05-05T09:28:07Z</dc:date>
    <item>
      <title>AD Authentication for RILOE/iLO</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975262#M6159</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I'm using the HP Lights-out Directories Migration Utility to configure the RILOE/iLO setting. I have a question regarding the section for Directory Server configuration.&lt;BR /&gt;&lt;BR /&gt;Instead of pointing to a DC IP address or the DC FQDN, is there a way to configure for a domain so that there is redundancy and not depends on just ONE DC information?&lt;BR /&gt;&lt;BR /&gt;If the DC failed, we will have problem login to the RILOE/iLOE.&lt;BR /&gt;&lt;BR /&gt;Thanks!!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;BLeng</description>
      <pubDate>Mon, 24 Apr 2006 22:18:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975262#M6159</guid>
      <dc:creator>BeeLeng</dc:creator>
      <dc:date>2006-04-24T22:18:43Z</dc:date>
    </item>
    <item>
      <title>Re: AD Authentication for RILOE/iLO</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975263#M6160</link>
      <description>If you have a multi-homed domain controller- that is, more than one server, you can use the DNS name of the domain controller instead of the IP address.&lt;BR /&gt;&lt;BR /&gt;If one of the domain controllers goes down and iLO tries to access it by name, it fails over to another domain controller.&lt;BR /&gt;&lt;BR /&gt;This is a good practice for robustness.</description>
      <pubDate>Wed, 26 Apr 2006 17:12:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975263#M6160</guid>
      <dc:creator>acartes</dc:creator>
      <dc:date>2006-04-26T17:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: AD Authentication for RILOE/iLO</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975264#M6161</link>
      <description>Thanks Acartes,&lt;BR /&gt;&lt;BR /&gt;First of all, our environment doesn't support multihome Domain Controller.&lt;BR /&gt;&lt;BR /&gt;Furthermore, I understand (pls correct me if I'm wrong) that A "multihomed" domain controller is a computer that has multiple network adapters or that has been configured with multiple IP addresses for a single network adapter. In such case, there is no redundancy when this particular DC is down?&lt;BR /&gt;&lt;BR /&gt;Is it possible to configure the Directory Server section to point to a domain (and it will find the nearest DC to authenticated by itself) or more than 1 DC IP address?&lt;BR /&gt;&lt;BR /&gt;Thanks!!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;BLeng</description>
      <pubDate>Wed, 26 Apr 2006 20:42:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975264#M6161</guid>
      <dc:creator>BeeLeng</dc:creator>
      <dc:date>2006-04-26T20:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: AD Authentication for RILOE/iLO</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975265#M6162</link>
      <description>You should be able to configure iLO to use the domain as opposed to a specific address.  Try this out on a specific iLO first.&lt;BR /&gt;&lt;BR /&gt;When iLO contacts the directory, it performs a DNS lookup on the field entered for the server name.  If DNS returns alternate IPs, then iLO will "fail over" to the next address.</description>
      <pubDate>Fri, 05 May 2006 09:23:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975265#M6162</guid>
      <dc:creator>acartes</dc:creator>
      <dc:date>2006-05-05T09:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: AD Authentication for RILOE/iLO</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975266#M6163</link>
      <description>There is an iLO Best Practices whitepaper linked below.  You can get to this page from &lt;A href="http://www.hp.com/servers/lights-out" target="_blank"&gt;www.hp.com/servers/lights-out&lt;/A&gt; then Support then Manuals&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lt;/A&gt;〈=en&amp;amp;cc=us&amp;amp;docIndexId=179111&amp;amp;taskId=101&amp;amp;prodTypeId=18964&amp;amp;prodSeriesId=397989&lt;BR /&gt;&lt;BR /&gt;Specifically, within the whitepaper, your concern is discussed on page 23:&lt;BR /&gt;&lt;BR /&gt;Setting up the directory server:&lt;BR /&gt;The directory server field can be configured with a DNS name or an IP address. The DNS name can be the DNS name of a single server or the DNS name of a domain. This field can be configured with multiple IP addresses or DNS names separated with a comma or space.</description>
      <pubDate>Fri, 05 May 2006 09:28:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975266#M6163</guid>
      <dc:creator>acartes</dc:creator>
      <dc:date>2006-05-05T09:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: AD Authentication for RILOE/iLO</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975267#M6164</link>
      <description>Hi Acartes,&lt;BR /&gt;&lt;BR /&gt;thank you very much. That's what I'm looking for.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;BLeng</description>
      <pubDate>Sun, 07 May 2006 20:46:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/ad-authentication-for-riloe-ilo/m-p/4975267#M6164</guid>
      <dc:creator>BeeLeng</dc:creator>
      <dc:date>2006-05-07T20:46:41Z</dc:date>
    </item>
  </channel>
</rss>

