<?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: Alarms: Configured nameserver is down in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506733#M519284</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Maja, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This alarm gets generated when the DNS configuration is not appropriate or some network connectivity issue . The alarm might be because of the primary node not being reachable. Can you please open the alarm and check the details ? &lt;/P&gt;&lt;P&gt;Also, please let me know if there is a TAC case opened for this which I can have a look at .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Nidhi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Dec 2017 04:27:43 GMT</pubDate>
    <dc:creator>Nidhi</dc:creator>
    <dc:date>2017-12-08T04:27:43Z</dc:date>
    <item>
      <title>Alarms: Configured nameserver is down</title>
      <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506732#M519280</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Hello!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;We have ISE 2.3. Every few hours we get following alarms: &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Configured nameserver is down Server=mfcu-ise1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Configured nameserver is down Server=mfcu-ise2&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;mfcu-ise1 and mfcu-ise2 are names of the ISE servers itself. mfcu-ise1 is primary, mfcu-ise2 is secondary. Both servers have DNS records.&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;DNS servers are configured on both ISE servers and are working:&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;ip domain-name carina.local&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;ip name-server 10.75.9.115 10.75.9.116 &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;mfcu-ise1/admin# nslookup mfcu-ise1&lt;/P&gt;&lt;P&gt;Trying "mfcu-ise1.carina.local"&lt;/P&gt;&lt;P&gt;;; -&amp;gt;&amp;gt;HEADER&amp;lt;&amp;lt;- opcode: QUERY, status: NOERROR, id: 14982&lt;/P&gt;&lt;P&gt;;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0&lt;/P&gt;&lt;P&gt;;; QUESTION SECTION:&lt;/P&gt;&lt;P&gt;;mfcu-ise1.carina.local.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ANY&lt;/P&gt;&lt;P&gt;;; ANSWER SECTION:&lt;/P&gt;&lt;P&gt;mfcu-ise1.carina.local. 3600&amp;nbsp;&amp;nbsp;&amp;nbsp; IN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; A&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.75.15.136&lt;/P&gt;&lt;P&gt;Received 56 bytes from 10.75.9.115#53 in 0 ms&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Internal DHCP and DNS services aren't configured. Is it the reason why this alarms appear? How to resolve them? Maybe it is connected, maybe not, but mfcu-ise2 GUI is reachable through its name (&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://mfcu-ise2.carina.local" rel="nofollow" target="_blank"&gt;https://mfcu-ise2.carina.local&lt;/A&gt;&lt;SPAN&gt;) and mfcu-ise1 isn't.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you and best regards,&lt;/P&gt;&lt;P&gt;Maja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Dec 2017 08:54:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506732#M519280</guid>
      <dc:creator>m.mojas</dc:creator>
      <dc:date>2017-12-07T08:54:40Z</dc:date>
    </item>
    <item>
      <title>Re: Alarms: Configured nameserver is down</title>
      <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506733#M519284</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Maja, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This alarm gets generated when the DNS configuration is not appropriate or some network connectivity issue . The alarm might be because of the primary node not being reachable. Can you please open the alarm and check the details ? &lt;/P&gt;&lt;P&gt;Also, please let me know if there is a TAC case opened for this which I can have a look at .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Nidhi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Dec 2017 04:27:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506733#M519284</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2017-12-08T04:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: Alarms: Configured nameserver is down</title>
      <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506734#M519289</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There si no details. &lt;/P&gt;&lt;P&gt;I didn't open a case. I first want to check if answer exists without TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you and regards,&lt;/P&gt;&lt;P&gt;Maja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Dec 2017 09:49:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506734#M519289</guid>
      <dc:creator>m.mojas</dc:creator>
      <dc:date>2017-12-08T09:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: Alarms: Configured nameserver is down</title>
      <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506735#M519293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The nslookup output&amp;nbsp; looks fine .&lt;/P&gt;&lt;P&gt;You can try restarting the node as well. But we would need further troubleshooting to see why you see this . &lt;SPAN style="font-size: 10pt;"&gt; I would suggest you open a TAC case as well to see if this is due to any issues or bug.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Nidhi&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Dec 2017 09:57:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506735#M519293</guid>
      <dc:creator>Nidhi</dc:creator>
      <dc:date>2017-12-08T09:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: Alarms: Configured nameserver is down</title>
      <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506736#M519297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Restart didn't help. I'll open a TAC case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Maja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Dec 2017 08:08:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506736#M519297</guid>
      <dc:creator>m.mojas</dc:creator>
      <dc:date>2017-12-15T08:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: Alarms: Configured nameserver is down</title>
      <link>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506737#M519298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CSCvh02628 might be related to your issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Dec 2017 15:59:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/alarms-configured-nameserver-is-down/m-p/3506737#M519298</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-12-15T15:59:33Z</dc:date>
    </item>
  </channel>
</rss>

