Thank you for the clarification and references @AjitKumar I just have couple of questions here, pardon me if I might ask stupid question. I would be happy to read up any reference you might point me towards. For Second Question below: Traditionally application aware routing works is: Identification: Traffic coming from LAN gets matched against the "application database" Application Policy Matching: Once application is matched, it is determined that what SLAs (Loss, Latency. Jitter) are applied to this flow. This is then matched against the BFD parameters Forwarding: Forwarding of the traffic to specific interface which matches such parameters. Once forwarded, encapsulation happens and the packet is on its way I was wondering would there not be the way, just to Identify the traffic using application db and define next hop interface, irrespective of the SLA or encapsulation? For third question below: I would use 3 interfaces, 2 MPLS and 1 LTE. MPLS would make VPN tunnel to DC and forward the traffic, LTE would be used to make a connection to the Meraki controller on cloud. Nothing else, esp no forwarding of traffic. I am looking at this because I have read that Meraki box would need a direct access to internet to work.
... View more
