Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Enterprise Linux > AS/ES/WS v. 3 > Issue <<  114 of 594 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 3760
Last update: 02-21-06
Issue:
How do I configure miimon and arp_interval/arp_ip_target for network interface bonding on Red Hat Enterprise Linux version 3 or 4?
Resolution:
These two options are configured as kernel module options in the /etc/modules.conf (in Red Hat Enterprise Linux 3) or /etc/modprobe.conf (in Red Hat Enterprise Linux 4) file. An example of using miimon is shown below. 

 
        alias bond0 bonding
        options bond0 mode=0 miimon=100
        alias bond1 bonding
        options bond1 -o bonding1 mode=0 miimon=200


These options actually set the bonding module to check the link status of every interface in bond0 every 100 milli-seconds and the link status of every interface in bond1 every 200 milli-seconds. If one of the links is down the interface will be avoided by the bond.

An example of using the arp_interval and arp_ip_target options be be seen below: 
 
        alias bond0 bonding
        options bond0 mode=0 arp_interval=100 arp_ip_target=10.10.10.1,10.10.10.2
        alias bond1 bonding
        options bond1 -o bonding1 mode=0 arp_interval=200 arp_ip_target=20.20.20.1,20.20.20.2

In this example bond0 will send arp requests for 10.10.10.1 and 10.10.10.2 every 100 milli-seconds. Bond1 will send ARP requests for 20.20.20.1 and 20.20.20.2 every 200 milli-seconds. If an interface does not receive an ARP response for a period of time it will be marked as down. This means that the arp_ip_target addresses must be selected such that the responses will be distributed over all of the interfaces.

After changes are made to the /etc/modules.conf (in Red Hat Enterprise Linux 3) or /etc/modprobe.conf (in Red Hat Enterprise Linux 4) file the bonding modules must be removed from the kernel and reloaded with the new options. To do this run the following commands:

service network stop
rmmod bonding
rmmod bonding1
service network start


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Enterprise Linux > AS/ES/WS v. 3 > Issue <<   114  of  594  >>