<?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 ISE adding secondary node in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3942078#M542452</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;i have problem with adding secondary node to primary. I can ping them, nslookup on both sides gives me correct entry. I did tcp dump on destination FW, don't see that something is blocking...primary is using 443 port when I try to register secondary node.&lt;/P&gt;&lt;P&gt;PRIMARY:&lt;/P&gt;&lt;P&gt;ise01/admin# nslookup ise02.net.biz&lt;BR /&gt;Trying "ise02.net.biz"&lt;BR /&gt;;; -&amp;gt;&amp;gt;HEADER&amp;lt;&amp;lt;- opcode: QUERY, status: NOERROR, id: 31656&lt;BR /&gt;;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0&lt;/P&gt;&lt;P&gt;;; QUESTION SECTION:&lt;BR /&gt;;ise02.net.biz. IN ANY&lt;/P&gt;&lt;P&gt;;; ANSWER SECTION:&lt;BR /&gt;ise02.net.biz. 3600 IN A 172.28.208.208&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ise01/admin# ping ise02.net.biz&lt;BR /&gt;PING ise021.net.biz (172.28.208.208) 56(84) bytes of data.&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=1 ttl=59 time=25.3 ms&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=2 ttl=59 time=24.7 ms&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=3 ttl=59 time=24.6 ms&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=4 ttl=59 time=25.1 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ise02/admin# nslookup ise01.net.biz&lt;BR /&gt;Trying "ise01.net.biz"&lt;BR /&gt;;; -&amp;gt;&amp;gt;HEADER&amp;lt;&amp;lt;- opcode: QUERY, status: NOERROR, id: 1261&lt;BR /&gt;;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0&lt;/P&gt;&lt;P&gt;;; QUESTION SECTION:&lt;BR /&gt;;ise01.net.biz. IN ANY&lt;/P&gt;&lt;P&gt;;; ANSWER SECTION:&lt;BR /&gt;ise01.net.biz. 293 IN A 10.64.96.96&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ise02/admin# ping ise01.net.biz&lt;BR /&gt;PING ise01.net.biz (10.64.96.96) 56(84) bytes of data.&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=1 ttl=59 time=24.7 ms&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=2 ttl=59 time=24.4 ms&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=3 ttl=59 time=24.5 ms&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=4 ttl=59 time=24.4 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both devices use same version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is message that I'm getting :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="dijitDialog xwtAlert"&gt;&lt;DIV class="containerTable"&gt;&lt;DIV class="middle-center"&gt;&lt;DIV class="dijitDialogPaneContent"&gt;&lt;DIV class="xwtAlert-information"&gt;&lt;DIV&gt;Communication failure with the host ise02.net.biz. Please check the information for the target machine, or if the target machine is accessible and try again.&lt;DIV class="dijitDialog xwtAlert"&gt;&lt;DIV class="containerTable"&gt;&lt;DIV class="middle-center"&gt;&lt;DIV class="dijitDialogPaneContent"&gt;&lt;DIV class="xwtAlert-information"&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Anyone knows what to check next?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;N&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 16 Oct 2019 23:51:20 GMT</pubDate>
    <dc:creator>nenadl</dc:creator>
    <dc:date>2019-10-16T23:51:20Z</dc:date>
    <item>
      <title>ISE adding secondary node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3942078#M542452</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;i have problem with adding secondary node to primary. I can ping them, nslookup on both sides gives me correct entry. I did tcp dump on destination FW, don't see that something is blocking...primary is using 443 port when I try to register secondary node.&lt;/P&gt;&lt;P&gt;PRIMARY:&lt;/P&gt;&lt;P&gt;ise01/admin# nslookup ise02.net.biz&lt;BR /&gt;Trying "ise02.net.biz"&lt;BR /&gt;;; -&amp;gt;&amp;gt;HEADER&amp;lt;&amp;lt;- opcode: QUERY, status: NOERROR, id: 31656&lt;BR /&gt;;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0&lt;/P&gt;&lt;P&gt;;; QUESTION SECTION:&lt;BR /&gt;;ise02.net.biz. IN ANY&lt;/P&gt;&lt;P&gt;;; ANSWER SECTION:&lt;BR /&gt;ise02.net.biz. 3600 IN A 172.28.208.208&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ise01/admin# ping ise02.net.biz&lt;BR /&gt;PING ise021.net.biz (172.28.208.208) 56(84) bytes of data.&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=1 ttl=59 time=25.3 ms&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=2 ttl=59 time=24.7 ms&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=3 ttl=59 time=24.6 ms&lt;BR /&gt;64 bytes from 172.28.208.208: icmp_seq=4 ttl=59 time=25.1 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ise02/admin# nslookup ise01.net.biz&lt;BR /&gt;Trying "ise01.net.biz"&lt;BR /&gt;;; -&amp;gt;&amp;gt;HEADER&amp;lt;&amp;lt;- opcode: QUERY, status: NOERROR, id: 1261&lt;BR /&gt;;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0&lt;/P&gt;&lt;P&gt;;; QUESTION SECTION:&lt;BR /&gt;;ise01.net.biz. IN ANY&lt;/P&gt;&lt;P&gt;;; ANSWER SECTION:&lt;BR /&gt;ise01.net.biz. 293 IN A 10.64.96.96&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;ise02/admin# ping ise01.net.biz&lt;BR /&gt;PING ise01.net.biz (10.64.96.96) 56(84) bytes of data.&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=1 ttl=59 time=24.7 ms&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=2 ttl=59 time=24.4 ms&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=3 ttl=59 time=24.5 ms&lt;BR /&gt;64 bytes from 10.64.96.96: icmp_seq=4 ttl=59 time=24.4 ms&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both devices use same version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is message that I'm getting :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class="dijitDialog xwtAlert"&gt;&lt;DIV class="containerTable"&gt;&lt;DIV class="middle-center"&gt;&lt;DIV class="dijitDialogPaneContent"&gt;&lt;DIV class="xwtAlert-information"&gt;&lt;DIV&gt;Communication failure with the host ise02.net.biz. Please check the information for the target machine, or if the target machine is accessible and try again.&lt;DIV class="dijitDialog xwtAlert"&gt;&lt;DIV class="containerTable"&gt;&lt;DIV class="middle-center"&gt;&lt;DIV class="dijitDialogPaneContent"&gt;&lt;DIV class="xwtAlert-information"&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Anyone knows what to check next?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;N&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 Oct 2019 23:51:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3942078#M542452</guid>
      <dc:creator>nenadl</dc:creator>
      <dc:date>2019-10-16T23:51:20Z</dc:date>
    </item>
    <item>
      <title>Re: ISE adding secondary node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3943159#M542465</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Remember when setting up ISE in distribute mode , both Primary and Secondary PAN need to trust each other aside all that you have confirmed above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Trust between the two PAN is built on certificate (mostly self-signed ). Have you export the default self signed certificate from the Secondary PAN to import into the Primary PAN vice versa . After doing all you mentioned and this , you should be able to add the Secondary PAN to the Primary. But if you are using externally signed certificate , then you have to create CSR to be signed externally ( But why would one need that , this is not externally faced ) , or using your corporate internal CA ( this option is also good because it gives longer expiry which depend on your corporate security polices).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know is this helps&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2019 09:41:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3943159#M542465</guid>
      <dc:creator>Afolarin Omole</dc:creator>
      <dc:date>2019-10-18T09:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: ISE adding secondary node</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3943343#M542489</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;problem was not with certificate. Problem was that on primary I had patch installed which I hadn't on secondary. After removing patch issue was resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;N&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2019 14:32:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-adding-secondary-node/m-p/3943343#M542489</guid>
      <dc:creator>nenadl</dc:creator>
      <dc:date>2019-10-18T14:32:14Z</dc:date>
    </item>
  </channel>
</rss>

