Is there a way to configure a failover scenario for source based static NATs? I know it's possible with destination based static NAT's through the use of route-maps, but not sure if I'd use the same method for source based.
Basically this is what I want to achieve:
10.10.10.10 = internal server 1 (primary)
10.10.10.11 = internal server 2 (backup)
I have a static nat entry for server 1:
ip nat inside source static 10.10.10.10 18.104.22.168
Currently, when we want to failover to the backup server, I have to manually change this static NAT entry (ip nat inside source static 10.10.10.11 22.214.171.124)
I want to find a way to have the NAT failover automatically when we failover to the backup server (i.e. if 10.10.10.10 stops translating to 126.96.36.199, make 10.10.10.11 translate to 188.8.131.52)
I hope that makes sense, I'm not a network genius. I really appreciate any help/advice I can get. Thanks!
You can probably accomplish this doing EEM scripting, but from a purely solution based view, I think assigning a VIP to 2 servers and configuring them for fail over may give you better results. In this scenario you have 2 servers sharing 1 virtual IP, depending on the server OS (windows clustering for example) when one fails the other takes up the load.
For 2008 server this is the info : http://blogs.technet.com/b/askcore/archive/2010/02/12/windows-server-2008-failover-clusters-networking-part-1.aspx
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...