Cisco – Best practice for using multiple links between switches when link aggregation is not supported

bondingciscolinux-networkingnetworkingtopology

I have a half-dozen servers and workstations in an office. The systems are connected to a Cisco SG200 gigabit switch in the room. The room has two gigabit wall-port ethernet outlets. I have the switch connected to one of the wall ports. I'd like to make use of the other port to increase throughput to/from the systems in the room. However, our network organization does not support link teaming/aggregation between switches for switches they don't install and control themselves (for reasons that make sense for our institution), so I can't set up my switch to use link aggregation over two ethernet connections directly to the wall port.

How can I put the additional port to best use? One alternative is to directly connect it to another NIC on one chosen computer, so at least one system can take advantage of dual links. But perhaps there is a better configuration? I would ideally like to see the highest throughput possible between any system in the room and the outside world. It's a shame to bottleneck all network connections to a single gigabit line.

The servers mostly serve web pages (which includes some large content like videos) and REST-based network services that involve file transfers in the multi-megabyte range.

Best Answer

One cheeky and simple way to do this is to use two switches rather than one. You could then uplink half of your devices to one switch and half on the other, and thereby double your total throughput.

If you then require more outgoing throughput from a single server, you could bond the two interfaces with uplinks to both switches in your room. Just make sure you use a bonding mode that is intended for this kind of application (that uses different MAC addresses for traffic out of the two interfaces).