If you just want your local users to have a fault tolerant internet connection you're pretty much set. You would just need to configure 2 default routes on your internet router, one to your primary ISP and one to your secondary. To avoid asymmetric routing use floating static routes and set the secondary route to a higher administrative distance then the primary. Then set your default route on the firewall to point to the router. Just remember you won't be using your secondary ISP unless your primary goes down.
If you need to balance your traffic between the two links or if you need fault tolerance for inbound connections things get a bit more complicated. I won't go into detail but here are a couple of options:
â¢ Use a device like a Radware Linkproof to manipulate NAT and DNS. (For load balancing and inbound fault tolerance.)
â¢ Talk BGP with your providers. (This usually is costly and complicated)
I'm currently using the smoke and mirrors approach (DNS and NAT) but it's defiantly not ideal if you want your solution to scale.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...