Hi Giuseppe,
To convert or resize Prism Central (PC) is not officially supported through any automated or native in-place tool or button inside Prism Central itself.
Here’s a vendor-aligned solution path you should follow:
Vendor-Supported Method to Resize Prism Central (PC):
This process involves deploying a new PC of the desired size and migrating functionality to it.
Step-by-Step Process:
- Back up the existing Prism Central
- Use a recent snapshot or perform full VM backup (agentless or agent-based) using your enterprise backup solution.
- Refer to your DR strategy if PC is part of one (e.g., DR plans in Leap).
- Deploy a new Prism Central VM
- Use the Prism Central deployment wizard (via Prism Element or Foundation Central).
- During deployment, choose the desired size profile:
- Small, Medium, or Large (depending on cluster scale and service requirements).
- Ensure network settings match your environment (VLANs, IPAM, routing, etc.).
- Unregister the old Prism Central
- If this is a standalone or test environment and no services (e.g., Calm, Flow, DR plans, NCC) are attached, unregister the old instance cleanly.
- Otherwise, proceed to the next step before decommissioning.
- Re-register Clusters to the New PC
- From each Prism Element UI, go to Settings > Prism Central Registration.
- Unregister from the old PC, then register with the new one.
- Confirm PC-PE sync is healthy (Services, Inventory, Alerts, etc.).
- Migrate Services (if applicable)
- If you were using Calm, Flow, LCM management, or Xi Leap, reconfigure or reimport configurations as needed.
- For Flow, export policies and reapply.
- For Calm or NCM Self-Service, export Blueprints and Projects.
- Decommission the old PC VM
- Once validation is complete and all dependencies are redirected to the new PC, power off and remove the old VM.
- Clean up DNS and IP references.
Important:
- In-place resizing (increasing vCPU or RAM) of Prism Central is not officially supported and may break functionality or invalidate support unless it matches a valid PC size class (e.g., from Small to Medium profile requirements).
- Always validate with
prism_central --version and ensure compatibility with managed cluster versions. - Monitor the new PC's health using
ncli, prism_central_cli, or via Alerts.