Hi there. I know something of this from my Cisco training. Firstly, your card probably does support link aggregation, and what this means is that simply you can share the load of data coming into or out of the card at any one time. How you implement this is sometimes down to proprietary protocols, and sometimes not so much the protocols but the hardarwe and the type of switch involved (such as a Cisco 29xx XL). What you normally need to watch for in such cases is looping (as someone here also stated before my post). When you don't implement the STA (Spanning Tree Algorithm) to designate root ports etc on your switches, things tend to lose their way around the LAN, get repeated, and generally cause lots of pain! STA stops this, and though needed at the switch (not at the card), it may be worth looking at this thought its not terribly important for your set-up right now. With "trunking", you are probably best using two lines for data access and two for redundancy; the server would be able to guarantee a certain level of service this way--and again, how you do this will be down to the individual switch manufacturer, type of switch and your Linux configuration etc. Personally I would aggregate the links and see what kind of throughput I'm getting at peak times; use a good analyser and find out if there are any problems, and watch for loops (though I doubt you'll have a problem there anyway). HTH Paul