Fibre Channel (SAN)

Reply
adi
Occasional Contributor
Posts: 5
Registered: ‎07-16-2010

Any one used zonemerge tool for fabric merge ?

Hello ,

Any one used zone merge tool to perform fabric merge?

Have downloaded and verified the zones with merge tool , and   shown one conflict error as active zone config is not unique .

My question is, after connecting ISL, when you click on U button on the merge tool, would it merge the zones to principle switch and all work done?

or any additional work needs to be done ?

Much appreciate if someone can reply who used merge tool to perform the fabric merge successfully.

Thanks.

Contributor
Posts: 31
Registered: ‎04-16-2007

Re: Any one used zonemerge tool for fabric merge ?

Hi

Rule for merging

  1. Different Domain id.
  2. Same Default zone access (no access or full access) this can segment the merge if not the same.
    1. Not access mean that if the effective zone is not available of any reason then no server will have access to their lun
    2. Full access mean that if the effective zone is not available for any reason then all the server will see all the lun and that could impact the data such like corruption. the default is no access. Run this command to view the default zone access defzone –show
    3. Identical Zone configuration (not rename).

Step 3 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.

Ex.: Zone config YY in Fabric y have Zone A with alias YYY
Ex.: Zone Config XX in Fabric X have Zone B with alias XXX

Before the merge

Zone config YY should contained
                Zone A with alias YYY
                Zone B with alias XXX

Zone config XX should contained
                Zone A with alias YYY
                Zone X with alias XXX

Again each object need to be identical line by line on both fabric zone config that you want to merge. DCFM or Fabric Manager

Super Contributor
Posts: 425
Registered: ‎03-03-2010

Re: Any one used zonemerge tool for fabric merge ?

If you do not have DCFM or FM, pls do not try it or else you will get error on configmismatch and if not handled properly you may lose your zones.The best way is to take the downtime and merge the fabric.Otherwise try in one fabric only, keeping all the devices in single path.Btw pls do let us know if you are successful with zone merge tool providing the step by step.

Thank you

External Moderator
Posts: 4,811
Registered: ‎02-23-2004

Re: Any one used zonemerge tool for fabric merge ?

@ hemant,

the Threads http://community.brocade.com/message/12042#12042 was opened first by adi,

and you post answer about migration.

today you post about migration

--->>>....pls do not try it or else you will get error on configmismatch and if not handled properly you may lose your zones.

TechHelp24
adi
Occasional Contributor
Posts: 5
Registered: ‎07-16-2010

Re: Any one used zonemerge tool for fabric merge ?

Hello techhelp24/hemanth ,

Thanks for the replies ...have decided not to use zone merger tool ,except to find any mismatches in alias and zoning .

As i posted before, different active config running on two different switches switchA and switchB ,hence i decided to disable the zoning on switchB   .

and after the merge ,i would hope can see the zones on source switch "SwitchA" ,and those will be added to the active config and will reenable .

would u think it would be the best approach to merge the fabric ,running two different active configs ?if not can you suggest straight forward sequence .

Thanks in advance .

Super Contributor
Posts: 644
Registered: ‎03-01-2007

Re: Any one used zonemerge tool for fabric merge ?

--->>> We are merging brocade 48k switches located in each data centre .  .

Q.:

1- Are both 48K Productive ?

2- What is the reason you want to Merge both DC ?

adi
Occasional Contributor
Posts: 5
Registered: ‎07-16-2010

Re: Any one used zonemerge tool for fabric merge ?

Hello ,

switchA and switchC at one data centere

switchB and switchD are at another data centre   .

we are creating diaster recovery sites ...hence

merging switchA and switchB

merging switchC and switchD .

All are 48k ,running 6.2.0b .

Super Contributor
Posts: 644
Registered: ‎03-01-2007

Re: Any one used zonemerge tool for fabric merge ?

adi,

--->>>switchA and switchC at one data centere....

--->>>switchB and switchD are at another data centre....

Q.:

1 - are a Pair of Director connected as ISL ?

Also,

2 - A + C in the same Fabric ?

3 - B + D in the same Fabric ?

