Study guide
11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP
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.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP
Key Takeaways Explain This Topic AI
Objective 3.1 opens by asking you to verify DNS, SMTP, SNMP, and NTP configurations, which are set in Prism under cluster settings.
Name servers are required for directory integration, LCM downloads, Pulse, and certificate validation; without DNS, features fail in ways that look unrelated to name resolution.
Time synchronization is the highest-consequence setting of the four, because Cassandra, Zookeeper, and directory authentication all depend on consistent cluster time.
Nutanix recommends that CVMs and hypervisor hosts use the same NTP sources, and NCC ships a dedicated check_ntp health check to verify it.
SMTP delivers alert email and is also the transport for Pulse when a direct HTTPS connection is unavailable; SNMP supports v2c and v3 traps to a monitoring platform.
Last updated: September 2026
11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP
Objective 3.1 begins with a single knowledge statement — "verify DNS, SMTP, SNMP, and/or NTP configurations" — that carries far more operational weight than its length suggests. These four settings are configured once, forgotten, and then cause outages that look like something else entirely.
All four are set from Prism Element under the cluster settings gear menu, and the equivalents for Prism Central are set in its own settings area.
Name Servers (DNS)
Configured under Settings → Name Servers , this list tells the CVMs which DNS servers to use.
What depends on it:
Directory services integration. Active Directory or LDAP authentication resolves domain controllers by name. Broken DNS presents as "users cannot log into Prism," which nobody diagnoses as a DNS problem on the first attempt.
Life Cycle Manager downloads. A connected-site LCM inventory reaches Nutanix download endpoints by hostname.
Pulse and Insights. Telemetry upload resolves a Nutanix endpoint.
SMTP, NTP, and syslog targets entered as hostnames rather than IP addresses.
Certificate validation , where hostname matching matters.
Tip
Configure more than one name server. A single DNS entry makes name resolution a single point of failure for authentication, updates, and telemetry all at once.
Time Synchronization (NTP)
Of the four, NTP has the most severe failure mode. Nutanix is a distributed system , and distributed systems reason about ordering using time.
What depends on consistent time:
Cassandra , the distributed metadata store, resolves competing writes with timestamps.
Zookeeper , which manages leadership and locks, depends on consistent timing for lease expiry.
Kerberos and Active Directory authentication , which typically rejects a request whose timestamp is skewed beyond about five minutes.
Certificates , whose validity windows are evaluated against local time.
Alerts, events, and logs , which become impossible to correlate across nodes when clocks disagree.
The guidance to remember
Use the same NTP sources for the CVMs and for the hypervisor hosts. Splitting them is how clusters end up with hosts and CVMs disagreeing about the time.
Configure multiple NTP servers , so the loss of one does not leave the cluster free-running.
In a Windows domain, point at the domain controllers , since that is the time source Kerberos authentication is already measured against.
Prism Central should use the same sources as the clusters it manages.
Verifying it
The blueprint points explicitly at the NCC health check check_ntp . Running it is the fastest way to answer "is time correct across this cluster," and it is the check to name if an exam item asks how you would verify NTP configuration. ncc health_checks network_checks check_ntp
SMTP
Configured under Settings → SMTP Server , this is how the cluster sends mail. It requires the server address, port, and — where the relay demands it — credentials and a security mode.
Two consumers matter:
Alert email. The alert notification policy sends to recipients through this relay. If SMTP is unset, the cluster still raises alerts in Prism but nobody is told about them out of hours. This is the single most common cause of "we never got the alert."
Pulse. When a direct outbound HTTPS connection to Nutanix is not permitted, Pulse can fall back to sending its telemetry by email through the configured SMTP relay.
Prism provides a test email function; using it after configuration is the verification step.
SNMP
Configured under Settings → SNMP , this exposes the cluster to an existing enterprise monitoring platform. Nutanix supports:
SNMP v2c , using a community string.
SNMP v3 , using a user with authentication and privacy — the version to choose when security matters, because v2c community strings cross the network in clear text.
You configure trap receivers so the cluster pushes events to the monitoring system, and Nutanix publishes a MIB that the monitoring platform imports so those traps are interpreted rather than displayed as raw OIDs.
SNMP is an additional notification path, not a replacement for the alert engine. Section 8.1 covers the alert model itself; SNMP is one of the ways alerts leave the cluster.
Verification Checklist
- Setting Where How you verify it
- Name servers Settings → Name Servers Directory logins succeed; LCM inventory completes
- NTP Settings → NTP Servers ncc health_checks network_checks check_ntp
- SMTP Settings → SMTP Server Send a test email from Prism
- SNMP Settings → SNMP Confirm traps arrive at the receiver
Warning
When troubleshooting anything strange on a Nutanix cluster — authentication failures, LCM stalls, certificate errors, metadata inconsistency — check DNS and NTP early. They are cheap to verify and they explain a disproportionate share of confusing symptoms.