11-06-2018 09:59 PM
Hi,
I have a problem about zone merge in the MDS9148S.
In my case, I have two MDS and they set as ISL on the two MDS device.
As you know on the default status, activate zoneset only can share between two ISL device.
I'd like to merge and share all of zone databases(including sh run config) so I searched command by cisco document.
after searching, I found two commands for merging.
What is different between "zoneset distribute full vsan" and "zone copy active-zoneset full-zoneset vsan"
Q1. Can I use both of them ?
Are their commands same function ?
Q2. If I use only default mode, Switch1(save all of zone database) device is failed, Can Switch2(Only have activate zonset database) have still activate zoneset database although Switch2 don't have all of zone database ?
Solved! Go to Solution.
11-07-2018 06:46 AM
Hi KJ,
Zone merge will automatically occur between switches if zone and vsan settings are the same on both switches. Existing switch will share zoning data with new switch across ISL link for each vsan that is trunked. By default, when you configure a ISL port it allows all vsans.
Zones for vsan on both switches cannot have the same zone names with differing members.
Regarding your questions:
Q1. Can I use both of them?
The two commands are not the same and do different things.
zoneset distribute full vsan # changes the distribution method for a vsan. There are two distinct distribution methods for mds. They are full and active.
Config guide for zoneset distribution:
zone copy active-zoneset full-zoneset vsan # replaces the full zoneset database with what is in the full zoneset database.
Use command: show zone status vsan # to check current method
You can manually induce an import by using the zoneset import or zone export command: this again will replace
Config guide for zone import/export:
Q2. If I use only default mode, Switch1(save all of zone database) device is failed, Can Switch2(Only have activate zonset database) have still activate zoneset database although Switch2 don't have all of zone database?
I don’t quite understand this question but devices will not be able to communicate across ISL if zoning is not the same for shared vsans.
Cisco best practice is to use enhanced zoning to ensure consistency of the zoning database across entire san fabric please see:
Please open a TAC case if you have some specific trouble you want to review
-EA
11-07-2018 06:46 AM
Hi KJ,
Zone merge will automatically occur between switches if zone and vsan settings are the same on both switches. Existing switch will share zoning data with new switch across ISL link for each vsan that is trunked. By default, when you configure a ISL port it allows all vsans.
Zones for vsan on both switches cannot have the same zone names with differing members.
Regarding your questions:
Q1. Can I use both of them?
The two commands are not the same and do different things.
zoneset distribute full vsan # changes the distribution method for a vsan. There are two distinct distribution methods for mds. They are full and active.
Config guide for zoneset distribution:
zone copy active-zoneset full-zoneset vsan # replaces the full zoneset database with what is in the full zoneset database.
Use command: show zone status vsan # to check current method
You can manually induce an import by using the zoneset import or zone export command: this again will replace
Config guide for zone import/export:
Q2. If I use only default mode, Switch1(save all of zone database) device is failed, Can Switch2(Only have activate zonset database) have still activate zoneset database although Switch2 don't have all of zone database?
I don’t quite understand this question but devices will not be able to communicate across ISL if zoning is not the same for shared vsans.
Cisco best practice is to use enhanced zoning to ensure consistency of the zoning database across entire san fabric please see:
Please open a TAC case if you have some specific trouble you want to review
-EA
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: