<?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: Registering of Secondary Fails in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538560#M518500</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Patch 1 did the trick!&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;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Jan 2018 21:46:26 GMT</pubDate>
    <dc:creator>Michael Voity</dc:creator>
    <dc:date>2018-01-22T21:46:26Z</dc:date>
    <item>
      <title>Registering of Secondary Fails</title>
      <link>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538557#M518492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have recently installed 2 New 3515 ISE appliance servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Servers are both running 2.3.0.298.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Admin certs and FQDN names have been configured for both servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Licensing has been done with both s/n's via portal. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have registered and deregistered 3 times and have rebooted the servers in between.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With out opening a tac case,&amp;nbsp; &lt;SPAN style="font-size: 10pt;"&gt;Is there a way to see any logs&amp;nbsp; on why they are failing, &lt;/SPAN&gt;besides&lt;SPAN style="font-size: 10pt;"&gt; the canned error message?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The servers are separated by routed geography.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Michael Voity&lt;/P&gt;&lt;P&gt;University of Vermont &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Jan 2018 18:02:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538557#M518492</guid>
      <dc:creator>Michael Voity</dc:creator>
      <dc:date>2018-01-21T18:02:15Z</dc:date>
    </item>
    <item>
      <title>Re: Registering of Secondary Fails</title>
      <link>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538558#M518496</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if this would help but did you trying installing patch 1 on both nodes then join them together?&amp;nbsp; Everything is NTP synced correctly?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 19:48:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538558#M518496</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-01-22T19:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Registering of Secondary Fails</title>
      <link>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538559#M518498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I will try Patch 1,&amp;nbsp;&amp;nbsp; These are brand new out of the box.&amp;nbsp;&amp;nbsp; NTP is setup correctly.&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;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 20:24:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538559#M518498</guid>
      <dc:creator>Michael Voity</dc:creator>
      <dc:date>2018-01-22T20:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: Registering of Secondary Fails</title>
      <link>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538560#M518500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Patch 1 did the trick!&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;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 21:46:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538560#M518500</guid>
      <dc:creator>Michael Voity</dc:creator>
      <dc:date>2018-01-22T21:46:26Z</dc:date>
    </item>
    <item>
      <title>Re: Registering of Secondary Fails</title>
      <link>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538561#M518503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is odd.  I usually apply patch 1 after I get the deployment put together.  Glad it worked.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Jan 2018 21:49:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/registering-of-secondary-fails/m-p/3538561#M518503</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-01-22T21:49:17Z</dc:date>
    </item>
  </channel>
</rss>

