Highlighted
3 Cadmium

virtual HBAs only showing port address set A in fabric

Jump to solution

Hello,

We have just started using virtual HBAs for our new Hyper-V environment. Here is what the Windows admin told me to look for after he did what he needs to do on his server.

VSAN 100 (HBA1)

port address set A

WWNN: C003FF0000FFFF00

WWPN: C003FF7748AD0000

port address set B

WWNN: C003FF0000FFFF00

WWPN: C003FF7748AD0001

VSAN 200 (HBA2)

port address set A

WWNN; C003FF0000FFFF00

WWPN: C003FF7748AD0002

port address set B

WWNN: C003FF0000FFFF00

WWPN: C003FF7748AD0003

I AM ONLY SEEING THE WWPN FOR PORT SET A IN BOTH VSAN 100/200. I AM NOT SEEING THE HBAS FOR PORT SET B.

I thought I see both port set A and B in each each VSAN. Is there something else he needs to do on the windows server? Or is it a problem with the fabric?

Many thanks!

Admingirl


Labels (1)
0 Kudos
1 Solution

Accepted Solutions
Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

4 adapters are needed for failover but i don't think the second pair comes online until after you "failover" that VM to another host. Have them perform Live Migration to another host and see if the other set logs-in.

View solution in original post

0 Kudos
22 Replies
Highlighted
5 Rhenium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

I noticed your tag so you're using Cisco MDS switches? Have you enabled NPIV on it? Maybe you can refer to this first:

Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide - Configuring N Port Virtualization  [Cis...

Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

4 adapters are needed for failover but i don't think the second pair comes online until after you "failover" that VM to another host. Have them perform Live Migration to another host and see if the other set logs-in.

View solution in original post

0 Kudos
Highlighted
3 Argentum

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Port set B is brought online only in case of live migration and vice versa.

Let's say your VM is sitting on node-A with port set A, when you live migrate this same VM to node-B hyper-V will actually bring port set B online on node-B migrate the VM resources and then bring port set-A offline, and similar operation happens when you failback.

So what you are seeing is normal. I would recommend testing live migration, many times VM won't live migrate because of zoning issues.

Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Hi,

How to I zone the B side for failover testing. Since they don't automatically appear in the fabric, would I manually add them to the fabric, or array? Someone who had done this before using brocades said he had to manually add the B side.

Benita

0 Kudos
Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

manually create fcalias/device alias and zones. Then manually create initiator records on VNX (WWNN:WWPN format)

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Hi,

I am not using fcaliases. I ran the sh fcalias vsan 100 and got no alias present. I would assume then I just create a device alias and then zone.

0 Kudos
Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

must be using device aliases ?

sh device-alias database

Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Yep, device alias it is!

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution


I plan on adding the device aliases through dcnm. Is there anything about this process that would be disruptive to my current prod fabric configuration? Since I've never had to do this before, I need to ask.

Thanks in advance!

Benita

0 Kudos
Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

nothing to worry, just make sure to commit changes when you are done otherwise you leave CFS locked.

10-22-2013 10-45-59 AM.png

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Great! Thank you so much Dynamox!


0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Hi

Added, and committed the initiator, however, I still do not see it in the host panel. Checked both the running config on dcnm and the switch itself and the new initiators show there. Any thoughts? Is there a step I am missing?

Thanks!

Benita

0 Kudos
Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

this is for initiator that is currently not logged-in right ?

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Yep, that is correct.

0 Kudos
Highlighted
7 Thorium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

ok, since it's not logged-in you are not going to see it in the list of available host ..so simply add the WWN manually when you add member to a zone.

10-22-2013 9-09-58 PM.png

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Grazi!!! Thanks again Dynamox!

Benita

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

OK, this is driving me nuts. I have done everything manually, it looks good. The windows folks keep pointing to my zones since failover is still not working.

Can someone tell me how the zones should look for windows hyper-v. My first group of zones is:

Individual zones(both A set, B set(failover) that are separate and look like this

VSAN 100 zones

virtual host ip

address set A HBA (2 in each VSAN)

virtual host ip

address set B HBA (2 each VSAN)

Per Microsoft: also include one zone per vsan with

All address set A/B in vsan

physical host HBAs for both host

VSAN 200 (same as 100)

Please tell me what should be in these zones for failover to work. I really appreciate it.

CISCO MDS 9509

0 Kudos
Highlighted
3 Argentum

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Below is what I usually do. I am running Brocade switches and I do most of the things through command line and it has been some time since I worked on Cisco switches so I don't exactly remember the commands but you should get the idea. Also, I borrowed your WWNs (sorry about that).

Assumption is that SPA0 & SPB1 connect to one fabric and SPA1 & SPB0 connect to second fabric. You want to zone all vHBAs to all the SP ports in that fabric as it is not under your control which vHBA Hyper-V will bring online.

C003FF7748AD0000---<Servername1_vHBA0>
C003FF7748AD0001---<Servername1_vHBA1>
C003FF7748AD0002---<Servername1_vHBA2>
C003FF7748AD0003---<Servername1_vHBA3>

VNX_SPA0, VNX_SPA1, VNX_SPB0, VNX_SPB1

Zones_FabricA

<Servername1_vHBA0>_VNX_SPA0
<Servername1_vHBA0>_VNX_SPB1

<Servername1_vHBA1>_VNX_SPA0
<Servername1_vHBA1>_VNX_SPB1

<Servername1_vHBA2>_VNX_SPA0
<Servername1_vHBA2>_VNX_SPB1

<Servername1_vHBA3>_VNX_SPA0
<Servername1_vHBA3>_VNX_SPB1


Zones_FabricB

<Servername1_vHBA0>_VNX_SPA1
<Servername1_vHBA0>_VNX_SPB0

<Servername1_vHBA1>_VNX_SPA1
<Servername1_vHBA1>_VNX_SPB0

<Servername1_vHBA2>_VNX_SPA1
<Servername1_vHBA2>_VNX_SPB0

<Servername1_vHBA3>_VNX_SPA1
<Servername1_vHBA3>_VNX_SPB0

When you mention failover is failing, do you mean Live Migration?

Also, you will have to manually register all paths on VNX.

If servers still cannot see paths make sure to check all paths in storage group---host tab---advanced (when you go in engineering mode).

Let us know how it goes

EDIT: This entry has some incorrect information. Please ignore it.

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution


Hello,

Yes, you are correct. I meant Live Migration. Thank you for your help. I am going to delete the microsoft zones and check each zone I have configured to match your specifications.

Thank you so much! I will report back on what worked.

Benita

0 Kudos
Highlighted
3 Cadmium

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Still getting resources unavailable. I am perplexed. All initiators are zoned in each vsan.

0 Kudos
Highlighted
3 Argentum

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

I am sorry my previous entry had information which is not correct. That was an extract from my first draft that I had created and we had the same issue as you have now.

Basically you want all the vHBAs zoned to every SP port, with the reason being that Hyper-V dynamically creates vHBAs on physical HBAs at time of live migration and there is no guarantee that a specific vHBA (Port Set A or Port Set B) will be created on a specific physical HBA.

I am so sorry for the wrong information before, I had to check my documentation to understand my mistake

Please let us know how things go.

0 Kudos
Highlighted
3 Argentum

Re: virtual HBAs only showing port address set A in fabric

Jump to solution

Both zoning and registering with VNX will have to be done manually.

0 Kudos