Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About OSPF71
Community Record
15
Posts
0
Kudos
1
Solution
Badges
Sep 12 2023
12:33 PM
Hi @DarrenOC No issues yet. We are in the process of migrating some of our remote cellular systems into multiple private ip networks. We have the option of using some MX's on hand or a couple of Cisco C8200 appliances. For one location, there is a MX in place connected to the public network and the isp's private network circuit was just installed.
... View more
Sep 11 2023
3:52 PM
Has anyone connected a MX to Verizon or AT&T's private ip network?
... View more
Labels:
- Labels:
-
Other
Dec 1 2022
4:00 AM
After placing a ticket with AWS and verifying that the AWS side of the network was configured correctly, I submitted a case to Meraki support. Thanks to the tech who had me place the vMX into pass-through mode from routed in deployment settings. Just added the local AWS subnet to be advertised and it works as expected now.
... View more
Nov 22 2022
12:55 PM
The #1 problem I run into with this issue is - Windows firewall on the host. Try disabling it temporarily to see if the issue is resolved. -That was the very first thing I did before looking at ACL's and Security group settings. Do you have any Meraki organisation VPN firewall rules that could be at play? https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-site_VPN_Firewall_Rule_Behavior -None >Can communicate from any subnet in our corporate LAN to the windows servers on our VPC, but cannot communicate from the servers to any subnet beyond the vMX. I don't clearly understand. You can talk to the machines in the VPC behind the Meraki VMX. Are these other machines you can not talk to located in the same VPC or a different VPC? Have all the subnets (at least in the same VPC) got the same AWS route table associated? Currently, the vMX is setup as a spoke connected to a specific data center hub. I can communicate from any subnet in the corporate LAN that is connected to that DC hub, to the servers in the VPC. The servers and vMX are in the same subnet. The subnet is associated with the routing table. The servers in the VPC need to talk to the servers in the DC hub but cannot. Looks like traffic is dropping off at the vMX.
... View more
Nov 22 2022
5:19 AM
The vMX is in default mode per the guide you reference, which I used to configure and deploy the vMX. As far as the route table, yes, I added a route table with all available subnets with the target as the vMX instance.
... View more
Nov 21 2022
11:03 AM
Set up a vMX for the first time in our AWS account. Can communicate from any subnet in our corporate LAN to the windows servers on our VPC, but cannot communicate from the servers to any subnet beyond the vMX. Thought it was a ACL rule somewhere. Have tried explicitly allowing icmp but must be missing something simple. Any ideas from AWS experts?
... View more
Sep 23 2018
4: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
Sep 23 2018
4: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
Jun 13 2018
2: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
Jun 13 2018
8:23 AM
Is the MX client VPN limited to local subnets or can resources in other MX sts vpn subnets be accessed?
... View more
Mar 7 2018
5:31 AM
Thank you! @AjitKumar
... View more
Mar 6 2018
3: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
Feb 7 2018
8: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
Feb 7 2018
6: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
Feb 7 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
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 2198 | Dec 1 2022 4:00 AM |
© 2024 Cisco Systems, Inc.
