Network Resilience

[farhsyed]

Hi,

We need to test the following scenario for network Resilience setup on RH 2.4/2.6 with AS2.1, 3, 4. Following is the requirements:

One Server has two ethrnet adapters(eth0, eth1)
IP on eth0 192.168.13.X
IP on eth1 192.168.13.Y

both adapters needs to be connected to Two different core switches for redundancy/resilience.

One Virtual IP of 192.168.13.Z needs to be defined on the server & also defined on both core switches.

For users the Virtual IP is known & Switch will route the traffic to any of the Physical IP(eth0, eth1)

In case of any of the ethernet adapters fails other one is available, similarly if any of the Core Switch is down, other one routes the traffic over Virtual IP to any of the Physical IP.

Please guide us, if possible any step by step tutorial/config details would be appreciated.

Farrukh

 

[SamBones]

I would think that would be some form of interface bonding as described in this link...

http://www.cyberciti.biz/tips/linux...ork-interfaces-nic-into-single-interface.html

 

[thedaver]

(I'm sorry, but it's kind of inconsistent design to have switch redundancy (very low rate of failure) for a single point of failure machine (higher rate of failure) with NIC redundancy (pretty low component level failure). That's an observation, sorry to stick my nose into your business on that regard. I'm guessing you've brought that message to someone's attention.)

The solution itself would largely be a switching fabric solution.

eth0 and eth1 would be cabled to each designated switch and the switches would need to be able to route the discrete routes (where justified) and the virtual IP to it's connected NIC.

You could simply bond the two NICs and use a single IP for the machine. Your switching model would allow for 1.1.1.Z to be delivered by the prevailing switch.

There's really no need to provde 1.1.1.X and 1.1.1.Y IPs on the NICs. Bond them and create a single IP. This single IP solution assumes you don't really have a specific use for the .X and .Y IPs.

If you had 2 or more machines answering the virtual IP, then that's a different story.

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/