This post is more than 5 years old
614 Posts
0
5648
virtual HBAs only showing port address set A in fabric
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
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
August 29th, 2013 08:00
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.
Roger_Wu
4K Posts
1
August 29th, 2013 08:00
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 [Cisco MDS 9000 NX-OS an…
Sridhar246
115 Posts
1
August 29th, 2013 09:00
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.
admingirl
614 Posts
0
October 21st, 2013 10:00
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
Sridhar246
115 Posts
0
October 21st, 2013 10:00
Both zoning and registering with VNX will have to be done manually.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 21st, 2013 10:00
manually create fcalias/device alias and zones. Then manually create initiator records on VNX (WWNN:WWPN format)
admingirl
614 Posts
0
October 21st, 2013 18:00
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.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
1
October 21st, 2013 19:00
must be using device aliases ?
sh device-alias database
admingirl
614 Posts
0
October 21st, 2013 20:00
Yep, device alias it is!
admingirl
614 Posts
0
October 22nd, 2013 07:00
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
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 22nd, 2013 07:00
nothing to worry, just make sure to commit changes when you are done otherwise you leave CFS locked.
admingirl
614 Posts
0
October 22nd, 2013 07:00
Great! Thank you so much Dynamox!
admingirl
614 Posts
0
October 22nd, 2013 17:00
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
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
October 22nd, 2013 18:00
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.
admingirl
614 Posts
0
October 22nd, 2013 18:00
Yep, that is correct.