Brocade Fibre Channel Networking Community

Expand all | Collapse all

Switch replacement

Jump to Best Answer
  • 1.  Switch replacement

    Posted 12-03-2018 11:12 AM

    Hello,  I was wondering of an easy way to bring over the config file with zones and aliases from a 5300 switch to a 6510 switch.  This is a single switch fiber.  The existing switch is running 7.4.2c  and the new one 6510 is running 8.0.2d


    All connections will need to move to 6510 switch.  I licensed all the 48 ports there and configured its management, snmp, ntp, timezone etc...


    I do have backups of the old switch by running configupload weekly to a repository on CMCNE (BNA)


    What is the recommended way of transferring a cfg file from one switch to another?  All zoning is done by WWNs which will stay the same for both targets and initiators. (I"m just replacing the switch)


    Was wondering if I can take a configupload of the new 6510 switch and then on test file modify only the area for zoning by adding all Zone section from 5300 backup file  and then do a configdownload of the modified backup of 6510 to same 6510 switch.


    Will this work?  Is there another way of transferring cfg file from one switch to another ?   I do not want to do a full configdownload from 5300 to 6510 as starting with FOS is different but I thought if I could modify only the section of [Zoning]  and do a configdownload. 




  • 2.  Re: Switch replacement

    Posted 12-03-2018 02:08 PM

    Assuming the 6510 is brand-new , nothing connected and has basic configuration setup completed (ip address, domain ID, zoning policy, etc) and assuming you want to use the same domain ID as the 5300, one idea is to temporarily set the 6510 domain ID to value different than 5300, connect an ISL between 5300 and 6510 to import the zoning from 5300. Then disconnect the ISL and reset 6510's domain ID, if necessary, back to desired domain ID value.


  • 3.  Re: Switch replacement

    Posted 12-04-2018 09:40 AM

    Yes, the 6510 is brand new.  If does have Domain ID 1 which it would conflict with existing 5300.  I can disable the 6510, change its domain ID to maybe 2 and run an ISL and do it this way.  


    No, I don't need to preserve domain ID.  It can use id 2 at the end or maybe change back to 1. Again this is a single switch fabric so it won't matter.




  • 4.  Re: Switch replacement

    Posted 12-17-2018 08:54 AM

    This is not working...   The 6510 switch says  (zone conflict)  when trying to ISL with existing 5300 switch.   I did change the domain ID on it.  So 5300 has Domain ID 1 and 6510 had domain ID 2.    I also ran cfgclear,  sfgsave on new switch,  although there was no current zones or cfg file in the new switch. 


    Does it matter that the new switch 6510 runs version 8.0.2d  and old 5300 is v7.4.2c?   Not sure why it segments out once I enable the port where the ISL link is.


    Any suggestions?


  • 5.  Re: Switch replacement

    Posted 12-17-2018 09:40 AM



    --->>>Does it matter that the new switch 6510 runs version 8.0.2d  and old 5300 is v7.4.2c?




    most probable is a defzone issue on 5300


    check with the command "defzone --show" if is set to noaccess or allaccess


    for major details refer command reference manuals




  • 6.  Re: Switch replacement

    Posted 12-17-2018 09:50 AM

    Hi Antonio,  thanks for the reply. 


    On 5300  if I run the defzone --show I get:


    Default Zone Access Mode

                  committed - All Access

                  transaction - No Transaction



    On 6510 (New switch)  I get:


    Default Zone Access Mode

                  committed - No Access

                  transaction - No Transaction


  • 7.  Re: Switch replacement
    Best Answer

    Posted 12-17-2018 09:52 AM



    well, then try set on 6510 to allaccess


  • 8.  Re: Switch replacement

    Posted 12-17-2018 11:13 AM

    That made it.  Now I see both switches on same fabric and active cfg file is present on new switch.




  • 9.  Re: Switch replacement

    Posted 12-04-2018 12:48 AM



    if you will connect switches together (as described above), you may reconnect all old connection without downtime, of course with correct multipath configuration.