fedora 12 - 4 port bonding failover - slowww
Hi, I hope you can help because I worked with my partner today and he is at a loss on this and I can't explain it
either. I will describe it the best I can since he set this up. We setup what he called 4 port bonding failover. The 4 ports were defined as slaves and bond0 and bond1 were setup. He defined bond0.conf and bond1.conf in the /etc/modprobe.d directory. Below are the configuration files. The interfaces are up...eth1, eth2, eth3, eth4 and the network 'seems to function' but it's not quite right, something seems wrong or slow, and there seem to be indications of excessive slowness for possibly a second sometimes. Let me know if you can help it would be greatly appreciated. Below are the file configurations made the only other change was entering the command -->> modprobe bonding Below are the configuration files: [root@hhlxnrcsas02 ~]# cd /etc/modprobe.d [root@hhlxnrcsas02 modprobe.d]# [root@hhlxnrcsas02 modprobe.d]# ls anaconda.conf blacklist.conf blacklist-visor.conf bond0.conf bond0.conf~ bond1.conf bond1.conf~ dist-alsa.conf dist.conf dist-oss.conf floppy-pnp.conf openfwwf.conf [root@hhlxnrcsas02 modprobe.d]# ls -ltr total 52 -rw-r--r--. 1 root root 16 2008-01-04 03:43 blacklist-visor.conf -rw-r--r--. 1 root root 30 2009-07-07 00:21 openfwwf.conf -rw-r--r--. 1 root root 845 2009-07-26 07:04 blacklist.conf -rw-r--r--. 1 root root 473 2009-10-21 00:25 dist-oss.conf -rw-r--r--. 1 root root 5616 2009-10-21 00:25 dist.conf -rw-r--r--. 1 root root 382 2009-10-21 00:25 dist-alsa.conf -rw-r--r--. 1 root root 53 2009-11-04 19:24 floppy-pnp.conf -rw-r--r--. 1 root root 52 2010-02-26 08:50 anaconda.conf -rw-r--r--. 1 root root 22 2010-02-26 12:12 bond0.conf~ -rw-r--r--. 1 root root 20 2010-02-26 12:15 bond1.conf~ -rw-r--r--. 1 root root 52 2010-02-26 12:34 bond0.conf -rw-r--r--. 1 root root 50 2010-02-26 12:35 bond1.conf [root@hhlxnrcsas02 modprobe.d]# cat bond0.conf~ alias bond0 bonding [root@hhlxnrcsas02 modprobe.d]# cont bond1.conf~ -bash: cont: command not found [root@hhlxnrcsas02 modprobe.d]# cat bond1.conf~ alias bond1 bonding [root@hhlxnrcsas02 modprobe.d]# cat bond0.conf alias bond0 bonding alias bond0 mode=5 miimon=100 [root@hhlxnrcsas02 modprobe.d]# cat bond1.conf alias bond1 bonding alias bond0 mode=5 miimon=100 [root@hhlxnrcsas02 modprobe.d]# ************************************************** /etc/sysconfig/network-scripts (below) [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth0~ # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth0 HWADDR=00:21:9B:9B:4F:21 ONBOOT=yes MASTER=bondo SLAVE=yes [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth1~ # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth1 HWADDR=00:21:9B:9B:4F:23 ONBOOT=yes MASTER=bondo SLAVE=yes [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth2~ # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth2 HWADDR=00:21:9B:9B:4F:25 ONBOOT=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth3~ # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth3 HWADDR=00:21:9B:9B:4F:27 ONBOOT=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth4~ cat: ifcfg-eth4~: No such file or directory [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth1 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth1 HWADDR=00:21:9B:9B:4F:23 ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth2 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth2 BOOTPROTO=none HWADDR=00:21:9B:9B:4F:25 ONBOOT=yes MASTER=bond1 SLAVE=yes [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth3 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth3 BOOTPROTO=none HWADDR=00:21:9B:9B:4F:27 ONBOOT=no MASTER=bond1 SLAVE=yes [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth4 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth4 HWADDR=00:10:18:64:35:68 ONBOOT=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-bond0 DEVICE=bond0 ONBOOT=yes BOOTPROTO=none #BONDING_OPTS="mode 1 miimon=100" NETWORK=10.35.13.0 IPADDR=10.35.13.85 NETMASK=255.255.255.0 BROADCAST=10.35.13.255 USERCTL=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-bond1 DEVICE=bond1 ONBOOT=yes BOOTPROTO=static #BONDING_OPTS="mode 5 miimon=100" NETWORK=10.35.13.0 IPADDR=10.35.13.86 NETMASK=255.255.255.0 BROADCAST=10.35.13.255 USERCTL=no [root@hhlxnrcsas02 network-scripts]# *********************************************************************************** |
In your listing of /etc/sysconfig/network-scripts
Your first result is from cat-ing a backup file You don't show the result of cat-ing the real file (eth0) But in that backup (ifcfg-eth0~) you have MASTER=bondo not MASTER=bond0 If the real file is the same, that might be a problem. Are you using gEdit ? You can disable those backups. |
backup files - bondo - was a mistake - the real files are fixed.
Yes, the backup files did have an error - bondo
but the real files have bond0 he did fix that. |
bond0.conf and bond1.conf aren't consistent, is that intended ?
The config I've found looks like Code:
alias bond0 bonding |
typo - good spot and fixed - is this good now?
This ping is from a machine on the same switch.
Is this good response time? [root@hhlxnrcsas02 /]# ping hhlxnrcsas01 PING hhlxnrcsas01.hh.chs (10.35.13.66) 56(84) bytes of data. 64 bytes from 10.35.13.66: icmp_seq=2 ttl=64 time=0.129 ms 64 bytes from 10.35.13.66: icmp_seq=5 ttl=64 time=0.116 ms 64 bytes from 10.35.13.66: icmp_seq=7 ttl=64 time=0.113 ms 64 bytes from 10.35.13.66: icmp_seq=9 ttl=64 time=0.106 ms 64 bytes from 10.35.13.66: icmp_seq=11 ttl=64 time=0.112 ms 64 bytes from 10.35.13.66: icmp_seq=13 ttl=64 time=0.118 ms 64 bytes from 10.35.13.66: icmp_seq=15 ttl=64 time=0.108 ms 64 bytes from 10.35.13.66: icmp_seq=17 ttl=64 time=0.109 ms 64 bytes from 10.35.13.66: icmp_seq=19 ttl=64 time=0.090 ms 64 bytes from 10.35.13.66: icmp_seq=21 ttl=64 time=0.092 ms 64 bytes from 10.35.13.66: icmp_seq=36 ttl=64 time=0.112 ms 64 bytes from 10.35.13.66: icmp_seq=37 ttl=64 time=0.107 ms 64 bytes from 10.35.13.66: icmp_seq=38 ttl=64 time=0.105 ms 64 bytes from 10.35.13.66: icmp_seq=39 ttl=64 time=0.119 ms 64 bytes from 10.35.13.66: icmp_seq=40 ttl=64 time=0.104 ms 64 bytes from 10.35.13.66: icmp_seq=60 ttl=64 time=0.113 ms 64 bytes from 10.35.13.66: icmp_seq=62 ttl=64 time=0.123 ms 64 bytes from 10.35.13.66: icmp_seq=64 ttl=64 time=0.115 ms 64 bytes from 10.35.13.66: icmp_seq=66 ttl=64 time=0.106 ms 64 bytes from 10.35.13.66: icmp_seq=68 ttl=64 time=0.093 ms 64 bytes from 10.35.13.66: icmp_seq=70 ttl=64 time=0.114 ms 64 bytes from 10.35.13.66: icmp_seq=72 ttl=64 time=0.113 ms 64 bytes from 10.35.13.66: icmp_seq=74 ttl=64 time=0.105 ms 64 bytes from 10.35.13.66: icmp_seq=76 ttl=64 time=0.115 ms |
still - NG
The ping time may look ok, but the icmp response sometimes hangs but the time still looks ok.
I think it's time to dump the idea of 2 x 2 failover and just go 4 x 1 bonding. I'm not sure this will work since I still see the terminal hang for minutes remotely. Ideas? |
May I ask, in your ping output, where is responses to icmp_seq=1,3,4,6,8,10,12....
Do you have any packets loss? |
As you made no reply to my last post, may I refer you here :
http://sourceforge.net/projects/bond...ms/forum/77913 |
RE: bond0.conf and bond1.conf aren't consistent, is that intended ?
No that wasn't intended. I fixed that typo.
There is still console latency, i.e. I did find 50% packet loss. See next reply. |
RE:May I ask, in your ping output, where is responses to icmp_seq=1,3,4,6,8,10,12....
Nice spot yes there is 50% packet loss below.
I must reiterate, I did not setup this up my partner did and I understand the basics of bonding, but not the configuration of bonding failover. Does the configuration look correct with the fixes to the typos? I will check out the source forge site as well. Should I bail on this bonding failover idea since I have to get this machine networked for all the next phases of the project. Below is the packet loss. Below is a ping from a good machine on the same switch to the bonding failover machine. [root@hclxnrcas01 ~]# ping hhlxnrcsas02 PING hhlxnrcsas02.hh.chs (10.35.13.85) 56(84) bytes of data. 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=2 ttl=64 time=1.16 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=4 ttl=64 time=0.087 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=6 ttl=64 time=0.084 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=9 ttl=64 time=0.104 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=11 ttl=64 time=0.130 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=13 ttl=64 time=0.131 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=15 ttl=64 time=0.129 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=17 ttl=64 time=0.129 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=19 ttl=64 time=0.127 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=21 ttl=64 time=0.128 ms 64 bytes from hhlxnrcsas02.hh.chs (10.35.13.85): icmp_seq=23 ttl=64 time=0.134 ms --- hhlxnrcsas02.hh.chs ping statistics --- 24 packets transmitted, 11 received, 54% packet loss, time 23000ms rtt min/avg/max/mdev = 0.084/0.213/1.164/0.301 ms [root@hclxnrcas01 ~]# |
I'm concerned that the proscribed way of creating ifcfg-bondX files is different from your method of using included files.
For example, the fedora documentation says to put your alias lines in /etc/modprobe.conf http://docs.fedoraproject.org/deploy...s-bonding.html And the ifcfg templates look like yours but you have commented out the bonding_opts in favour of relying on the included files. http://docs.fedoraproject.org/deploy...aces-chan.html You say you fixed the typos in the ifcfg-bondX files, does that mean they look like : Code:
alias bond1 bonding Code:
alias bond0 bonding It's hard to track down problems when the basic outlines for bonding configuration have not been followed. Notice my links are specific fedora documentation for Fedora 12. |
RE: I'm concerned that the proscribed way of creating ifcfg-bondX files is different
To be clear, I completely relied on my partner to configure this, so I can't answer as to why he decided on certain configurations.
Here is what he stated the goal was (as best I understand): - "create bonding failover" using the 4 ports, with 2 bonds - Physically the machine has (4) ports - we created a dns entry for hhlxnrcsas02 - 10.35.13.85 for the primary bond0 (eth1, eth2) - we created a dns entry for hhlxnrcsas02b - 10.35.13.86 for the failover bond1 (eth3, eth4) - he mentioned being uncomfortable with a fedora 12 deployment and ext4 since he thinks ext4 is not tested enough...but I assured him I researched this and ext4 is stable enough for this (2 server 120TB deployment - we are viewing hhlxnrcsas02 - one server) He also said "there is no /etc/modprobe.conf but there is a /etc/modprobe.d directory" and below are the contents:root@hhlxnrcsas02 etc]# cd modprobe.d [root@hhlxnrcsas02 modprobe.d]# ls -ltr total 52 -rw-r--r--. 1 root root 16 2008-01-04 03:43 blacklist-visor.conf -rw-r--r--. 1 root root 30 2009-07-07 00:21 openfwwf.conf -rw-r--r--. 1 root root 845 2009-07-26 07:04 blacklist.conf -rw-r--r--. 1 root root 473 2009-10-21 00:25 dist-oss.conf -rw-r--r--. 1 root root 5616 2009-10-21 00:25 dist.conf -rw-r--r--. 1 root root 382 2009-10-21 00:25 dist-alsa.conf -rw-r--r--. 1 root root 53 2009-11-04 19:24 floppy-pnp.conf -rw-r--r--. 1 root root 52 2010-02-26 08:50 anaconda.conf -rw-r--r--. 1 root root 22 2010-02-26 12:12 bond0.conf~ -rw-r--r--. 1 root root 20 2010-02-26 12:15 bond1.conf~ -rw-r--r--. 1 root root 52 2010-02-26 12:34 bond0.conf -rw-r--r--. 1 root root 50 2010-02-26 21:25 bond1.conf [root@hhlxnrcsas02 modprobe.d]# cd .. [root@hhlxnrcsas02 etc]# ls -ltr modprobe.conf ls: cannot access modprobe.conf: No such file or directory [root@hhlxnrcsas02 etc]# So he put (what I think) would normally go in the /etc/modprobe.conf file and created these bond0.conf and bond1.conf files with the entries below since he stated there "was no /etc/modprobe.conf" He then ran the command 'modprobe bonding' Just an FYI I also saw him run the command '/sbin/insmod bond0' and from what I read you need options for this and this is for tuning. As you can see there is no /etc/modprobe.conf file so I cannot speak about this, should there be? (I'll keep reading...) As far as the typo goes I corrected from your previous response: [root@hhlxnrcsas02 modprobe.d]# cat bond1.conf alias bond1 bonding alias bond0 mode=5 miimon=100 [root@hhlxnrcsas02 modprobe.d]# - NO - I have not changed the 2nd line to options but it looks like I should according to what I have learned so far and I think I should? (I'll keep reading the docs...) - Is mode 5 correct for the goal we are trying to achieve? This is the whole picture...I'll keep reading... Let me know what you think...thank you Charles |
Personally, I like to keep things simple and "by the book" for one reason really. If something works, but there are errors or inconsistencies, it is very hard to trace those problems if you have strayed from the usual path. Sometimes things work even when it has been set up wrongly, it's not always black or white.
I accept that modprobe.conf is missing, and cannot comment on that. Maybe a separate googling will establish why that is. Regarding the contents of the bondX.conf files, alias is a command. If you use it as a label (which appears to be the case in line 2 of those files) you are actually aliasing bondX again, but with unpredictable results. The syntax is not correct for either alias or for assigning options. This is as far as I can establish. I can find no other evidence of it being done like that. And in bond1.conf, there should be no refs to bond0 your last post shows it as it was when I mentioned it before. Another interesting thing is you say there are 4 physical ports, but you have listings for eth0, eth1, eth2, eth3, eth4. How is eth0 involved ? |
Just in case, can you check with "ifconfig -a" and when just "ifconfig", what all ethernet card are active and have the same configuration. Also all of them connected to the same equipment.
|
RE: Personally, I like to keep things simple
RE: ifconfig.... -->Are you stating this "bonding failover" using bond0 and bond1 was a bad idea and I should revert to a 4x1 ? (I'll keep reading...) - I'll find out what I can about the fed. 12 missing /etc/modprobe.conf - I have just changed the bond0 and bond1.conf files to as follows: changes made /etc/modprobe.d/bond0.conf alias bond0 bonding options bond0 -o bond0 mode=5 miimon=100 changes made /etc/modprobe.d/bond1.conf alias bond1 bonding options bond1 -o bond1 mode=5 miimon=100 (I followed your suggestion and need to check the syntax of: options bond1 -o bond1 mode=5 miimon=100) - "And in bond1.conf, there should be no refs to bond0 your last post shows it as it was when I mentioned it before." ----> I have corrected this a few posts ago - "Another interesting thing is you say there are 4 physical ports, but you have listings for eth0, eth1, eth2, eth3, eth4." ---> Actually there is more interfaces than needed...good spot...What should ifcfg-eth(x) should I start with (I'll keep reading)????? Below is another clue to this problem and may be causing the packet loss which did not disappear after change the 2nd line in the bond0.conf and bond1.conf files and issuing-->> 'modprobe bonding' and 'service network restart' commands. -->TOO MANY interfaces per below should I start at ifcfg-eth0 or ifcfg-eth1?? --->see below Thanks. AFTER CHANGE DETAILED BELOW --- changes made /etc/modprobe.d/bond0.conf alias bond0 bonding options bond0 -o bond0 mode=5 miimon=100 alias bond1 bonding options bond1 -o bond1 mode=5 miimon=100 ~ still plenty of packet loss below [root@hhlxnrcsas02 modprobe.d]# ping hhlxnrcsas01 PING hhlxnrcsas01.hh.chs (10.35.13.66) 56(84) bytes of data. 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=3 ttl=64 time=0.122 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=6 ttl=64 time=0.116 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=8 ttl=64 time=0.115 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=10 ttl=64 time=0.104 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=12 ttl=64 time=0.107 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=14 ttl=64 time=0.115 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=16 ttl=64 time=0.114 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=18 ttl=64 time=0.112 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=20 ttl=64 time=0.112 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=22 ttl=64 time=0.109 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=24 ttl=64 time=0.109 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=26 ttl=64 time=0.117 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=28 ttl=64 time=0.108 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=29 ttl=64 time=0.117 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=30 ttl=64 time=0.107 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=31 ttl=64 time=0.106 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=117 ttl=64 time=0.107 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=119 ttl=64 time=0.083 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=121 ttl=64 time=0.112 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=123 ttl=64 time=0.116 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=125 ttl=64 time=0.120 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=127 ttl=64 time=0.116 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=129 ttl=64 time=0.114 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=131 ttl=64 time=0.114 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=133 ttl=64 time=0.117 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=135 ttl=64 time=0.116 ms 64 bytes from hhlxnrcsas01.hh.chs (10.35.13.66): icmp_seq=137 ttl=64 time=0.117 ms ^C --- hhlxnrcsas01.hh.chs ping statistics --- 138 packets transmitted, 27 received, 80% packet loss, time 141998ms rtt min/avg/max/mdev = 0.083/0.111/0.122/0.016 ms [root@hhlxnrcsas02 modprobe.d]# ORIGINAL CONFIG ALSO BELOW - too many ethx -rw-r--r--. 1 root root 254 2009-10-27 16:11 ifcfg-lo -rw-r--r--. 3 root root 108 2010-02-26 08:50 ifcfg-eth5 -rw-r--r--. 3 root root 108 2010-02-26 08:50 ifcfg-eth4 lrwxrwxrwx. 1 root root 20 2010-02-26 08:58 ifdown -> ../../../sbin/ifdown lrwxrwxrwx. 1 root root 11 2010-02-26 08:58 ifdown-isdn -> ifdown-ippp lrwxrwxrwx. 1 root root 18 2010-02-26 08:58 ifup -> ../../../sbin/ifup lrwxrwxrwx. 1 root root 9 2010-02-26 08:58 ifup-isdn -> ifup-ippp -rw-r--r--. 1 root root 108 2010-02-26 11:54 ifcfg-eth3~ -rw-r--r--. 1 root root 108 2010-02-26 11:57 ifcfg-eth2~ -rw-r--r--. 1 root root 132 2010-02-26 12:20 ifcfg-eth1~ -rw-r--r--. 1 root root 132 2010-02-26 12:20 ifcfg-eth0~ -rw-r--r--. 3 root root 147 2010-02-26 12:44 ifcfg-eth2 -rw-r--r--. 3 root root 146 2010-02-26 12:44 ifcfg-eth3 -rw-r--r--. 1 root root 168 2010-02-26 12:46 ifcfg-bond0 -rw-r--r--. 1 root root 169 2010-02-26 12:46 ifcfg-bond1 -rw-r--r--. 3 root root 143 2010-02-26 12:48 ifcfg-eth0 -rw-r--r--. 3 root root 143 2010-02-26 12:49 ifcfg-eth1 [root@hhlxnrcsas02 network-scripts]# [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth0 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth0 HWADDR=00:21:9B:9B:4F:21 ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth1 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth1 HWADDR=00:21:9B:9B:4F:23 ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth2 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth2 BOOTPROTO=none HWADDR=00:21:9B:9B:4F:25 ONBOOT=yes MASTER=bond1 SLAVE=yes [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth3 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth3 BOOTPROTO=none HWADDR=00:21:9B:9B:4F:27 ONBOOT=no MASTER=bond1 SLAVE=yes [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth4 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth4 HWADDR=00:10:18:64:35:68 ONBOOT=no [root@hhlxnrcsas02 network-scripts]# cat ifcfg-eth5 # Broadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet DEVICE=eth5 HWADDR=00:10:18:64:35:6A ONBOOT=no [root@hhlxnrcsas02 network-scripts]# ***TOO MANY INTERFACES DISPLAYED BELOW [root@hhlxnrcsas02 network-scripts]# ifconfig -a bond0 Link encap:Ethernet HWaddr 00:21:9B:9B:4F:21 inet addr:10.35.13.85 Bcast:10.35.13.255 Mask:255.255.255.0 inet6 addr: fe80::221:9bff:fe9b:4f21/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:859 errors:0 dropped:0 overruns:0 frame:0 TX packets:703 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:147375 (143.9 KiB) TX bytes:158673 (154.9 KiB) bond1 Link encap:Ethernet HWaddr 00:21:9B:9B:4F:25 inet addr:10.35.13.86 Bcast:10.35.13.255 Mask:255.255.255.0 inet6 addr: fe80::221:9bff:fe9b:4f25/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:439 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:100805 (98.4 KiB) TX bytes:3744 (3.6 KiB) eth0 Link encap:Ethernet HWaddr 00:21:9B:9B:4F:21 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:841 errors:0 dropped:0 overruns:0 frame:0 TX packets:349 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:144006 (140.6 KiB) TX bytes:74741 (72.9 KiB) Interrupt:36 Memory:d2000000-d2012800 eth1 Link encap:Ethernet HWaddr 00:21:9B:9B:4F:21 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:18 errors:0 dropped:0 overruns:0 frame:0 TX packets:354 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3369 (3.2 KiB) TX bytes:83932 (81.9 KiB) Interrupt:48 Memory:d4000000-d4012800 eth2 Link encap:Ethernet HWaddr 00:21:9B:9B:4F:25 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:426 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:99241 (96.9 KiB) TX bytes:1727 (1.6 KiB) Interrupt:32 Memory:d6000000-d6012800 eth3 Link encap:Ethernet HWaddr 00:21:9B:9B:4F:25 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1564 (1.5 KiB) TX bytes:2017 (1.9 KiB) Interrupt:42 Memory:d8000000-d8012800 eth4 Link encap:Ethernet HWaddr 00:10:18:64:35:68 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:40 Memory:da000000-da012800 eth5 Link encap:Ethernet HWaddr 00:10:18:64:35:6A 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:50 Memory:dc000000-dc012800 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:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2400 (2.3 KiB) TX bytes:2400 (2.3 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) [root@hhlxnrcsas02 network-scripts]# |
All times are GMT -5. The time now is 03:10 PM. |