> We have a router configured to work with 2 ISPs, one of > them through a satelite link. This particular link is > beeing monitored with a ip sla and track commands. When > this link fails the default route is deleted automatically > form the routing table, and the backup default route is > then installed. We also use automatic nat failover. The > problem is that some inside servers that always go to > the same destination IP/PORT get NATed in the moment > the backup link is up, and when the primary comes up > they go to the internet with the source address equal > to the backup outside interface.
We fixed this with an EEM script that reacts to route or track changes and then executes the "clear ip nat trans *" command to clear the NAT table. B. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
