On Jun 17, 4:14pm, Alexei Rodriguez wrote:
Subject: Re: ATM and Fore SPANS failover +--- In a previous state of mind, Scott Miller skottie@fa.disney.com
wrote:
| | On some platforms, all interfaces in a given system can have the same
IP
| address, which simplifies management, and means there is one "view" | of a multi-interface machine from the outside. Routing gets simpler,
too.
Sounds like etherchannel... I think Alteon was trying this with their Gigabit stuff; unfortunately, no other vendor supports this feature.
SGI is working on interface aggregation for 100baseT, but nothing is released yet. SGI's SPANS implementation does this, but it is connection-based load balancing, not traffic based. We've also talked with SGI about doing this for TCP/IP over HIPPI, but we haven't heard anything back.
For Solaris systems, the ATM interfaces have seperate IP addresses, and the device driver re-directs VC's across both interfaces, independent of the IP layer routing. it's kind of funky, but it does provide load balancing and failover.
I had always wondered if anybody was using (packet-slicing) ATM for their filers. What sort of performance are you getting?
We're not using packet slicing, just two interfaces, each on a different subnet.
I can get 11 MB/sec per interface sustained read, using two interfaces in a fibrechannel F630. For sustained writes, the F630 pegs the CPU at 100% at 12 MB/sec across both interfaces.
-Skottie