Meraki Routing priority

SOLVED
Yasuomi
Here to help

Meraki Routing priority

 

Hi,

 

Current,
The environment is constructed with non-meraki vpn peer.
One non-meraki vpn peer sets the Private Subnet to 0.0.0.0/0.

 

Yasuomi_0-1574662795586.png

 

 

When you check the routing, the priority is like this.

 

Yasuomi_1-1574663030982.png

 

As a result, no routing to the ASA is performed,
Communication to ASA is also going to Palo Alto.

 

What is the priority for this?
Is this expected behavior?

 

 

 

 

1 ACCEPTED SOLUTION

 

Even if it matches 192.168.x.0 / 24, it is not routed to the ASA.
Contact Meraki support.
 
Thank you very much.

View solution in original post

2 REPLIES 2
DensyoV
Meraki Employee
Meraki Employee

Hi,

 

Based on your route table, if the destination IP matches the 192.168.X.0/24 network then the traffic should be routed to ASA. However, if it does not match and falls under the default route 0.0.0.0/0 then it will go to the Palo Alto because it has a higher priority than the default route over the WAN connection.

 

If you suspect that the traffic is not routing over the IPsec even if it matches the 192.168.X.0/24 destination subnet, then you may need to call Meraki support so they can check whether this is the case or not.

 

Hope this helps. 

 

 

 

Please hit kudos if you found this post helpful and/or click "accept as solution" if this solved your problem.

 

Even if it matches 192.168.x.0 / 24, it is not routed to the ASA.
Contact Meraki support.
 
Thank you very much.
Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels