08-20-2014 02:06 PM
Hi there, We have an edge core topology. The number of edge switches stands at ~40. All hosts are on the edge switches while there is storage directly connected to the core switches. The way the SAN was designed there are 2 Fabrics, A and B. The two Fabrics are on completely independent hardware so they have know knowledge of eachother.
We want to expand the SAN as the core switches are running low on ports.
I am wondering what is the best way to conenct up additional core switches. The current core switches are 5300b's.
Also is there a limit to the number of edge swithces in a Fabric and if so is there a way to continue growing the SAN such as using MetaSAN?
08-20-2014 09:45 PM
There is a limit to how many Domain IDs you can have in a fabric, how many devices can be logged in to the fabric.
Brocade has a document called Brocade SAN Scalability Guidelines, there are different versions of this document per FOS version.
For expanding edge ports (to hosts I presume) without consuming Domain IDs you could just add more Brocade switches but set them in Access Gateway mode, that way you wouldn't have to worry about the max DID limit at least.
For expanding the core, would you be able to draw a diagram? Are the core switches in a mesh or connected in serial?
With ~20 switches per fabric perhaps it's time to consider director class switches.
For just adding a switch you just connect it to the fabric where there's room, move some cables around?
To free up ports perhaps some trunks to edge switches are under-used and can be made smaller.
08-20-2014 11:01 PM
--->>>We want to expand the SAN as the core switches....
core expand is very simple.
in example you have current in Fabric_A ONE Brocade 5300 and want to add a additional Core Switch.
You need just to made the Basic config in a NEW Switch - Switch Parameters, unique Domain ID, check for FOS compatibility.
Now, connect - ISL or ISL/Trunking - this NEW Switch to existing Core Switch, and the core is expanded.
as second step you must for better HA failure create ISL from all EDGE Switches to NEW Core Switch, otherwise the EDGE switches continue to work in the same Fabric as Single-Point-of-Failure.
08-21-2014 01:59 AM
if we are talking about the classic "core-edge" topology, then core switches _are_not_ connected to each other. the same applies to the edge switches. each edge is connected to each core. and each core is connected to each edge - that's the way it work. and the exact reason behind it - this topology is very easy to scale and grow. you get new edge switch and you connect it to all your core switches. done.
08-21-2014 02:30 AM
I don't seem to be able to attach a diagram. One edge switch is connected to one of the core switches. An edge switch is never connected to both core switches. Is this incorrect? I think that it was done this way to keep the zoning separate.
08-21-2014 02:48 AM
08-21-2014 03:27 AM
Yes I suppose that would be how to describe the SAN as it is currently "dual redundant san". What would be the limitations to this design? With regards to extending the core then we should create ISL's between the existing core switches and the new core switches?
Thanks for all your responses!!
08-21-2014 03:53 AM
08-21-2014 04:02 AM
all is here most confused.
you open the threads as:
--->>>We want to expand the SAN as the core switches ...
also both Core in Fabric A + B
what you intend with "Expand" ?
08-21-2014 04:13 AM - edited 08-21-2014 04:17 AM
ah, thanks! me too, i'm not a good reader!
so if you want to add a new core switch:
- you get the new core switch and connect it to all the edge switches. done.
and just to summarize, as mentioned earlier, if you want to add a new edge:
- you get the new edge switch and connect it to all the core switches. done.
as you can see, scaling the core-edge is very symmetric. but that is if you really have a core-edge.