From: Sam James <sam.james@adelphia.com>
To: linux-kernel@vger.kernel.org
Subject: bonding problems?
Date: Thu, 1 Nov 2001 21:22:47 -0500 [thread overview]
Message-ID: <69DCAE8DF2BFD411AACC0002A50A63F00B693CDA@cdptex1.adelphiacom.com> (raw)
Hello,
I have been expermenting with the bonding driver and well, it works, but..
if you unplug the cable to one of the bonded interfaces it never appears to
figure out that that part of the channel is down, hense it drops every other
ping you send it(or any other packet for that matter). Is this the way it
is supposed to work? I know when I configure cisco etherchannel between
swithes, if you lose a link, all traffic is then sent across the remaining
link[s].
also if this is not the right way to achieve my goal, please point me in the
correct direction.
well anyways here is my setup
compaq proliant 2500 (linux does not detect the memory correctly in this
box,
requiring me to pass:append="mem=exactmap mem=640K@0 mem=255M@1M" in
lilo.conf)
any plans to fix that??
2xPPro200, 256M ram, 400meg swap, raid5 blah blah
Kernel: 2.4.14-pre6 SMP
[root@flounder /etc]# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:80:C8:5A:F1:8B
inet addr:10.156.15.20 Bcast:10.156.15.255 Mask:255.255.252.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1547 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:80:C8:5A:F1:8B
inet addr:10.156.15.20 Bcast:10.156.15.255 Mask:255.255.252.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:19492 errors:1 dropped:0 overruns:0 frame:0
TX packets:774 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:5 Base address:0x8000
eth1 Link encap:Ethernet HWaddr 00:80:C8:5A:F1:8B
inet addr:10.156.15.20 Bcast:10.156.15.255 Mask:255.255.252.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:9317 errors:0 dropped:0 overruns:0 frame:0
TX packets:773 errors:6 dropped:0 overruns:0 carrier:6
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x7400
here is the config on the cisco(3524XL) side:
joe-dc3524#sh port group 1
Group Interface Transmit Distribution
----- --------------------- ---------------------
1 FastEthernet0/21 source address
1 FastEthernet0/22 source address
next reply other threads:[~2001-11-02 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 2:22 Sam James [this message]
2001-11-02 9:41 willy tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69DCAE8DF2BFD411AACC0002A50A63F00B693CDA@cdptex1.adelphiacom.com \
--to=sam.james@adelphia.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®