https://community.hpe.com/t5/switches-hubs-and-modems/problems-with-distributed-trunks/m-p/4796719#M26151 I'm having some issues with the following setup. <BR /><BR />Two 5400 switches each with latest firmware (K.15.03.0007) connected via switch-interconnect for allowing servers to be connected redundant. <BR /><BR />In this example the server (RHEL6) with bonding (802.3ad) eth8/eth9 and tagged vlans (vid 100 and 108) is connected to both switches on port b20 which is configured as trk55 with dt-lacp. <BR />After "failing" switch0 by disabling port b20 only the ip on vlan 108 is reachable. Trying to fail switch1 both vlans are reachable on the server. <BR />I noticed also, that in regular operation only one server interface is used for communication. I'm used to see traffic beeing splitted over all interfaces using all slave interfaces. <BR />What's the mistake?<BR /><BR />switch0:<BR />switch-interconnect Trk1 <BR />trunk A23-A24,B1-B4 Trk1 LACP <BR />trunk B20 Trk55 dt-lacp <BR />spanning-tree<BR />spanning-tree instance 1 vlan 100-200 301-400<BR />spanning-tree instance 1 priority 0<BR />spanning-tree instance 2 vlan 1-99 201-300<BR />spanning-tree instance 2 priority 1<BR />spanning-tree priority 0<BR />primary-vlan 100<BR />management-vlan 108<BR /><BR />switch1:<BR />switch-interconnect Trk1 <BR />trunk A23-A24,B1-B4 Trk1 LACP <BR />trunk B20 Trk55 dt-lacp <BR />spanning-tree<BR />spanning-tree instance 1 vlan 100-200 301-400<BR />spanning-tree instance 1 priority 1<BR />spanning-tree instance 2 vlan 1-99 201-300<BR />spanning-tree instance 2 priority 0<BR />spanning-tree priority 1<BR />primary-vlan 100<BR />management-vlan 108<BR /><BR />Thanks and best regards<BR /> Wed, 08 Jun 2011 08:05:18 GMT mkont 2011-06-08T08:05:18Z https://community.hpe.com/t5/switches-hubs-and-modems/problems-with-distributed-trunks/m-p/4796719#M26151 I'm having some issues with the following setup. <BR /><BR />Two 5400 switches each with latest firmware (K.15.03.0007) connected via switch-interconnect for allowing servers to be connected redundant. <BR /><BR />In this example the server (RHEL6) with bonding (802.3ad) eth8/eth9 and tagged vlans (vid 100 and 108) is connected to both switches on port b20 which is configured as trk55 with dt-lacp. <BR />After "failing" switch0 by disabling port b20 only the ip on vlan 108 is reachable. Trying to fail switch1 both vlans are reachable on the server. <BR />I noticed also, that in regular operation only one server interface is used for communication. I'm used to see traffic beeing splitted over all interfaces using all slave interfaces. <BR />What's the mistake?<BR /><BR />switch0:<BR />switch-interconnect Trk1 <BR />trunk A23-A24,B1-B4 Trk1 LACP <BR />trunk B20 Trk55 dt-lacp <BR />spanning-tree<BR />spanning-tree instance 1 vlan 100-200 301-400<BR />spanning-tree instance 1 priority 0<BR />spanning-tree instance 2 vlan 1-99 201-300<BR />spanning-tree instance 2 priority 1<BR />spanning-tree priority 0<BR />primary-vlan 100<BR />management-vlan 108<BR /><BR />switch1:<BR />switch-interconnect Trk1 <BR />trunk A23-A24,B1-B4 Trk1 LACP <BR />trunk B20 Trk55 dt-lacp <BR />spanning-tree<BR />spanning-tree instance 1 vlan 100-200 301-400<BR />spanning-tree instance 1 priority 1<BR />spanning-tree instance 2 vlan 1-99 201-300<BR />spanning-tree instance 2 priority 0<BR />spanning-tree priority 1<BR />primary-vlan 100<BR />management-vlan 108<BR /><BR />Thanks and best regards<BR /> Wed, 08 Jun 2011 08:05:18 GMT https://community.hpe.com/t5/switches-hubs-and-modems/problems-with-distributed-trunks/m-p/4796719#M26151 mkont 2011-06-08T08:05:18Z