Enterprise storage virtualization frequently requires guest virtual machines to connect directly to Fibre Channel Storage Area Networks (SANs) using N_Port ID Virtualization (NPIV). Under Microsoft Hyper-V, Virtual Fibre Channel allows guest operating systems to bypass the hypervisor storage stack and establish direct, unmediated communication with storage arrays, tape libraries, and LUNs. For a virtual machine’s synthetic Fibre Channel host bus adapter (HBA) to register on a physical SAN switch fabric, it requires globally unique 64-bit hardware addresses: a World Wide Node Name (WWNN) and World Wide Port Names (WWPNs). In Windows 11 and Windows Server Hyper-V environments, administrators manage the allocation boundaries of these virtual storage identifiers by configuring host Fibre Channel WWN Pools via PowerShell.
Understanding Hyper-V Virtual Fibre Channel and WWN Architecture
In physical Fibre Channel networks, every HBA port has a burned-in 64-bit hex identifier known as a WWPN (e.g., 50:01:43:80:18:6b:1a:02). When virtualizing these adapters inside Hyper-V virtual machines:
- N_Port ID Virtualization (NPIV): The physical host HBA shares its physical link with multiple virtual machines. The physical SAN switch assigns distinct FC-IDs to each virtual port based on its virtual WWPN.
- WWNN (World Wide Node Name): Identifies the virtual machine entity or host adapter node across the fabric. Hyper-V defines a default host-wide WWNN prefix (starting with
20:00:00:15:5d:...using Microsoft’s registered OUI). - WWPN (World Wide Port Name) Pairs: Hyper-V assigns two distinct WWPNs (Set A and Set B) to every virtual Fibre Channel adapter. During Live Migration, Set B connects to the destination host fabric before Set A disconnects from the source, guaranteeing zero I/O interruption or drop in SAN multipathing (MPIO).
- WWN Pool Allocation: The hypervisor host maintains an address range defined by
FibreChannelWwnn,FibreChannelWwpnMinimum, andFibreChannelWwpnMaximum. Ensuring pools do not overlap between Hyper-V hosts prevents SAN zoning conflicts and security breaches.
Inspecting Active Fibre Channel WWN Pools
To view the current Fibre Channel address range allocated to your Windows 11 Hyper-V host, launch an elevated PowerShell prompt (Run as Administrator) and execute Get-VMHost:
Get-VMHost | Select-Object FibreChannelWwnn, FibreChannelWwpnMinimum, FibreChannelWwpnMaximum | Format-ListA typical default configuration appears as follows:
FibreChannelWwnn : c003ff0000000000
FibreChannelWwpnMinimum : c003ff1a2b3c0000
FibreChannelWwpnMaximum : c003ff1a2b3c00ffThese values represent hexadecimal integers. Hyper-V uses Microsoft’s registered IEEE company ID prefix (c0:03:ff) to prevent collisions with third-party SAN hardware vendors.
Configuring Custom Fibre Channel WWN Pools with Set-VMHost
When deploying multiple Hyper-V virtualization hosts connected to the same SAN fabric, SAN storage administrators typically carve out dedicated, non-overlapping WWPN address blocks for each hypervisor. You configure these ranges using the Set-VMHost cmdlet.
Example 1: Defining a Dedicated Host WWPN Block
The following command assigns a custom, non-conflicting 256-address WWPN range to the local Hyper-V host:
# Define dedicated WWPN range for Host 01
Set-VMHost `
-FibreChannelWwnn "c003ff0000000001" `
-FibreChannelWwpnMinimum "c003ff0100000000" `
-FibreChannelWwpnMaximum "c003ff01000000ff"Example 2: Verifying Pool Boundaries
Confirm that the new minimum and maximum boundaries are successfully registered in the hypervisor database:
Get-VMHost | Select-Object FibreChannelWwnn, FibreChannelWwpnMinimum, FibreChannelWwpnMaximumInspecting Virtual Machine Fibre Channel Adapters and Assigned WWNs
When a virtual machine is equipped with a synthetic Fibre Channel adapter, Hyper-V dynamically leases WWPN pairs from the host’s configured pool.
To inspect the assigned WWNN and WWPN pairs on a virtual machine:
Get-VMFibreChannelAdapter -VMName "SQL-Cluster-Node01" | Select-Object VMName, SanName, WorldWideNodeName, WorldWidePortNameA, WorldWidePortNameB | Format-ListA typical output displays:
VMName : SQL-Cluster-Node01
SanName : Production-SAN-A
WorldWideNodeName : c003ff0000000001
WorldWidePortNameA : c003ff0100000012
WorldWidePortNameB : c003ff0100000013Notice that WorldWidePortNameA and WorldWidePortNameB fall squarely within the configured minimum and maximum pool boundaries. Storage administrators copy these two hex strings directly into their SAN switch zoning tables and storage array LUN masking configurations.
Manually Overriding Virtual Machine WWPNs
In disaster recovery replication or migration scenarios where a virtual machine must inherit a specific pre-existing SAN zone without altering switch zoning rules, administrators can manually assign static WWPNs directly to the adapter:
# Ensure VM is powered off
Stop-VM -VMName "SQL-Cluster-Node01" -Force
# Assign explicit static WWPNs matching existing SAN storage zones
Set-VMFibreChannelAdapter -VMName "SQL-Cluster-Node01" `
-WorldWideNodeName "c003ff0000000001" `
-WorldWidePortNameA "c003ff0100000050" `
-WorldWidePortNameB "c003ff0100000051"
Start-VM -VMName "SQL-Cluster-Node01"Best Practices for Hyper-V SAN Fabric Administration
When engineering Virtual Fibre Channel fabrics:
- Coordinate with SAN Teams: Always agree upon WWN pool allocations with your enterprise SAN storage team before provisioning virtual machines to avoid duplicate WWN errors on the fabric.
- Zone Both WWPNs: Always include both Port Name A and Port Name B in your SAN switch zone and storage array LUN masking groups to guarantee seamless Live Migration support.
- Ensure NPIV Support: Verify that physical host HBAs and SAN switch ports have NPIV enabled in their firmware.
By leveraging PowerShell’s Set-VMHost and *-VMFibreChannelAdapter cmdlets, virtualization administrators maintain disciplined, non-overlapping SAN address ranges, ensuring resilient high-throughput storage connectivity across enterprise Hyper-V deployments.