04-01-2014 05:24 AM
I never done storage networking before and while configuring and testing our zone/zoneset config I ended up adding targets and all members to the same zone. I'm positive this is not best practice and hoping someone will point me in the right direction.
This is working fine with the config below, VMs are seeing LUNs. Should I create separate zone for each target? So each host would have two zones with target(VNX-SP-A) & (VNX-SP-B) on each switch? all in the same zoneset?
SW1:
!Full Zone Database Section for vsan 31
zone name NX1-VNX-SP-A vsan 31
member pwwn 50:06:01:64:08:60:21:65
! [VNX-SP-A]
member pwwn 50:06:01:6d:08:60:21:65
! [VNX-SP-B]
member pwwn 22:ce:00:2a:6a:9d:d4:7f
! [UCS-FI-A]
member fcid 0xef00ef
member fcid 0xef01ef
member fcid 0x0c0001
member pwwn 20:00:00:25:b5:b0:00:1e
! [ESX-01]
member fcid 0xef0002
member pwwn 20:00:00:25:b5:b0:00:3f
member fcid 0xef0003
member pwwn 20:00:00:25:b5:b0:00:3e
member fcid 0xef0004
member pwwn 20:00:00:25:b5:b0:00:1f
member fcid 0xef0005
zoneset name ZoneSet_NX1-VNX-SP-A vsan 31
member NX1-VNX-SP-A
zoneset activate name ZoneSet_NX1-VNX-SP-A vsan 31
SW2:
!Full Zone Database Section for vsan 32
zone name NX1-VNX-SP-A vsan 32
member pwwn 50:06:01:65:08:60:21:65
! [VNX-SP-A]
member fcid 0x1400ef
member pwwn 50:06:01:6c:08:60:21:65
! [VNX-SP-B]
member fcid 0x1401ef
member pwwn 22:cf:00:2a:6a:9d:d7:3f
! [UCS-FI-B]
member fcid 0x140001
member pwwn 20:00:00:25:b5:b0:00:0e
! [EXS-01]
member fcid 0x140002
member pwwn 20:00:00:25:b5:b0:00:2f
member fcid 0x140003
member pwwn 20:00:00:25:b5:b0:00:2e
member fcid 0x140004
member pwwn 20:00:00:25:b5:b0:00:0f
member fcid 0x140005
zoneset name ZoneSet_NX2-VNX-SP-A vsan 32
member NX1-VNX-SP-A
zoneset activate name ZoneSet_NX2-VNX-SP-A vsan 32
04-01-2014 09:57 AM
Usually most storage vendors mandate single initiator - single target zoning; this could of course end up in quite some work.
Cisco invented some proprietary solution, called smart zoning, see eg.
http://www.cisco.com/c/dam/en/us/products/collateral/storage-networking/mds-9100-series-multilayer-fabric-switches/at_a_glance_c45-708533.pdf
Caveat: not every platform does support smart zoning (N5k doesn't for the moment).
My 2c: use device alias for building your zone's ! and enhanced zoning (to be enabled per vsan)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide