How to configure zones and zone sets for UCS

[simon.han]

Hi,

A reseller's engineer create two types of zones,pWWN-based zoning and interface-based zoning.

The interface-based zones were added to a zone set.

Should the pWWN-based zones be added to the zone set?

Example:

Storage system , 1 set

Storage  controller A  Channel 0  's  pWWN is 21:00:00:d0:23:09:5c:6c , connect to Switch A port 5

Storage  controller A  Channel 1  's  pWWN is 22:00:00:d0:23:09:5c:6c , connect to Switch B port 5

Storage  controller B  Channel 0  's  pWWN is 21:00:00:d0:23:19:5c:6c , connect to Switch A port 6

Storage  controller B  Channel 1  's  pWWN is 22:00:00:d0:23:19:5c:6c , connect to Switch B port 6

MDS 9148 , 2 sets

UCS 6140XP , 2 sets

UCS 5108 ,   6 sets

UCS B250 M2 , 45 sets

zone  configuration on switch A :

zone name hz_1_5_6 vsan 801
member interface fc1/1 swwn 20:00:00:05:73:bb:7b:10
member interface fc1/5 swwn 20:00:00:05:73:bb:7b:10
member interface fc1/6 swwn 20:00:00:05:73:bb:7b:10

zone name hz_2_5_6 vsan 801
member interface fc1/2 swwn 20:00:00:05:73:bb:7b:10
member interface fc1/5 swwn 20:00:00:05:73:bb:7b:10
member interface fc1/6 swwn 20:00:00:05:73:bb:7b:10

zone name PS01-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:bf
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS02-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:af
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS03-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:8f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS04-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:9f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS05-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:6f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS06-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:7f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS07-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:4f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS08-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:5f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS09-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:2f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS10-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:3f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zoneset name zoneset801 vsan 801
member hz_1_5_6
member hz_2_5_6

zone  configuration on switch B :

zone name hz_1_5_6 vsan 802
member interface fc1/1 swwn 20:00:00:05:73:b7:8e:d8
member interface fc1/5 swwn 20:00:00:05:73:b7:8e:d8
member interface fc1/6 swwn 20:00:00:05:73:b7:8e:d8

zone name hz_2_5_6 vsan 802
member interface fc1/2 swwn 20:00:00:05:73:b7:8e:d8
member interface fc1/5 swwn 20:00:00:05:73:b7:8e:d8
member interface fc1/6 swwn 20:00:00:05:73:b7:8e:d8

zone name PS01-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:8f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS02-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:9f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS03-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:6f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS04-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:7f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS05-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:4f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS06-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:5f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS07-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:2f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS08-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:3f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS09-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:0f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zone name PS10-HBA1 vsan 802
member pwwn 20:00:00:21:01:ff:01:1f
member pwwn 22:00:00:d0:23:09:5c:6c
member pwwn 22:00:00:d0:23:19:5c:6c

zoneset name zoneset802 vsan 802
member hz_1_5_6
member hz_2_5_6

[simon.geary · Accepted solution]

Any zones not added to the zoneset are effectively unused, so depending on if the zones that are not yet in the zoneset are required, yes you will have to add them in.

However, the WWPNs you have listed do not appear to be using the Cisco recommended format for WWPN Pools (20:00:00:25:B5:xx:yy:zz) so perhaps you are not using pools or these zones are not related to UCS? If they are indeed UCS related zones then yes add them to the zoneset, but consider using the Pools instead if this is so.

My suggestion would be to use all WWPN zones and not mix with interface zones.

On each MDS switch, create a zone that contains only the two WWPNs of the storage controllers, ideally using an easy to identify alias. This guarantees the SAN ports can always see each other. Then, create an additional zone for each UCS blade that contains the blade WWPN from the WWPN Pool as well as the storage zone mentioned above. This allows the vHBA to see the SAN ports.

Here is a reference document you may find helpful.

http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/san-os/quick/guide/qcg_zones.html

[simon.han]

Thanks a lot for your reply!

to use all WWPN zones ,like below?

zone name Str1_A0_B0 vsan 801
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS01-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:bf
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zone name PS02-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:af
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

......

zone name PS10-HBA0 vsan 801
member pwwn 20:00:00:21:01:ff:00:3f
member pwwn 21:00:00:d0:23:09:5c:6c
member pwwn 21:00:00:d0:23:19:5c:6c

zoneset name zoneset801 vsan 801
member Str1_A0_B0
member PS01-HBA0
member PS02-HBA0
......
member PS10-HBA0

[simon.geary]

Yes exactly, you have the right idea. So in your example the zone Str1_A0_B0 contains only the storage ports, while all the other zones contain both the storage ports as well as a vHBA address from the WWPN pool. And finally the zoneset contains every zone created.

And of course you do the exact same thing on the second MDS switch but just use a different VSAN number.

[simon.han]

Thanks for your help!

I'll tell the reseller engineer about your idea. I hope he can change the zone settings .

We encountered some problems during deployment.

Problem 1 :  When booting from san , a server try to boot from a target lun ,but the lun doesn't belong to this server ,boot failed.

The reseller engineer created a boot policy ,set lun id 0 as a boot device for all servers.

But the lun id is actually different from each server . I changed the boot policy,and deleted the unnecessary boot entry of hba.This problem was resolved.

Problem 2 :  A server could occasionally find a target lun that doesn't belong  to it ,while booting or running.

This problem is still confusing us now .