Study guide

11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown

Nutanix Certified Associate NCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Nutanix Cloud Platform & HCI Foundations

1.1 Nutanix NCA Exam Overview, Format, and Objectives 1.2 Hyperconverged Infrastructure (HCI) vs. Traditional 3-Tier Architecture 1.3 The Nutanix Enterprise Cloud Portfolio (NCI, NUS, NCM, EUC, NC2)

2 Chapter 2: Platform Architecture & Distributed Core Services

2.1 Hardware Building Blocks: Nodes, Blocks, Clusters, and Quorum 2.2 Controller VM (CVM) Architecture, Datapath, and Autopathing 2.3 Core Distributed Services: Cassandra, Stargate, Curator, Zookeeper, and Genesis

3 Chapter 3: Prism Administration & Cluster Operations

3.1 Prism Element vs. Prism Central Architecture and Interface Navigation 3.2 Entity Management, Categories, and Role-Based Access Control 3.3 Nutanix Licensing Tiers, Add-ons, and Pulse Telemetry

4 Chapter 4: AOS Distributed Storage Fabric & Data Placement

4.1 Storage Pools, Storage Containers, and vDisk Virtual Architecture 4.2 Redundancy Factor (RF2 vs. RF3), Failure Domains, and Fault Tolerance 4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

5 Chapter 5: Storage Optimization & Business Continuity

5.1 Storage Efficiency: Compression, Deduplication, and Erasure Coding (EC-X) 5.2 Space-Efficient Redirect-on-Write (ROW) Snapshots and Zero-Byte Clones 5.3 Protection Domains, Consistency Groups, and Disaster Recovery Replication

6 Chapter 6: AHV Virtual Machine Lifecycle Management

6.1 AHV VM Provisioning, Resource Allocation (vCPU, vRAM, Disks), and Boot Types 6.2 Nutanix Image Service and Virtual Machine Templates 6.3 Nutanix Guest Tools (NGT) Architecture, Features, and Deployment 6.4 AHV High Availability (HA), Acropolis Dynamic Scheduling (ADS), and Affinity Rules

7 Chapter 7: AHV Networking & Flow Security Fundamentals

7.1 AHV Virtual Networking Architecture, Open vSwitch (OVS), and Bridges 7.2 Host Network Uplinks, Virtual Switch Configuration, and NIC Bonding Modes 7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM 7.4 Nutanix Flow Network Security & Microsegmentation Fundamentals

8 Chapter 8: Cluster Maintenance, Health Monitoring & Support

8.1 Nutanix Cluster Health Monitoring, Alerts, and Events Engine 8.2 Nutanix Cluster Check (NCC) Architecture and Execution 8.3 Life Cycle Manager (LCM) and Rolling Non-Disruptive Upgrades 8.4 Nutanix Support Ecosystem: Diagnostics, Log Gathering, and Support Bundles

9 Chapter 9: Recognizing Nutanix Solutions, Hypervisors & the Product Portfolio

9.1 Supported Hypervisors for NCI and Feature Supportability 9.2 NCI Core Components, Configurations, and Common Deployment Scenarios 9.3 Nutanix Unified Storage: Files, Objects, and Volumes Use Cases 9.4 Nutanix Database Service (NDB) and Database Automation 9.5 Nutanix Kubernetes Platform, Enterprise AI, and End-User Computing

10 Chapter 10: Nutanix Tools — Migration, Deployment, and Validation

10.1 Nutanix Move: Cross-Hypervisor and Cloud Migration 10.2 Foundation and Foundation Central: Imaging and Cluster Deployment 10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

11 Chapter 11: Cluster Configuration, Security & Hardware Maintenance

11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP 11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin 11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown 11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities 11.5 Out-of-Band Management and Remote Console Access

12 Chapter 12: Storage, Network, and Software Administration Tasks

12.1 Volume Groups, vDisk Placement, and Live vDisk Migration 12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation 12.3 The Software Compatibility Matrix and Upgrade Path Planning 12.4 Taking and Managing VM Snapshots in Prism 12.5 License Operations: State, Assignment, Reclamation, and Expiry

13 Chapter 13: Performance Analysis, Reporting & Support Operations

13.1 Prism Analysis: Metric Charts, Entity Charts, and Custom Reports 13.2 Custom Alert Policies and Behavioural Anomaly Detection 13.3 Interpreting Workload Performance: CPU Contention, CPU Ready, Memory, and I/O Latency 13.4 Creating Support Cases, Required Documentation, and Insights

11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown

Key Takeaways Explain This Topic AI

