sh log error

Unanswered Question
Mar 19th, 2009

Mar 17 17:24:10.053: %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x61E82888

--More-- -Process= "<interrupt level>", ipl= 1

-Traceback= 6046BCBC 6046D100 608C73C0 608C5A44 6001E290 60135410 60135560 6036B0F0 6036B494

can any one help w/ this .. this is cisco 3660

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
lamav Thu, 03/19/2009 - 09:36

I would open a TAC case with Cisco. I always do with traceback errors. They usually have their roots in IOS bugs.

Ran the error code tool on Cisco CCO.

1. %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: [hex]

This message occurs when the TCP driver code accesses the TCP encap structure, which is already freed elsewhere in the code.

Recommended Action: If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.

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

cisco steps Thu, 03/19/2009 - 09:40

yah !! thanks lamav, I did open a case w/ Tac.. I was just wondering if anyone incounter this one in the past and have a quick work around

lamav Thu, 03/19/2009 - 09:41

According to the output I sent you, there is no quick work around. :-)

Actions

This Discussion