<?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 External Managed DHCP in Server Clustering</title>
    <link>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6835192#M615</link>
    <description>&lt;P&gt;My organization will not allow my department to manage our own DHCP server. However i would like to use HP CMU. Does anybody have experience in using an externally managed DHCP server that points to CMU in the "next-server" entry? If so, is that all that is needed or should we also ask that a filename record also be added to the DCHP pool options?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
    <pubDate>Mon, 22 Feb 2016 20:21:13 GMT</pubDate>
    <dc:creator>wilsonc</dc:creator>
    <dc:date>2016-02-22T20:21:13Z</dc:date>
    <item>
      <title>External Managed DHCP</title>
      <link>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6835192#M615</link>
      <description>&lt;P&gt;My organization will not allow my department to manage our own DHCP server. However i would like to use HP CMU. Does anybody have experience in using an externally managed DHCP server that points to CMU in the "next-server" entry? If so, is that all that is needed or should we also ask that a filename record also be added to the DCHP pool options?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2016 20:21:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6835192#M615</guid>
      <dc:creator>wilsonc</dc:creator>
      <dc:date>2016-02-22T20:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: External Managed DHCP</title>
      <link>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6835677#M616</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;We don't have any customers/users in using externally managed dhcp servers. cmu doesn't support such configuration.&lt;BR /&gt;&lt;BR /&gt;cmu wants dhcp server running on the management node itself.&lt;BR /&gt;&lt;BR /&gt;During netboot,backup,cloning,autoinstall&amp;nbsp; operations, cmu writes the node specific entries (mentioned as below) to the dhcpd.conf file on management node.&lt;/P&gt;&lt;P&gt;/etc/dhcpd.conf&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;P&gt;host vito-c7n4 { hardware ethernet d8:9d:67:72:06:6e; fixed-address 172.17.231.28; next-server 172.17.224.4; allow bootp; option host-name "vito-c7n4"; option root-path "172.17.224.4:/opt/cmu/ntbt/rp/x86_64,nfsvers=3,proto=tcp"; }&lt;/P&gt;&lt;P&gt;...&lt;BR /&gt;cmu binds the mac address to the static IP address&amp;nbsp; for that compute node and also writes next-server entries too in dhcpd.conf file on management node.&lt;BR /&gt;&lt;BR /&gt;cmu writes the node entries only when the above operations are performed.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Pradeep A.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Feb 2016 18:28:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6835677#M616</guid>
      <dc:creator>Armugam_Pradeep</dc:creator>
      <dc:date>2016-02-23T18:28:49Z</dc:date>
    </item>
    <item>
      <title>Re: External Managed DHCP</title>
      <link>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6838263#M617</link>
      <description>&lt;P&gt;Thank you for the information. We will have to find a way to get a DHCP helper address in place that points to CMU.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Mar 2016 13:40:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/external-managed-dhcp/m-p/6838263#M617</guid>
      <dc:creator>wilsonc</dc:creator>
      <dc:date>2016-03-02T13:40:56Z</dc:date>
    </item>
  </channel>
</rss>

