Access Failed over SD-WAN

[Maiquel]

In our new meraki deployments, some branches are having problems.
Through the branch I cant exec the ping or intranet access (http), Terminal server nothing works, but from the HQ to the Branch I access normally. If I reboot the meraki the branch can ping the HQ, exec the Terminal server to AD-Server, access internaet HTTP. If I turn off the Meraki and power on, the problem occurs and nothing work over Brach. Some one have this problem? 

MX-65 -> Firmware Current 14.20 

[PhilipDAth]

To be clear; rebooting the MX works - power cycling the MX breaks things?

How is the branch connecting to the HQ?  AutoVPN over the Internet?  AutoVPN over MPLS?  Routed over MPLS?

[Maiquel]

Yes, rebooting the MX works power cycling breaks. The  Branch use  AutoVPN over MPLS (wan2). 

[PhilipDAth]

Is this an MPLS WAN circuit or an MPLS Internet circuit?

[Maiquel]

Hi Philip, tks for your help. 

MPLS WAN circuit. 

[PhilipDAth]

This is very unusual.  Is there anything doing NAT between between the MX's (you re not likely to have this)?

When is is broken, does the MX appear to be online in the Dashboard?  Does the VPN status for the MX appear to be up (green circle)?

Is there a single Hub in your AutoVPN (aka only a single VPN path to the destination)?

[Maiquel]

Hi Philip,
The MPLS router have the Cisco WaaS Module with WCCP redirect. When i use ftp for example where the Cisco Waas does not accelerate the ftp work and i can get the file, but i try use the tcp/80 for the same server does not work. But tcp/80 for that server is accelerating. When i remove the wccp redirect all its work very well.

[PhilipDAth]

It sounds like you have a WAAS mis-configuration then (since using tcp/80 through it does not work).  The Meraki kit shouldn't realy be bothered by this, as it is mostly using ports that WAAS is not interested in (except for perhaps tcp/443 if enabled).

If you disabled WAAS do you still have the same failover issue?