adi
Occasional Contributor
Posts: 5
Registered: ‎07-16-2010

Re: Any one used zonemerge tool for fabric merge ?

Hello ,

SwitchA and SwitchC are two single  isolated directors at first-site ,each one running its own config .No isl between .If server has two hba's ,each hba connects to each director for redundancy .

SwitchB and SwitchD are two single  isolated directors at second site ,each one running its own config .No isl between .If server has two hba's ,each hba  connects to each director for redundancy .

using long wave SFP's ,we are planing  to merge SwitchA +SwitchB into single fabric .

same way ,will merge SwitchC + SwitchD

Super Contributor
Posts: 425
Registered: ‎03-03-2010

Re: Any one used zonemerge tool for fabric merge ?

Hi Aditya,

When you will disable the  active config of SW B and then you will try to merge it with SW A to make one Fabric.SW A's active config will be seen in the fabric because zone DB will be spread accross the fabric, which now contains SW A and B.

When you will disable the active config file in SW B, if the defzone --all acess is there in SW B, then each device will be able to see every other device.This  is a problem here.You have to make it defzone --no access in SW B.But it is disruptive. So you have to think

Now when u r ready to merge, then disable the SW B with switchdisable, cfgdisable, configure, set the Domain id(unique) and other parameters as it is in SW A(configshow), then enable the switch with switchenable and then connect one of the ISL, if you do not see any error, through errdump, islshow, fabricshow,then connect the other ISL, now ur SW B is merged. now you can check through zoneshow or cfgshow.SW B's zones will not be in ur SW A's active config, now you have to enable those zones with cfgadd "active config name", "zone a; zone b; .....of ur SW B", the cfgsave and cfgenable "active config name".

Then check with ur SAN devices.

see the all these cmnds' help page.

look here the difference:

switch:admin> cfgShow
         Defined configuration:
          cfg:   USA1    Blue_zone
          cfg:   USA_cfg Red_zone; Blue_zone
          zone:  Blue_zone
                 1,1; array1; 1,2; array2
          zone:  Red_zone
                 1,0; loop1
          alias: array1  21:00:00:20:37:0c:76:8c; 21:00:00:20:37:0c:71:02
          alias: array2  21:00:00:20:37:0c:76:22; 21:00:00:20:37:0c:76:28
          alias: loop1   21:00:00:20:37:0c:76:85; 21:00:00:20:37:0c:71:df

        Effective configuration:
          cfg:   USA_cfg
          zone:  Blue_zone
                 1,1
                 21:00:00:20:37:0c:76:8c
                 21:00:00:20:37:0c:71:02
                 1,2
                 21:00:00:20:37:0c:76:22
                 21:00:00:20:37:0c:76:28
          zone:  Red_zone
                 1,0
                 21:00:00:20:37:0c:76:85
                 21:00:00:20:37:0c:71:df

     To display only configuration names:

       sw5:admin> cfgShow "*"
        cfg:   USA1    Blue_zone
        cfg:   USA_cfg Red_zone; Blue_zone

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

also look here from my SW:

DS4800_B16_SW1:admin> cfgdisable
You are about to disable zoning configuration. This
action will disable any previous zoning configuration enabled.
Do you want to disable zoning configuration? (yes, y, no, n): y
Updating flash ...
DS4800_B16_SW1:admin> cfgshow
Defined configuration:
cfg:   HDFCBANK_ZONE_1
                CHA1675_CTL_A; HBH4249_CTL_A; CHA1675_CTL_B; HBH4249_CTL_B;
                HBH4246_CTL_A; HBH4246_CTL_B; E_TREASURY_CTL_A;
                E_TREASURY_CTL_B; MISYSLVAPP_CTL_A; MISYSLVAPP_CTL_B;
                MISYSLVDB_CTL_A; MISYSLVDB_CTL_B
zone:  CHA1675_CTL_A
                1,0; 1,3
zone:  CHA1675_CTL_B
                1,1; 1,3
zone:  E_TREASURY_CTL_A
                1,0; 1,14
zone:  E_TREASURY_CTL_B
                1,1; 1,14
