Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello Community,We were forced into swapping out the vMX100 for a vMX-M, and now we cannot reach the servers on AWS. It seems to be an issue with the AWS server instances' route back to the vMX-M.1) YES. autoVPN is up - able to ping LAN interface ...
edit: RESOLVED: Issue was with AWS Security Groups that someone applied to the servers.====================================Hello,I have an AWS routing issue when using the vMX100, but not sure. Everything worked great with the AWS VPN up. But wh...
It started working.Wow. I am so embarrassed. With Meraki Support we rebuilt the vMX three times. We missed checking that box on the last instance that we built. I just "stopped" it, and now traffic is going both ways over autoVPN network.Thanks t...
I agree that a lot of terms are over-used. Unfortunately, I have inherited these various networks with ms225s. I suppose that my frustration with Meraki on this, is that if OSPF is not possible on the ms225, then why even mention OSPF in the dashboa...
Thanks for the responses. I'm disappointed. I was really looking forward to implementing OSPF to get rid of confusing static routes everywhere.Heads-up. It is possible to use the MS225 SVI's for client default-gateways and then route between subnets ...
Your post was very timely for me. Trying to get rid of static routes on Meraki ms225's. Thought I was going to implement simple OSPF.....but no.....Meraki strikes again. Totally amazing that even simple OSPF cannot be configured on the Meraki m...