Unsolved
This post is more than 5 years old
157 Posts
0
12181
Zone conflict when re-ISL'ing 2 switches together
I've looked at similar discussions on this but just don't see the answer as to what the issue is. Originally I had 2 seperate DS300's and zoning them as seperate fabrics, no problem, with ECC. Then, in order to replace them with DS5100's as cores, I added a DS5100 to each fabric and they merged fine. After making sure both switches had the same zonesets, I migrated all hosts/storage from the 300s to the 5100s, and subsequently blocked the ports on the DS300s so they could be moved to different racks, etc. This all happened about 2 months ago. ECC was quite pissy about the missing switches, so I removed them from the SMI-S provider and rediscovered only the DS5100s, thus cleaning up ECC anyways. Several zone changes later and I'm now trying to link those DS300's back into the DS5100s. Sounds so simple I bet the monkey could do it but as soon as I connect them the switches log "zone conflict" and fabricshow only shows one switch in each fabric. They simply won't merge back. No domain IDs were changed, only the zonesets would have ever gotten changed.
Domain ID for sw1 is #97, sw2 is #1
The only thing I see is the DS300 (the one I am adding back in to a working fabric) has the lower WWN than the DS5100. I've played around with the fabricprincipal, but it seems to make no diff.
Anyone have any clues as to how to force these things to link back up into their previously happy state?
thanks!
Dave
downhill2
157 Posts
0
June 8th, 2011 07:00
I realize that VF stuff is optional, but since I didn't really see a need for it ever in this environment, I preferred to just disable it and make them all look like our other switches. To clarify the steps on the DS300 which really solved the issue after disabling VF on the DS5100, and forcing the principal on there,
1. switchdisable
2. cfgdisable
3. cfgclear
4. cfgsave
5. defzone --allaccess
6. cfgsave
7. switchenable
voila, merged! thanks again.
Richard_Butler
84 Posts
0
June 8th, 2011 07:00
Hi Dave,
Glad the 'defzone' changes fixed the merge.
Just a point around the solution, rather than setting both switches to 'allaccess' it is probably better to set both switches to 'noaccess'; you will then have disabled the default zoning behaviour on each switch (hence still no conflict). This solution would be similar to a Cisco 'no zone default-zone permit vsan 1-4093'
Rgds, Richard.