So I'm having a strange issue. We have a VMX in AWS and a VMX in Azure. I have an EC2 instance in AWS on the same subnet as our VMX but I cannot ping the instance from the VMX or vice versa. Likewise, our AWS VMX cannot seem to reach instances through our Azure VMX. Route tables are advertising all routes as appropriate. I can reach other physical MX appliances through the AWS VMX. Any ideas on what I might be overlooking?
... View more
Hey, I'm having an issue that I'm going in circles with Support on but just wanted to get some community insight on it first. We have a MX65W that has 3 VLANs setup - Default (1), a VoIP (12), and a test network (16). All ports except 11, 12, and 13 are disabled on the MX. Port 11 is a trunk with all VLANs allowed and default VLAN 1. Ports 12 and 13 are set to access ports on VLAN 16. On the MS side, port 1 is a trunk, all VLANs allowed, default VLAN 1. All ports on the MS are set to trunk, default VLAN. Port 12 and port 24 on the MS are set to access ports and VLAN 16. Here's where things get strange. I plug a computer into port 12 on the MS. It pulls an IP from the proper VLAN but limited connectivity. The MS cannot ping the device but it shows connectivity. I plug the computer into the MX port 12, obtains the proper IP (same DHCP IP it gets from the switch, in fact, all DHCP details are the same), full connectivity. I plug the computer into any other port on the MS so it pulls from VLAN 1, full connectivity. When I engaged Meraki Support, they checked the switch and said everything was configured properly. I pull packet captures from the switch, I see the DHCP process in full. Do I have a bad switch that doesn't like VLANs or did I miss something somewhere? No ACLs or anything other than the defaults. Thanks!
... View more