NAT problem , the CPU becomes FULL

[mendrika13]

Hello,

We have got some problem in our router (a 1841, IOS Version 12.4(15)T12),

I activated the command "debug ip packet" (to observ nat translation) then the cpu became full (100%) and I wasn't able to reach the management IP of it.

After restarting the router, I can reach it BUT the cpu still in very high average 80-100% and we have loss some packets.

What should we do to decrease the CPU utilisation?

How can I be sure that the debug ip packet is off ? (I tried the command "show debugging {condition} {all}" but no result)

Thank you

[chris noon]

Use the command:

# undebug all  

This will turn off all debugging 

[Ganesh Hariharan]

Hello,

NAT translation debug command is 

debug ip nat

Which would give you the  translations being created on the device as well as packets that are being translated using the NAT translations.

debug ip packet

This debug command essentially shows all the packets that hit the access list for which this command is used. It is also useful for troubleshooting NAT issue but recommended to use with proper ACL to get the actual packet insight.

To stop all debugging.

Just type Undebug all

Hope it Helps

-GI