Cisco Cisco IOS Software Release 11.0(20)BT Guide De Dépannage
Background Information
The Cisco IOS software scheduler, which is part of the Cisco IOS software Kernel, manages all the processes
in the system using a series of process queues that represent each process state. The queues hold context
information for processes in that state. Processes transition from one state to another as the scheduler moves
their context from one process queue to another. Some of the process queues are:
in the system using a series of process queues that represent each process state. The queues hold context
information for processes in that state. Processes transition from one state to another as the scheduler moves
their context from one process queue to another. Some of the process queues are:
Idle queueContains processes that are still active but wait on an event to occur before they run.
•
Dead queueContains processes that have terminated, but need to have their resources reclaimed
before they can be totally removed from the system.
before they can be totally removed from the system.
•
Ready queuesContains processes that are eligible to run. There are four ready queues, one for each
process priority. When a running process suspends, the scheduler regains control of the CPU and uses
an algorithm to select the next process from one of its four ready queues.
process priority. When a running process suspends, the scheduler regains control of the CPU and uses
an algorithm to select the next process from one of its four ready queues.
•
Troubleshoot
SCHED−3−STUCKMTMR
A process can register to be notified when various events occur in the router. This specific message appears
whenever a registered timer expires and the timer value is unchanged after the process executes two
successive times. This is always a cosmetic software−related issue.
whenever a registered timer expires and the timer value is unchanged after the process executes two
successive times. This is always a cosmetic software−related issue.
These messages on the console indicate such a problem:
%SCHED−3−STUCKMTMR: Sleep with expired managed timer 1C7410,
time 0x1063F9C52 (00:00:00 ago).
−Process= "IP SNMP", ipl= 6, pid= 44
−Traceback= 31BC79A 31BC9C0 323E130
The process in which this error message occurs is a good indication for narrowing down the cause of these
tracebacks. This list shows the more common reasons for these messages to appear:
tracebacks. This list shows the more common reasons for these messages to appear:
IP Simple Network Management Protocol (SNMP) ProcessThis message can appear during
SNMP WriteNet request:
SNMP WriteNet request:
%SCHED−3−STUCKMTMR: Sleep w/expired mgd timer 13AF58,
time 0xBDBE878A (00:00:03 ago).
−Process= "IP SNMP", ipl= 6, pid= 29
−Traceback= 313B218 313B5D2 3192A76 319EFEC 319F234 30FF17E 319F446 319F88E 30FEA70
3304C1E 33045F0 32F78E4 32F82AE 32F383E 32F7ABA 30FF19A
%SYS−4−SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to
146.61.55.230.
%SYS−4−SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to
146.61.10.20.
Earlier Cisco IOS software releases contained some IP SNMP poll−related problems. An upgrade to
the latest Cisco IOS Software Release 12.0 or 12.1 main release solves this issue. This is a cosmetic
message, and there are no adverse side−effects which might affect the operation of the router (or the
IP SNMP process).
the latest Cisco IOS Software Release 12.0 or 12.1 main release solves this issue. This is a cosmetic
message, and there are no adverse side−effects which might affect the operation of the router (or the
IP SNMP process).
•
Virtual Integrated Network Service (VINES) Protocols ProcessThese tracebacks can be
generated on a router configured for VINES:
generated on a router configured for VINES:
%SCHED−3−STUCKMTMR: Sleep w/expired mgd timer 6100606C, time 0x222DF318
(00:00:00 ago).
−Process= "VINES Protocols", ipl= 6, pid= 60
•