Setting up ISC and distibuted trunking

[ISoliman]

One more thing, once u configure the DT-LACP on both switches make sure you assign the configure trkx to the correct VLAN in both switches.

[deflowjo]

i want to set this up with 4 switches

2 pairs of 660024XG 

pair 1& 2 = pair A, isc trunk1

pair 3 & 4 = pair B, isc trunk1

both pairs setup with a peer keepalive and switch interconnect

now; if i put the first pair and configure a dt trunk to switch 3

next i would configure a dt trunk to switch 4

still is there a loop, because of the trunk between pair B, how do i set this up?

[deflowjo]

i have configured all the ports with trk2 dt-lacp, (except for the switch interconnect)

now it forms 1 big trunk with 4 network cables between the 2 pairs of switches

[Helensteve]

I would like to have a sample configuation.

Thanks

[Jeffaffa]

Hi,

I have the issue when i hit enter on my last rule [trunk E10-E12 trk107 dt-trunk] in switch2.
That switch2 is starting spanning tree to block trk1 and becomes root switch.
This keeps in a loop untill i register [no trunk E10-E12]

I have not tried to disable spanning tree yet.

I 01/11/15 19:57:56 00077 ports: port F2 in Trk1 is now off-line
I 01/11/15 19:57:56 00078 ports: trunk Trk1 is now active
I 01/11/15 19:57:56 00435 ports: port F1 is Blocked by STP
I 01/11/15 19:57:56 00435 ports: port F2 is Blocked by STP
I 01/11/15 19:57:56 00002 vlan: Storage virtual LAN disabled
W 01/11/15 19:57:56 03225 DT: Switch-interconnect link is down
I 01/11/15 19:57:56 00839 stp: CST Root changed from 4096: (this device) to 0:
001871-dca200
I 01/11/15 19:57:56 00076 ports: port F1 in Trk1 is now on-line
I 01/11/15 19:57:56 00076 ports: port F2 in Trk1 is now on-line
I 01/11/15 19:57:56 00001 vlan: Storage virtual LAN enabled
I 01/11/15 19:57:56 03226 DT: Switch-interconnect link is up
I 01/11/15 19:58:03 03304 DT: ISC protocol flow control is activated
I 01/11/15 19:58:04 03304 DT: ISC protocol flow control is activated
I 01/11/15 19:58:04 00077 ports: port F1 in Trk1 is now off-line
I 01/11/15 19:58:04 00079 ports: trunk Trk1 is now inactive
I 01/11/15 19:58:04 00839 stp: CST Root changed from 0: 001871-dca200 to 4096:
(this device)

These are my configs.

Switch1

trunk F1-F2 trk1 trunk
trunk E11-E12,E24 trk107 dt-trunk

vlan 4092
name "LACP-Heartbeat"
untagged E22
ip address 192.168.192.1 255.255.255.252
exit

spanning-tree
spanning-tree Trk1 priority 3
spanning-tree Trk107 priority 4
spanning-tree priority 0
distributed-trunking peer-keepalive vlan 4092
distributed-trunking peer-keepalive destination 192.168.192.2
distributed-trunking role-priority 30000

Switch2

trunk F1-F2 trk1 trunk
trunk E10-E12 trk107 dt-trunk

vlan 4092
name "LACP-Heartbeat"
untagged E22
ip address 192.168.192.2 255.255.255.252
exit

spanning-tree
spanning-tree Trk1 priority 3
spanning-tree Trk107 priority 4
spanning-tree priority 1
distributed-trunking peer-keepalive vlan 4092
distributed-trunking peer-keepalive destination 192.168.192.1

Any ideas ?

Jeff

[Stephen A Swain]

Would recommend you update to latest stable Kx.15 OS series due to dt-trunk bug fixes and peer-keepalive. The late releases include some major dt-trunk fixes.

Also would recommend you utilise UDLD (link-keepalive) to protect against problems caused by unidirectional link failure. This is more important on "Trunk" links than "LACP" links, as LACP adds some protection during LACP timeouts.

Trunk links do come up faster leading to faster convergence, but they cause problems when one fibre fails and the interface does not go down.

Finally, it is handy using trunking for the peer-keepalive (or more generally for any switch to switch link), as it eases the movement of links to other modules or ports. Rather than recreate a new layer 2 or 3 link, you just migrate the trunks to new ports, activate the link, then remove the old ports.