Unsolved
This post is more than 5 years old
160 Posts
0
751
How to interconnect 2 FC fabrics
Hello,
I was wondering how to interconnect 2 FC fabrics.
See picture.
In fabric 1, we have a vnx connected to a vSphere environment via a failover setup with 2 DS300B FC switches.
The hosts are soft-zoned with WWN's of the VNX and the HBA.
But now we want to connect both environments, so that VM's can be migrated (vmotion) between the CX4 and the VNX.
I was thinking about connecting DS300B1 with DS300B3 and connecting DS300B2 with DS300B4.
But I'm not sure it's the right way and how to do this.
Please help.
cris_danci
39 Posts
0
January 22nd, 2013 03:00
If its purely for migration just connect one set (DS300B1 <-> BS300B3) to limit the impact. Fabric merges require the new members not to have an active configuration. So by only doing one set you reduce the likelihood of error and outages
Here is the high level process you should follow:
1. Verify that all hosts are multipathed and can see all paths (across both environments) (there should be at least 1 active path through each switch.
2. Verify that DS300B1 and DS300B3 have different domain IDs (use the CLI: switchshow)
3. On DS300B1,backup the zone configuration to a text file then clear the zone configuration (use zoneshow or cfgshow on DS300B1 to confirm there is no activezonet on the switch)
4. Attach an FC cable between free port on DS300B1 and DS300B3 (the port should change to an E-Port)
5. Verify the that the zoning database has propgated from DS300B3 to DS300B1 (using zoneshow on FC300B1)
6. Use 'fabricshow' to confirm both switches are part of a fabric
7. Login to DS300B3 and redo the zoning removed in step 3
8. Still on DS300B3 configure new zones required for the migration
9. Migrate with VMotion (or other method)
Hope this helps.
dynamox
20.4K Posts
0
January 22nd, 2013 04:00
if zones names, aliases and domain id are unique you don't need to clear zoneset config on one of the switches, they will merge just fine and if they don't you will see in the logs which entry is causing an issue.
etaljic81
1K Posts
0
January 22nd, 2013 08:00
Just to expand to what dynamox said. Use the Broacade Zone Merger tool to make sure the zoning info is identical before you ISL the switches: http://community.brocade.com/thread/2654?start=0&tstart=0
I've used the tool in the past and it works great. The tool is a bit old but it works.
cris_danci
39 Posts
0
January 22nd, 2013 11:00
Not having one of the new members (not both in a 2 fabric config) cleared is a hit a miss process, particular when dealing with FOS 4/5 or in legacy interoperability modes. Brocade support recommend the clean config process should all else fail.
dynamox
20.4K Posts
0
January 22nd, 2013 20:00
so you either spend some time upfront or after the fact recreating zones which can be scripted, different strokes for different folks.
kelleg
4.5K Posts
0
January 24th, 2013 08:00
Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award points to the person providing the answer. This helps others searching for a similar issue.
glen