cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
962
Views
5
Helpful
7
Replies

Remove a static NAT but the static route remains in the routing table

JOSEPH GAYNOR
Level 1
Level 1

For a test added the following:

Ip nat outside source static 10.151.112.9 10.226.133.219 add-route

At test conclusion issued the following commands:

no Ip nat outside source static 10.151.112.9 10.226.133.219 add-route

clear IP nat trans

cle ip route *

Issue:

show ip route

Routing entry for 10.226.133.219/32
Known via "static", distance 1, metric 0
Redistributing via eigrp 99
Routing Descriptor Blocks:
* 10.151.112.9
Route metric is 0, traffic share count is 1

!

I've also deleted and re-added the route for 10.151.112.0/24 and 10.226.133.0/24.  Verified the outside source static statement is gone when I do a show run. No change in status.

router is a ISR4321/K9 running bootflash:isr4300-universalk9.16.09.03.SPA.bin

any ideas short of reloading the router?

1 Accepted Solution

Accepted Solutions

First, let me thank you for your continuous feedback.
The NAT is not the issue. Actually the IP that was being NATed with that statement is no longer being NATed.
Traffic is running as it should, this just appears to be some sort of ghost entry in the routing table.
I was looking around in Cisco and found this: - not exactly my problem, but very close. I'm just not using the no-alias keyword.
Bug SearchCSCvk13358
Help | Feedback Feedback
outside NAT Add-route with no-alias cause permanent static route
CSCvk13358
Description
Symptom:
Static route added by NAT add-route option is not cleared after remove NAT config.
Conditions:
After config and unconfig of no-alias/add-route static NAT CLI an static route is permanently added in the routing table and not getting removed.
ip nat outside source static 192.168.21.20 192.168.121.70 no-alias add-route
no ip nat outside source static 192.168.21.20 192.168.121.70 no-alias add-route
S 192.168.121.70 [1/0] via 192.168.21.20 >>>>>>>>>>>>> Route not removed after removing CLI
Workaround:
Reloading router.

View solution in original post

7 Replies 7

Hello,

 

--> Redistributing via eigrp 99

 

What EIGRP neighbors is this being redistributed to ? Chances are that it is coming back from there...

The eigrp neighbors are not seeing the route.
The route table on the offending router lists the route as static
S 10.226.133.219/32 [1/0] via 10.151.112.9

Hello


@JOSEPH GAYNOR wrote:

show ip route

Routing entry for 10.226.133.219/32
Known via "static", distance 1, metric 0
Redistributing via eigrp 99
Routing Descriptor Blocks:
* 10.151.112.9
Route metric is 0, traffic share count is 1


Sh ip route static
clear ip nat trans * force

 


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

# cle ip nat trans * force
^
% Invalid input detected at '^' marker.
Force is not an option.

Hello,

 

what if you remove the 'ip nat outside' and 'ip nat inside' statements from all interfaces (temporarily of course) ?

First, let me thank you for your continuous feedback.
The NAT is not the issue. Actually the IP that was being NATed with that statement is no longer being NATed.
Traffic is running as it should, this just appears to be some sort of ghost entry in the routing table.
I was looking around in Cisco and found this: - not exactly my problem, but very close. I'm just not using the no-alias keyword.
Bug SearchCSCvk13358
Help | Feedback Feedback
outside NAT Add-route with no-alias cause permanent static route
CSCvk13358
Description
Symptom:
Static route added by NAT add-route option is not cleared after remove NAT config.
Conditions:
After config and unconfig of no-alias/add-route static NAT CLI an static route is permanently added in the routing table and not getting removed.
ip nat outside source static 192.168.21.20 192.168.121.70 no-alias add-route
no ip nat outside source static 192.168.21.20 192.168.121.70 no-alias add-route
S 192.168.121.70 [1/0] via 192.168.21.20 >>>>>>>>>>>>> Route not removed after removing CLI
Workaround:
Reloading router.

Hello,

 

the reload is what we wanted to avoid...looks like there is no other way...thanks for sharing the bug info !

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco