Load average over 5 Minutes = #load_average_5min@, number of vCPUs in CVM or Prism Central VM = num_procs. Timed out waiting for Partner Server/Notification Policy creation. Note: With NCC 3.9.3, this check has been enabled on Prism Central. Failed to add file server record in ElasticSearch index, exception details can be seen in API logs. If the new/changed NTP server is not listed in the output of the above command then check genesis.out for problems grep -i ntp data/logs/genesis.out 8. Nutanix supports user authentication using Local settings that use the local authentication provided by Nutanix. Impact: Prism Central may run out of disk space to store data. Failed to update service in Analytics user1).And The Directory Service setting that use Microsoft Active directory to validates users accounts. The next step is to login to Next server. The proxy is not reachable. Please configure name server". No.#1 Build a new Nutanix cluster with at least 3 nodesIf you are planning to create new Nutanix cluster required at least three nodes for RF-2 clusterMake sure that all the CVMs, Nodes and IPMI IP addresses are reachable or ping able to each other. Every VM must have a UUID; ESXi hosts should be reachable from Nutanix Move on ports TCP 443 and TCP 902. Check that Prism Central VM CPU load is not high. Request was accepted by File Server to create a partner server/notification policy, but the entity was not created. Alert message: The PC does not have enough storage for the number of VM entities it has. If the check reports a FAIL status indicating that Nutanix Files Server is unreachable, ensure through Prism that all Nutanix Files VMs are up and running. Failed to save File Server. Alert and Event Monitoring | Prism Web Console Guide | Prism | 374 Nutanix Guest Tools Agent is not reachable on the VM [130081] [A130081] Name VSS VM Reachable Description VssVmNotReachable Alert message VM(s) vm_names Guest Agent Service is not reachable, protected by protection_domain_name. Issue following commands of any controller VM (CVM) cvm$> cluster… Output messaging Cause: The CPU load on the Prism Central VM has been high. Further trouble shooting showed me that the time of the CVM and the PC is wrong. it says " could not reach NEXT server. But this time it did not work. Checks if the amount of storage is sufficient for the number of VM entities in Prism Central. Note, setting up authentication is a requirement if you would like to use the Self Service features within Prism Central. The port specified on the proxy is not reachable. 7. This method is employed when a user enters just a login name without specifying a domain (e.g. This lesson will show you how to setup Prism Central authentication using Active Directory on Nutanix AOS 5.5. Hosts must not be in maintenance mode. Cause: Too many VMs in Prism Central for the amount of storage in Prism Central. The ESXi hosts must have complete configuration details of the VMs. vCenter is reachable from Move on port TCP 443. If the check reports a FAIL status indicating that FSVM hardware clock timezone is set to a non-UTC value , change the FSVM hwclock back to UTC as specified in KB 6559 . The credentials specified are not valid or wrong. Last time when I got this error, I had to edit the Hosts file and enter the IP address of My.Nutanix.com in that file. Check the CVMs for time skew (NOTE: If greater than 5sec difference see Nutanix KB1429 or … Alert message: CPU load in or Prism Central VM ip_address is high. Resolution "nutanix.com" is not reachable through the proxy. Configuring Prism Central Authentication. Cause The communication link to the VMs Nutanix Guest Agent service … The VMs must be compatible with the multiple snapshots taken by Move.