 Is there another way to change the Domain ID without disruptive configurations? Just to know, because if all redundancy is well configured I should have no problems of bringing a pair of switches down for a little time (if no other conflicts are generated like you mentioned).    i don't know of a non-disruptive way, whenever you change domain id the switch will tell you that it has to reboot but if you have two redundant fabrics and all systems will be setup with redundancy you should be fine. This is what i would  do, others can correct me or add if i missed anything :  pre-work  1) On Fabric A - i would disable all ports to force all host I/O to go through fabric B 2) On Fabric A - delete zoneset config on both switches, set domain id to be unique on each switch 3) On Fabric A - load zoneset config you pre-created for fabric A on one switch, then connect ISL connections to the other switch. At this point fabrics should merge, verify by running "fabricshow". It should display both switches. 4) On Fabric A - re-enable switch ports. Go into each CX4 Connectivity status and verify all hosts are logged-in. Go to each host and run "powermt restore", and then "powermt display". At this point old paths should have come back, verify before proceeding. If you do not see old paths, go into diskpart and run "rescan" and then try "powermt restore/display" again. If you still do not see the old paths you might have to reboot the system.  Once everything looks good, proceed to fabric B. I always schedule this kind of work during maintenance window because no matter how much you plan, there are always one or two stubborn systems that have to be rebooted.
Hi.  I have two brocade switches ( The first thing is that both switches have the same Domain ID, I know that I need to change this before trying to make the ISL and so, but does this change affects production? It's an online change or is there any disruption?  I found this procedure to do the change, can anyone tell me if that is ok?  On the switch which I want to be secondary: switch:admin> switchDisable switch:admin> configure Fabric parameters (yes, y, no, n): [no] y Domain: (1..239) [1] 2 Ctrl-d switch:admin> switchEnable  After this, there is the need to create a new Zone Config, as each enabled config on each switch is different and I want to merge them clean, so I really want to sincronize all configurations on both switches. I create the new Zone Config equally, same name and clone all zoning information independently, then I'm planning to use de Zone Merger to sincronize both configurations so I have the two switches exactly with the some config (clearing all conflicts - just found one).  The activation of this new Zone Config will disrupt communications with production hosts?  Is this the way to success?? hehehe I've reviewed all procedures and I'm think to be on the good road. Any suggestion will be appreciated.
Basic questions for creating fabric with production switches