Meraki Community
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • About Guest2019

About Guest2019

Re: MS 350 behind ASA 5516 won't route traffic

by in Switching
‎Sep 17 2019 1:53 PM
‎Sep 17 2019 1:53 PM
Thanks for the suggestion but it wasn't NAT or ACL. In my current Cisco networks I've avoided using vlan 1 for anything and I was trying to attempting to do the same on this network but Meraki makes that pretty difficult to do.  I had vlan 10 set as the native vlan which apparently was causing the issues.  Once I added vlan 1 as a transit vlan to the 350 and pointed the ASA static route at that and set it as the native vlan on the Meraki switches it worked.  If anyone has any ideas on how to eliminate vlan 1 from the environment i'm all ears.   Thanks again for the suggestions. ... View more

MS 350 behind ASA 5516 won't route traffic

by in Switching
‎Sep 16 2019 6:41 PM
‎Sep 16 2019 6:41 PM
Hello,   In all of my previous networks that I've managed i used EIGRP on Cisco ASAs to connect to Catalyst L3 switches and it worked flawlessly with minimal setup.  This is my first L3 Meraki network and I'm having issues getting it to properly route traffic sitting behind an ASA 5516-X. My inside interface on the ASA is 172.17.10.1/24. On the MS I have 3 vlans, (172.17.10.0/24, 172.17.20.0/24, and 172.17.30.0/24) I configured the uplink route of 0.0.0.0/0 with the next hop being the IP of the inside interface on the ASA, 172.17.10.1.  On the ASA i have static routes for each of the vlans pointing at the IP of the vlan interface.  The management IPs of the Merakis are in the 172.17.10.0/24 range and they can all get to the internet.  However, anything on vlan 20 and 30 can't and I'm at a loss.  A device on vlan 20 or 30 can ping each of the vlans on the device but can't ping the ASA.  Any ideas?   Thanks in advance. ... View more
© 2024 Cisco Systems, Inc.