Study guide
7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM
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
7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM
Key Takeaways Explain This Topic AI
AHV Virtual Networks establish Layer 2 broadcast domains on virtual switches, where VLAN 0 designates native untagged traffic and VLANs 1 through 4094 implement standard IEEE 802.1Q tagging.
Unmanaged Networks provide traditional Layer 2 bridging, leaving IP address assignment, DHCP services, and lease tracking entirely to external physical or virtual network infrastructure.
Managed Networks utilize Nutanix native IP Address Management (IPAM) embedded directly into the hypervisor OVS layer, intercepting guest DHCP requests locally to eliminate broadcast storms across physical uplinks.
Nutanix IPAM enables administrators to define DHCP pools, default gateways, DNS servers, domain search suffixes, PXE/TFTP boot options, and static IP reservations directly within Prism.
AHV supports live, non-disruptive virtual network modifications, enabling administrators to re-assign a running VM vNIC to a different VLAN or managed network without rebooting the guest OS.
Last updated: September 2026
Virtual Networks: Managed vs. Unmanaged Networks and IPAM
Quick Summary: Virtual networks in Nutanix AHV define the logical broadcast domains, VLAN boundaries, and IP addressing policies for guest virtual machines. Built on top of AHV virtual switches, virtual networks are categorized into two fundamental operational models: Unmanaged Networks (which provide standard Layer 2 bridging, passing all IP assignment and DHCP responsibilities to external network infrastructure) and Managed Networks (which leverage Nutanix native IP Address Management [IPAM] embedded directly inside the hypervisor to provide hypervisor-local DHCP, static IP reservations, and automated guest network provisioning). Mastering these virtual network types, IEEE 802.1Q tagging rules, and live vNIC lifecycle management is essential for architecting enterprise multicloud fabrics.
1. AHV Virtual Network Architecture and VLAN Segmentation
In Nutanix AHV, a Virtual Network represents an isolated logical network segment configured on an underlying virtual switch (such as vs0 / br0 ). When an administrator creates a virtual machine and attaches a virtual network interface card (vNIC), the vNIC is bound to a specific virtual network. +-------------------------------------------------------------------------+
- | AHV Virtual Network Topology |
- | |
- | +-------------------+ +-------------------+ +-------------------+ |
- | | VM-Web-01 | | VM-App-01 | | VM-DB-01 | |
- | | [vNIC: NetA] | | [vNIC: NetB] | | [vNIC: NetC] | |
- | +---------+---------+ +---------+---------+ +---------+---------+ |
- | | | | |
- | v v v |
- | (VLAN 10 Tag) (VLAN 20 Tag) (VLAN 0 Untagged) |
- | +-----------------------------------------------------------------+ |
- | | Virtual Switch: vs0 (Bridge br0) | |
- | | - Open vSwitch manages 802.1Q tagging and untagging | |
- | | - Strips VLAN headers on ingress to VM vNIC (Access Mode) | |
- | | - Injects VLAN headers on egress to physical uplinks | |
- | +--------------------------------+--------------------------------+ |
- | | |
- | v |
- | [ Bond Interface: br0-up ] |
- | Carries Tagged (802.1Q) and Native Frames |
- +-------------------------------------------------------------------------+
- IEEE 802.1Q VLAN Tagging Rules
Every virtual network in AHV is defined with a specific VLAN ID ranging from 0 to 4094 :
VLAN 0 (Native / Untagged VLAN):
Setting the VLAN ID to 0 designates that traffic exiting the virtual machine must be forwarded across the physical network without an IEEE 802.1Q VLAN tag .
Physical switches receive these frames as native untagged Ethernet frames, typically assigning them to the native VLAN configured on the physical switch port (e.g., PVID 1).
VLAN 0 is commonly used for legacy flat networks, DMZ perimeter networks without 802.1Q trunking, or specific enterprise management segments.
VLAN 1 through 4094 (Tagged VLANs):
Assigning a VLAN ID between 1 and 4094 configures standard 802.1Q VLAN tagging.
Access Port Emulation (Default): The virtual machine operating system remains completely unaware of the VLAN tag. The guest OS transmits standard untagged Ethernet frames. When the frame enters the AHV virtual switch tap interface, OVS automatically tags the frame with the configured VLAN ID before sending it across br0-up . Conversely, incoming frames arriving from physical switches have their 802.1Q tags stripped by OVS before being handed to the guest vNIC.
VLAN Trunking to Guest VM: For specialized virtual appliances that require multi-VLAN visibility (such as virtual routers, firewalls, or container host nodes), AHV supports vNIC VLAN trunking. Using the Acropolis Command-Line Interface ( acli ), administrators can expose multiple tagged VLANs directly to a single guest vNIC: # Expose multiple VLANs (e.g., 10, 20, 30) to a virtual appliance vNIC
- acli vm.nic_create <vm-name> network=<network-name> trunked_networks=10,20,30
- 2. Unmanaged Networks: Traditional Layer 2 Bridging
An Unmanaged Network in Nutanix AHV functions as a pure Layer 2 virtual bridge. +-------------------------------------------------------------------------+
- | Unmanaged Network Model |
- | |
- | +-------------------+ +-------------------+ |
- | | AHV Host | | Physical Switch | |
- | | | | | |
- | | +-------------+ | Broadcast / DHCP Req | +-------------+ | |
- | | | Guest VM |==|========================>| | External | | |
- | | | [vNIC: L2] |<=|=========================|==| DHCP Server | | |
- | | +-------------+ | Unicast DHCP Ack | +-------------+ | |
- | | | | (e.g., Infoblox/ | |
- | | (No Nutanix IPAM)| | Active Dir.) | |
- | +-------------------+ +-------------------+ |
- +-------------------------------------------------------------------------+
- Operational Characteristics of Unmanaged Networks
External IP Lifecycle: AHV does not participate in IP address assignment, subnet routing, or lease management. IP configuration is handled entirely by external datacenter infrastructure—such as an enterprise Windows DHCP server, Infoblox appliance, or manual static IP assignment inside the guest OS.
Pass-Through Forwarding: OVS forwards all broadcast, multicast, and unicast traffic transparently between the guest VM vNIC and the physical ToR switches based purely on MAC address learning tables.
Prism IP Address Discovery: Because AHV does not assign the IP address, Prism relies on secondary discovery mechanisms to report the VM's IP address in the Prism dashboard:
Nutanix Guest Tools (NGT): The NGT guest agent queries the guest OS network stack directly and reports assigned IPv4/IPv6 addresses securely back to the CVM via TCP port 2074.
Hypervisor ARP Snooping: If NGT is not installed, OVS snoops Address Resolution Protocol (ARP) reply frames emitted by the guest VM and populates Prism with the discovered IP address.
When to Select Unmanaged Networks
Environments with strict, centralized external IPAM architectures (e.g., Infoblox, BlueCat, EfficientIP).
Subnets where specialized DHCP options (such as custom VoIP phone boot scopes or dynamic DNS updates) are already managed by corporate infrastructure.
Production clusters where guest VM IP addresses are statically assigned and audited through enterprise configuration management tools (Ansible, Puppet, Terraform).
3. Managed Networks: Nutanix Native IPAM
A Managed Network activates the built-in Nutanix IP Address Management (IPAM) engine embedded directly into the AHV hypervisor and Acropolis control plane. +-------------------------------------------------------------------------+
- | Managed Network Model |
- | |
- | +-----------------------------------------------------------------+ |
- | | AHV Physical Host | |
- | | | |
- | | +-------------+ DHCP Discover | |
- | | | Guest VM |---------------------------+ | |
- | | | [vNIC] |<-----------------------+ | | |
- | | +-------------+ DHCP Offer / Ack | | | |
- | | | v | |
- | | +--------------------------------------+------------------+ | |
- | | | Nutanix Hypervisor-Level IPAM | | |
- | | | - OVS intercepts DHCP requests locally at vnet tap | | |
- | | | - ZERO DHCP broadcast traffic sent to physical uplinks | | |
- | | | - Deterministic IP assignment from defined pool | | |
- | | +---------------------------------------------------------+ | |
- | +-----------------------------------------------------------------+ |
- | |
- | Physical Datacenter Network (Completely isolated from DHCP chatter) |
- +-------------------------------------------------------------------------+
- How Hypervisor-Level DHCP Interception Works
In standard networks, when a newly provisioned virtual machine powers on, its operating system broadcasts a DHCPDISCOVER packet across the Layer 2 network ( 255.255.255.255:67 ). In large virtualized environments with hundreds of VMs, simultaneous boot storms generate significant broadcast traffic.
In a Nutanix Managed Network:
Local Interception: The OVS flow table on the local AHV host detects the outgoing DHCP broadcast frame directly at the guest VM's virtual tap interface.
Hypervisor-Level DHCP Server: Rather than forwarding the broadcast frame out through physical uplinks, OVS diverts the packet to a localized hypervisor DHCP responder daemon managed by Acropolis.
Zero Broadcast Storms: The local hypervisor evaluates the managed subnet configuration, selects an available IP address from the designated pool, generates a standard DHCPOFFER / DHCPACK , and transmits it directly back to the guest vNIC.
Physical Network Isolation: Zero DHCP broadcast traffic escapes onto the physical ToR switches. IP assignment occurs in milliseconds, even if physical network uplinks are disconnected or undergoing spanning-tree convergence.
Managed Network Configuration Parameters
When creating a Managed Network in Prism Element or Prism Central, administrators define comprehensive network properties:
- Configuration Parameter Description Practical Example
- Network Name & VLAN Logical identifier and 802.1Q tag VLAN-120-AppTier (VLAN 120 )
- Network IP / Prefix Subnet network address and CIDR mask 10.10.120.0 / 24 (255.255.255.0)
- Default Gateway IP Upstream router IP for outbound routing 10.10.120.1
- DHCP Address Pool Contiguous range for dynamic allocation 10.10.120.50 through 10.10.120.200
- Domain Name / Suffix Search domain injected into guest DNS resolver corp.nutanix.internal
- DNS Server Addresses Primary and secondary DNS resolvers 10.10.10.10 , 10.10.10.11
TFTP / Boot Server (PXE) Next Server IP and Boot File Name for network provisioning Next Server: 10.10.120.20 , File: pxelinux.0
Static IP Reservations via Prism
Nutanix IPAM provides powerful governance through Static IP Reservations :
Administrators can allocate specific, permanent IP addresses to critical workloads (such as Active Directory Domain Controllers, Oracle databases, or SAP application servers) directly within Prism.
When the VM requests an IP via DHCP, Nutanix IPAM identifies the VM's virtual NIC MAC address and returns the statically reserved IP address every time.
This achieves the operational stability of static IP addressing without requiring administrators to manually log into individual guest operating systems to configure static network properties.
4. Managed vs. Unmanaged Networks: Comprehensive Comparison
- Feature / Capability Unmanaged Network Managed Network (Nutanix IPAM)
- Primary Function Standard Layer 2 VLAN Bridging L2 Bridging + Hypervisor L3 IPAM
- DHCP Service Location External physical/virtual DHCP server Native AHV Hypervisor / OVS Responder
- Physical Broadcast Impact DHCP broadcasts flood physical uplinks Zero DHCP broadcast egress to physical wire
- Static IP Reservations Configured in external DHCP or inside guest Managed natively via Prism UI / CLI / API
Network Boot (PXE / TFTP) Handled by external DHCP options 66/67 Configured natively within Prism subnet settings
- IP Reporting in Prism Learned via NGT agent or hypervisor ARP Tracked authoritatively by Acropolis IPAM
- Subnet Expansion / Pools Modified on external DHCP servers Dynamically adjustable within Prism Central
- Best For Existing corporate DHCP / Infoblox setups Automated provisioning, VDI, Cloud blueprints
- 5. Virtual Network Interface (vNIC) Lifecycle and Live Operations
Nutanix AHV provides advanced flexibility when managing virtual network interfaces throughout a virtual machine's lifecycle. +-------------------------------------------------------------------------+
- | vNIC Lifecycle Operations |
- +-------------------------------------------------------------------------+
- | 1. Dynamic Network Migration: Change VLAN without rebooting guest OS |
- | 2. MAC Address Assignment: Deterministic Nutanix OUI (50:6b:8d) |
- | 3. Hot-Plug Virtual Adapters: Add/remove vNICs on live running VMs |
- | 4. Network Disconnection: Administrative link-state toggling |
- +-------------------------------------------------------------------------+
- MAC Address Architecture
Every virtual network adapter created on AHV is automatically assigned a globally unique Layer 2 hardware address. Nutanix utilizes an IEEE-registered Organizationally Unique Identifier (OUI) prefix: Nutanix MAC Address Format = 50 : 6 b : 8 d : X X : Y Y : Z Z \text{Nutanix MAC Address Format} = \mathbf{50:6b:8d}:XX:YY:ZZ Nutanix MAC Address Format = 50 : 6b : 8d : XX : YY : ZZ
Administrators can also specify a custom MAC address during VM creation if legacy software licensing or network access control (NAC) policies mandate specific hardware identifiers.
Live VLAN Re-assignment (Zero-Downtime Migration)
In legacy virtualization platforms, changing a virtual machine's port group or VLAN often required disconnecting the virtual NIC or restarting the guest operating system. In Nutanix AHV:
An administrator can edit a running virtual machine in Prism and select a completely different virtual network (e.g., transitioning VM-App-01 from VLAN-10-Dev to VLAN-20-Prod ).
Acropolis immediately instructs the local AHV host's ovs-vswitchd daemon to update the OpenFlow VLAN action on the VM's active tap interface.
The guest operating system maintains link state without dropping its virtual adapter . If operating on a managed network, the guest automatically renews its IP configuration or executes a smooth transition without requiring a VM reboot.
Hot-Plugging and Administrative Link States
Hot-Add / Hot-Remove: AHV natively supports adding new vNICs to running virtual machines. Linux and Windows operating systems equipped with Nutanix VirtIO drivers detect newly attached adapters immediately without downtime.
Administrative Disconnection: In Prism, administrators can toggle the Connected state of individual vNICs. Toggling a vNIC to disconnected simulates pulling a physical network patch cable, severing connectivity immediately at the hypervisor tap interface while leaving the virtual hardware attached to the VM.