Cisco 2811 nat rule will not delete % similar static entry already exist

[j.bontje]

ios c2800nm-advipservicesk9-mz.124-11.XJ4.bin

problem : nat rule will not be deleted keeps saying similar static entry

rtr cisco 2811 vrf environment

Hi

one of my CM asked to change their nat rule, calling later that they mixed up the ports. now something strange happend on the Cisco 2811 it will not accept my no statements......huh ?even if I added the forced command behind it (forced     Delete all dynamic translations (forcefully)

As it's a production router reload is not considered unless... Guess there plenty knowledgable people over who hint me or advice me in the right direction

for sure I'm overlooking something or my skill needs an upgrade (both always work in progress)

my google fu skill ended here in relation to nat and cisco 2811 and this specific error. but deemed not to be usefull

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_q_and_a_item09186a00800e523b.shtml

NAT with VRF/MPLS

even though it's not in use, the NAT statement, cisco 2811 is witholding my new nat rule

what am I missing ? specific for 2811

ip : 192.168. is from the lan

ip : 1.1      is the wan/public address

1) tried with no  ip nat inside source static tcp 192.168.x.x 456 1.1.1.1 456 vrf falcoaisthebest extendable

% similar static entry (192.168.x. -> 1.1.1.1) already exists  no joy Cisco keeps complaining

2) tried  with no  ip nat inside source static tcp 192.168.x.x 456 1.1.1.1 456 vrf  falcoaisthebest extendable forced

% similar static entry (192.168.x. -> 1.1.1.1) already exists      no joy Cisco keeps complaining

my google fu skill ended here in relation to nat and cisco 2811 and this specific error.

http://www.cisco.com/en/US/tech/tk648/tk361/technologies_q_and_a_item09186a00800e523b.shtml

NAT with VRF/MPLS does not really fit in my problem at 1st sight

action

conf t

no ip nat inside source static tcp 192.168.x.x 1234 1.1.1.1 1234 vrf falcoaisthebest extendable

past the following ip nat rule same source&destination different soure/dest port

ip nat inside source static tcp 192.168.x.x 456 1.1.1.1 456 vrf falcoaisthebest extendable

% similar static entry (192.168.x. -> 1.1.1.1) already exists

past the following ip nat rule with forced added same result

ip nat inside source static tcp 192.168.x.x 456 1.1.1.1 456 vrf falcoaisthebest extendable forced

ip nat inside source static tcp 192.168.x.x 1234 1.1.1.1 1234 vrf falcoaisthebest extendable

% similar static entry (192.168.x. -> 1.1.1.1) already exists

[Sandeep Choudhary]

Hi ,

Have you removed config (Ip nat inside/ outside) from the interfaces ?

First remove from them and the do :

https://supportforums.cisco.com/docs/DOC-3097 -----Follow this document

You can try to remove the "ip nat inside" and "ip nat outside" commands  from the related interfaces and then do a "clear ip nat trans *".  Once  disabled, you should be able to safely remove the stale static NAT  entries.

and then

no ip nat inside source ........

or

just check this link.

http://www.phirebird.net/2009/07/cant-remove-ip-nat-entries-on-cisco-router-static-entry-in-use-cannot-remove/

or

just See the answer of this thread:

https://supportforums.cisco.com/message/3754385#3754385

Regards

Please rate if it helps.

[j.bontje]

thanks a lot will plan a maint window for that :-) will let you know the outcome