Prism, Lifecycle Management, and Operational Tasks
This section covers Prism, Lifecycle Management, and Operational Tasks: using Prism Element and Prism Central for monitoring and administration, managing tasks and alerts, and using LCM for inventory, firmware, and software lifecycle operations.
Operational rules
- Prism Element is the per-cluster UI and API surface; Prism Central aggregates clusters and adds multi-cluster functions.
- Tasks show asynchronous operations. A failed task often needs the detailed task status, not just the top-level alert.
- Alerts indicate conditions requiring attention; they are not the same as tasks or audit events.
- LCM performs inventory, identifies updates, generates plans, and applies firmware or software updates with prechecks.
- Before lifecycle operations, confirm NCC health, available capacity, and compatibility. LCM is not a backup tool.
Worked example
An administrator needs to update firmware across a cluster. In Prism Central, LCM inventory discovers node models and current firmware. The administrator reviews the generated plan, checks prechecks and maintenance impact, then applies the update. If a precheck fails because a host is unreachable, the correct action is to restore management connectivity and rerun inventory, not to force the plan.
Traps that cost marks
Do not use Prism Central as a requirement for every single-cluster task. Do not confuse an alert with the task that caused it. Do not skip LCM prechecks or assume LCM backs up VM data. Do not apply updates without checking NCC and capacity.