<?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 Re: Synchronize database into Cisco ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/synchronize-database-into-cisco-ise/m-p/3812479#M484699</link>
    <description>&lt;P&gt;When you register a secondary PAN node to your initial PRIMARY PAN node, then you are creating a deployment (ISE Cube).&amp;nbsp; That has the built in effect that the Secondary PAN will be kept in sync with the Primary PAN.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The issue you're describing seems to be with the secondary PAN registration.&amp;nbsp; If you don't have certificate trust&amp;nbsp; between the two servers then the registration will fail.&lt;/P&gt;
&lt;P&gt;The cleanest way to make this happen is to create Admin certs from a common PKI (e.g. your internal Windows CA Server).&amp;nbsp; &amp;nbsp;Then install the PKI CA cert chain on ALL of your ISE nodes.&amp;nbsp; Then import the ISE Admin to each node (or if you created a CSR per node, then simply bind the cert from your PKI back to each node).&lt;/P&gt;
&lt;P&gt;Then when you register node 02 to node 01, the node 01 will trust the cert of node 02 because the node 02 cert was issued by a CA that is in node 01's trust store.&lt;/P&gt;
&lt;P&gt;Don't be tempted to import each other's ISE self-signed Admin cert - that's the quick and dirty (and lazy) approach.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 01 Mar 2019 12:46:33 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2019-03-01T12:46:33Z</dc:date>
    <item>
      <title>Synchronize database into Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/synchronize-database-into-cisco-ise/m-p/3812324#M484696</link>
      <description>&lt;P&gt;Hello guys,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a problem...&lt;/P&gt;&lt;P&gt;I need to create a synchronize database betewen two serveur ISE (ISE1 Primary server and ISE2 secondary server).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;More precisely, i&amp;nbsp;would like the identities&amp;nbsp; create on my ISE1 server to be automatically replicated to the ISE2 server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have already imported the certificates and activated the option "&lt;EM&gt;Trust for authentication within ISE&lt;/EM&gt;" But an error message occurs....&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;"Unable to authenticate ISE SGISE02.tiretech.contiwan.com. Please check server and CA certificate configuration and make sure 'Trust for authentication within ISE' option is selected."&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Thx you....&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 07:37:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/synchronize-database-into-cisco-ise/m-p/3812324#M484696</guid>
      <dc:creator>Etlicher</dc:creator>
      <dc:date>2019-03-01T07:37:08Z</dc:date>
    </item>
    <item>
      <title>Re: Synchronize database into Cisco ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/synchronize-database-into-cisco-ise/m-p/3812479#M484699</link>
      <description>&lt;P&gt;When you register a secondary PAN node to your initial PRIMARY PAN node, then you are creating a deployment (ISE Cube).&amp;nbsp; That has the built in effect that the Secondary PAN will be kept in sync with the Primary PAN.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The issue you're describing seems to be with the secondary PAN registration.&amp;nbsp; If you don't have certificate trust&amp;nbsp; between the two servers then the registration will fail.&lt;/P&gt;
&lt;P&gt;The cleanest way to make this happen is to create Admin certs from a common PKI (e.g. your internal Windows CA Server).&amp;nbsp; &amp;nbsp;Then install the PKI CA cert chain on ALL of your ISE nodes.&amp;nbsp; Then import the ISE Admin to each node (or if you created a CSR per node, then simply bind the cert from your PKI back to each node).&lt;/P&gt;
&lt;P&gt;Then when you register node 02 to node 01, the node 01 will trust the cert of node 02 because the node 02 cert was issued by a CA that is in node 01's trust store.&lt;/P&gt;
&lt;P&gt;Don't be tempted to import each other's ISE self-signed Admin cert - that's the quick and dirty (and lazy) approach.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Mar 2019 12:46:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/synchronize-database-into-cisco-ise/m-p/3812479#M484699</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-03-01T12:46:33Z</dc:date>
    </item>
  </channel>
</rss>

