Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
BladeSystem Infrastructure and Application Solutions
Showing results for 
Search instead for 
Did you mean: 

Virtual Fibre channel for Hyper-V in Microsoft Server 2012

Trusted Contributor

Virtual Fibre channel for Hyper-V in Microsoft Server 2012

Arno had some questions regarding support for the new Microsoft Virtual Fibre Channel implementation:




Customer first tested Hyper-V server in Blade enclosure with Ethernet and FC Pass-thru modules.

2nd test was in enclosure with Flex-10 and 24 port VC-FC module.


In the Blade enclosure they use the Virtual Connect assigned WWN and MAC Addresses.

In the second scenario they are facing some issues :


2 Questions :

-          Is Microsoft Virtual Fiber channel supported with VC-FC  / Is there some certification needed ?


-          Any special setting that needs to be made to this configuration as we get the error message below :




Info from Jim:




Server side NPIV is supported on VC-FC and VC-FF modules.  With FlexFabric we support up to 255 logins per port.


The key for virtual Fiber Channel in Server 2012 is that the driver should fully adhere to Windows Server 2012 requirements. I.e. it should be explicitly listed as a new driver released specifically for Windows Server 2012 or Older driver (e.g. released for Windows Server 2008 R2) might work for general host use but not for virtual Fiber Channel.


Best Place to check is on HP SPOCK( Single Point of Connectivity Knowledge for HP Storage Products) page.


Given there were no issues in the first test and  MS Cluster works well in 2012  correct setup is likely but you might want to ensure:

  • Check that each v-hba in vm has the WWPN zoning set for A and B ports
    A simple way of doing this is to shut down the VM and change the value of the WWPN A by B and vice versa, go up the VM and check if the same disks are seen.
  • Check Hyper-V-SynthFC logs for event 32218



Any other suggestions or comments?