7206VXR (NPE-G2) - Reboots

jgitau123 · ‎09-18-2008

I have a 7206VXR (NPE-G2) processor running c7200p-spservicesk9-mz.124-15.T4.bin. Every once in a while at peak hour, i get the following:

.Sep 18 18:07:02: %SYS-3-CPUHOG: Task is running for (2004)msecs, more than (2000)msecs (230/230),process = IP NAT Ager.

-Traceback= 0x1A738CC 0x1A1E620 0x1A47908 0x1A48F10 0x1A10574 0x1A106C0 0x1A107E8 0x2804F3C 0x28050BC 0x1A10EBC 0x717158

.Sep 18 18:07:04: %SYS-3-CPUHOG: Task is running for (4004)msecs, more than (2000)msecs (230/230),process = IP NAT Ager.

-Traceback= 0x1A73728 0x1A1E614 0x1A47908 0x1A48F10 0x1A10574 0x1A106C0 0x1A107E8 0x2804F3C 0x28050BC 0x1A10EBC 0x717158

Is there a command that limits the amount of time a single process can 'hold' the routers CPU? This is referenced to a bug CSCee51764. We do have lots of fragmented packets which could cause NAT to get overloadedâ€¦â€¦.my concern right now is to ensure that the process doesn't kill the whole router.

Giuseppe Larosa · ‎09-18-2008

Hello,

see

scheduler allocate

To guarantee CPU time for processes, use the scheduler allocate command in global configuration mode. To restore the default, use the no form of this command.

scheduler allocate interrupt-time process-time

no scheduler allocate

http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_r1.html#wp1015986

Hope to help

Giuseppe

jgitau123 · ‎09-18-2008

hmm I used the

scheduler process-watchdog terminate .

Im not sure whether the process stops and starts.I'll find out soon enough. If it stops the process completely then a reload is preferred.