Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Different server vendors have different features, often under the label of "teaming". Sometimes their features will allow connections to multiple physical different switches. If so, they might require both switches to be interconnected within the same L2 domain. Also, you might not get full advantage of the multiple link bandwidths. (For example, I recall one server "teaming" technology that allowed the server to transmit on multiple ports, but would only receive on one.)
In the Cisco world, often the best "teaming" interconnection, to obtain maximum benefit of multiple links, is some variation of Etherchannel, or on Nexus switches, vPC. These technologies, when dealing with different physical Cisco devices, require some "glue" technology, such as FlexStack, StackWise, VSS, vPC. The servers usually need to support something like LACP.
