	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.4

NIC bonding on Linux rhel5 results in heavy packet loss and the failover to eth2 does not work

Asked by structuredweb in Linux Networking, Linux Programming, Red Hat Linux

Tags: Linux, bond, bonding

Hello experts,
We have new rhel5 linux machine which is to replace our production machine. we configure the bonding (mode 0 - round robin) on the machine to be the interface while eth0 and eth2 its slaves. after this configuration we encounter heavy packet loss pinging from and to the machine. more then that, when we disconnect the eth0 network connection we lose the communication with the machine. (while disconnecting eth2, when eth0 is connected, does not change anything and we still have the communication to the machine).
We also saw that there is a bug with round robin and bonding with rhel5 (http://kbase.redhat.com/faq/docs/DOC-16051) and they recommend to work with active-backup configuration (mode=1), which we tried as well with the same results.
attached are the configuration files we use and the process of configuring the bonding. we will appreciate any help.
Thanks

Get your answer NOW

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:

           
           
             the cnofiguration flow and the files:
service network stop
ifcfg-bond0 file:
------------------------------
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
NETWORK=10.0.2.0
NETMASK=255.255.255.0
IPADDR=10.0.2.15
BROADCAST=10.0.2.255
GATEWAY=10.0.2.1
USERCTL=no
-----------------------------------
ifcfg-eth0 file:
-----------------------------------
DEVICE=eth0
HWADDR=00:24:E8:50:FA:E0
ONBOOT=yes
BOOTPROTO=none
MASTER=bond0
SLAVE=yes
USERCTL=no
 
#ONBOOT=no
#IPADDR=10.0.2.15
#NETMASK=255.255.255.0
#NETWORK=10.0.2.0
#BROADCAST=10.0.2.255
#GATEWAY=10.0.2.1
-----------------------------------
ifcfg-eth2 file:
-----------------------------------
DEVICE=eth2
HWADDR=00:15:17:B0:61:5C
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
 
#ONBOOT=no
#IPADDR=10.0.2.15
#NETMASK=255.255.255.0
#NETWORK=10.0.2.0
#BROADCAST=10.0.2.255
#GATEWAY=10.0.2.1
-----------------------------------
 
in /etc/modprobe.conf we added the lines:
alias bond0 bonding mode=1
options bond0 miimon=100
 
------------------------------------
 
we run:
modprobe bonding
modprobe mii
 
service network start
----------------------------
 
ifconfig shows that the bond0 is teh interface and eth0 and eth1 are its slaves.
also ethtool eth0 and eth1 show they are connected in the appropriate speed.

           
         

20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20090701_SELECT_ZONES

Hall of Fame

1. fosiul01121,113
2. KeremE66,870
3. it4soho55,301
4. noci55,120
5. Nopius53,612
6. oklit50,436
7. Roachy1...31,790
8. omarfarid31,437
9. arnold30,200
10. Redimido29,100
11. ravenpl27,405
12. rindi25,330
13. Blaz22,600
14. jar381721,962
15. jools20,855
16. WizRd-Li...20,000
17. Tintin19,993
18. ai_ja_nai19,052
19. savone15,664
20. stephenh...13,998
21. liddler13,700
22. kosarajud...12,280
23. mwecom...11,992
24. fmarzocca11,850
25. gheist11,122

1. jlevie726,902
2. Redimido450,376
3. pablourug...398,760
4. Nopius393,415
5. ravenpl389,671
6. noci282,640
7. wesly_c...261,418
8. rindi190,492
9. fosiul01166,313
10. KeremE163,756
11. omarfarid135,329
12. ahoffmann129,635
13. alextoft125,713
14. Blaz111,291
15. jar3817102,008
16. shakoush...100,219
17. uetian170797,633
18. grblades94,858
19. owensleft...81,427
20. e-tsik79,472
21. WizRd-Li...79,441
22. pjedmond76,703
23. slyong72,714
24. giltjr72,391
25. Tintin68,630

NIC bonding on Linux rhel5 results in heavy packet loss and the failover to eth2 does not work

Asked by structuredweb in Linux Networking, Linux Programming, Red Hat Linux

Tags: Linux, bond, bonding

About this solution