Microsoft Hypervisor: Can we map LUNs directly to VM like VMWare RDM using HyperV’s Virtual Fibre Channel Feature

What you're saying doesn't really make sense. The "correct" way to setup networking with Hyper-V is to:

• Connect the one Physical NIC to the MVNS only, nothing else, Hyper-V will configure this for you and there's no reason to mess with it.
• Create a virtual NIC that's connected to one of the virtual switches (or virtual networks as the Hyper-V Manager calls them).

There are three types of Virtual Networks you can create:

• External: connected to the Physical NIC, the Virtual NIC on the Host, and any VMs you assign to it.
• Internal: connected to the Virual NIC on the Host and any VMs you assign it to.
• Private: connected to any VMs you assign it to and nothing else.

The Virtual NIC will always have access to the Physical NIC when configure properly.

If you just want the VMs to have access to just the Hyper-V Host, you can use an Internal. You can also use an External Network and they will have access to the Physical NIC's network.

Just on the off chance the machine has cluster services installed and the SAN volume is offline with "the disk is offline because of a policy set by an administrator" error, then check if the cluster service is started and if it is, whether the relevant cluster group is online.