OpenSuse 10.2

BrianK · 01-16-2007, 03:09 PM

I just installed OpenSuse10.2 on my file server. It has a 4 port NIC & will be configured to run 802.3ad link aggregation. I've done this on 3 other Suse machines (not OpenSuse - but the pay-for Suse) without issue.

I have my 4 port bond working. It shows up properly when I run ifconfig. It shows up properly when I cat /proc/net/bonding/bond0. I can't seem to ping anything, however. I can ping my own ip address (it's static), but nothing else.

The switch is configured properly (this machine had a working Ubuntu install prior to moving to OpenSuse). I've tried adding a default route to the routing table by hand.

Any ideas?

acid_kewpie · 01-16-2007, 03:45 PM

i'm not massively experienced with bonding, but let's start by checking what ifconfig says, and what the contents of /proc/net/bonding/bond0 says, assuming your bonded interface *IS* bond0. show them to us, and also show us your arp cache directly after trying to ping something, you can at least see there if you are arping correctly. as well as showing us though, if you already have some very similar systems running, compare these settings to those. one thign may be the bonding method is different, and you could be firing ip packets into disabled interfaces.

also give us more info about what the switch is... presumably it's somethign decent like a Cisco, Nortel or Extreme job?

BrianK · 01-16-2007, 04:19 PM

Quote:

Originally Posted by acid_kewpie

...

Thanks for the help.

Sneakernet to the resucue!

ifconfig:

Code:

bond0     Link encap:Ethernet  HWaddr 00:04:23:B6:92:E0  
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:9052 errors:0 dropped:0 overruns:0 frame:0
          TX packets:775 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1384790 (1.3 Mb)  TX bytes:99200 (96.8 Kb)

eth2      Link encap:Ethernet  HWaddr 00:04:23:B6:92:E0  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:196 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:25088 (24.5 Kb)
          Base address:0x4000 Memory:da500000-da520000 

eth3      Link encap:Ethernet  HWaddr 00:04:23:B6:92:E0  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:2937 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:987676 (964.5 Kb)  TX bytes:24704 (24.1 Kb)
          Base address:0x4040 Memory:da520000-da540000 

eth4      Link encap:Ethernet  HWaddr 00:04:23:B6:92:E0  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:1468 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:95542 (93.3 Kb)  TX bytes:24704 (24.1 Kb)
          Base address:0x4080 Memory:da540000-da560000 

eth5      Link encap:Ethernet  HWaddr 00:04:23:B6:92:E0  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:4647 errors:0 dropped:0 overruns:0 frame:0
          TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:301572 (294.5 Kb)  TX bytes:24704 (24.1 Kb)
          Base address:0x40c0 Memory:da560000-da580000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:730 errors:0 dropped:0 overruns:0 frame:0
          TX packets:730 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:46672 (45.5 Kb)  TX bytes:46672 (45.5 Kb)

/proc/net/bond0/bonding:

Code:

Ethernet Channel Bonding Driver: v3.0.3 (March 23, 2006)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: down
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: slow
Active Aggregator Info:
	Aggregator ID: 1
	Number of ports: 1
	Actor Key: 17
	Partner Key: 1
	Partner Mac Address: 00:00:00:00:00:00

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:04:23:b6:92:e0
Aggregator ID: 1

Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:04:23:b6:92:e1
Aggregator ID: 2

Slave Interface: eth4
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:04:23:b6:92:e2
Aggregator ID: 3

Slave Interface: eth5
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:04:23:b6:92:e3
Aggregator ID: 4

arp table after a ping to 192.168.0.1:

Code:

Address                  HWtype  HWaddress           Flags Mask            Iface
192.168.0.1                      (incomplete)                              bond0

routing table:

Code:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 bond0
loopback        *               255.0.0.0       U     0      0        0 lo

Here are my config files if you'd like to see 'em.

The switch is a managed Linksys SRW2404. I've used the 48 port version of this switch on the oher Suse machines. I used this very switch with the previous OS on this file server (Ubuntu) & it worked. Well... only one of the 4 ports ever worked at one time - it wasn't always the same port... I blamed the OS - hence my switching to Suse.

XavierP · 01-16-2007, 05:06 PM

I have moved this to Linux-Networking because it seems not to be Suse specific.

acid_kewpie · 01-17-2007, 09:38 AM

well everythign says it's happy, but i'm not familiar with the linksys switches. i expect they're a lot closer to Cisco than i'd like, but i'm sure they don't admit to running IOS...i can see tx and rx's on the physical nics, so it's recivning *something* from the switch. are you sure it's on the right vlan? what happens if you disconnect 3 of the cables and only leave on left? their MII status will drop to down i take it, and so all packets must only go on one nic, which removess potential confuusion from load balancing. also as you are seeing *some* packets being recieved, what do you get if you run a tcpdump on bond0 and leave it for a while? any brnadcasts? spanning tree bpdu's?

BrianK · 01-18-2007, 10:27 PM

As it turns out, it was the switch. For anyon who comes across this in the future, the Linksys SRW2024 evidently does NOT do link aggregation properly. I borrowed a Linksys SRW2048 (the 48 port version of the same swich - although less similar than Linksys will have you believe), setup link aggregation & was up & running on all 4 ports without issue.

Unfortunately, it has taken literally over 1 year to figure that out. I didn't have access to a 48 port switch to test until tonight. ::sigh:: so much time wasted.

acid_kewpie · 01-19-2007, 01:43 AM

heh, well from my perspective, phew! i was all out of ideas! i'm so used to not blaming the switches what with working in a purely cisco catalyst switching environment!