Cumulus linux 3.2 leaf to leaf communication


I have a simple setup of spine leaf of cumulus linux on dell 4000 leaf and spine 6000...i have the hosts attached to the leafs on ports that are bridged with multiple vlans..however im unable to ping host 2 on leaf 2 from host 1 on leaf 1 ...both of them exist on same VLAN on the different leafs...appreciate any inputs as a newbie to cumulus linux...Thanks in advance

6 replies

Userlevel 4
Could you post the /etc/network/interface configurations from both Leaf1 and Leaf2 and the Spine between them?
Leaf 1
Leaf 2 #SWP49 "RACK to RACK connected to port L-SWP49 to S-SWP29
auto swp49
iface swp49
#SWP51 "RACK to RACK connected to port L-SWP51 to S-SWP30
auto swp51
iface swp51

#auto br0
#iface br0
#bridge-vlan-aware yes
#bridge-ports glob swp49-51
#bridge-stp on
#bridge-vids 401 402 403 404 405 406 407 408 409
#the loopbackinterface
auto lo
iface lo inet loopback
address 192.168.4.4
netmask 255.255.255.255
auto ACI_LAB
iface ACI_LAB
bridge-ports swp49 swp50 swp51 swp52
bridge-ageing 150
bridge-stp on
bridge-vids 401 402 403 404 405 406 407 408 409 410 411
bridge-vlan-aware yes
auto br-401
iface br-401
address x.y.1.254/24
bridge-ports swp1.401 swp2.401 swp3.401 swp4.401 swp5.401 swp17.401 swp18.401 swp19.401 swp20.401
bridge-stp on
auto br-402
iface br-402
address x.y.2.254/24
bridge-ports swp1.402 swp2.402 swp3.402 swp4.402 swp5.402 swp17.402 swp18.402 swp19.402 swp20.402 swp22.402
bridge-stp on
auto br-403
iface br-403
address x.y.3.254/24
bridge-ports swp1.403 swp2.403 swp3.403 swp4.403 swp5.403 swp17.403 swp18.403 swp19.403 swp20.403 swp23.403
bridge-stp on
auto br-404
iface br-404
address x.y.4.254/24
bridge-ports swp1.404 swp2.404 swp3.404 swp4.404 swp5.404 swp17.404 swp18.404 swp19.404 swp20.404
bridge-stp on
auto br-405
iface br-405
address x.y.5.254/24
bridge-ports swp1.405 swp2.405 swp3.405 swp4.405 swp5.405 swp17.405 swp18.405 swp19.405 swp20.405
bridge-stp on
auto br-406
iface br-406
address x.y.6.254/24
bridge-ports swp1.406 swp2.406 swp3.406 swp4.406 swp5.406 swp26.406 swp17.406 swp18.406 swp19.406 swp20.406
bridge-stp on
auto br-407
iface br-407
address x.y.7.254/24
bridge-ports swp1.407 swp2.407 swp3.407 swp4.407 swp5.407 swp46.407 swp17.407 swp18.407 swp19.407 swp20.407
bridge-stp on
auto br-408
iface br-408
address x.y.8.254/24
bridge-ports swp1.408 swp2.408 swp3.408 swp4.408 swp5.408 swp17.408 swp18.408 swp19.408 swp20.408
bridge-stp on
auto br-409
iface br-409
address x.y.9.254/24
bridge-ports swp27 swp28 swp29 swp30 swp31 swp32 swp33 swp35
bridge-stp on
auto br-410
iface br-410
address x.y.10.254/24
bridge-ports swp1.410 swp2.410 swp3.410 swp4.410 swp5.410 swp17.410 swp18.410 swp19.410 swp20.410
bridge-stp on


auto br-411
iface br-411
address x.y.11.254/24
bridge-ports swp1.411 swp2.411 swp3.411 swp4.411 swp5.411 swp17.411 swp18.411 swp19.411 swp20.411
bridge-stp on

swp 17,18,19,20 are the interseting ports and 401 bridge
below is identcal for all swp ports and link is up on all and eth0 has a management ip
# swp1

auto swp1
iface swp1
link-speed 10000
link-duplex full
link-autoneg off
Spine 2
#P30 "RACKx to RACky connected to port SWP30 to SWP51"
auto swp30
iface swp30

#29-30 downlinks to 2 leafs

#SWP51 "RACKx to RACky connected to port SWP29 to SWP49"
auto swp29
iface swp29

