I would be real careful debugging NAT on that 
router, specially if it does a lot of NATing. 
I have seen 7200 series router that do a 
considerable amount of NAT, and which usually 
ran at 0-5% utilization day in day out, ground
to a halt when debugging NAT was applied.

AFAIK, logging to console also adds a significant overhead to a busy router.

Also make sure the last command you enter before debug is "u all" so you have it in 
your buffer in case you need it.

> -----Original Message-----
> From: Tom Casaer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 31, 2000, 7:51 AM
> To: "'Zenzo'" <[EMAIL PROTECTED]>, "firewalls" <[EMAIL PROTECTED]>
> Subject: RE: monitoring NAT activity on CISCO-2621
> 
> on the router prompt type : router#conf term
>                                        router(config)# logging console
>                                         router(config)"exit
>                                         router#term mon
>                                         router#debug ip nat (or : debug ip
> nat detail)
>  
> You'll see all the  NAT-related output.  To stop: router#no debug all
>  
> use "?" to see more options ...  router#debug ip nat ? 
>  
>  
> regards,
> Tom
> 
> -----Oorspronkelijk bericht-----
> Van: Zenzo [mailto:[EMAIL PROTECTED]]
> Verzonden: donderdag 31 augustus 2000 12:29
> Aan: firewalls
> Onderwerp: monitoring NAT activity on CISCO-2621
> 
> 
> 
> (Pardon me, my previous msg was without subject :o))
>  
> Hi everyone,
> I'm posting a old question; I would like monitoring NAT activity
> on CISCO-2621. How can I do?
> Tanks in advance,
> Enzo.
> 
> 


*  Get free, secure online email at http://www.ziplip.com/  *
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]

Reply via email to