cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
29235
Views
31
Helpful
3
Replies

What are traceback logs?

Pradeep H A
Level 1
Level 1

I just want to know generally when are traceback logs generated on a router? does it mean the router would crash soon or IOS has hit a bug?

1 Accepted Solution

Accepted Solutions

David White
Cisco Employee
Cisco Employee

Hi Pradeep,

Unfortunately, there is no 'easy' or 'consistant' answer here.  Syslog messages which contain Tracebacks are a way of providing additional information to developers about what was on the processes stack at the time the syslog was generated.  This can be printed because an unknown condition was detected, or data corruption was detected, or for many other reasons.  In many cases, this does not mean the device will crash.  However, in some cases, the device may crash sortly after.  You really need to look as the message generated and see what it says.

Ideally, the tracebacks were intented to be printed when a 'problem' was detected, and they provided further information to analyze that problem.  However, as time went on, they have been more widely used for other contexts as a way of just providing more information/context to many syslogs.  Some are completely benign, or just descriptive messages with zero impact to the device.

Hope it helps,

Sincerely,

David.

View solution in original post

3 Replies 3

daniel.dib
Level 7
Level 7

From http://www.cisco.com/networkers/nw01/pres/pr/ps_presos/PS_540_5DUNN_C1.pdf

Stack trace vs.—Traceback

Same thing—a stack of functions that were

executing when we found an error—sh stack

displays stack that was saved at time of crash

Tracebacks routinely used to report stack

trace when a message needs to be reported—

not indicative of crash in this case

And from http://www.cisco.com/web/applicat/errmess/emd_help.html

Traceback Messages

You may also receive traceback messages on a device. These take the following format:

Traceback= 60A6CA64 60A6CBA4 60A6220C 6099C498 605D3CCC 605D3CB8.

Note: These messages may accompany other messages.

The Cisco Output Interpreter tool mentioned above can also assist you with decoding the traceback messages.

The Cisco Output Interpreter can be used to decode them:

https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl

Daniel Dib
CCIE #37149

Please rate helpful posts.

Daniel Dib
CCIE #37149
CCDE #20160011

Please rate helpful posts.

David White
Cisco Employee
Cisco Employee

Hi Pradeep,

Unfortunately, there is no 'easy' or 'consistant' answer here.  Syslog messages which contain Tracebacks are a way of providing additional information to developers about what was on the processes stack at the time the syslog was generated.  This can be printed because an unknown condition was detected, or data corruption was detected, or for many other reasons.  In many cases, this does not mean the device will crash.  However, in some cases, the device may crash sortly after.  You really need to look as the message generated and see what it says.

Ideally, the tracebacks were intented to be printed when a 'problem' was detected, and they provided further information to analyze that problem.  However, as time went on, they have been more widely used for other contexts as a way of just providing more information/context to many syslogs.  Some are completely benign, or just descriptive messages with zero impact to the device.

Hope it helps,

Sincerely,

David.

Heyy David, how do i disable those traceback logs from my switch/router let's say on top of GNS3 tool. They keep flooding my cli and i'm unable to preperly execute the commands. Help me out