bonding connection for MX and cisco switch catalyst

Dmen
New here

bonding connection for MX and cisco switch catalyst

Hello, I am using a MX68 and a WS-C2960X. I want to connect 5 LAN ports on MX to 5 sw ports on c2960x with trunk mode and bonding it to achieve a 5Gbps bonded connection.

How can I do it? Thanks

7 Replies 7
ConnorL
Meraki Employee
Meraki Employee

MX does not support LAG/LACP, so you cannot do this. 

 

It's worth noting the MX68 is rated for 700Mbps, so it won't fully saturate a 1G Ethernet link.

https://documentation.meraki.com/MX/MX_Sizing_Information/MX_Sizing_Principles

Dmen
New here

Thanks connorL, so is there any solution to configure a pair of physical ports on both devices as "trunk" ports, enabling VLANs to be carried across the connection? 

ConnorL
Meraki Employee
Meraki Employee

1 port on both the MX and switch, configured as a trunk with the same required VLAN(s), yes 🙂 

 

You may find this KB regarding VLAN configuration useful: https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Fundamentals_of_80...

Dmen
New here

No, I mean a solution which can utilize a redundancy protocol like VRRP. There are 2 trunks connections between MX and WS. One can standby for failover functionality.

thomasthomsen
Kind of a big deal

You can have STP blocking one of the links to your switch.

If you configure the same settings on the two links on the MX, and have spanning-tree enabled on your switch (it should be by default), then your switch should block one of the links.

In case of the active link fails, the other link should then be opened.

Dmen
New here

Thank you 🙂

DarrenOC
Kind of a big deal
Kind of a big deal

As @thomasthomsen has stated, you’ll need a separate link into each switch with loopguard configured on the switch uplinks 

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
Get notified when there are additional replies to this discussion.