Channel bonding, I have some questions?
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Orlando Donato Rocha Filho orlandorocha at digi.com.brFri May 11 05:52:53 PDT 2001
- Previous message: [PBS-USERS] checkpointing PBS jobs under linux
- Next message: interesting Athlon/P4 discussion from FreeBSD-Q-l
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all,
Frist off all, We have a cluster with a node master and a node
slave; We configure a channel bond in the node master and in the
node slave. We have two switches and two ethernets cards in each
host (MASTER and SLAVE)
The IPADDR (switch A): 192.168.0.254
The IPADDR (switch B): 192.168.0.253
The IPADDR (Node Master): 192.168.0.1
The IPADDR (Node Slave): 192.168.0.2
----------
----------
|switch A| |switch
B|
----------
----------
| | | |
| | | |
________| |_______ | |
| | | |
| | | |
------------- ------------ | |
|Node Master| |Node Slave| | |
------------- ------------ | |
| | | |
|
|_________|__|
|_________________________|
OS: Red Hat 7.1
Kernel: 2.4.2-2
Look at the files following: (NODE SLAVE)
ifcfg-bond0:
device:bond0
userctl:no
onboot:yes
bootproto:no
broadcast:192.168.0.255
network:192.168.0.0
netmask:255.255.255.0
ipaddr:192.168.0.2
ifcfg-eth0:
device:eth0
master:bond0
slave:yes
usrectl:no
bootproto:yes
ifcfg-eth1:
device:eth1
master:bond0
slave:yes
usrectl:no
bootproto:yes
When I do as follow:
node A:
#ifconfig (NODE SLAVE)
bond0 Link encap:Ethernet HWaddr 00:80:AD:74:74:87
inet addr:192.168.0.2 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500
Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
eth0 Link encap:Ethernet HWaddr 00:80:AD:74:74:87
inet addr:192.168.0.2 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500
Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xe800
eth1 Link encap:Ethernet HWaddr 00:80:AD:74:74:87
inet addr:192.168.0.2 Bcast:192.168.0.255
Mask:255.255.255.0
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500
Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:15 Base address:0xec00
At (NODE MASTER) I did the same configuration, but the IPADDR is
192.168.0.1.
When I do as follow: (NODE SLAVE)
#ping 192.168.0.1
ping 192.168.0.1 (192.168.0.1) from 192.168.0.2 56(84) of bytes
from 192.168.0.2:Destination Host Unreachable
from 192.168.0.2:Destination Host Unreachable
from 192.168.0.2:Destination Host Unreachable
from 192.168.0.2:Destination Host Unreachable
from 192.168.0.2:Destination Host Unreachable
When I do as follow: (NODE MASTER)
#ping 192.168.0.2
ping 192.168.0.2 (192.168.0.2) from 192.168.0.1 56(84) of bytes
from 192.168.0.1:Destination Host Unreachable
from 192.168.0.1:Destination Host Unreachable
from 192.168.0.1:Destination Host Unreachable
from 192.168.0.1:Destination Host Unreachable
from 192.168.0.1:Destination Host Unreachable
#ping 192.168.0.254
PING 192.168.0.254 (192.168.0.254) from 192.168.0.1 : 56(84)
bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 192.168.0.254: icmp_seq=0 ttl=255 time=3.155 msec
64 bytes from 192.168.0.254: icmp_seq=3 ttl=255 time=1.724 msec
64 bytes from 192.168.0.254: icmp_seq=5 ttl=255 time=1.700 msec
64 bytes from 192.168.0.254: icmp_seq=7 ttl=255 time=1.740 msec
64 bytes from 192.168.0.254: icmp_seq=9 ttl=255 time=1.740 msec
#ping 192.168.0.253
PING 192.168.0.253 (192.168.0.253) from 192.168.0.1 : 56(84)
bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 192.168.0.253: icmp_seq=0 ttl=255 time=3.155 msec
64 bytes from 192.168.0.253: icmp_seq=1 ttl=255 time=1.724 msec
64 bytes from 192.168.0.253: icmp_seq=3 ttl=255 time=1.700 msec
64 bytes from 192.168.0.253: icmp_seq=5 ttl=255 time=1.740 msec
64 bytes from 192.168.0.253: icmp_seq=7 ttl=255 time=1.740 msec
64 bytes from 192.168.0.253: icmp_seq=9 ttl=255 time=1.740 msec
When I do as follow: (NODE SLAVE)
#route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric
Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0
0 0 bond0
192.168.0.0 0.0.0.0 255.255.255.0 U 0
0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0
0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0
0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0
0 0 bond0
Which was the kernell proper to work with the channel bonding?
Does anybody have just the same problem?
Does anybody know if there is some problems with kernel 2.4.2-2
and channel bonding her?
If the configuration was right what can we do it?
I thank who could help me.
Thanks a lot,
Orlando Rocha.
Prof. Sistemas Digitais - CEFET-MA/BR
Administração de Redes com Windows NT Server e
Linux.
---------------------------------------------
Webmail Diginet - Internet é Diginet.
http://www.digi.com.br/
- Previous message: [PBS-USERS] checkpointing PBS jobs under linux
- Next message: interesting Athlon/P4 discussion from FreeBSD-Q-l
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list