<?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 NODE-NOT-REACHABLE on ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180382#M177078</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For out of sync issues, which most likely are due to time changes or NTP&amp;nbsp; sync&lt;/P&gt;&lt;P&gt;issues, you must correct the system time and perform a manual sync up&amp;nbsp; through&lt;/P&gt;&lt;P&gt;the UI.&lt;/P&gt;&lt;P&gt;• For certificate expiry issues, you must install a valid&amp;nbsp; certificate and perform a&lt;/P&gt;&lt;P&gt;manual sync up through the UI.&lt;/P&gt;&lt;P&gt;• For a node that&amp;nbsp; has been down for more than six hours, you must restart the node,&lt;/P&gt;&lt;P&gt;check for&amp;nbsp; connectivity issues, and perform a manual sync up through the&amp;nbsp; UI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 24 Jun 2013 13:24:19 GMT</pubDate>
    <dc:creator>Venkatesh Attuluri</dc:creator>
    <dc:date>2013-06-24T13:24:19Z</dc:date>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180378#M176838</link>
      <description>&lt;P&gt;Primary ISE node (Serving Admin and Monitor personas) is showing two of the PSNs as "NODE-NOT-REACHABLE" under Replication Status on Deployment page on GUI. It can ping the PSNs and PSNs are actually registered to the Primary admin/monitor node. How can I fix this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kashish&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:10:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180378#M176838</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2019-03-11T03:10:43Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180379#M176882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;How does DNS look when resolving all the hosts. Download a support bundle from the administration node and check the ise-psc.log files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Mar 2013 20:31:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180379#M176882</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-03-10T20:31:56Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180380#M176960</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to Tarik's recommendation, can you also tell us if you have a firewall(s) between the different nodes? If yes, do you have the appropriate ports opened?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Mar 2013 03:40:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180380#M176960</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2013-03-11T03:40:17Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180381#M177028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Neno,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no firewall in between. This was working fine all this while and was observed only recently. The effect of this is that a config change done on primary admin/monitor node is not getting reflected on the PSNs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ritika&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Mar 2013 05:27:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180381#M177028</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2013-03-11T05:27:49Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180382#M177078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For out of sync issues, which most likely are due to time changes or NTP&amp;nbsp; sync&lt;/P&gt;&lt;P&gt;issues, you must correct the system time and perform a manual sync up&amp;nbsp; through&lt;/P&gt;&lt;P&gt;the UI.&lt;/P&gt;&lt;P&gt;• For certificate expiry issues, you must install a valid&amp;nbsp; certificate and perform a&lt;/P&gt;&lt;P&gt;manual sync up through the UI.&lt;/P&gt;&lt;P&gt;• For a node that&amp;nbsp; has been down for more than six hours, you must restart the node,&lt;/P&gt;&lt;P&gt;check for&amp;nbsp; connectivity issues, and perform a manual sync up through the&amp;nbsp; UI&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 13:24:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180382#M177078</guid>
      <dc:creator>Venkatesh Attuluri</dc:creator>
      <dc:date>2013-06-24T13:24:19Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180383#M177155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;kashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What version are you currently on, I am seeing this behavior on an ise 1.1.4 environment after doing failover testing. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 14:07:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180383#M177155</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-06-24T14:07:34Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180384#M177234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not 1.1.4..I think we saw this on 1.1.1.xxx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 24 Jun 2013 15:56:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180384#M177234</guid>
      <dc:creator>Kashish_Patel</dc:creator>
      <dc:date>2013-06-24T15:56:15Z</dc:date>
    </item>
    <item>
      <title>NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180385#M177290</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you try de-register and then register again ??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jul 2013 07:38:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180385#M177290</guid>
      <dc:creator>myanznki</dc:creator>
      <dc:date>2013-07-05T07:38:59Z</dc:date>
    </item>
    <item>
      <title>Re:NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180386#M177313</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I found the issue on ny network and it was due to a different dns record.&lt;BR /&gt;&lt;BR /&gt;Simple way to check is issuing a dns lookup from admin node cli of the problem node. Then repeat from problem node attempting to resolve admin node.&lt;BR /&gt;&lt;BR /&gt;Then if that looks good you can issue the command on both nodes...&lt;BR /&gt;&lt;BR /&gt;Show logging application ise tail,&lt;BR /&gt;&lt;BR /&gt;That output should give you a listing of the nodes in the ise deployment and the ip addresses of each node.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Jul 2013 23:56:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/2180386#M177313</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-07-06T23:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: NODE-NOT-REACHABLE on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/5323410#M597922</link>
      <description>&lt;P&gt;Tell me the solution&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Aug 2025 20:51:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/node-not-reachable-on-ise/m-p/5323410#M597922</guid>
      <dc:creator>oa476220</dc:creator>
      <dc:date>2025-08-22T20:51:07Z</dc:date>
    </item>
  </channel>
</rss>

