Single initiator different zones with different targets

[Steven Williams]

Can you have a single identical HBA initiator in different zones on an MDS with different targets in each zone? or can an initiator only log in under one zone?

Is below allowed on the same MDS also the same vsan?

zone name VM005_S05_C1_TO_VNX5300_SPA0_SPA1_SPB0_SPB1 vsan 10
member pwwn 20:01:b4:e1:0f:28:02:0d init
! [VM005_S05_C1]
member pwwn 50:06:01:60:3e:e0:2a:f2 target
! [VNX5300_SPA0]
member pwwn 50:06:01:61:3e:e0:2a:f2 target
! [VNX5300_SPA1]
member pwwn 50:06:01:68:3e:e0:2a:f2 target
! [VNX5300_SPB0]
member pwwn 50:06:01:69:3e:e0:2a:f2 target
! [VNX5300_SPB1]

zone name VM005_S05_C1_TO_VNX5400_SPA2_SPB2 vsan 10
member pwwn 20:01:b4:e1:0f:28:02:0d init
! [VM005_S05_C1]
member pwwn 50:06:01:62:36:e0:14:2d target
! [VNX5400_SPA2]
member pwwn 50:06:01:6a:36:e0:14:2d target
! [VNX5400_SPB2]

[xiazhen01]

HI, Steven Williams:

    what's wrong with you ? about zone,  according to best practices , cisco advise the zone include

single initiator  and many target . no problem with you design , i think. 

[Steven Williams]

I just cant get the blade HBA able to see both targets with this setup so thats why i thought it was a supported design.

[Walter Dey]

Please just show us the output of

Show zoneset active vsan 10

Maybe the second target didn't do a flogi ?

I can't see any reason why single initiator - multiple target works, and single initiator - single target not ?

[Steven Williams]

ummmm i think i see the issue.....

zoneset name MID_PROD_DR vsan 10
member MIDPVMW001_S01_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW002_S02_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW003_S03_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW004_S04_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW005_S05_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW006_S06_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW007_S07_C1_TO_MIDVNX5400_SPA2_SPB2
member MIDPVMW008_S08_C1_TO_MIDVNX5400_SPA2_SPB2

I dont see my 5300 zone sets in this list.....but i paste this command and they dont add.

zoneset name MID_PROD_DR vsan 10
member MIDPVMW005_S05_C1_TO_MIDVNX5300_SPA0_SPA1_SPB0_SPB1
member MIDPVMW006_S06_C1_TO_MIDVNX5300_SPA0_SPA1_SPB0_SPB1
member MIDPVMW007_S07_C1_TO_MIDVNX5300_SPA0_SPA1_SPB0_SPB1
member MIDPVMW008_S08_C1_TO_MIDVNX5300_SPA0_SPA1_SPB0_SPB1

so whats the issue here.....

[Walter Dey · Accepted solution]

So you are using device alias ? correct ?

Do you use enhanced zoning ?

May you should do a

"commit vsan 10"

and finally you also have to activate the zonset !

btw. do you see any error messages, while pasting this list of 5300 zones ?

PS.

Have a look at "show running" and you see how zones and zoneset are configured and enabled

[Steven Williams]

that was it. They dont show in the zoneset list until the zone is reactivated...boo

Thanks guys!

[Steven Williams]

Ok still not working. I see this from the show zoneset active vsan 10

zone name MIDPVMW007_S07_C1_TO_MIDVNX5400_SPA2_SPB2 vsan 10
* fcid 0x200800 [pwwn 20:01:b4:e1:0f:28:02:27] [MIDPVMW007_S07_C1] init
* fcid 0x200000 [pwwn 50:06:01:62:36:e0:14:2d] [MIDVNX5400_SPA2] target
* fcid 0x200100 [pwwn 50:06:01:6a:36:e0:14:2d] [MIDVNX5400_SPB2] target

zone name MIDPVMW008_S08_C1_TO_MIDVNX5400_SPA2_SPB2 vsan 10
* fcid 0x200900 [pwwn 20:01:b4:e1:0f:28:02:34] [MIDPVMW008_S08_C1] init
* fcid 0x200000 [pwwn 50:06:01:62:36:e0:14:2d] [MIDVNX5400_SPA2] target
* fcid 0x200100 [pwwn 50:06:01:6a:36:e0:14:2d] [MIDVNX5400_SPB2] target

zone name MIDPVMW006_S06_C1_TO_MIDVNX5300_SPA0_SPA1_SPB0_SPB1 vsan 10
* fcid 0x200700 [pwwn 20:01:b4:e1:0f:28:02:1a] [MIDPVMW006_S06_C1] init
pwwn 50:06:01:60:3e:e0:2a:f2 [MIDVNX5300_SPA0] target
pwwn 50:06:01:61:3e:e0:2a:f2 [MIDVNX5300_SPA1] target
pwwn 50:06:01:68:3e:e0:2a:f2 [MIDVNX5300_SPB0] target
pwwn 50:06:01:69:3e:e0:2a:f2 [MIDVNX5300_SPB1] target

zone name MIDPVMW007_S07_C1_TO_MIDVNX5300_SPA0_SPA1_SPB0_SPB1 vsan 10
* fcid 0x200800 [pwwn 20:01:b4:e1:0f:28:02:27] [MIDPVMW007_S07_C1] init
pwwn 50:06:01:60:3e:e0:2a:f2 [MIDVNX5300_SPA0] target
pwwn 50:06:01:61:3e:e0:2a:f2 [MIDVNX5300_SPA1] target
pwwn 50:06:01:68:3e:e0:2a:f2 [MIDVNX5300_SPB0] target
pwwn 50:06:01:69:3e:e0:2a:f2 [MIDVNX5300_SPB1] target

why do the ones working have a *fcid in front of them and the ones not working dont?

[Walter Dey]

This means, that the pwwn without a * in front, have not done a flogi

pwwn 50:06:01:60:3e:e0:2a:f2 [MIDVNX5300_SPA0] target
pwwn 50:06:01:61:3e:e0:2a:f2 [MIDVNX5300_SPA1] target
pwwn 50:06:01:68:3e:e0:2a:f2 [MIDVNX5300_SPB0] target
pwwn 50:06:01:69:3e:e0:2a:f2 [MIDVNX5300_SPB1] target

and

pwwn 50:06:01:60:3e:e0:2a:f2 [MIDVNX5300_SPA0] target
pwwn 50:06:01:61:3e:e0:2a:f2 [MIDVNX5300_SPA1] target
pwwn 50:06:01:68:3e:e0:2a:f2 [MIDVNX5300_SPB0] target
pwwn 50:06:01:69:3e:e0:2a:f2 [MIDVNX5300_SPB1] target

I cannot tell you why ?

[Steven Williams]

I figured it out. The wrong SP ports were connected to the SAN. 3 days of my life gone!

[Walter Dey]

Hi Steven

This is ok !

However, most storage vendors (IBM, EMC, HDS, NetApp...) prefer and recommend single initiator - single target zoning.

Walter.

[Steven Williams]

Ya i read that alot, but then why is there smart zoning lol.