# Account for both virtual Fibre Channel WWN sets before live migration

> What Fibre Channel identity should be reviewed before migrating a VM with a virtual HBA?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-117-account-for-both-virtual-fibre-channel-wwn-sets-before-live-migration/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:15:14+00:00
- Modified: 2026-09-08T18:23:27+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

What Fibre Channel identity should be reviewed before migrating a VM with a virtual HBA?

## Potentially affected

Administrators connecting Hyper-V guests directly to Fibre Channel storage.

## DSE recommendation

Create a mapping of the adapter’s two WWN sets to the authorized storage presentation on both hosts.

## Article

## Source facts

Hyper-V virtual Fibre Channel gives a guest direct SAN access using a VM-associated World Wide Name. It relies on NPIV: starting a VM with a virtual HBA creates an NPIV port on the host, and stopping the VM removes it. The topology and SAN must support those ports. For live migration, each virtual adapter has two WWN sets and Hyper-V alternates between them. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v).

## Applicability

Identify the guest workload, virtual HBA, physical ports, SAN, supported topology, and intended migration hosts. Review the complete platform requirements before adapting a virtual Fibre Channel example.

## DSE recommendation

Create a mapping of the adapter’s two WWN sets to the authorized storage presentation on both hosts. Have the SAN owner review the mapping and confirm the intended LUN access. Include a maintenance and recovery decision for the workload before exercising a migration.

## Verification

Validate guest storage access on the source host and after an approved migration to the destination. Record the active WWN identity and the LUNs actually visible at each step. Test the planned return move and investigate missing storage or unexpected access before authorizing routine migration of that workload.

## Official references

[Microsoft Learn: Hyper-V Virtual Fibre Channel in Windows Server](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v). Source reviewed September 8, 2026.

## Primary reference

- Name: Hyper-V Virtual Fibre Channel in Windows Server
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/virtual-fibre-channel-for-hyper-v
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Account for both virtual Fibre Channel WWN sets before live migration,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-117-account-for-both-virtual-fibre-channel-wwn-sets-before-live-migration/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.