auto br0
iface br0
bridge-vlan-aware yes
bridge-ports glob swp29-30
bridge-stp on
bridge-vids 401 402 403 404 405 406 407 408 409 410 411
leaf 1..all links are up and interesting hosts on swp 17,18.19.20 on br-401 not able to ping interetsting hosts on br-401 of leaf2 on 17,18,19,20
SWP49 "RACKx to RACKy connected to port L-SWP49 to S-SWP29
auto swp49
iface swp49


#SWP51 "RACKx to RACKy connected to port L-SWP51 to S-SWP30
auto swp51
iface swp51

#auto br0
#iface br0
#bridge-vlan-aware yes
#bridge-ports glob swp49-51
#bridge-stp on
#bridge-vids 401 402 403 404 405 406 407 408 409



#the loopbackinterface
auto lo
iface lo inet loopback
address x.y.z.c
netmask 255.255.255.255


auto ACI_LAB
iface ACI_LAB
bridge-ports swp49 swp50 swp51 swp52
bridge-ageing 150
bridge-stp on
bridge-vids 401 402 403 404 405 406 407 408 409 410 411
bridge-vlan-aware yes



auto br-401
iface br-401
address x.y.1.254/24
bridge-ports swp1.401 swp2.401 swp3.401 swp4.401 swp5.401 swp17.401 swp18.401 swp19.401 swp20.401
bridge-stp on




auto br-402
iface br-402
address x.y.2.254/24
bridge-ports swp1.402 swp2.402 swp3.402 swp4.402 swp5.402 swp17.402 swp18.402 swp19.402 swp20.402 swp22.402
bridge-stp on


auto br-403
iface br-403
address x.y.3.254/24
bridge-ports swp1.403 swp2.403 swp3.403 swp4.403 swp5.403 swp17.403 swp18.403 swp19.403 swp20.403 swp23.403
bridge-stp on



auto br-404
iface br-404
address x.y.4.254/24
bridge-ports swp1.404 swp2.404 swp3.404 swp4.404 swp5.404 swp17.404 swp18.404 swp19.404 swp20.404
bridge-stp on

auto br-405
iface br-405
address x.y.5.254/24
bridge-ports swp1.405 swp2.405 swp3.405 swp4.405 swp5.405 swp17.405 swp18.405 swp19.405 swp20.405
bridge-stp on



auto br-406
iface br-406
address x.y.6.254/24
bridge-ports swp1.406 swp2.406 swp3.406 swp4.406 swp5.406 swp26.406 swp17.406 swp18.406 swp19.406 swp20.406
bridge-stp on


auto br-407
iface br-407
address x.y.7.254/24
bridge-ports swp1.407 swp2.407 swp3.407 swp4.407 swp5.407 swp46.407 swp17.407 swp18.407 swp19.407 swp20.407
bridge-stp on


auto br-408
iface br-408
address x.y.8.254/24
bridge-ports swp1.408 swp2.408 swp3.408 swp4.408 swp5.408 swp17.408 swp18.408 swp19.408 swp20.408
bridge-stp on



auto br-409
iface br-409
address x.y.9.254/24
bridge-ports swp27 swp28 swp29 swp30 swp31 swp32 swp33 swp35
bridge-stp on


auto br-410
iface br-410
address x.y.10.254/24
bridge-ports swp1.410 swp2.410 swp3.410 swp4.410 swp5.410 swp17.410 swp18.410 swp19.410 swp20.410
bridge-stp on


auto br-411
iface br-411
address x.y.11.254/24
bridge-ports swp1.411 swp2.411 swp3.411 swp4.411 swp5.411 swp17.411 swp18.411 swp19.411 swp20.411
bridge-stp on
Userlevel 4
It looks like you're mixing the SVI style of the traditional bridge with the VLAN aware bridge to cover another set of ports.... I would refactor the configuration to look something like this. auto lo iface lo inet loopback address 192.168.4.4/32 auto eth0 iface eth0 inet dhcp % for i in range(1,53): auto swp${i} iface swp${i} mtu 9216 % endfor auto ACI_LAB iface ACI_LAB bridge-vlan-aware yes bridge-ageing 150 bridge-ports glob swp1-5 glob swp17-20 glob swp49-52 bridge-vids 401-411 bridge-stp on % for i in range(1,12): auto ACI_LAB.${i+400} iface ACI_LAB.${i+400} alias SVI for VLAN ${i+400} address x.y.${i}.254/24 % endfor
Can you show a sample 2 leaf 2 spine config with same vlans on the 2 leafs all leaf ports southbound being trunk ports and VMs on one leaf should be able to ping VMs on another leaf in same VLAN..esxi hosts are attached to leafs..no dynamic routing involved

above ACI_lab is an uplink from leaf to spine ...so is the config above for a leaf

Reply