Fedora Linux Support Community & Resources Center
  #1  
Old 24th July 2005, 04:26 PM
bvgsy Offline
Registered User
 
Join Date: Jul 2005
Posts: 3
Channel Bonding

I've recently installed the latest kernel for FC3 just so that I could setup
channel bonding. In the menuconfig, Channel Bonding was selected as "M"
for modularization(I think). Recompiled kernel and installed without problem.

However, after creating the bond0 and associated eth config files, I rebooted
my system but bond0 was not created.

Is there a way I can check to make sure channel bonding has been correctly
installed or are there other things I can check?

Here are my configs:

[root@amed network-scripts]# cat ifcfg-bond0
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.1.3
NETMASK=255.255.255.0
NETWORK=192.168.1.0
BROADCAST=192.168.1.255
GATEWAY=192.168.1.1
TYPE=Ethernet

[root@amed network-scripts]# cat ifcfg-eth0
DEVICE=eth0
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
TYPE=Ethernet

[root@amed network-scripts]# cat ifcfg-eth3
DEVICE=eth3
USERCTL=no
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
TYPE=Ethernet

Additional info:
[root@amed network-scripts]# /sbin/service network restart
Shutting down interface eth2: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface bond0: [ OK ]
Bringing up interface eth2: [ OK ]

[root@amed network-scripts]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:40:F4:49:49:DB
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:10:B5:83:0F:F6
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:b5ff:fe83:ff6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:91 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13312 (13.0 KiB) TX bytes:5982 (5.8 KiB)
Interrupt:12 Base address:0xc400

eth2 Link encap:Ethernet HWaddr 00:10:B5:52:D3:D9
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:b5ff:fe52:d3d9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1121 errors:0 dropped:0 overruns:0 frame:0
TX packets:1164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:97351 (95.0 KiB) TX bytes:152270 (148.7 KiB)
Interrupt:10 Base address:0xc800

eth3 Link encap:Ethernet HWaddr 00:40:33:D2:E1:25
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xcc00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:76 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5356 (5.2 KiB) TX bytes:5356 (5.2 KiB)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


I'm at wits end. Any suggestion is appreciated.

Thanks!
bvgsy
Reply With Quote
  #2  
Old 24th July 2005, 04:34 PM
alexp_789 Offline
Registered User
 
Join Date: Jan 2005
Posts: 13
Modprobe.conf

Hi,
What you need to do is add an entry to /etc/modprobe.conf that reads something like:

Code:
alias bond0 bonding
Note: This is of the top of my head, you'll find much more info in the bonding.txt in the 'kernel source'/documentation/ directory (again top of my head!)

Hope this helps!
Reply With Quote
  #3  
Old 24th July 2005, 07:54 PM
bvgsy Offline
Registered User
 
Join Date: Jul 2005
Posts: 3
LOL! Thanks for your reply alexp_789. Your suggestion solved my problem.

Per documentations and others who posted something simillar, none has mentioned
about adding "alias bond0 bonding" to /etc/modprobe.conf. All that is mentioned is
by adding the entry to /etc/modules.conf which I did. Here's my entry:

[root@amed network-scripts]# cat /etc/modules.conf
alias bond0 bonding
options bond0 miimon=100 mode=balance-rr
...

When I added the same entry to /etc/modprobe.conf per your suggestion, restarted network,
only then the device bond0 was created. I appreciate your help. Had I know about this, I
probably didn't have to recompile and rebuild my kernel. Nevertheless, it's working now.

[root@amed etc]# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:40:F4:49:49B
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:696 (696.0 b) TX bytes:676 (676.0 b)

eth0 Link encap:Ethernet HWaddr 00:40:F4:49:49B
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::240:f4ff:fe49:49db/64 Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:318 (318.0 b) TX bytes:368 (368.0 b)
Interrupt:5 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:10:B5:83:0F:F6
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:b5ff:fe83:ff6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:205 errors:0 dropped:0 overruns:0 frame:0
TX packets:1049 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:25934 (25.3 KiB) TX bytes:156792 (153.1 KiB)
Interrupt:12 Base address:0xc400

eth2 Link encap:Ethernet HWaddr 00:10:B5:5239
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::210:b5ff:fe52:d3d9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2218 errors:0 dropped:0 overruns:0 frame:0
TX packets:1198 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:209689 (204.7 KiB) TX bytes:154378 (150.7 KiB)
Interrupt:10 Base address:0xc800

eth3 Link encap:Ethernet HWaddr 00:40:F4:49:49B
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::240:f4ff:fe49:49db/64 Scope:Link
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:378 (378.0 b) TX bytes:308 (308.0 b)
Interrupt:11 Base address:0xcc00

Thanks again!
bvgsy
Reply With Quote
Reply

Tags
bonding, channel

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
bonding Roberto_kellog Servers & Networking 2 20th March 2009 03:29 PM
FC5 - Channel Bonding 69javelin Servers & Networking 4 5th December 2006 04:21 PM
Channel Bonding with sk98lin and e1000 wmusil Hardware & Laptops 0 14th October 2005 11:23 PM
Channel Bonding Error monjur Servers & Networking 3 7th October 2005 07:37 PM


Current GMT-time: 15:59 (Thursday, 23-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat