Environment:
- Organization with HQ and multiple remote offices
- Subscribed to 2 types of WAN services, MPLS Private WAN and Public Internet links
- In normal condition, Intranet traffic will go through MPLS Private WAN, Internet traffic will go out via Internet link
Requirement:
- To optimize both WAN links for better data transfer throughput between HQ and remote offices, as well as link fail-over protection
- Possible to establish a tunnel between HQ and remote offices, that can combine both MPLS WAN and Internet links into single logical pipe
- The tunnel has the intelligent to recognize which type of WAN (Private or Public) failed, and able to divert the packets from failed WAN pair to the working WAN pair automatically
Recommended Solution:
- Deploy Peplink Balance in each site, and establish SpeedFusion VPN Bonding with Connection Mapping enabled at both sites Balance routers
Special Notes for Connection Mapping:
- During the normal condition, packets will be load balance across both MPLS WAN and Internet links in SpeedFusion bonded VPN tunnel
- When remote office MPLS WAN failed, HQ Balance router will stop forward packets via it’s MPLS WAN, and divert these packets to it’s Internet WAN link
- After remote office MPLS WAN restored, HQ Balance router will resume forward packets via it’s MPLS WAN
- These load balance, fail-over, and fallback operations are perform automatically by the Peplink Balance routers, when Connection Mapping enabled
Devices Can be Deployed: Balance Series and MAX HD2/HD4 Series**