[AusNOG] How to setup something like LACP across two switches

[Philip Loenneker]

Hi James,

MLAG or MC-LAG would allow you to have LACP across multiple switches on your side, with a single switch on the customer side. They would see your gear as a single LACP peer. I’m not sure if the Nexus 3064 supports it or not – it appears some Nexus gear can, but I couldn’t find anything specific on the 3064.

Regards,
Philip Loenneker | Network Engineer | TasmaNet
40-50 Innovation Drive, Dowsing Point, Tas 7010, Australia
P: 1300 792 711
philip.loenneker at tasmanet.com.au<mailto:philip.loenneker at tasmanet.com.au>
www.tasmanet.com.au<http://www.tasmanet.com.au/>

From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of James Cunningham
Sent: Friday, 20 April 2018 9:18 AM
To: ausnog at lists.ausnog.net
Subject: [AusNOG] How to setup something like LACP across two switches

Hello Fellow Ausnoggers,

I'm hoping that I can quickly pick the brain of someone more knowledgeable in data centre networking than myself.

We have a customer in one of our racks in Equinix who has a single network switch, and some servers connected to it. We currently have two connections from our switch to the customer's switch, with LACP for redundancy (and as a side effect, we get a slight bandwidth boost for 2 x 1Gbps connections, which is a slight bonus).

We would like to improve this by putting in two network switches on our end, to protect again a single switch failure on our side, but the customer will still have one single network switch.

I'm pretty sure we can't do LACP with this style of setup - so what would people recommend to achieve redundancy here? Main thing is that the connection needs to auto-failover if a network switch fails, or if one of the uplinks fails.

I have created the attached diagram which illustrates what we are trying to do.

Can anyone please help? I'll owe a beer at the Next AusNOG meetup!

Thanks

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20180419/5319de49/attachment.html>