You are wanting port bonding (http://www.linuxhorizon.ro/bonding.html)
This will bond two port together as a single port and IP. You then have twice the bandwidth and should a port die the other will traffic the load. For reliablity you want the two ports to be coming from different chips. Say, on on the mother board and another from a card. ----- Original Message ----- From: "Peter Butler" <[email protected]> To: [email protected] Sent: Friday, April 29, 2011 1:04:30 PM Subject: [Linux-HA] DRBD and HA-Linux Hello, I have two Linux systems (i.e. two SBCs in a single chassis) A and B that are connected to one another via two independent Ethernet fabrics: System A System B +----------+ |----------+ | | | | | eth0---+------+---eth0 | | | | | | | | | | | | | | | | | | eth1---+------+---eth1 | | | | | +----------+ +----------+ I am setting up DRBD between the two Systems, which is easy enough in itself, however I want to implement it with redundant IP connectivity. DRBD only allows for a single IP address to be listed for both the local and remote nodes (i.e. *either* the eth0 IP addresses *or* the eth1 addresses), but not both. As such I was hoping that maybe HA-Linux could help me in this regard. That is, is there a way to configure each system such that it presents a single IP address to the other system, such that HA-Linux manages which Ehternet fabric is used (should one of them fail)? i.e. System A System B +----------+ |----------+ | | | | | eth0---+ +---eth0 | | |\ /| | | | \ / | | | | ethA------ethB | | | | / \ | | | |/ \| | | eth1---+ +---eth1 | | | | | +----------+ +----------+ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
