Hi everyone, first of all, I'm sorry for my english!!!
I have a Cisco ASA with 03 interfaces:
- outside (22.214.171.124/24)
- primary (126.96.36.199/24)
- backup (188.8.131.52/24)
Also, I have one primary server with its backup server located in other site. Both servers have a real IP address and a virtual IP address:
- Primary Server: (real IP: 184.108.40.206) (virtual IP: 220.127.116.11)
- Backup Server: (real IP: 18.104.22.168) (virtual IP: 22.214.171.124)
The ASA has two routes for the "virtual IP address" of the servers, like this:
route primary 126.96.36.199 255.255.255.255 188.8.131.52 1 track 123
route backup 184.108.40.206 255.255.255.255 220.127.116.11 10 (note the weight of this second route)
The track 123 monitors the real ip address of the primary server (18.104.22.168), so when this server is down, the ASA automatically
changes the route to 22.214.171.124, using 126.96.36.199 as next-hop instead 188.8.131.52. This works fine.
But, we also need to hide the IP address 184.108.40.206 to the clients that access through the outside interface. So, we use a static NAT mapping the IP 220.127.116.11 with the IP 18.104.22.168.
static (primary,outside) 22.214.171.124 126.96.36.199
static (backup,outside) 188.8.131.52 184.108.40.206
The problem is that if I do this neither of the statics work (OF COURSE, conceptually this totally makes sense to me)
I have to choose only one of both "statics", the primary or the backup interface.What I actually need is that the ASA map the global IP to the local IP through the interface where the route is active to the virtual IP address at that moment, and all this has to be automatic.
We had recently migrated from one Cisco 1811 Router to this ASA, and with the router this works just fine (sure, no INTERFACE mapping is needed for the static).
Can somebody please help me with this!!!!!!
through the interface where it knows