<?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>question Re: what is the procedure to change IP's in amari cluster in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-procedure-to-change-IP-s-in-amari-cluster/m-p/184124#M75651</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Have you followed the steps mentioned in the following article: &lt;A href="https://community.hortonworks.com/content/supportkb/48998/correct-procedure-to-re-ip-a-client-host-in-a-clus.html" target="_blank"&gt;https://community.hortonworks.com/content/supportkb/48998/correct-procedure-to-re-ip-a-client-host-in-a-clus.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This is just to see if by any chance if you might have missed any step. Specially this command should return the new IP address of the node&lt;/P&gt;&lt;PRE&gt;# nslookup nodename.fqdn              &lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Else it might be a DNS cache issue.&lt;/P&gt;</description>
    <pubDate>Mon, 12 Mar 2018 05:26:35 GMT</pubDate>
    <dc:creator>jsensharma</dc:creator>
    <dc:date>2018-03-12T05:26:35Z</dc:date>
    <item>
      <title>what is the procedure to change IP's in amari cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-procedure-to-change-IP-s-in-amari-cluster/m-p/184123#M75650</link>
      <description>&lt;P&gt;we change the IP's of the masters and worker machines and performed service network restart  on each linux machine&lt;/P&gt;&lt;P&gt;then we restart all ambari agent and ambari server but the old IP's are still exists in amabri GUI , why?&lt;/P&gt;&lt;P&gt;what need else to do in order amabri GUI will show the new IP's &lt;/P&gt;</description>
      <pubDate>Sun, 11 Mar 2018 17:37:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-procedure-to-change-IP-s-in-amari-cluster/m-p/184123#M75650</guid>
      <dc:creator>mike_bronson7</dc:creator>
      <dc:date>2018-03-11T17:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: what is the procedure to change IP's in amari cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-procedure-to-change-IP-s-in-amari-cluster/m-p/184124#M75651</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/26229/uribarih.html" nodeid="26229"&gt;@Michael Bronson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Have you followed the steps mentioned in the following article: &lt;A href="https://community.hortonworks.com/content/supportkb/48998/correct-procedure-to-re-ip-a-client-host-in-a-clus.html" target="_blank"&gt;https://community.hortonworks.com/content/supportkb/48998/correct-procedure-to-re-ip-a-client-host-in-a-clus.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This is just to see if by any chance if you might have missed any step. Specially this command should return the new IP address of the node&lt;/P&gt;&lt;PRE&gt;# nslookup nodename.fqdn              &lt;/PRE&gt;&lt;P&gt;.&lt;/P&gt;&lt;P&gt;Else it might be a DNS cache issue.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Mar 2018 05:26:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/what-is-the-procedure-to-change-IP-s-in-amari-cluster/m-p/184124#M75651</guid>
      <dc:creator>jsensharma</dc:creator>
      <dc:date>2018-03-12T05:26:35Z</dc:date>
    </item>
  </channel>
</rss>

