Prism central unreachable

i  have tried to restart the PCVM also i restarted all the services but the issue still occurs

Hello,

This kb is worth a look.

https://portal.nutanix.com/page/documents/kbs/details?targetId=kA07V000000H7fVSAS

Is this a single node scale out configuration?

When you deployed did you use the default domain name?

hello Kcmount

i have tried the solution in this kb but server si still not reachable however all services are up

its a single node

also i have used the default domain name

Hey thanks.

Does the name resolution work for the hostname?

iam-proxy.ntnx-base.prism-central.cluster.local

I've not tested this (but can tomorrow I'm just quoting from https://portal.nutanix.com/page/documents/kbs/details?targetId=kA0VO0000001Wtt0AE though not the same)

yes i know its not the same but also i have tested this but the commands listed in that kb is not working in my PC 

Which command?

I'm specifically interested in whether your pc can resolve the hostname iam-proxy.ntnx-base.prism-central.cluster.local I suspect that's relevant to the error message.

I can test similar on my pc tomorrow to see whether the resolution is direct on the pc or within a container.

Sorry I'm not in front of one right now to confirm.

If this is on a supported cluster rather than CE it would be worth giving support a call it'll be quicker troubleshooting 

Hello Kcmount,

Yes issue is that it cannot resolve iam-proxy.ntnx-base.prism-central.cluster.local

nutanix@NTNX-192-168-39-42-A-PCVM:~$ curl --insecure -X GET -H "Content-Type: application/json" --key /home/certs/APLOSService/APLOSService.key --cert /home/certs/APLOSService/APLOSService.crt https://iam-proxy.ntnx-base:8445/api/iam/v4.0.a2/authn/federation
curl: (6) Could not resolve host: iam-proxy.ntnx-base

I followed KB https://portal.nutanix.com/page/documents/kbs/details?targetId=kA0VO0000002Njh0AE by editing dnsmasq.conf with the IP of prism central but same issue.

Any advise how can we check this please?

Check the prism central services using 

cluster status