I have a cluster consisting of three machines.As you can see in the attached screenshot, on the Prism Element home screen, each resource in the cluster is displayed as "not available.
"The Storage Summary also shows values that differ from actual usage.
I've configured SNMP in Prism Element, and when I use snmpwalk to retrieve values such as hypervisorRxBytes from the monitoring server, the values always show the same.
If you know the cause, please let me know.
Thank you in advance.
Page 1 / 1
Was is always like this or did it just happen?? Can you lcm to 6.10?
Hi JeroenTielen
Thank you for your reply.
I have the same version and the same three-machine configuration in a different environment, and no problems have occurred there.
I don't think it's a version issue.
But was it always like this or did it just happen?
I don't know when this started.
The cluster had previously stopped, so I started it, and received the following error: "Cassandra data files with a future modify time: /home/nutanix/data/stargate-storage/disks/234900014587/metadata/ cassandra/data/default_WAL_keyspace/default_WAL_paxos_cf-j-3544-Filter.db."
NTP wasn't working, and the file timestamp was set to 2037, so I used the touch command to set it to the current date and time. I performed the same process on multiple files under /home/nutanix/data.
The cluster start was successful.
This may have been the trigger.
Wow. Never ever modify files On the cvm or ahv.
make sure dns and ntp are working correctly. The cluster will slowly go to the correct time. And hopefully the info will come back
Butto be honest, I dont know it it will work as you modified system files.
Better is to redeploy the cluster with ce2.1 as you are running a very old version at the moment.
Wow, I made a mistake.
DNS and NTP should be fine now, but the alert "Hardware clock in host ***.***.***.*** has failed" won't go away. The created time is in 2037.
I ran ncc health_checks hypervisor_checks and hwclock_check as per KB2462, but the results were PASS.
If the hardware clock is really broken change the cmos battery on the mainboard and set the time in the bios/uefi correctly.
