Hi,

I am having the hardest time getting this to work. My A set shows up and so after I manually add the B set nothing happens.

In each VSAN I have four sp connections (2 for SPA, 2 for SPB)

My question is do the vhbas have to be zoned to all SPs?

Thanks in advance,

Admingirl

Every SP ( not SP port, only the ones you want to connect to ) needs to be zoned.

for Instance:

you have to  NPIV vHBAS, NPIV0 and NPIV1, where you use NPIV0 in Fabric A.

you have to SP´s and use one Port per SP in Fabric A: SPA0 and SPB1

You need to have the Following Zones created in Fabric A:

zonecreate "HOST_NPIV0_A_VNX5500_A0P0", "HOST_NPIV0_A;VNX5500_A0P0" zonecreate "HOST_NPIV0_A_VNX5500_B0P1", "HOST_NPIV0_A;VNX5500_B0P1" zonecreate "HOST_NPIV0_B_VNX5500_A0P0", "HOST_NPIV0_B;VNX5500_A0P0" zonecreate "HOST_NPIV0_B_VNX5500_B0P1", "HOST_NPIV0_B;VNX5500_B0P1"

Since the B WWPN is inactive, it will not show ap ath th VNX SP´s, thus you have to register them Manually or do a Live Migration to register !

Please note that NPIV is not supported on 2012 HA VM´s ...

Since the B WWPN is inactive, it will not show ap ath th VNX SP´s, thus you have to register them Manually or do a Live Migration to register !

Karsten,

how can you do a live migration before the B side is registered ?  Can you also provide more details regarding "NPIV is not supported on 2012 HA VMs"

Thank you

I apologize if this is obvious, but just to be clear.  The B side virtual HBAs were manually registered, and zoned.  Were they also connected to the same storage group as the A side?

Thanks,

Mike

Thank you Karsten and Dynamox.

I already did that(manually registered the HBASs) and then zoned them on the B side. It still did not work when we tried failover.

That is why I reached out again.

Benita

Yep, they are all connected to the same storage group.

Here is the question I have. We have two separate VSANs. I manually added all of the vhbas to each VSAN regardless of whether or not the A address set was originally zoned there. This was per one

tech here who said he did this before in a past life on a brocade and that is what he did. Is this a mistake?

Thanks again.

Benita

One thing you could try in order to troubleshoot is to swap the A and B address set WWPNs.  With the VM powered off go to the settings for each adapter and swap the WWPN like the image below.    The next time the VM is powered up, it will use the other WWPN.  Hopefully this will tell you if it's a zoning issue for the VM addresses, or perhaps a problem with a specific cluster node.

I also wrote a script that does the same thing.  Replace the $vmname variable with your VM.  Use at your own risk:

$vmname = "FCPTSMIS"

function SwapWWPN {
$vmhba = Get-VMFibreChannelHba $vmname

foreach ($hba in $vmhba){
Set-VMFibreChannelHba $hba -NewWorldWidePortNameSetA $hba.WorldWidePortNameSetB -NewWorldWidePortNameSetB $hba.WorldWidePortNameSetA
}

}

function CurrentWWPN {
$vmhba = Get-VMFibreChannelHba $vmname

foreach ($hba in $vmhba){
write-host -BackgroundColor Blue "Current WWPN"
$hba.SanName
write-host "Address Set A" $hba.WorldWidePortNameSetA
write-host "Address Set B" $hba.WorldWidePortNameSetB
}
}
#SwapWWPN
CurrentWWPN

If I understand correctly, you'll end up with addresses that won't log in to a given zone given their physical connectivity, but I don't think that will cause your current issue.  To make sure we're on the same page please see the image below.  Both the A address set and the B address set for a given Virtual Adapter will go through the same Hyper-V Virtual SAN and therefore the same Physical Adapter(s) and same Fabric.  For example, address set A and B for Virtual Adapter A would be zoned through Fabric A (or VSAN A in your case) to the desired SP Ports.  If you added address set A and B from Virtual Adapter B to Fabric (VSAN) A, that wouldn't hurt anything, but it also wouldn't help.

Thanks all , this helps me lot 

Hi,

I did all zoning, registered vHBAs, etc.

LUN access from guest OS is working and live migration as well.

Just a cosmetic issue: since some vHBAs are used only for live migration, this means they are almost never used (not logged in to the storage array except during live migration). The VNX array shows the following warning:

"The following hosts have initiators that no longer have an active connection to the storage system:( VMNAME).

The following hosts have initiators that no longer have an active connection to the storage system:( VMNAME).

Troubleshoot any inactive connections or deregister all connections that are no longer in use.

0x724b"

is there a way to avoid this warning since it's totally normal ?

thank you for you replies.

regards,

not that i know off, they are not logged-in on my either until they failover the guest.