spanning tree issue with Dell switch


I have 2 HP cumulis switches sw1 & sw2 sw1 config # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/*.intf # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 address 10.172.250.51/24 gateway 10.172.250.1 mtu 9216 # # MLAG auto peerlink iface peerlink bond-slaves swp49 swp52 mtu 9216 auto peerlink.4094 iface peerlink.4094 address 169.254.255.1 netmask 255.255.255.0 clagd-priority 4096 clagd-peer-ip 169.254.255.2 clagd-backup-ip 10.172.250.52 clagd-sys-mac 44:38:39:ff:00:01 # LACP to ybosw3 # swp1 - sw1 -> ybosw3 A te1/0/18 # swp1 - sw2 -> ybosw3 B te1/0/19 # swp2 - sw1 -> ybosw3 A te2/0/18 # swp2 - sw2 -> ybosw3 B te2/0/19 auto lacp-ybosw3 iface lacp-ybosw3 bond-slaves swp1 swp2 mtu 9216 clag-id 1 # LACP to ybortr2 # swp17 - sfp1 # swp17 - sfp2 auto lacp-ybortr2 iface lacp-ybortr2 bond-slaves swp17 mtu 9216 clag-id 2 mstpctl-portadminedge yes mstpctl-bpduguard yes # bridge that carries everything ?? auto br-trunk iface br-trunk mtu 9216 bridge-vlan-aware yes bridge-vids 4-5 8-11 17-19 24 80 95 99 201-205 207-209 212-222,250 bridge-pvid 1 bridge-ports lacp-ybosw3 lacp-ybortr2 bridge-stp on sw2 config # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/*.intf # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 address 10.172.250.52/24 gateway 10.172.250.1 mtu 9216 # # MLAG auto peerlink iface peerlink bond-slaves swp49 swp52 mtu 9216 auto peerlink.4094 iface peerlink.4094 address 169.254.255.2 netmask 255.255.255.0 clagd-priority 8192 clagd-peer-ip 169.254.255.1 clagd-backup-ip 10.172.250.51 clagd-sys-mac 44:38:39:ff:00:01 # LACP to ybosw3 # swp1 - sw1 -> ybosw3 A te1/0/18 # swp1 - sw2 -> ybosw3 B te1/0/19 # swp2 - sw1 -> ybosw3 A te2/0/18 # swp2 - sw2 -> ybosw3 B te2/0/19 auto lacp-ybosw3 iface lacp-ybosw3 bond-slaves swp1 swp2 mtu 9216 clag-id 1 # LACP to ybortr2 # swp17 - sfp1 # swp17 - sfp2 auto lacp-ybortr2 iface lacp-ybortr2 bond-slaves swp17 mtu 9216 clag-id 2 mstpctl-portadminedge yes mstpctl-bpduguard yes # bridge that carries everything ?? auto br-trunk iface br-trunk mtu 9216 bridge-vlan-aware yes bridge-vids 4-5 8-11 17-19 24 80 95 99 201-205 207-209 212-222,250 bridge-pvid 1 bridge-ports lacp-ybosw3 lacp-ybortr2 bridge-stp on Connected via a LACP connection to 2 DELL switches show interfaces port-channel 6 Channel Ports Ch-Type Hash Type Min-links Local Prf ------- ----------------------------- -------- --------- --------- --------- Po6 Active: Te1/0/18, Te1/0/19, Dynamic 6 1 Disabled Te2/0/18, Te2/0/19 Hash Algorithm Type 1 - Source MAC, VLAN, EtherType, source module and port Id 2 - Destination MAC, VLAN, EtherType, source module and port Id 3 - Source IP and source TCP/UDP port 4 - Destination IP and destination TCP/UDP port 5 - Source/Destination MAC, VLAN, EtherType, source MODID/port 6 - Source/Destination IP and source/destination TCP/UDP port 7 - Enhanced hashing mode and I have it connected to my mikrotek router (2 x 10G SFP) on my dell switch show spanning-tree Spanning tree :Enabled - BPDU Flooding :Disabled - Portfast BPDU filtering :Disabled - mode :rstp CST Regional Root: 20:00:D0:67:E5:AF:12:68 Regional Root Path Cost: 0 ROOT ID Priority 8192 Address D067.E5AF.1268 This Switch is the Root. Hello Time 2 Sec Max Age 20 sec Forward Delay 15 sec TxHoldCount 6 sec Bridge Max Hops 20 show spanning-tree port-channel 6 Port Po6 Enabled State: Forwarding Role: Designated Port id: 96.151 Port Cost: 500 Port Fast: No Root Protection: No Designated bridge Priority: 8192 Address: D067.E5AF.1268 Designated port id: 96.151 Designated path cost: 0 CST Regional Root: 20:00:D0:67:E5:AF:12:68 Root Guard..................................... FALSE Loop Guard..................................... FALSE TCN Guard...................................... FALSE Auto Portfast.................................. TRUE Port Up Time Since Counters Last Cleared....... 0 day 4 hr 1 min 40 sec BPDU: sent 520025, received 14041 on sw1 mstpctl showport br-trunk E lacp-ybortr2 8.001 forw 2.000.D0:67:E5:AF:12:68 8.000.44:38:39:FF:00:01 8.001 Desg lacp-ybosw3 8.002 forw 2.000.D0:67:E5:AF:12:68 2.000.D0:67:E5:AF:12:68 6.097 Root mstpctl showbridge br-trunk CIST info enabled yes bridge id 8.000.44:38:39:FF:00:01 designated root 2.000.D0:67:E5:AF:12:68 regional root 8.000.44:38:39:FF:00:01 root port lacp-ybosw3 (#2) path cost 1000 internal path cost 0 max age 20 bridge max age 20 forward delay 15 bridge forward delay 15 tx hold count 6 max hops 20 hello time 2 ageing time 300 force protocol version rstp time since topology change 11749s topology change count 1 topology change no topology change port lacp-ybosw3 last topology change port None My issue is it seems like STP is not talking to each other, notice the root bridge id is different. what do I need to do to fix this ???? I'm not sure whats wrong! does this have something todo with old style vs new style bridging ????

5 replies

Hmm so i commented out #mstpctl-portadminedge yes #mstpctl-bpduguard yes for the ybortr2 config and it seems to be working now ?? Why is that. Its an edge device
Userlevel 4
I didn't see anything too out of the ordinary in your configurations. I might recommend hardcoding the STP priority under the br-trunk interface using the "mstpctl-treeprio xxxxx" command, in this setup switches in an MLAG pair should share the same STP priority. What does the output from "clagctl" look like? If you could include a picture of the topology as well, that would be ideal.
When Creating the Bond w/clag id: try the following:

  bond-mode 802.3ad
  bond-miimon 100
  bond-use-carrier 1
  bond-min-links 1
  bond-xmit-hash-policy layer3+4
  clag-id 1
  mstpctl-portadminedge yes
  mstpctl-bpduguard yes
  mtu 9000
Also for the bridge: instead of using Rapid STP (PVRST - Bridge aware) tried just STP (per vlan bridge - PVST)
Mihir Mehta wrote:

When Creating the Bond w/clag id: try the following:

  bond-mode 802.3ad
  bond-...

Isn't that what I have done. I thought it was all meant to be done in interfaces . how do I specify STP ?
Thanks for the replies guys. Still I am struggling to see why when I have LACP A - to switch LACP B - to router Bridge of LACP A and LACP B if I have port fast and spantree filter / admin egde on lacp B ... why it stops LACP a from forming a proper stp with the switch. it couldn't get the root bridge id right ?

Reply