Menu

does the bonding code work when not a module?

Help
Anonymous
2003-09-04
2003-09-19
  • Anonymous

    Anonymous - 2003-09-04

    Does the bonding code work if built into the kernel(not
    using modules)?

    The reason I ask:

    built a 2.4.21 kernel without module support but with
    the bonding bits.

    I can bond 2 interfaces together but can not reach or
    see the other end. This is 2 linux machines connected
    via a pair of cross over cables.

    The files I created/edit are:

    /etc/sysconfig/network-scripts/ifcfg-bond0
    /etc/sysconfig/network-scripts/ifcfg-eth1
    /etc/sysconfig/network-scripts/ifcfg-eth2

    the howto mentions to add the below line to
    modules.conf but since i am not using modules I'd
    suspect this is not even looked at.. correct?

    alias bond0 bonding
    options bond0 miimon=200 mode=1

    thanks folks.

    greg

    Here is some info / contents of files on the system:

    /etc/sysconfig/network-scripts/ifcfg-*

    ifcfg-eth0:
    DEVICE=eth0
    ONBOOT=yes
    BOOTPROTO=static
    IPADDR=172.16.92.244
    NETMASK=255.255.252.0
    GATEWAY=172.16.92.2

    ifcfg-eth1:
    DEVICE=eth1
    BOOTPROTO=none
    ONBOOT=yes
    USERCTL=no
    MASTER=bond0
    SLAVE=yes

    ifcfg-eth2:
    DEVICE=eth2
    BOOTPROTO=none
    ONBOOT=yes
    MASTER=bond0
    SLAVE=yes
    USERCTL=no

    ifcfg-bond0:
    DEVICE=bond0
    IPADDR=192.168.1.1
    NETMASK=255.255.255.0
    NETWORK=192.168.1.0
    BROADCAST=192.168.1.255
    ONBOOT=yes
    BOOTPROTO=none
    USERCTL=no

    modules.conf(?)
    options bond0 miimon=200 mode=1
    (the above was added afterwards in an attempt to fix
    things)

    [root@nova root]# ifconfig
    bond0 Link encap:Ethernet HWaddr 00:09:6B:63:37:E7
    inet addr:192.168.1.1 Bcast:192.168.1.255
    Mask:255.255.255.0
    UP BROADCAST RUNNING MASTER MULTICAST
    MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0
    frame:0
    TX packets:6 errors:0 dropped:0 overruns:0
    carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:3852 (3.7 Kb)

    eth0 Link encap:Ethernet HWaddr 00:03:47:DE:29:37
    inet addr:172.16.92.244 Bcast:172.16.95.255
    Mask:255.255.252.0
    UP BROADCAST RUNNING MULTICAST MTU:1500
    Metric:1
    RX packets:3555 errors:0 dropped:0 overruns:0
    frame:0
    TX packets:2173 errors:0 dropped:0 overruns:0
    carrier:0
    collisions:0 txqueuelen:100
    RX bytes:458454 (447.7 Kb) TX bytes:410930
    (401.2 Kb)
    Interrupt:16 Memory:febc0000-febe0000

    eth1 Link encap:Ethernet HWaddr 00:09:6B:63:37:E7
    inet addr:192.168.1.1 Bcast:192.168.1.255
    Mask:255.255.255.0
    UP BROADCAST RUNNING SLAVE MULTICAST
    MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0
    frame:0
    TX packets:3 errors:0 dropped:0 overruns:0
    carrier:0
    collisions:0 txqueuelen:100
    RX bytes:0 (0.0 b) TX bytes:1926 (1.8 Kb)
    Interrupt:24

    eth2 Link encap:Ethernet HWaddr 00:09:6B:63:37:E7
    inet addr:192.168.1.1 Bcast:192.168.1.255
    Mask:255.255.255.0
    UP BROADCAST RUNNING SLAVE MULTICAST
    MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0
    frame:0
    TX packets:3 errors:0 dropped:0 overruns:0
    carrier:0
    collisions:0 txqueuelen:100
    RX bytes:0 (0.0 b) TX bytes:1926 (1.8 Kb)
    Interrupt:25

    Sep 2 14:45:52 nova kernel: e1000: eth0 NIC Link is Up
    1000 Mbps Full Duplex
    Sep 2 14:45:52 nova kernel: bond0: enslaving eth1 as
    an active interface with an up link.
    Sep 2 14:45:52 nova kernel: bond0: enslaving eth2 as
    an active interface with an up link.
    Sep 2 14:45:52 nova kernel: tg3: eth1: Link is up at
    1000 Mbps, full duplex.
    Sep 2 14:45:53 nova kernel: tg3: eth1: Flow control is
    on for TX and on for RX.
    Sep 2 14:45:53 nova kernel: tg3: eth2: Link is up at
    1000 Mbps, full duplex.
    Sep 2 14:45:53 nova kernel: tg3: eth2: Flow control is
    on for TX and on for RX.
    Sep 2 14:45:53 nova kernel: Attached scsi generic sg1
    at scsi0, channel 0, id 8, lun 0, type 3
    Sep 2 14:46:31 nova sshd(pam_unix)[1070]: session
    opened for user root by (uid=0)
    Sep 2 14:47:31 nova kernel: qla2x00_set_info starts at
    address = f8955060
    Sep 2 14:47:31 nova kernel: qla2x00: Found VID=1077
    DID=2312 SSVID=1077 SSDID=10a
    Sep 2 14:47:31 nova kernel: scsi(1): Found a QLA2312
    @ bus 1, device 0x2, irq 18, iobase 0x2400

     
    • Joseph

      Joseph - 2003-09-19

      I got it working compiled into the module, but now I don't know to set the settings.

      Surely there should be a way to set the settings,  maybe on the kernel command line of grub or something...

      Any ideas?

       
    • Jay Vosburgh

      Jay Vosburgh - 2003-09-19

          Do you mean compiled into a module, or into the kernel?

          If bonding is compiled as a module, parameters may be passed to it as described in the bonding documentation, in the kernel source code: Documentation/networking/bonding.txt

          If bonding is compiled into the kernel, there is no way to pass parameters to it, it uses whatever the compiled in defaults are.

          -J

       

Log in to post a comment.