4 . On the switch, add the newly visible WWPNs to the alias.
5 . Complete zoning to storage.Figure 4.24 shows my switch with an alias created for each of the vFCAs for each
virtual machine. Notice that each alias has two WWPNs, the A and the B set, but only
one is active. Figure 4.25 shows the same view after I live-migrate the two virtual
machines to another host. Notice now that the second set of WWPNs is active.
Figure 4.24 The A set of WWPNs being used
Figure 4.25 The B set of WWPNs being used
A great feature here is that the Hyper-V host itself has no access to the storage.
Nowhere is the WWPN of the host zoned to storage; only the virtual machines have
access to the storage, which is important from a security perspective and simplifies
management because there is no need to ensure that every Hyper-V host is zoned to
storage, only the virtual machines’ vFCAs that actually need the access.
With storage now zoned to all the WWPNs for the vFCAs used, the virtual machines
can be started and the storage can be accessed as shared storage, allowing guest
clustering. While this is not a Hyper-V-specific step, it is important to realize that in
my architecture shown in Figure 4.19, I have redundant paths to the storage through
my two vFCAs and the two virtual SANs (which can both see the storage via redundant
paths), which means that for each LUN zoned, the storage will actually be seen four