Hi,

Yes that would be an option.

But copying the zones from LS to the other,  is like re-creating them anyway.

You actually can do that all before you do the move.

Regards,

Ed

1) Per your steps, what will happen to existing aliases once ports are moved ?

2) Is there any alternative other then removing & recreating zoning, as this will be a very lenghty stuff as FID 2 & 6 have too many zones ?

for e.g can this be done;

a. Create New Defined Zone in FID 128, say New_Zone

b. Move ports to default switch FID 128

c. Copy zones from current effective config of FID 2 & FID 6 to new config New_Zone

d. Delete LS

Can this be done like below;

-----------------------------------------------------------

Switches are already ISL connected

On Switch_1 > DID is already 1 & Principal

Run switchdisable on Switch_1

Run switchdisable on Switch_2

1) Do configupload_Switch1_FID2.txt from Switch_1:FID 2

2) Do configupload_Switch1_FID6.txt from Switch_1:FID 6

3) Create new zone config New_Zone in FID 128

4) Do configupload_Switch1_FID128.txt from Switch_1:FID 128

5) Move all ports from FID 2 & FID 6 to FID 128

6) Delete FID 2 & FID 6

7) Copy zones and alias information from configupload_Switch1_FID2.txt & configupload_Switch1_FID6.txt file and paste appropriately in configupload_Switch1_FID128.txt

6) Do configdownload_Switch1_FID128.txt while in FID 128 context

7) Add all zones to New_Zone using cfgadd

8) cfgsave

9) switchenable

10 cfgenable New_Zone

On Switch_2 > DID is already 2 & Principal

11) Do configupload_Switch2_FID2.txt from Switch_2:FID 2

12) Do configupload_Switch2_FID6.txt from Switch_2:FID 6

13) NOT CREATING ANY DEFINED ZONE CONFIG IN FID 128

14) Do configupload_Switch2_FID128.txt from Switch_2:FID 128

15) Move all ports from FID 2 & FID 6 to FID 128

16) Delete FID 2 & FID 6

17) Copy zones and alias information from configupload_Switch2_FID2.txt & configupload_Switch2_FID6.txt file and paste appropriately in configupload_Switch2_FID128.txt

18) Do configdownload_Switch2_FID128.txt while in FID 128 context

19) switchenable

At this point switch will merge and I guess Switch_2 will become subordinate

Are this steps correct?

Hi there,

I see that you posted the same question on the Brocade community.

Setting this questions as answered.

Best Regards,

Ed

Hello EdSchulte,

Yes I did, but I am not getting any answer or help. Hence posted here also, and infact I got help here

Would appreciate any help on my question. So the steps I have mentioned are ok or any modification required?

Thanks,

Hi,

No, that will not work. Switch 1 and 2 have in the end different zoning, and will not merge. You need to have on both switches the EXACT same zoning to be able to merge.

The principal of the actions are correct.

Regards,

Ed

Ok, so these means whatever steps I have mentioned are logically ok, but will not work in my case then.

Then I believe only option left to me is to follow either of the two solutions what you stated earlier;

Scenario 1:

- Remove zoning.

- Move ports from LS to default.

- Delete LS.

- Once done, in default switch disable VF, and reboot.

- Re-create zoning.

Scenario 2:

Is easier.

- Remove zoning.

- Move ports to default switch.

- Delete LS.

- In default switch re-create zoning.

For either of,

1) On Switch_1 > Will create zoning config with name "New_Zone_Config" and follow your steps

2) On Switch_2 > Will create zoning config with name "New_Zone_Config" and follow your steps

At this stage, both switches will have;

> Zoning Config with same name

> Different zone names on both switches as that will depend on the hosts (aliases) connected

Now If I merge switch, then operation will be ok which will have have single fabric with single zoning config name with 2 switches ?

Hi,

You need to make sure that the zoning is the same on BOTH fabrics are exactly the same, otherwise they won't merge.

Another option would be to create the all zoning on 1 switch, clear the zoning on the other and merge, so that the zoning is also merged to the other switch.

Refer to Admin and Command guides downloadable from our support website.

Regards,

Ed