The administrator must first run an LCM inventory. Inventory establishes the cluster's current software and firmware state, refreshes component metadata, and obtains information about compatible updates available through the connected Nutanix source. LCM requires this baseline before it can accurately identify upgrade candidates and construct a valid update plan.
Executing an upgrade immediately is premature because LCM must first know which component versions are installed and which update combinations are supported. The upgrade workflow subsequently performs dependency evaluation and prechecks before applying selected components. Directly uploading software bundles is principally associated with dark-site or disconnected workflows. An Internet-connected cluster can retrieve the required metadata and available bundles through its configured online source. Restarting cluster services is neither the initial preparation step nor a normal manual prerequisite for LCM discovery.
Inventory also refreshes the LCM framework when required and makes the resulting component information available in the management interface. After inventory completes, the administrator reviews available updates, selects applicable components, executes prechecks, resolves reported issues, and then initiates the upgrade plan. This sequence minimizes compatibility and dependency risks.
NHCF/NCA reference: Life Cycle Manager, connected-site operation, inventory, prechecks, and upgrade planning. Official references: Performing LCM Inventory and Pre-Upgrade Configurations and Recommendations .