cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2926
Views
5
Helpful
5
Replies

Alarms: Configured nameserver is down

m.mojas
Level 1
Level 1

Hello!

We have ISE 2.3. Every few hours we get following alarms:

Configured nameserver is down Server=mfcu-ise1

Configured nameserver is down Server=mfcu-ise2

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.

DNS servers are configured on both ISE servers and are working:

ip domain-name carina.local

ip name-server 10.75.9.115 10.75.9.116


mfcu-ise1/admin# nslookup mfcu-ise1

Trying "mfcu-ise1.carina.local"

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14982

;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;mfcu-ise1.carina.local.                IN      ANY

;; ANSWER SECTION:

mfcu-ise1.carina.local. 3600    IN      A       10.75.15.136

Received 56 bytes from 10.75.9.115#53 in 0 ms


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 (https://mfcu-ise2.carina.local) and mfcu-ise1 isn't.

Thank you and best regards,

Maja

1 Accepted Solution

Accepted Solutions

Nidhi
Cisco Employee
Cisco Employee

The nslookup output  looks fine .

You can try restarting the node as well. But we would need further troubleshooting to see why you see this . I would suggest you open a TAC case as well to see if this is due to any issues or bug.


Thanks,

Nidhi

View solution in original post

5 Replies 5

Nidhi
Cisco Employee
Cisco Employee

Hi Maja,

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 ?

Also, please let me know if there is a TAC case opened for this which I can have a look at .

Thanks,

Nidhi

There si no details.

I didn't open a case. I first want to check if answer exists without TAC.

Thank you and regards,

Maja

Nidhi
Cisco Employee
Cisco Employee

The nslookup output  looks fine .

You can try restarting the node as well. But we would need further troubleshooting to see why you see this . I would suggest you open a TAC case as well to see if this is due to any issues or bug.


Thanks,

Nidhi

Restart didn't help. I'll open a TAC case.

Regards,

Maja

hslai
Cisco Employee
Cisco Employee

CSCvh02628 might be related to your issue.