An administrator renames a production cluster from 'Prod-01' to 'Prod-Core' via Prism Element to align with a new naming convention. Several hours later, Prism Central stops reporting metrics for this cluster, and LCM cannot push updates to it. The cluster nodes are healthy, and SSH access to the CVMs works. What is the most likely cause of this management-plane disruption?
Select an answer to reveal the explanation.
Short Explanation
Think of the cluster name like your nickname, but the UUID is your Social Security Number. Prism Central and LCM don't care what you call yourself; they track you by that immutable ID. If a rename process messes with that underlying identity link, the management plane loses sight of the cluster entirely. You can't just re-register it and hope for the best; you have to fix the identity sync.
Full Explanation
In Nutanix architectures, the cluster UUID serves as the immutable identifier for all management-plane components, including Prism Central (PC) and the Life Cycle Manager (LCM). While the cluster name is a mutable display attribute, the UUID anchors the trust relationship and data association between CVMs and the management plane. If a rename operation disrupts the synchronization of this UUID or corrupts the metadata mapping, PC and LCM can no longer authenticate or associate telemetry and updates with the correct cluster entity. This leads to the observed silence in metrics and updates. The first distractor is incorrect because renaming a cluster does not trigger a CVM reboot; CVMs remain active during metadata updates. The second distractor is wrong because Prism Central automatically discovers and updates cluster metadata changes via periodic polling; manual re-registration is not required for a simple rename. The third distractor is inaccurate because Stargate is a data-plane service for I/O pathing; a rename does not inherently cause a Stargate restart that would block management APIs handled by the Prism Gateway. Exam caveat: Always distinguish between mutable display attributes and immutable identity keys when troubleshooting management plane connectivity. Operational check: Verify the cluster UUID consistency between Prism Element and Prism Central using the API or CLI before attempting any remediation steps.