One or more routers might be the best type of device to support multiple paths to a remote destination. Depending on your needs, it's possible to design redundacy to avoid most single points of failure (although often not inexpensively).
However, meeting the requirement of no downtime, even a second's, might be practically impossible. With much redundancy, especially for (non LAN) remote destinations, usually failure recovery/bypass takes some amount of time (milliseconds to seconds) and some traffic already in transit might be lost.
You can do this a number of ways, but because you mention no downtime and wanting redundancy when one goes down it really means you need another connection out from the remote site. If you ran a parrallel line from the remote device to the existing local device you really don't solve anything with respect to "in case one goes down" because that will still take the new parrallel line down as well. You could drop a second router at the remote site, set up HSRP on the user side and set up a connection out from the new router to your local device (or different device). Care must be taken for routing to outside world, and depending on what protocol you are running it may be exploited to load balance.
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...