We have 2 datarooms and on the Brocade switches that connects the datarooms, there are 2 isl links. (in each fabric)
Switches are running code 7.3.1a and we use exhange-Based Routing. No trunking. There is lots of fc traffic going on between the sites.
Is there a kind of round-robin algorithm deciding how the traffic is split between the isl links?
I would like to piggy back on this conversation and take it a step further.
Talking Gen5 ...
An edge switch has two ISL connections to the core switch (8510), and each ISL is on a different blade / ASIC. There is also a target port on each ASIC on the 8510.
In Fabric SPF, does the edge switch know which ISL to route traffic based on the location of the target port or will the traffic use the first available ISL even though the traffic may have to cross ASICs on the 8510?
I guess traffic isolation is the only way to control traffic in that aspect... I'm probably trying to be too strict. Just worried about oversubscription on 16gb blades.
Would extended fabric licenses or trunking be the best way of utlizing the bandwith of the isl links?
Extended fabric license is about distance. How far are your sites from each other?
Trunking is OK if you have more than four independent links between the sites. So let's say if I'd have eight links, I'd create two dual-link trunks in each of two fabrics.
Four links is like a minimum IMHO, in this case you have two independent single links in each of two fabrics -- so there's no trunking in this minimal case...