HA MX250 pair with temporarily mismatched LAN connections

Solved
Pugmiester
Building a reputation

HA MX250 pair with temporarily mismatched LAN connections

Hi all,

 

We're in the middle of a switch migration project and I hadn't considered how best to get the MX LAN links moved over. Our setup is a little unconventional, in that the appliances are sat in different buildings and subsequently connected to differnet LAN switches, but each using port 9 on the MX with a matching set of MX and switch port VLAN config.

 

What I'm hoping to be able to do, is configure Port 19 (SFP+ 10Gb) with a matching VLAN setup and then migrate the LAN connection over on each appliance. In a perfect world, we would have multiple pairs of local hands around to do this simultaneously, but it's more likley I'll be on my own.

 

I should clarify that the old and new switches are currently trunked together so communicatiosn between the MX's over the LAN link will still be possible once the connections are moved to the new switches.

 

Am I likely to give the MX's a headache by having different LAN ports in use on the Primary and Spare MX, even if it's only for 15 minutes while I run between buildings?

1 Accepted Solution
RWelch
Kind of a big deal
Kind of a big deal

You should be OK as long as these conditions are met:
 
Both MXs can reliably communicate with each other over the LAN (VRRP heartbeats must pass between them).
 
The VLAN configuration matches on both MXs and the connected switches.
 
The switches (old and new) are trunked together, ensuring the MXs remain in the same broadcast domain and can see each other on all VLANs.
If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.

View solution in original post

5 Replies 5
alemabrahao
Kind of a big deal
Kind of a big deal

I don't see any reason for it to cause a problem, if I'm not mistaken, I've done migrations this same way running two MX at the same time and didn't have any issues.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Pugmiester
Building a reputation

Thanks for the quick reply. I was reasonably sure things would be OK, but it's Friday and my brain is frazzled after a busy week so figure a second opinion would be wise.

RWelch
Kind of a big deal
Kind of a big deal

You should be OK as long as these conditions are met:
 
Both MXs can reliably communicate with each other over the LAN (VRRP heartbeats must pass between them).
 
The VLAN configuration matches on both MXs and the connected switches.
 
The switches (old and new) are trunked together, ensuring the MXs remain in the same broadcast domain and can see each other on all VLANs.
If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
Pugmiester
Building a reputation

Thanks for the quick reply. I was reasonably sure things would be OK, but it's Friday and my brain is frazzled after a busy week so figure a second opinion would be wise.

 

I'm certainly not making any changes today, but I feel much more confortable now to get something planned in for next week.

PhilipDAth
Kind of a big deal
Kind of a big deal

I have done exactly this, but permanently.

 

The primary site had plenty of 10Gbe switch ports, so I used those.

The DR site didn't, so I used a Gigabit port on the switch.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco ID. If you don't yet have a Cisco ID, you can sign up.
Labels