Some Router Errors

Unanswered Question
Apr 28th, 2009
User Badges:

I have 2811 router and i am receiving the following errors:

%SYS-2-INTSCHED: 'suspend' at level 3 -Process= "Exec", ipl= 3, pid= 168, -Trac

eback= 0x4167DBF0 0x40064070 0x42CF8DEC 0x43386F50 0x43387004 0x41E98D10 0x41E99

C7C 0x43386F04 0x43387004 0x41E90A04


000852: *Apr 27 07:34:47.819 UTC: %IP_VFR-4-FRAG_TABLE_OVERFLOW: Dialer1: the fr

agment table has reached its maximum threshold 16


001634: *Apr 27 11:01:47.391 UTC: %SYS-3-LOGGER_FLUSHING: System pausing to ensu

re console debugging output.


%SCHED-7-WATCH: Attempt to enqueue uninitializ

ed watched queue (address 0). -Process= "Exec", ipl= 0, pid= 3, -Traceback= 0x4

167DBF0 0x42CFE17C 0x42A1EFDC 0x42A5D5E4


any help on the above issues will be highly appreciated.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joseph W. Doherty Tue, 04/28/2009 - 04:13
User Badges:
  • Super Bronze, 10000 points or more

The Tracebacks might indicate a software defect. You could either present them to TAC or perhaps first try a different IOS release or version.

johnlloyd_13 Tue, 04/28/2009 - 04:16
User Badges:
  • Blue, 1500 points or more

According to Cisco.com's online error message decoder tool (http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi):


%IP_VFR-4-FRAG_TABLE_OVERFLOW: [chars]: the fragment table has reached its maximum threshold [dec]

The number of datagrams being reassembled at any one time has reached it maximum limit.


Recommended Action: Increase the maximum number of datagrams that can be reassembled by entering the ip virtual-reassembly max-reassemblies number command, with number being the maximum number of datagrams that can be reassembled at any one time.


Related documents- No specific documents apply to this error message.



%SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.

Debugging or informational messages are being generated faster than they can be displayed on the console. To ensure that the messages could be seen, the rest of the system has been paused until the console output catches up. This condition might cause an interruption in time-critical operations (for example, maintaining an ISDN link).


Recommended Action: To reduce the number of debugging or informational messages that are displayed, use conditional debugging and turn off console logging. Enter the no logging console guaranteed command, or turn off link-state messages for some other interfaces.



%SCHED-7-WATCH: Attempt to [chars] uninitialized watched [chars] (address [hex]).

A process can register to be notified when various events occur. An attempt was made to register for an event without first creating the data structure for that event.


Recommended Action: If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.


Related documents- No specific documents apply to this error message.


%SCHED-7-WATCH: Attempt to [chars] uninitialized watched [chars] (address [hex]).


A processes can register to be notified when various events occur. This message indicates that an attempt was made to register for an event without first creating the data structure for that event.


Recommended Action: If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at

http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at

http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.


Related documents- No specific documents apply to this error message.


Actions

This Discussion