cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
2265
Views
0
Helpful
5
Replies

Adding new zones into an existing zoneset

ciscomdsmagic
Level 1
Level 1

There is already a zoneset which has one storage and a number of hosts. Now, we added one more different type storage with a different set of hosts. If I understand correctly, two zoneset cannot be activated at the same time, so, without using VSAN, we will have to add new zones into the existing zoneset, then activate it including both existing zones and new added zones.

Will that cause any issues?

Thanks for your help in advance.

5 Replies 5

Walter Dey
VIP Alumni
VIP Alumni

You are 100% correct !  all zoning (zones and zonesets) is per vsan ! I hope you are not using default vsan nr. 1 ??

And yes, no problems activating the modified zoneset with the new additional zones.

Thanks for your help!

We are not using default vsan, but only one vsan per switch, people here doesn't know what vsan is all about, so, they don't want to use it. So, they put everything in one vsan and then one zoneset.

Since there is already an existing environment with a storage and associated hosts, if we add one new storage and  along with new hosts, new zones, by adding all these into the existing zoneset, deactivate and activate two environments  all together, one is alraedy shown working fine, the other is in developing, can you foresee any issues with this approach?i

Hi

Wether you like it or not, vsan's must be used, by default, vsan 1 exists, cannot be deleted, and all interfaces are in vsan 1.

Best practise it to create (at least) one vsan different from 1, for each fabric A resp B, and use different vsan id's for this fabrics.

I would just use one zoneset, and create a backup before making any changes.

Show zoneset ..... vsan ...

show zoneset active .... vsan .... 

Understand all you have said.

Yes, we have vsan 2 in Fabric A, and vsan 3 in Fabric B, in addition to the default vsan 1. Currently, there is only one zoneset and one vsan for a storage X in each fabric, vsan 2 and vsan 3 respectively.

without creating one more vsan for the new added storage Y, and just adding new zones which is only related to the new storage Y into the existing zoneset in vsan 2 (or 3 in Fabric B), would that cause any issues? why is it not a best practice?

This is 100% correct ! sorry for any misunderstanding !

You should just be concerned about size of saveset and zones, which might hit a MDS limitation (very unlikely), but may also be challenging for the management. Some customers create separate vsan's eg. for backup, or partition windows from linux/unix OS. 

Do you know, that you can configure MDS, such that management for a particual vsan (zoning,..) can be delegated to a particual group of users.

see Table 2 Fabric-level Fibre Channel Configuration Limits in 

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/7_3/configuration/config_limits/b_mds_9000_configuration_limits_7_3.html#con_1153967

Review Cisco Networking for a $25 gift card