Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2882

January 21st, 2014 08:00

question about manually adding hbas in dcnm

Hello,

I took a brief hiatus from this project and now I need to refresh my memory. We use dev-alias, not fcaliases. I need to manually add the b set addresses for hyper-v virtual hba failover. Do I choose the core switch as the switch, after clicking on end devices, or the edge switch the server is zoned to? Not sure what to do here. The edge switch is not coming up as an option in the list of switches to pick.

Many thanks in advance!

Admingirl

1 Rookie

 • 

20.4K Posts

January 21st, 2014 12:00

adding device-alias ? Absolutely not   . Once you add the new alias don't forget to commit it (little green button)

1-21-2014 3-25-10 PM.png

1 Rookie

 • 

20.4K Posts

January 21st, 2014 08:00

c9513# sh device-alias status

Fabric Distribution: Enabled

Database:- Device Aliases 102  Mode: Basic

           Checksum: 0xffa810c446628d1dbed234fbef9ed932

is fabric distribution enabled ?

614 Posts

January 21st, 2014 11:00

Thank you Dynamox, I will check now.

1 Rookie

 • 

20.4K Posts

January 21st, 2014 12:00

i just select my fabric (that consists if different switches). Then on the right side select "configuration" tab and add add device-alias there.

1-21-2014 3-14-04 PM.png

614 Posts

January 21st, 2014 12:00

On the edge and core switches, fabric distribution is enabled.

614 Posts

January 21st, 2014 12:00

Great! I will do that. Is any of this disruptive? Thanks so much Dynamox!

Benita

614 Posts

January 21st, 2014 12:00

Great! Thanks again!

Benita

614 Posts

January 23rd, 2014 08:00

Hi there, so I added it to the dev-alias database, committed the changes and it looks good, the manual entry appears under the configuration tab.

Now I just have one more question. The entry doesn't appear under the hosts tab when I click on the vsan. It's been awhile since I have done this so to zone, would I just manually add the HBA in the www box instead of choosing an entry from the hosts lists? Is this the norm?

Many thanks!

Benita

614 Posts

January 23rd, 2014 09:00

Capture.zone.PNG.pngOk, so I added the hba wwn and zoned it.

Here is what I get(see image), Is there a way for me to manually add the switch as well as the wwn?

Thanks!

1 Rookie

 • 

20.4K Posts

January 23rd, 2014 10:00

i assume that WWN is not on the fabric unless you force that VM to failover ? I would not worry about it. I to zone my (secondary set) of WWN for Hyper-v "blind".  You just manually enter  the WWN to your zone.

614 Posts

January 23rd, 2014 11:00

That is what I have above. Sorry for the all questions. So I have

Vsan 100 - HBA 1 set a (zoned works)

                   HBA 1 set b (manually zoned picture above, not seen by host, failover not working)

Vsan 200 - HBA 2 set a (zoned works)

                  HBA 2 set b (manually zoned, not seen by host, failover not working)

Each zone consists of the 4 virtual controllers(compellent) 1 host wwn.

Is the above zone format correct or do I have to put every wwn in the same zone? Do you or anyone have a real sample zone you can attach? So sorry for all the questions.

Thanks!

Admingirl

1 Rookie

 • 

20.4K Posts

January 23rd, 2014 12:00

i don't know anything about compellent storage but this is how my Hyper-V VMs that are using virtual HBAs are connected. Note that sqlserver-h3 and sqlserver-h1 are "set B" WWNs. I had to manually add their WWN into zone configuration and manually register them in Initiators/Connectivity Status on VNX.

Fabric A

  zone name sqlserver-h2-vnx5700-spb0 vsan 112

  zone name sqlserver-h2-vnx5700-spa1 vsan 112

  zone name sqlserver-h2-vnx5700-spa2 vsan 112

  zone name sqlserver-h2-vnx5700-spa3 vsan 112

zone name sqlserver-h3-vnx5700-spb0 vsan 112

  zone name sqlserver-h3-vnx5700-spb1 vsan 112

  zone name sqlserver-h3-vnx5700-spa2 vsan 112

  zone name sqlserver-h3-vnx5700-spa3 vsan 112

Fabric B

  zone name sqlserver-h0-vnx5700-spa0 vsan 114

  zone name sqlserver-h0-vnx5700-spa1 vsan 114

  zone name sqlserver-h0-vnx5700-spb2 vsan 114

  zone name sqlserver-h0-vnx5700-spb3 vsan 114

  zone name sqlserver-h1-vnx5700-spa0 vsan 114

  zone name sqlserver-h1-vnx5700-spa1 vsan 114

  zone name sqlserver-h1-vnx5700-spb2 vsan 114

  zone name sqlserver-h1-vnx5700-spb3 vsan 114

614 Posts

January 23rd, 2014 12:00

Thanks again Dynamox, this is very helpful!

Since each host hba gets zoned to all of the virtual ports for the compellent storage array in each vsan, then it seems like I am doing it correctly.

1 wwn, 4 compellent virtual ports per zone

Thanks again!

Benita

1 Rookie

 • 

20.4K Posts

January 23rd, 2014 12:00

yeah, if you look at any recent Cisco MDS best practices ...they are ok with having one initiator and multiple targets in one zone. Now there are instances where a storage array is pre-installed with SANCopy or MirrorView (or Open Replicator for Symmetrix/VMAX) and by putting multiple targets into one zone could force those ports to login into each other ..not a good thing. For that reason i continue to practice "single initiator / single target" zoning. It might be a non issue for Compellent storage. One way to address single initiator /multiple target zoning (and prevent ports from loggin in into each other) is to use Cisco feature introduced in NX-OS 5.2.6 called "Smart Zoning" ..but that's a discussion for another topic

No Events found!

Top