Hot fail over with big pipe Internet, how do you manage bandwidth?

Hi all,

We’re looking to use FusionHub for high availability for some customers, so they might have 100Mbps fibre that we want to fail over to 100Mbps cable, keeping their IP addresses and no interruption to VoIP. I was going to do this with FusionHub on AWS but the customer uses more than 1000GB of bandwidth each month so that’s over $100+ monthly in AWS usage fees.

Since we aren’t bonding anything, is it possible to instead have all Internet traffic stay local, but instead only route traffic that needs to be highly available through the VPN? So for example, if they have a PBX on prem, have it connect to the SIP trunk provider via FusionHub, or a FTP server etc, anything that requires inbound fail over, but for normal traffic or music streaming etc it stays local and doesn’t go through the VPN? That way the VPN bandwidth usage is significantly lower than having 100% of traffic over it?

I guess if we bond then 100% traffic has to go on it, but just curious for these customers with 100Mbps+ primary pipes, or 500Mbps even. If they just want hot fail over it’s pretty expensive routing 500Mbps of bandwidth through FusionHub 24/7 vs only important traffic. Thanks!

Hello again psychobunny,

Using outbound policies you can select a specific IP Address, IP Network, or Domain be sent out via FusionHub or you can have it sent out directly to the internet. This means that you won’t have to send the full 1000 GB out to FusionHub.

If you’d like to bond and have all traffic take advantage of the bonding, you would need to have 100% of that traffic sent out to the FusionHub.

1 Like