zone:  HBH4246_CTL_A
                1,0; 1,4
zone:  HBH4246_CTL_B
                1,1; 1,4
zone:  HBH4249_CTL_A
                1,0; 1,2
zone:  HBH4249_CTL_B
                1,1; 1,2
zone:  MISYSLVAPP_CTL_A
                1,0; 1,6
zone:  MISYSLVAPP_CTL_B
                1,1; 1,6
zone:  MISYSLVDB_CTL_A
                1,0; 1,5
zone:  MISYSLVDB_CTL_B
                1,1; 1,5

Effective configuration:
no configuration in effect

DS4800_B16_SW1:admin> zoneshow
Defined configuration:
cfg:   HDFCBANK_ZONE_1
                CHA1675_CTL_A; HBH4249_CTL_A; CHA1675_CTL_B; HBH4249_CTL_B;
                HBH4246_CTL_A; HBH4246_CTL_B; E_TREASURY_CTL_A;
                E_TREASURY_CTL_B; MISYSLVAPP_CTL_A; MISYSLVAPP_CTL_B;
                MISYSLVDB_CTL_A; MISYSLVDB_CTL_B
zone:  CHA1675_CTL_A
                1,0; 1,3
zone:  CHA1675_CTL_B
                1,1; 1,3
zone:  E_TREASURY_CTL_A
                1,0; 1,14
zone:  E_TREASURY_CTL_B
                1,1; 1,14
zone:  HBH4246_CTL_A
                1,0; 1,4
zone:  HBH4246_CTL_B
                1,1; 1,4
zone:  HBH4249_CTL_A
                1,0; 1,2
zone:  HBH4249_CTL_B
                1,1; 1,2
zone:  MISYSLVAPP_CTL_A
                1,0; 1,6
zone:  MISYSLVAPP_CTL_B
                1,1; 1,6
zone:  MISYSLVDB_CTL_A
                1,0; 1,5
zone:  MISYSLVDB_CTL_B
                1,1; 1,5

Effective configuration:
no configuration in effect

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

DS4800_B16_SW1:admin> alishow
Defined configuration:
cfg:   HDFCBANK_ZONE_1
                CHA1675_CTL_A; HBH4249_CTL_A; CHA1675_CTL_B; HBH4249_CTL_B;
                HBH4246_CTL_A; HBH4246_CTL_B; E_TREASURY_CTL_A;
                E_TREASURY_CTL_B; MISYSLVAPP_CTL_A; MISYSLVAPP_CTL_B;
                MISYSLVDB_CTL_A; MISYSLVDB_CTL_B
zone:  CHA1675_CTL_A
                1,0; 1,3
zone:  CHA1675_CTL_B
                1,1; 1,3
zone:  E_TREASURY_CTL_A
                1,0; 1,14
zone:  E_TREASURY_CTL_B
                1,1; 1,14
zone:  HBH4246_CTL_A
                1,0; 1,4
zone:  HBH4246_CTL_B
                1,1; 1,4
zone:  HBH4249_CTL_A
                1,0; 1,2
zone:  HBH4249_CTL_B
                1,1; 1,2
zone:  MISYSLVAPP_CTL_A
                1,0; 1,6
zone:  MISYSLVAPP_CTL_B
                1,1; 1,6
zone:  MISYSLVDB_CTL_A
                1,0; 1,5
zone:  MISYSLVDB_CTL_B
                1,1; 1,5

Effective configuration:
no configuration in effect

admin> switchshow
switchName:     DS4800_B16_SW1
switchType:     34.0
switchState:    Online
switchMode:     Native
switchRole:     Principal
switchDomain:   1
switchId:       fffc01
switchWwn:      10:00:00:05:1e:02:35:55
zoning:         OFF
switchBeacon:   OFF

Area Port Media Speed State     Proto
=====================================
  0   0   id    N4   No_Light
  1   1   id    N4   No_Light
  2   2   id    N4   No_Light
  3   3   id    N4   No_Light
  4   4   id    N4   No_Light............

