Best practice to switch/migrate Meraki.

Solved
Dipen
Getting noticed

Best practice to switch/migrate Meraki.

Hey Community!  We are planning to switch from Pfsense(Garbage) to Meraki platform coming thursday, any suggestions or things we should do prior to make switch over smooth as possible? We are also having folks that are working from home right now we have populated them on Client VPN. 

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

I would do it the following way:

  1. Set up the MX parallel to the pfSense
  2. Configure AnyConnect VPN and only route the VPN-subnet to the MX
  3. Move all VPN-clients to the MX
  4. Move the outgoing default-route to the MX
  5. Remove the pfSense from the network

View solution in original post

4 Replies 4
KarstenI
Kind of a big deal
Kind of a big deal

I would do it the following way:

  1. Set up the MX parallel to the pfSense
  2. Configure AnyConnect VPN and only route the VPN-subnet to the MX
  3. Move all VPN-clients to the MX
  4. Move the outgoing default-route to the MX
  5. Remove the pfSense from the network
Dipen
Getting noticed

We set MX parallel to pfsense also checked Anyconnect and it is set to route on default VPN-subnet. However not sure about the outgoing route what exactly that means are you talking about traffic shaping because we don't have any traffic routing right now. 

 

KarstenI
Kind of a big deal
Kind of a big deal

You probably have any internal systems. At the moment they are likely routed to the pfSense and has to be later switched to the MX.

Dipen
Getting noticed

Got it thanks 

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