Brocade 48000 ISL trunk load balancing - one work one not - any ideas?

[Godfrey Zhang]

subject:Brocade 48000 ISL trunk load balancing - one work one not - any ideas?

Hi all, I have three directors in one fabric:
Brocade 48K (edge) <==ISL Trunk==> Brocade 48K Core <==ISL trunk==> Brocade 24K (edge)

Brocade 48Ks: OS:6.10b
Brocade 24K: OS:5.3.1a

The ISL trunk between core and 24K_edge has load balancing (port 1/0 - 1/3 - 4 port trunk group):

cscclar48d04:admin> portperfshow 20
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Total
==============================================================================================
slot 1: 28m 27m 12m 15m 0 0 0 0 9.7m 140k 31k 43k 31k 39k 20k 20k 94m


but the ISL trunk between core and 48K_edge has NOT - it always uses the master port (above: port 1/8 - 1/15 - 8 port trunk group).

B48K_CORE's trunkshow:
cscclar48d04:admin> trunkshow
1: 0->127 10:00:00:60:69:e2:16:60 3 deskew 15 MASTER => B24K_DIR2 (24d02)
1->126 10:00:00:60:69:e2:16:60 3 deskew 16
2->125 10:00:00:60:69:e2:16:60 3 deskew 15
3->124 10:00:00:60:69:e2:16:60 3 deskew 16

2: 8-> 8 10:00:00:05:1e:36:5c:34 21 deskew 15 MASTER => B48K_EDGE2 (48d02)
9-> 9 10:00:00:05:1e:36:5c:34 21 deskew 15
10-> 10 10:00:00:05:1e:36:5c:34 21 deskew 15
11-> 11 10:00:00:05:1e:36:5c:34 21 deskew 15
12-> 12 10:00:00:05:1e:36:5c:34 21 deskew 15
13-> 13 10:00:00:05:1e:36:5c:34 21 deskew 15
14-> 14 10:00:00:05:1e:36:5c:34 21 deskew 16
15-> 15 10:00:00:05:1e:36:5c:34 21 deskew 16

B48K ports are 8Gb ports, while B24k ports are 2Gb ports.

I would've thought B48 <==> B48 (8Gb ports on both) should have load balancing, but the reality is not, which hammers the first port all the time. Any ideas?

[KathyL1]

Have you checked the routing policy on the edge 48K. I'm not certain of this but verify that it is set the same as the core 48K.
"aptpolicy"

[Godfrey Zhang]

run aptpolicy, both 48000s showed "Current Policy: 3 0 (ap) - which is the default - that supports DLS.

run the same command on the 24000, showed "This switch supports only Port Based Routing Policy". run dlsshow --> "DLS is set". This explains the load balancing for this ISL trunking group.

But for the two 48000s, I think as long as a trunk is formed, it should always do the load balancing. Otherwise, there is no point to do so.