-------------------------------------------------------------------------------------
DS4800_B16_SW1:admin> cfgenable "HDFCBANK_ZONE_1"
You are about to enable a new zoning configuration.
This action will replace the old zoning configuration with the
current configuration selected.
Do you want to enable 'HDFCBANK_ZONE_1' configuration  (yes, y, no, n): y
zone config "HDFCBANK_ZONE_1" is in effect
Updating flash ...
DS4800_B16_SW1:admin>

DS4800_B16_SW1:admin> alishow
Defined configuration:
cfg:   HDFCBANK_ZONE_1
                CHA1675_CTL_A; HBH4249_CTL_A; CHA1675_CTL_B; HBH4249_CTL_B;
                HBH4246_CTL_A; HBH4246_CTL_B; E_TREASURY_CTL_A;
                E_TREASURY_CTL_B; MISYSLVAPP_CTL_A; MISYSLVAPP_CTL_B;
                MISYSLVDB_CTL_A; MISYSLVDB_CTL_B
zone:  CHA1675_CTL_A
                1,0; 1,3
zone:  CHA1675_CTL_B
                1,1; 1,3
zone:  E_TREASURY_CTL_A
                1,0; 1,14
zone:  E_TREASURY_CTL_B
                1,1; 1,14
zone:  HBH4246_CTL_A
                1,0; 1,4
zone:  HBH4246_CTL_B
                1,1; 1,4
zone:  HBH4249_CTL_A
                1,0; 1,2
zone:  HBH4249_CTL_B
                1,1; 1,2
zone:  MISYSLVAPP_CTL_A
                1,0; 1,6
zone:  MISYSLVAPP_CTL_B
                1,1; 1,6
zone:  MISYSLVDB_CTL_A
                1,0; 1,5
zone:  MISYSLVDB_CTL_B
                1,1; 1,5

Effective configuration:
cfg:   HDFCBANK_ZONE_1
zone:  CHA1675_CTL_A
                1,0
                1,3
zone:  CHA1675_CTL_B
                1,1
                1,3
zone:  E_TREASURY_CTL_A
                1,0
                1,14
zone:  E_TREASURY_CTL_B
                1,1
                1,14
zone:  HBH4246_CTL_A
                1,0
                1,4
zone:  HBH4246_CTL_B
                1,1
                1,4
zone:  HBH4249_CTL_A
                1,0
                1,2
zone:  HBH4249_CTL_B
                1,1
                1,2
zone:  MISYSLVAPP_CTL_A
                1,0
                1,6
zone:  MISYSLVAPP_CTL_B
                1,1
                1,6
zone:  MISYSLVDB_CTL_A
                1,0
                1,5
zone:  MISYSLVDB_CTL_B
                1,1
                1,5

DS4800_B16_SW1:admin> zoneshow
Defined configuration:
cfg:   HDFCBANK_ZONE_1
                CHA1675_CTL_A; HBH4249_CTL_A; CHA1675_CTL_B; HBH4249_CTL_B;
                HBH4246_CTL_A; HBH4246_CTL_B; E_TREASURY_CTL_A;
                E_TREASURY_CTL_B; MISYSLVAPP_CTL_A; MISYSLVAPP_CTL_B;
                MISYSLVDB_CTL_A; MISYSLVDB_CTL_B
zone:  CHA1675_CTL_A
                1,0; 1,3
zone:  CHA1675_CTL_B
                1,1; 1,3
zone:  E_TREASURY_CTL_A
                1,0; 1,14
zone:  E_TREASURY_CTL_B
                1,1; 1,14
zone:  HBH4246_CTL_A
                1,0; 1,4
zone:  HBH4246_CTL_B
                1,1; 1,4
zone:  HBH4249_CTL_A
                1,0; 1,2
zone:  HBH4249_CTL_B
                1,1; 1,2
zone:  MISYSLVAPP_CTL_A
                1,0; 1,6
zone:  MISYSLVAPP_CTL_B
                1,1; 1,6
zone:  MISYSLVDB_CTL_A
                1,0; 1,5
zone:  MISYSLVDB_CTL_B
                1,1; 1,5

Effective configuration:
cfg:   HDFCBANK_ZONE_1
zone:  CHA1675_CTL_A
                1,0
                1,3
