My preference in this is to just scope the translation clearing to just the affected static, then quickly delete the static translation which I think sridder was saying.
In particularly busy environments an inbound acl on the internal/external interfaces will keep traffic from triggering the static translation while you can delete it and then remove the additional acl denies. If you do it all carefully no other endpoints will have service distrupted and that should always be a goal. AMR wrote: > > You dont shut down the interface. Just remove the 'ip nat outside' or other > such necessary command from the interface. It's far less affecting to the > router to remove the nat command than it is to shut down an interface which > would possibly cause a change in the route table, forcing calculations, etc. > > ""Steven A. Ridder"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Also shut down the local lan interface in case some lan client tries to go > > out to the internet while you are changing nat. Some busy sites this > > happens at. And include an * after the trans for all the translations. > > > > -- > > RFC 1149 Compliant. > > > > > > FAQ, list archives, and subscription info: > http://www.groupstudy.com/list/cisco.html > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=31584&t=31560 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
