03-30-2009 05:56 AM - edited 03-06-2019 04:54 AM
I have a 3745 running IOS 12.3. We are trying to enter this:
---------------
ip nat inside source static 172.1.1.2 125.254.1.1 redundancy HSRP100 route-map ITNAT
access-list 101 permit ip host 172.1.1.2 host 149.1.1.1
route-map ITNAT permit 10
match ip address 101
------------------------
We get an invalid command indicating that "redundancy" and the "route-map" may not be permitted in the "ip nat inside source static statement together. Has anyone run across this before?
03-30-2009 06:43 AM
AKAIK - route-map nat is not supported on the 3745, I know it's not supported on the 65xx.
HTH>
03-30-2009 06:56 AM
When I enter in the command "ip nat inside source static ", I have the following commands to choose from:
extendable - Extend this translation when used
no-alias - Do not create an alias for the global address
no-payload - No translation of embedded address/port in the payload
redundancy - NAT redundancy operation
route-map - Specify route-map
vrf - Specify vrf
So.. it looks like it supports "route-map"
03-30-2009 06:59 AM
When I enter in the command "ip nat inside source static ", I have the following commands to choose from:
extendable - Extend this translation when used
no-alias - Do not create an alias for the global address
no-payload - No translation of embedded address/port in the payload
redundancy - NAT redundancy operation
route-map - Specify route-map
vrf - Specify vrf
So.. it looks like it supports "route-map"
03-30-2009 07:06 AM
I hate to point this out - but just because the command is visible, does not mean that it will work or it's acutally supported.
I just check the cisco feature navigator and "NAT - Ability to use Routes Maps with Static Translations" is only availabile in
GD Release 12.3(26)
LD Release 12.4(13) 12.4(4)T3 12.3(17c)
ED Release 12.4(11)XJ4 12.4(6)XT2 12.4(4)XC7 12.4(2)XA2 12.3(14)T7 12.3(11)YZ2 12.3(11)XL1
12.3(8)ZA 12.3(4)XD4 12.2(15)ZJ5 12.2(15)T16 12.2(11)YT2
MD Release 12.4(23) 12.4(15)T8
on the 3745 platform.
03-30-2009 07:14 AM
Ok. I understand. Would you happen to know how we could NAT ip address 172.1.1.2 to 125.254.1.1 only when the 172.1.1.2 source is trying to get to 149.1.1.1 without a route-map?
03-30-2009 07:21 AM
Mmmmm off the top of my head no - I would try a route-map first. Then I would see if it were possible to NAT closer to the destination rather than the source? if that is not possible - then I would consider to upgrade the IOS.
03-30-2009 07:03 AM
When I enter in the command "ip nat inside source static ", I have the following commands to choose from:
extendable - Extend this translation when used
no-alias - Do not create an alias for the global address
no-payload - No translation of embedded address/port in the payload
redundancy - NAT redundancy operation
route-map - Specify route-map
vrf - Specify vrf
So.. it looks like it supports "route-map"
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide