cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
1855
Views
10
Helpful
5
Replies

zone merge with different VSAN id

Hello gurus-

I am planning to ISL a factory reset 9148s with a Nexus 5k (both production), in order  to migrate the zoning config  to the 9148s. (essentially we are simply upgrading the switch), this I have done before no issues. I subsequently will decomm the Nexus then ISL across data centers the 9148s to another 9148s with already existing zoning configurations. My question is, in that the zone information from the old Nexus is now on the 9148s and will have a VSAN Id inherited from the old Nexus, will I have issues; major or otherwise, when I merge the fabric with my 9148s in the other data center. Keep in mind this second MDS has an existing (production) zoning configuration with its own VSAN ID. Thank You in advance for your input and assistance.

2 Accepted Solutions

Accepted Solutions

Walter Dey
VIP Alumni
VIP Alumni

Not quite clear what you want to achieve.

my 2c

Zoning is done per VSAN, therefore a zone merge between 2 switches, connected by ISL, requires identical VSAN's.

The Merge process is explained in great detail p76ff in Configuring and Managing Zones,

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/8_x/config/fabric/cisco_mds9000_fabric_config_guide_8x/configuring_and_managing_zones.html

View solution in original post

I assume, that in the initial 2 MDS, you have eg. a active zoneset named "xyz".

Then you ISL one of this MDS to a NEXUS which has a different active zoneset "abc". the result of the zoneset merge will be: active zoneset with the higher value, which I think is "xyz", which contains all the zones, which existed on the MDS and the NEXUS. now you have to copy the active zoneset to the full zoneset, to make sure that after a boot, everything is consistent. Connecting back to the other MDS: same process….

View solution in original post

5 Replies 5

Walter Dey
VIP Alumni
VIP Alumni

Not quite clear what you want to achieve.

my 2c

Zoning is done per VSAN, therefore a zone merge between 2 switches, connected by ISL, requires identical VSAN's.

The Merge process is explained in great detail p76ff in Configuring and Managing Zones,

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/8_x/config/fabric/cisco_mds9000_fabric_config_guide_8x/configuring_and_managing_zones.html

Good Morning and thank you for the response. For clarification and a bit more detail, I have two 9148s that had been ISL and have matching VSANs and ZOning info. I will take one of these switches to a new data center. There is an existing switch there (NEX 5k) with its own VSANs/ zoning config. IN that the ISL requires matching VSANs, might I simply copy the zoneset information from this Nexus and then place it in my Zoneset on the 9148, then re create the ISL from this 9148 back to the other 9148 in the other data center with no issue. ALl VSANs will still be congruent and then a full distribute of the zoneset should get me up to date and synched? Thank You in Advance ...your assist is greatly appreciated.

Good Morning and thank you for the response. For clarification and a bit more detail, I have two 9148s that had been ISL and have matching VSANs and ZOning info. I will take one of these switches to a new data center. There is an existing switch there (NEX 5k) with its own VSANs/ zoning config. IN that the ISL requires matching VSANs, might I simply copy the zoneset information from this Nexus and then place it in my Zoneset on the 9148, then re create the ISL from this 9148 back to the other 9148 in the other data center with no issue. ALl VSANs will still be congruent and then a full distribute of the zoneset should get me up to date and synched? Thank YOu in A

I assume, that in the initial 2 MDS, you have eg. a active zoneset named "xyz".

Then you ISL one of this MDS to a NEXUS which has a different active zoneset "abc". the result of the zoneset merge will be: active zoneset with the higher value, which I think is "xyz", which contains all the zones, which existed on the MDS and the NEXUS. now you have to copy the active zoneset to the full zoneset, to make sure that after a boot, everything is consistent. Connecting back to the other MDS: same process….

Thank Good Sir

Review Cisco Networking for a $25 gift card