I have two WAN connections and one LAN connection.
FE0/0 (T1) and FE0/1 (Cable)
FE0/1/0 is LAN
I need to make sure that when Cable FE0/1 is down or track is unsuccessful that workstations (and possibly servers, read on) are able to still reach the WAN through FE0/0 (T1). I'm not sure if my NAT statement (or lack thereof) is correct.
I currently have:
ip nat inside source list 1 interface FastEthernet0/0 overload
and I tried to add:
ip nat inside source list 1 interface FastEthernet0/1 overload
for the T1, but when I add the additional ip nat statement, it replaces the other one. Do I need two NAT statements for this to be successful? How would I configure this?
Additionally I have 4 static NAT statements which are for servers to reach the WAN on their designated public IP's (if the T1 is available, we want them to go out this interface.) If the T1 is not available, is it possible to NAT them to public addresses on the Cable interface (FE0/1)?
Thanks for giving me a hand with this! Please see attached config.
I used route-maps as you can see in the attached modified configuration. Could you tell me how I can prefer the T1 route FOR THE SERVERS ONLY (as it has a higher AD and is not default unless CABLE is down)? I only want the servers to go out CABLE if T1 is down.
Please let me know what you think and if this is possible.
Great, that looks promising. One last question: if we are forcing the connection out the T1 interface at 220.127.116.11; what happens if the T1 is down? How can we then have it go out CABLE connection (18.104.22.168) ONLY IF the T1 is down?
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...