{"id":407,"date":"2026-08-31T01:07:17","date_gmt":"2026-08-30T23:07:17","guid":{"rendered":"https:\/\/nutanix.ma\/index.php\/2026\/08\/31\/deploying-prism-central-and-registering-a-cluster-a-field-walkthrough\/"},"modified":"2026-08-31T01:36:43","modified_gmt":"2026-08-30T23:36:43","slug":"deploying-prism-central-and-registering-a-cluster-a-field-walkthrough","status":"publish","type":"post","link":"https:\/\/nutanix.ma\/index.php\/2026\/08\/31\/deploying-prism-central-and-registering-a-cluster-a-field-walkthrough\/","title":{"rendered":"Deploying Prism Central and Registering to a Nutanix Cluster"},"content":{"rendered":"

Prism Central (PC) is Nutanix’s multi-cluster management plane \u2014 it sits above one or more Prism Element clusters and adds fleet-wide dashboards, role-based access, capacity planning, and the automation and lifecycle tooling that Prism Element alone doesn’t provide. On a recent engagement we deployed a new Prism Central instance straight from an existing Prism Element cluster and registered that cluster to it. This post walks through the deployment wizard end to end, the first-run configuration, and connecting the cluster back to its new management plane \u2014 with screenshots from the actual project (customer identifiers and IP addresses have been redacted throughout).<\/p>\n

Kicking off the deployment from Prism Element<\/h2>\n

Every Prism Element cluster ships with a shortcut into Prism Central setup. On the cluster dashboard, the Prism Central<\/strong> panel shows Not Registered<\/em> until the cluster is either connected to an existing PC instance or used to deploy a new one. Clicking through opens a simple choice: deploy a brand new Prism Central instance, or connect to one that’s already running elsewhere.<\/p>\n

\"Prism
Prism Element’s Prism Central panel \u2014 the starting point for either deploying a new PC instance or connecting to one that already exists.<\/figcaption><\/figure>\n

We picked Deploy<\/strong>, which launches a three-step wizard: Version, Size and Scale, and Configuration.<\/p>\n

Step 1 \u2014 Version<\/h2>\n

The wizard asks for a name for the new Prism Central instance and an installation image. Since this environment doesn’t have direct internet access to Nutanix’s portal, we uploaded the installation binary manually from a local machine rather than pulling the latest version automatically. Once the upload finishes, the version shows up in the table as a “User uploaded version” and can be selected to continue.<\/p>\n

\"Uploading
Uploading the Prism Central installation binary \u2014 useful when the cluster can’t reach Nutanix’s portal directly.<\/figcaption><\/figure>\n
\"Prism
With the binary uploaded, pc.7.3.0.5 appears as a selectable version and the new instance is named.<\/figcaption><\/figure>\n

Step 2 \u2014 Size and Scale<\/h2>\n

Prism Central comes in four sizes \u2014 Extra-Small, Small, Large and Extra-Large \u2014 each sized for a maximum number of VMs, clusters and hosts, with the vCPU, memory and disk footprint scaling accordingly. Extra-Small supports up to 500 VMs, 5 clusters and 50 hosts on just 4 vCPUs and 18 GB of memory, which comfortably covers a single-cluster lab or small production environment, so that’s what we chose here. Larger environments would size up to Small or beyond, trading a bigger footprint for headroom to register more clusters and hosts under the same Prism Central.<\/p>\n

\"Prism
Picking a size tier \u2014 Extra-Small was more than enough for this deployment.<\/figcaption><\/figure>\n

Step 3 \u2014 Configuration<\/h2>\n

The last step covers the networking Prism Central will run on: which virtual network to attach to, subnet mask, gateway, DNS and NTP servers, the storage container the PC VM’s disks will live on, and the IP address the new instance will answer on. DNS was pointed at a public resolver and NTP at the regional Nutanix-recommended pool servers, both fine to leave as-is; the network, subnet, gateway and IP address are specific to the target environment and were filled in accordingly. Once everything validates, Deploy<\/strong> kicks off the actual provisioning.<\/p>\n

\"Prism
Networking configuration for the new Prism Central VM before deployment.<\/figcaption><\/figure>\n

Watching the deployment<\/h2>\n

Deployment runs as a background task visible from the Prism Element task tray, with a progress percentage that climbs as the appliance is provisioned, boots, and comes up for the first time. It took a few minutes end to end in this environment.<\/p>\n

\"Prism
Deployment in progress \u2014 roughly halfway through.<\/figcaption><\/figure>\n
\"Prism
Nearing completion \u2014 the new Prism Central VM is almost ready to log into.<\/figcaption><\/figure>\n

First login: password, EULA and Pulse<\/h2>\n

Once deployment finishes, Prism Central is reachable on its own IP address and runs through the same first-run flow as any fresh Nutanix management interface. First, the default admin password has to be changed before anything else is accessible.<\/p>\n

\"Prism
Setting the initial admin password on the freshly deployed Prism Central instance.<\/figcaption><\/figure>\n

Next comes the Nutanix End User License Agreement, which has to be read and accepted before proceeding to the console proper.<\/p>\n

\"Nutanix
Accepting the EULA on first login to the new Prism Central instance.<\/figcaption><\/figure>\n

Finally, Prism Central asks whether to enable Pulse \u2014 Nutanix’s opt-in telemetry service that monitors cluster health and feeds usage data back to Nutanix’s support and analytics pipeline. Leaving it enabled (the default and Nutanix’s recommendation) means faster, more proactive support if something goes wrong later; we kept it on.<\/p>\n

\"Pulse
The Pulse opt-in screen \u2014 telemetry is enabled by default and recommended by Nutanix.<\/figcaption><\/figure>\n

Registering the Prism Element cluster<\/h2>\n

With Prism Central up and running, the last step ties it back to the source cluster. Nutanix’s registration flow is a two-way door: from Prism Element you can either deploy a brand-new PC (what we just did) or connect to a PC instance that already exists \u2014 which is exactly what we did next, pointing this same cluster’s registration flow at the Prism Central instance we’d just deployed rather than treating it as a separate exercise. Before confirming, Prism Element shows a short comparison of what changes after registration: cluster unregistration remains available from both sides (scripted only), while day-to-day self-service management moves to Prism Central.<\/p>\n

\"Prism
Before registering, Prism Element shows what stays available locally versus what moves to Prism Central.<\/figcaption><\/figure>\n

The connection itself just needs the new Prism Central’s IP or FQDN, its management port (9440, same as Prism Element), and a set of admin credentials to authenticate the registration call.<\/p>\n

\"Connect
Supplying the new Prism Central’s IP, port and credentials to complete registration.<\/figcaption><\/figure>\n

Once the registration task completes, the Prism Central panel on the Prism Element dashboard flips from “Not Registered” to Connected<\/strong>, with a link straight through to the new management console.<\/p>\n

\"Prism
Registration complete \u2014 the cluster now shows as connected to its Prism Central instance.<\/figcaption><\/figure>\n

Confirming Pulse on both sides<\/h2>\n

Pulse connectivity is configured independently on Prism Element and on Prism Central’s own Admin Center, so it’s worth checking both after registration. Prism Element’s Settings > Pulse page confirmed a successful connection status.<\/p>\n

\"Prism
Pulse connection status on the Prism Element side \u2014 SUCCESS.<\/figcaption><\/figure>\n

Prism Central’s Admin Center has its own separate Pulse settings page (under Settings, distinct from Prism Element’s), which also reported a healthy connection.<\/p>\n

\"Prism
Pulse status on the Prism Central Admin Center side \u2014 also SUCCESS, confirming telemetry is flowing from both layers.<\/figcaption><\/figure>\n

Wrapping up with an LCM inventory<\/h2>\n

With the cluster registered and Pulse confirmed, the last housekeeping step was a Life Cycle Manager (LCM) inventory run from Prism Central’s Admin Center. LCM tracks firmware and software versions across every registered Prism Element cluster and flags anything that’s fallen behind the latest framework \u2014 in this case prompting an inventory run to bring the newly registered cluster’s LCM framework up to date. Running an inventory here, right after registration, is a good habit: it gives Prism Central an accurate baseline of what’s installed before any future firmware or software upgrades are planned.<\/p>\n

\"Prism
Running an LCM inventory against the newly registered cluster from Prism Central’s Admin Center.<\/figcaption><\/figure>\n

From a single Prism Element cluster with no Prism Central at all, we ended up with a fully deployed PC instance, the cluster registered and reporting healthy telemetry, and an up-to-date LCM inventory ready for future patching \u2014 the whole thing done inside a single browser session, without needing outbound internet access to Nutanix’s portal at any point.<\/p>\n","protected":false},"excerpt":{"rendered":"

Prism Central (PC) is Nutanix’s multi-cluster management plane \u2014 it sits above one or more Prism Element clusters and adds fleet-wide dashboards, role-based access, capacity planning, and the automation and lifecycle tooling that Prism Element alone doesn’t provide. On a recent engagement we deployed a new Prism Central instance straight from an existing Prism Element […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-407","post","type-post","status-publish","format-standard","hentry","category-nutanix"],"_links":{"self":[{"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/posts\/407","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/comments?post=407"}],"version-history":[{"count":1,"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/posts\/407\/revisions"}],"predecessor-version":[{"id":429,"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/posts\/407\/revisions\/429"}],"wp:attachment":[{"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/media?parent=407"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/categories?post=407"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nutanix.ma\/index.php\/wp-json\/wp\/v2\/tags?post=407"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}