Introducing storage and networking for Hyper-V
The key concept for both storage
and networking for Hyper-V is that, in both situations, the virtualized
devices are communicating on behalf of the Windows 8 connectivity
technologies. Both the Hyper-V virtual switch and Virtual Fibre Channel
technologies have an underlying address scheme.
In the case of the networking technologies associated with Hyper-V, as
with physical network interfaces, a MAC address is used. A MAC address is the hardware
address of a network interface. Hyper-V virtual machine MAC addresses
have a range that starts with the first three sections of this format:
00-15-5D-xx-xx-xx. In this example, the xx-xx-xx placeholders are the
unique elements of the MAC address for the specific network interface.
Physical interfaces have a MAC address format; for example,
00-05-B5-xx-xx-xx is for the network interface manufacturer Broadcom.
Every brand of network interface has its own format of MAC address, and
Hyper-V virtual machines are easy to find because they adhere to this format in default configurations. Figure 1 shows the Hyper-V Virtual Switch Manager, located in the Action menu of Hyper-V Manager. Virtual machines that are on the Hyper-V virtual switch will have MAC addresses in the defined range.
Note
TRACKING DOWN A VIRTUAL MACHINE CAN BE DIFFICULT
Be sure you know the MAC addresses for Hyper-V virtual machines
(00-15-5D-xx-xx-xx) because this will help you quickly identify a
system on the network that needs to be located. It will help to know
whether the address you are looking for is a virtual machine.
Storage functions in much the same way. The Virtual Fibre Channel host bus adapter (HBA) interface technology for Hyper-V uses an implementation of N_Port ID Virtualization (NPIV) for storage networking. For Fibre Channel networks, this means that individual World
Wide Names (WWNs) of virtualized Fibre Channel interfaces can be
presented on the storage network. For most Windows 8 systems, having
Fibre Channel interfaces is more storage I/O than is needed, but it is
a great option for the technology to be available in the hypervisor (Figure 2).