multi nic redundancy to increase availability

[O'Neill, Donald (US - Deerfield)]

Bonding two nic's to the same IP is an easy process.  This is taken from
the bonding.txt file. 

1) create a bond0 file in your /etc/sysconfig/network-scripts directory

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

2)add an entry into your /etc/modprobe.conf file

Alias bond0 bonding

3) Change your /etc/sysconfig/network-scripts/ifcfg-eth0 file to 
DEVICE=eth0
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

4)Change your /etc/sysconfig/network-scripts/ifcfg-eth1 file to 
DEVICE=eth1
USERCTL=no
ONBOOT=yes
MASTER=bond0
SLAVE=yes
BOOTPROTO=none

Restart network
-----Original Message-----
From: redhat-list-bounces at redhat.com
[mailto:redhat-list-bounces at redhat.com] On Behalf Of zhicheng wang
Sent: Friday, December 03, 2004 6:27 AM
To: redhat-list at redhat.com
Subject: multi nic redundancy to increase availability

hi,

we have a dell pe 2650 and other dell servers, all
with two ether cards, running redhat EL AS3. i need to
make use of both cards so that the down time may be
reduced.

it seems that there are a few different ways to do so.
binding two cards to the same IP seems complicated. is
it possible to give each card different ip, but the
same domain name? i remembered something like each
card's IP must be on different subnet? but I want them
to be on the same subnet. any suggestions?

thanks
cheng

=====
Best wishes
Z C Wang


	
	
		
___________________________________________________________ 
ALL-NEW Yahoo! Messenger - all new features - even more fun!
http://uk.messenger.yahoo.com

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message.  Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.