Placing an AHV node into maintenance mode live migrates its highly available VMs to other hosts and powers off pinned and RF1 VMs that cannot be migrated.

Entering maintenance mode from Prism puts both the AHV host and its CVM into maintenance mode; the CLI additionally allows the host to be maintained while the CVM stays in the cluster.

Placing a node into maintenance mode does not automatically shut down the AHV host — that is a separate, deliberate step.

Only one node should be in maintenance mode at a time on an RF2 cluster, because the cluster is already down one copy of its data.

A full cluster shutdown means powering off guest VMs first, then stopping the cluster, then shutting down the CVMs and hosts, in that order.

Last updated: September 2026

11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown

"Place a node into or out of maintenance mode" is the first knowledge statement under Objective 3.2, and it is the single most common planned operational task an associate-level administrator performs. Anything that requires a host to stop running workloads — replacing a failed DIMM, reseating a NIC, a manual firmware update, physically moving a node — begins here.

What Maintenance Mode Does

Maintenance mode tells the cluster: stop scheduling work on this node, and move what is already there . On AHV, entering maintenance mode through Prism produces the following sequence:

The AHV host begins entering maintenance mode.

Guest VMs are evacuated. Highly available VMs are live migrated to other hosts in the cluster. VMs that cannot be migrated are powered off — specifically pinned VMs (those bound to this host by an affinity rule) and RF1 VMs (whose single data copy lives on this node).

The AHV host enters maintenance mode.

The CVM enters maintenance mode , so the cluster stops directing storage work to it and its services are gracefully taken out of the data path.

Important

Not everything live migrates. Pinned VMs and RF1 VMs are powered off, not moved. If an exam scenario says an administrator entered maintenance mode and a specific VM went down while its neighbours moved cleanly, the reason is almost always an affinity rule pinning it to that host, or RF1 placement.

Prism vs. the Command Line

Nutanix recommends using the Prism web console to place nodes into maintenance mode, and that is the answer to give unless a question specifically asks about CLI capability.

The distinction worth knowing:

Path Behaviour

Prism Element / Prism Central Evacuates VMs, puts the AHV host and its CVM into maintenance mode together. The recommended method.

Command line Can put the AHV host into maintenance mode while leaving the CVM up and operational in the cluster . This option is not available in Prism.

That CLI-only capability exists because the two roles are genuinely separable: the host runs guest VMs, while the CVM contributes storage services. Work on the hypervisor need not always remove a node's storage contribution.

The Host Is Not Shut Down Automatically

A detail that catches people out regardless of which method they used: placing a node into maintenance mode does not power off the AHV host. Maintenance mode evacuates and isolates the node logically. If the physical work requires the server to be off, shutting it down is a separate, deliberate action taken after maintenance mode is established.

The correct order for physical work on a node is therefore:

Enter maintenance mode and confirm the VMs have evacuated.

Shut down the CVM and then the host, if the task requires power off.

Perform the physical work.

Power the host back on and let the CVM start.

Exit maintenance mode.

Confirm cluster health and data resiliency have returned to normal before touching another node.

One Node at a Time

On an RF2 cluster, a node in maintenance mode means the cluster is already operating without one copy of some data. Taking a second node out at the same time risks data unavailability.

The discipline:

Work on one node at a time.

Confirm the cluster has returned to full resiliency — the Prism data resiliency status — before starting the next node.

This is exactly what LCM does automatically during a rolling upgrade, which is why LCM is the right tool for software and firmware updates rather than a manual node-by-node procedure.

Shutting Down an Entire Cluster

Occasionally a whole cluster must go down — a planned power event, a datacenter move. Order matters, because the cluster must stop serving storage after its consumers have stopped using it:

Gracefully shut down all guest VMs. Anything still running is still writing.

Stop the cluster , which stops the AOS services across the CVMs.

Shut down the CVMs.

Shut down the hypervisor hosts.

Bringing it back is the reverse: power on the hosts, let the CVMs boot, start the cluster, confirm services are up and health is green, then power on guest VMs.

Warning

Do not stop the cluster while guest VMs are still running. Removing storage from beneath live workloads is how filesystems get corrupted. Shut the workloads down first, every time.

Exiting Maintenance Mode

Exiting is as important as entering, and easier to forget. A node left in maintenance mode contributes nothing: it hosts no VMs and its CVM is out of the data path, so the cluster is quietly running with less capacity and less resiliency than it appears to have. After exiting, the AHV host is once again a scheduling target — and because VMs are not automatically migrated back, the cluster may be unbalanced until Acropolis Dynamic Scheduling redistributes load.

Loading diagram... Maintenance Mode Sequence and Cluster Shutdown Order