- About OSPF71
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Community Record
9
Posts
0
Kudos
0
Solutions
Badges
09-23-2018
04:19 PM
We refreshed our entire network with all Meraki devices and the last piece of the puzzle is to replace the old Watchguard firewall with the new MX250. I am trying to minimize interruption to the network since we do have 24 hour operations that rely on email, etc. and have pre-configured all settings, routes, vlans, etc. from the current firewall to the MX. The MX has not been turned on since we started the project and probably has some firmware updates to download so I am wondering if I connect it to our secondary WAN connection would that be the best way to get the device up to date to ensure a quick transfer on the switch-over date?
... View more
Labels:
09-23-2018
04:17 PM
We refreshed our entire network with all Meraki devices and the last piece of the puzzle is to replace the old Watchguard firewall with the new MX250. I am trying to minimize interruption to the network since we do have 24 hour operations that rely on email, etc. and have pre-configured all settings from the current firewall to the MX. The MX has not been turned on since we started the project and probably has some firmware updates to download so I am wondering if I connect it to our secondary WAN connection would that be the best way to get the device up to date to ensure a quick transfer on the switch-over date?
... View more
Labels:
06-13-2018
02:23 PM
Thanks, @Mr_IT_Guy. That info helps a lot. The one security appliance we have not replaced with a MX yet is a non Meraki peer which has the subnet(s) with needed resources and is not accessible.
... View more
06-13-2018
08:23 AM
Is the MX client VPN limited to local subnets or can resources in other MX sts vpn subnets be accessed?
... View more
03-07-2018
05:31 AM
Thank you! @AjitKumar
... View more
03-06-2018
03:03 PM
We have a branch office near our corporate headquarters that is connected via a direct VLAN service using Meraki switches with L3 routing enabled. It is pretty much the same setup as described in the Meraki L3 Switch Example documentation. We are currently replacing the primary third party firewall at the corporate office with a Meraki MX250. My question is what should the configuration be under Addressing & VLAN's-Routing for the corporate office/branch office connection? Add a Local VLAN? Example: A. Branch office switch setup - Meraki L3 enabled interface (172.0.0.1, VLAN 100) & gateway (upstream firewall - 172.0.0.254, VLAN 100) B. Corporate MX250 - Add a local vlan, MX IP 172.0.0.254, VLAN 100, subnet 172.0.0.0/24, etc.plus static routes to branch office data and voice subnets.
... View more
Labels:
02-07-2018
08:09 AM
So to summarize...under Addressing & VLAN's-Routing: -Configure branch office VLAN/subnet -Add static routes for user & phone subnets at branch -Configure Per port VLAN for branch office ethernet handoff Thanks again for clarifying!
... View more
02-07-2018
06:38 AM
Hi @DCooper. The Watchguard has the branch office VLAN configured on one of the interfaces and is directly connected to the branch via a Dell switch. After looking at the network information on the WG again under "Routes" I do see static routes for the subnets at the branch office (user, phone vlan's). Would I need to add those static routes under "Add a Static Route" on the Addressing & VLAN's section of the MX250?
... View more
02-07-2018
12:28 AM
We are refreshing our network with Meraki gear and I am in the planning stages of moving over all the firewall rules, VLAN information, etc. to a MX250. We have a point to point vlan connection to a branch office that is local to our corporate headquarters. On our current WatchGuard XTM 5 the port is configured as a trusted subnet. I am assuming on the MX250 I just need to configure the branch office subnet vlan along with the others (in Addressing & VLANs) and in the section below that (per Port VLAN configuration) configure a port for the branch office vlan?
... View more
Labels:
