Highlighted
downhill2
3 Argentium

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

Labels (1)
0 Kudos
17 Replies
dynamox
6 Thallium

Re: Zone conflict when re-ISL'ing 2 switches together

was DS300 in use somewhere else ? Could you just wipe it clean and then re-connect to 5100.

0 Kudos
downhill2
3 Argentium

Re: Zone conflict when re-ISL'ing 2 switches together

well, not exactly, but it has all the NTP, SNMP, all the PITA stuff I really don't want to have to wipe it. I thought of that, but hey, this should be easy right?

I also tried pushing the same exact zoneset to the DS300 and then tried ISLing them, they wont merge (even though the sets are now identical on both).

Running 6.3.1b code on both.

thanks

0 Kudos
dynamox
6 Thallium

Re: Zone conflict when re-ISL'ing 2 switches together

did you look in the logs, i think it should tell you what's causing the conflict. Can you export both zoneset into a file and compare the two (using something like WinMerge)

0 Kudos
downhill2
3 Argentium

Re: Zone conflict when re-ISL'ing 2 switches together

The effective zones are the same and I can’t make sense of the logs (which one specifically)?

Effective configuration:

cfg: CCWSAN01

zone: appbms004_12e8_1556_SPab1

10:00:00:00:c9:84:12:e8

50:06:01:69:39:a0:1f:5c

50:06:01:61:39:a0:1f:5c

zone: esx101dev_b6aa_1556_SPab1

50:06:01:61:39:a0:1f:5c

50:06:01:69:39:a0:1f:5c

10:00:00:00:c9:6e:b6:aa

zone: esx102dev_b69d_1556_SPab1

50:06:01:69:39:a0:1f:5c

10:00:00:00:c9:6e:b6:9d

50:06:01:61:39:a0:1f:5c

zone: vir203dev_4fcd_1556_SPab1

10:00:00:00:c9:5a:4f:cd

50:06:01:61:39:a0:1f:5c

50:06:01:69:39:a0:1f:5c

zone: vir204dev_135c_1556_SPab1

10:00:00:00:c9:89:13:5c

50:06:01:61:39:a0:1f:5c

50:06:01:69:39:a0:1f:5c

CCWSAN03:admin>

Effective configuration:

cfg: CCWSAN01

zone: appbms004_12e8_1556_SPab1

10:00:00:00:c9:84:12:e8

50:06:01:61:39:a0:1f:5c

50:06:01:69:39:a0:1f:5c

zone: esx101dev_b6aa_1556_SPab1

10:00:00:00:c9:6e:b6:aa

50:06:01:69:39:a0:1f:5c

50:06:01:61:39:a0:1f:5c

zone: esx102dev_b69d_1556_SPab1

10:00:00:00:c9:6e:b6:9d

50:06:01:69:39:a0:1f:5c

50:06:01:61:39:a0:1f:5c

zone: vir203dev_4fcd_1556_SPab1

10:00:00:00:c9:5a:4f:cd

50:06:01:61:39:a0:1f:5c

50:06:01:69:39:a0:1f:5c

zone: vir204dev_135c_1556_SPab1

10:00:00:00:c9:89:13:5c

50:06:01:61:39:a0:1f:5c

50:06:01:69:39:a0:1f:5c

CCWSAN01:FID128:admin>

It does not make sense.

0 Kudos

Re: Zone conflict when re-ISL'ing 2 switches together

Instead of wiping the switch clean, have you tried just disabling the current config on the switch you are trying to add?  i believe - cfgdisable "CCWSAN01"  and then cfgclear.  This will get rid of the zoning and then try to isl the switches back.  Again do this on the switch you are trying to add and NOT the current running switch

downhill2
3 Argentium

Re: Zone conflict when re-ISL'ing 2 switches together

Yes. I did that multiple times, and finally tried the configdefault but that did not help either.

0 Kudos

Re: Zone conflict when re-ISL'ing 2 switches together

As minute as it may sound the following zones:

zone:  esx101dev_b6aa_1556_SPab1

                10:00:00:00:c9:6e:b6:aa

                50:06:01:69:39:a0:1f:5c

                50:06:01:61:39:a0:1f:5c

zone:  esx102dev_b69d_1556_SPab1

                10:00:00:00:c9:6e:b6:9d

                50:06:01:69:39:a0:1f:5c

                50:06:01:61:39:a0:1f:5c

dont have the same order of membership.  Meaning that the zones have members added in the wrong spot.  According to brocade they need be 100% identicle:

----

Identical zone configuration is the most critical one, you need to edit both effective zone and make sure that each entry or object on each merging zone config are the same. They need to be identical, line by line object by object in the same order. Each zone need to have the same content in the same order.

----

try that...

0 Kudos

Re: Zone conflict when re-ISL'ing 2 switches together

Hi,

It might also be worthwhile checking the default zoning behavior of each switch. It looks like for the 5100 you are using logical FID 128. So,

setcontext 128

defzone --show

Then see if the settings are the same for the switch that you are trying to join.

Best regards.

downhill2
3 Argentium

Re: Zone conflict when re-ISL'ing 2 switches together

Dude, thanks for the advice but I need some real help. These are different because they are 2 different zones.

0 Kudos