zone:  CHA1675_CTL_B
                1,1
                1,3
zone:  E_TREASURY_CTL_A
                1,0
                1,14
zone:  E_TREASURY_CTL_B
                1,1
                1,14
zone:  HBH4246_CTL_A
                1,0
                1,4
zone:  HBH4246_CTL_B
                1,1
                1,4
zone:  HBH4249_CTL_A
                1,0
                1,2
zone:  HBH4249_CTL_B
                1,1
                1,2
zone:  MISYSLVAPP_CTL_A
                1,0
                1,6
zone:  MISYSLVAPP_CTL_B
                1,1
                1,6
zone:  MISYSLVDB_CTL_A
                1,0
                1,5
zone:  MISYSLVDB_CTL_B
                1,1
                1,5

DS4800_B16_SW1:admin> cfgshow
Defined configuration:
cfg:   HDFCBANK_ZONE_1
                CHA1675_CTL_A; HBH4249_CTL_A; CHA1675_CTL_B; HBH4249_CTL_B;
                HBH4246_CTL_A; HBH4246_CTL_B; E_TREASURY_CTL_A;
                E_TREASURY_CTL_B; MISYSLVAPP_CTL_A; MISYSLVAPP_CTL_B;
                MISYSLVDB_CTL_A; MISYSLVDB_CTL_B
zone:  CHA1675_CTL_A
                1,0; 1,3
zone:  CHA1675_CTL_B
                1,1; 1,3
zone:  E_TREASURY_CTL_A
                1,0; 1,14
zone:  E_TREASURY_CTL_B
                1,1; 1,14
zone:  HBH4246_CTL_A
                1,0; 1,4
zone:  HBH4246_CTL_B
                1,1; 1,4
zone:  HBH4249_CTL_A
                1,0; 1,2
zone:  HBH4249_CTL_B
                1,1; 1,2
zone:  MISYSLVAPP_CTL_A
                1,0; 1,6
zone:  MISYSLVAPP_CTL_B
                1,1; 1,6
zone:  MISYSLVDB_CTL_A
                1,0; 1,5
zone:  MISYSLVDB_CTL_B
                1,1; 1,5

Effective configuration:
cfg:   HDFCBANK_ZONE_1
zone:  CHA1675_CTL_A
                1,0
                1,3
zone:  CHA1675_CTL_B
                1,1
                1,3
zone:  E_TREASURY_CTL_A
                1,0
                1,14
zone:  E_TREASURY_CTL_B
                1,1
                1,14
zone:  HBH4246_CTL_A
                1,0
                1,4
zone:  HBH4246_CTL_B
                1,1
                1,4
zone:  HBH4249_CTL_A
                1,0
                1,2
zone:  HBH4249_CTL_B
                1,1
                1,2
zone:  MISYSLVAPP_CTL_A
                1,0
                1,6
zone:  MISYSLVAPP_CTL_B
                1,1
                1,6
zone:  MISYSLVDB_CTL_A
                1,0
                1,5
zone:  MISYSLVDB_CTL_B
                1,1
                1,5

========================================================================================

look at the difference, now you can see the effective configuration, but the problem is you have keep a note of ur all aliases and zones of SW B because you will not be able to see the aliases of SW B and zones will make you confusing.

so the best practice is take the down time . Make a note of the zones and HBAs of SW B. on SW B , do a switchdisable, cfgdisable, cfgclear( that will clear your all aliases and zones in SW B), cfgsave,  then configure the SW with configure cmd and then do  switchenable. Connect ISLs, check the merging is successful , then create aliases, zones and cfgadd, cgsave, cfgenable with active configuration .

This is tedious but make you safer.

Pls note: after ISL connection, never ever do a cfgdisable or cfgclear, disconnect the ISL and do these on SW B.

Like this do with SW C and SW D. Always maintain safer side with the best practice and that is switchdisable, cfgdisable, cfgclear,cfgsave, configure, switchenable, and merge the SWs, create aliases, zones, add those to active config and cfgsave, and enable the active  config.

Pls let me know in case you face any issue.

mark the thread correct if you find it helpful

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.