Brocade Fibre Channel Networking Community

Expand all | Collapse all

Merging 2 Different Fabrics

  • 1.  Merging 2 Different Fabrics

    Posted 09-24-2019 11:31 AM
    Hello, I have a task that I must complete for a large customer and seek advice. The task is merging 2 running fabrics, both fabrics have effective configurations. There are about 7 switches in each fabric on each side of various types, most are director class switches.

    I feel comfortable in that all switches in each fabric have unique DIDs. All zone(s) names in each fabric are unique. All aliases names in each fabric are also unique. Effective configurations on each side are named differently.

    My question is the procedure to execute the merge. Below is some detail and the context is I am only talking about merging Fabric A on Day 1. I need to do the same on Fabric B day 2.

    Documentation is scarce. Side A is larger so that side will be the primary fabric that will remain and will use that effective configuration name. Side B needs to merge into side A. All hosts have verified redundant HBAs and multipath is working. This is my cloudy plan and seek advice as to which plan below might be close.

    Plan A
    Side A remains untouched
    Side B execute cfgdisable on effective config
    Side B execute zoneobject rename on the old effective config matching the same name as site A
    ISL the sites together and verify no segmentation
    Execute cfgenable and verify all the zones from both sides are in the effective configuration

    Plan B
    Side A remains untouched
    Side B execute cfgdisable on effective config
    ISL the sites together and verify no segmentation
    Execute cfgenable and verify all the zones from both sites are in the effective configuration

    Am I close? Seems like Plan A would do it.

    I also understand all the link parameters and time outs etc need to match as well as FOS versions etc. Will get backups of each switch prior configupload etc.

    Any feedback would greatly appreciated.

    Thanks,

    jim


  • 2.  RE: Merging 2 Different Fabrics

    Posted 09-26-2019 03:38 AM
    Hi Jim, how are you?

    1- You plan looks good, you looks on the way =]
    2- As you know to merge SAN Fabrics the main key to do not get a zone segmentation once ISL is enabled is making sure the effective zone configuration is the same at both sides (Fabric A and Fabric B)
    3- It means that the mentioned zone object rename will not help you at this point, you need to choose a Fabric to be the principal (like Fabric A) and then add this zone configuration into Fabric B, so once it is merged, both fabrics will have same zone/aliases characteristics
    4- Export the effective zone configuration from Fabric A and add each zone/alias/member into Fabric B zone configuration
    5- Rename the zoneset of Fabric B to the same name of Fabric A

    Hope that's help.




  • 3.  RE: Merging 2 Different Fabrics

    Posted 09-26-2019 09:47 PM
    Thank you for the reply.

    I understand what you are saying. I do have a question on #3.

    Will I need just all the zones in the Fabric A effective configuration added to Fabric B? Or also all the other zones on the switch in other configurations as well from Fabric A. ​​And does all the zones in the Fabric B effective configuration need to be added to fabric A before the merge? Including all the other zones in Fabric B?  Both fabrics have active production workloads.

    Thanks,

    jim

    ------------------------------
    Presidio
    ------------------------------



  • 4.  RE: Merging 2 Different Fabrics

    Posted 09-28-2019 09:58 AM
    Hi Jim.

    1- Why are you going to merge two different fabrics? Is it a consolidation?
    2- You do not need to have the same zone configuration from Fabric A on Fabric B, except if you are going to use all SAN switches from Fabric B on Fabric A, and vice versa
    3- It means, if you are going to do some SAN Switch consolidation, you should have the same zone configuration from Fabric A replicated to Fabric B, and zone configuration from Fabric B replicated to Fabric A, so once ISL is enabled "both fabrics" will have same zone configuration and won't cause a zone segmentation

    Regards

    ------------------------------
    [Senior IT Consultant]
    [Brazil]
    ------------------------------



  • 5.  RE: Merging 2 Different Fabrics

    Posted 09-28-2019 10:56 AM
    That's exactly what I am doing. Consolidating and interconnecting 2 data centers, Fabric A consolidation both sites, and Fabric B consolidations both sites.

    My plan now is to export the effective configs, zones, alias etc from each site and add them to the other site so basically the fabrics are the same.  Rename the effective configuration to the same name (rename one side only matching the other name with zoneobject rename), then cfgenable.

    Thanks for all you assistance.

    Jim


  • 6.  RE: Merging 2 Different Fabrics

    Posted 27 days ago
    Well I/we completed the merge/consolidation this weekend.  Thanks so much... what we ended up doing to consolidate both sites is add all the zoning from the secondary site to the primary larger site, clear out the secondary site and ISL them together.  Had to wrestle the switches at the secondary site to get all the ISLs working but we got it done without issue.  Awesome..... 26 switches involved total, 13 per fabric.  18km distance 32G per fabric site to site :)

    Jim


  • 7.  RE: Merging 2 Different Fabrics

    Posted 26 days ago

    Hello Jim, awesome!!

    Congrats, you were the man!!

     

    Keep us updated on next issues... CYA

     

    Obrigado.

    Atenciosamente,

     

    Rafael Vilela Dias

    Senior IT Consultant / Storage Specialist  | Brazil | UTC-3

    Accenture Technology | Intelligent Cloud and Infrastructure | Infrastructure Services for Accenture
    Email & Skype/Teams: rafael.vilela@accenture.com

    Phone: +55 11 2360-7084

     

    TS Brazil - Accenture Operations

     




    This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
    ______________________________________________________________________________________

    www.accenture.com