Author Topic: Peering Between Multiple Remote Sites?  (Read 5334 times)


  • VIP
  • Full Member
  • *****
  • Posts: 39
    • View Profile
Peering Between Multiple Remote Sites?
« on: May 27, 2015, 01:55:43 PM »
Do remote sites need to be setup as peers to one another, like a mesh setup vs hub and spoke? There will occasionally be direct data transfers between one remote site to another remote site. The firewalls here have a VPN setup that is hub and spoke topology, but data transferred between remote sites will not traverse the wanos box at the main site since the firewall will just pass (route) the data on to the other remote site.


  • Team Wanos
  • Administrator
  • Full Member
  • *****
  • Posts: 629
    • View Profile
Re: Peering Between Multiple Remote Sites?
« Reply #1 on: May 27, 2015, 02:09:36 PM »
They don't need to, but if the inter-branch traffic needs to be optimized, then a MultiSite config on the spokes is needed.

If the mesh inter-branch traffic is insignificant, then the spoke sites traffic can fall within a default #99 bypass policy. In this case only traffic destined to the hub site is optimized and inter-branch traffic falls in a bypass rule.

Note: Having inter-branch traffic optimized (default) without a MultiSite config will cause the datastores to go out of sync and have a negative impact.
« Last Edit: May 27, 2015, 02:22:04 PM by ahenning »
CCIE RS, CCIE SP, Mnet&sys

Note: Forum posts may be outdated. Please see the latest documentation at