Study guide

12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation

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

12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation

Key Takeaways Explain This Topic AI

Network Visualizer renders the end-to-end path from a VM through its virtual NIC, virtual switch, and host uplink to the physical switch port it lands on.

Physical switch visibility depends on LLDP for topology discovery and SNMP for port statistics, so a switch must be added to Prism before its ports can be monitored.

Network Visualizer is a Prism Central capability and is used for troubleshooting and verification rather than for configuration.

Network segmentation isolates management, backplane, and other traffic types onto separate VLANs or interfaces so storage replication does not share a broadcast domain with user traffic.

Objective 2.2 lists describing Network Visualizer and monitoring physical switches as two distinct knowledge statements.

Last updated: September 2026

12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation

Sections 7.1 to 7.3 covered how AHV networking is built. This section covers how you see it, which is what Objective 2.2 asks for in its last two knowledge statements.

The Problem Network Visualizer Solves

When an application team reports a network problem, the administrator has to reason across a chain that spans two teams' equipment: VM → vNIC → subnet/VLAN → virtual switch → bond → host uplink NIC → cable → physical switch port

Historically, the Nutanix administrator could see the left-hand side and the network team could see the right-hand side, and the join between them was a conversation. Network Visualizer renders the whole chain in one view.

What it shows

Each VM and its virtual NICs.

The subnet or VLAN each vNIC uses.

The virtual switch carrying the traffic.

The host uplinks and the bond they belong to.

The physical switch and switch port each uplink connects to.

Typical uses: confirming that a host's two uplinks actually land on two different physical switches rather than both on one — a redundancy assumption that is wrong more often than anyone expects; tracing which switch port to examine when a VM has connectivity problems; and verifying a cabling change matches the design.

Important

Network Visualizer is a Prism Central feature, and it is for visibility and troubleshooting , not configuration. You do not create subnets or virtual switches in it. If an exam option describes configuring networking through Network Visualizer, that option is wrong.

Monitoring Physical Switches

For the physical half of that picture to appear, the cluster must learn about the switches. Two protocols do the work, and knowing which does what is the examinable detail:

Protocol What it provides

LLDP (Link Layer Discovery Protocol) Topology discovery — which switch and which port each host uplink is connected to. Neighbours advertise their identity, so the host learns what is on the other end of the cable.

SNMP Port statistics and status — throughput, errors, discards, and link state on the switch ports.

The workflow, corresponding to the blueprint reference "Creating a Network Switch":

Enable LLDP on the physical switches so uplink neighbours are discoverable.

Add the switch in Prism with its address and SNMP credentials — a community string for v2c, or a user with authentication and privacy for v3.

Prism then collects port statistics and correlates them with the host uplinks LLDP identified.

The payoff is diagnostic. When a VM has intermittent packet loss, you can see error and discard counters climbing on the specific switch port carrying its traffic, in the same console as the VM — instead of raising a ticket and waiting for someone else to look.

Tip

Remember the split: LLDP tells you what is connected where . SNMP tells you how that connection is behaving . Questions about discovering topology point to LLDP; questions about port counters and statistics point to SNMP.

Network Segmentation

Objective 2.2 also asks you to "identify types of networking," and the blueprint reference list includes Network Segmentation . It answers a different question from managed versus unmanaged networks (section 7.3) — not how guest VMs get addresses , but whether different kinds of cluster traffic share a network .

By default, several traffic types can share the same network:

Management traffic — Prism, SSH, and API calls.

Backplane traffic — CVM-to-CVM communication, including RF replication writes and rebuild traffic.

Guest VM traffic — the workloads themselves.

Optionally Volumes traffic , and disaster recovery replication to a remote site.

Network segmentation separates these onto distinct VLANs or distinct physical interfaces . Two motivations:

Security. Backplane traffic is the cluster's internal storage conversation. It should not be reachable from a general user VLAN.

Performance and predictability. A node rebuild after a drive failure generates significant replication traffic. Kept on its own segment, that burst cannot contend with production application traffic.

At NCA level, recognize what it is and why it is done . Designing a segmentation scheme is professional-level work.

Putting the Three Together

  • Requirement Answer
  • See the full path from a VM to a physical switch port Network Visualizer in Prism Central
  • Discover which switch port a host uplink connects to LLDP
  • See throughput, errors, and discards on that port SNMP , after adding the switch in Prism
  • Keep storage replication traffic off the user VLAN Network segmentation
  • Give guest VMs IP addresses from Nutanix Managed network with IPAM (section 7.3)

Loading diagram... Network Visualizer: The Chain from VM to Physical Switch Port