We don't support static nat with route-maps at all. We had a bug to block the CLI but it appears it got exposed again.
I'm filing a bug now to get that CLI blocked again. Rodney On Tue, Jul 24, 2007 at 02:13:27AM -0500, Scott Mace wrote: > Is the static NAT route-map feature supported in hardware on the PFC3B > in 12.2SR? > > Something like: > > int g2/1 > ip address 10.50.1.1 255.255.255.0 > ip nat outside > int g2/2 > ip address 10.55.1.1 255.255.255.0 > ip nat outside > int g2/3 > ip address 10.1.1.1 255.255.255.0 > ip nat inside > > ip nat inside source static 10.1.1.10 172.16.15.1 route-map test1 > ip nat inside source static 10.1.1.10 192.168.1.50 route-map test2 > > access-list 111 permit ip host 10.1.1.10 10.8.0.0 0.0.255.255 > access-list 112 permit ip host 10.1.1.10 192.168.100.0 0.0.0.255 > > route-map test1 permit 10 > match ip address 111 > set ip next-hop 10.50.1.2 > > route-map test2 permit 10 > match ip address 112 > set ip next-hop 10.55.1.2 > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
