<?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 If you have NTP and other in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866798#M40333</link>
    <description>&lt;P&gt;If you have NTP and other basic stuff configured fine. You can quickly reload the Secondary PAN and PRI MNT. We could have looked at the logs but I'm sure the replication logging components were not set to DEBUG level.&lt;/P&gt;
&lt;P&gt;~ Jatin&lt;/P&gt;</description>
    <pubDate>Thu, 18 Feb 2016 14:18:56 GMT</pubDate>
    <dc:creator>Jatin Katyal</dc:creator>
    <dc:date>2016-02-18T14:18:56Z</dc:date>
    <item>
      <title>ISE Distributed Node Registration Issue - "Registration Failed" Status</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866795#M40330</link>
      <description>&lt;P&gt;I have a distributed ISE 2.0 deployment with 6 nodes (2 X PAN, 2 X MNT, 2 X PSN), there is no firewall in the middle. I have successfully added all 5 nodes into the PRI PAN and all the messages show successfully added for each of them.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;However, after Sync, the Secondary PAN and PRI MNT's Node Status showing Yellow triangle and the "Registration Failed". The option "Syncup" is also disabled. All other 3 nodes show green square "Connected".&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;They have the same config and are added the same way. What could be the problem. Please help.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:30:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866795#M40330</guid>
      <dc:creator>zma</dc:creator>
      <dc:date>2019-03-11T06:30:09Z</dc:date>
    </item>
    <item>
      <title>What version of ISE?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866796#M40331</link>
      <description>&lt;P&gt;What version of ISE?&lt;/P&gt;
&lt;P&gt;SSH to the CLI. &amp;nbsp;Can you ping each node from each other?&lt;/P&gt;
&lt;P&gt;Are there forward and reverse DNS entries for all nodes?&lt;/P&gt;
&lt;P&gt;Are the timezones for all nodes the same and is the NTP server the same and all node times synchronized?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2016 03:19:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866796#M40331</guid>
      <dc:creator>jj27</dc:creator>
      <dc:date>2016-02-18T03:19:54Z</dc:date>
    </item>
    <item>
      <title>They are ISE 2.0. Network</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866797#M40332</link>
      <description>&lt;P&gt;They are ISE 2.0. Network connectivity is all fine, ping or SSH no problem. I did miss DNS initially and ISE would not allow any node to be added without DNS. So I added DNS entries and they all got added successfully. But I do not have reverse DNS entries, not really sure if they are needed or not. They are all configured in the same timezone with same NTP servers. I will check the NTP status tomorrow.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2016 06:16:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866797#M40332</guid>
      <dc:creator>zma</dc:creator>
      <dc:date>2016-02-18T06:16:50Z</dc:date>
    </item>
    <item>
      <title>If you have NTP and other</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866798#M40333</link>
      <description>&lt;P&gt;If you have NTP and other basic stuff configured fine. You can quickly reload the Secondary PAN and PRI MNT. We could have looked at the logs but I'm sure the replication logging components were not set to DEBUG level.&lt;/P&gt;
&lt;P&gt;~ Jatin&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2016 14:18:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866798#M40333</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2016-02-18T14:18:56Z</dc:date>
    </item>
    <item>
      <title>It's required for those DNS</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866799#M40334</link>
      <description>&lt;P&gt;It's required for those DNS entries to be there. Not sure it is your problem, but definitely required.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/ise/2-0/admin_guide/b_ise_admin_guide_20/b_ise_admin_guide_20_chapter_010.html#ID209"&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/2-0/admin_guide/b_ise_admin_guide_20/b_ise_admin_guide_20_chapter_010.html#ID209&lt;/A&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;Configure the Reverse DNS lookup for all Cisco ISE nodes in your distributed deployment in the DNS server. Otherwise, you may run into deployment related issues when registering Cisco ISE nodes, and restarting Cisco ISE nodes.&lt;/PRE&gt;</description>
      <pubDate>Thu, 18 Feb 2016 14:19:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-distributed-node-registration-issue-quot-registration-failed/m-p/2866799#M40334</guid>
      <dc:creator>jj27</dc:creator>
      <dc:date>2016-02-18T14:19:07Z</dc:date>
    </item>
  </channel>
</rss>

