04-06-2014 07:26 PM - edited 03-04-2019 10:43 PM
04-06-2014 10:49 PM
It is possible with a static default pointing towards both of the ISPs. if you are specific towards any one of the routes then point a static route for that particular route towards both of the ISPs.
04-07-2014 06:20 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Does your feature set support PfR? If so, it can dynamically load balance.
04-07-2014 08:10 PM
Hello.
Totally Agree with Joseph that the more advanced, Scalable and dynamic way to do this will be with oer/PfR.
Now as Thanveer said you can do Equal Load Balancing via different interfaces with static routes as well.
So you have the options over the table what you will need to define are the exact requirements cause you could even use PBR to send traffic over one link depending on the source , etc (This can also be done with PfR)
It would make sense to use the link with the more available bandwith for the critical traffic and the other link for the rest of the traffic or even have the one with the highest bandwith sending all traffic and only using the secondary if the primary fails. U have many options which is good :)
Keep us Posted!
Regards,
Jcarvaja
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: