Cat6500:%TCP-2-INVALIDTCB: Invalid TCB pointer

Unanswered Question
Dec 28th, 2009

Hello :

   I have one Cat6513 switch which has crashed recently with the following error msgs;

Dec  3 16:58:05.597: %TCP-2-INVALIDTCB: Invalid TCB pointer: 0x51781B10
-Process= "SSH Process", ipl= 0, pid= 46
-Traceback= 409F8B88 409FC394 409FC7A0 40A00864 40A01E48 4043D57C 4043CCB4 40A062C4 40A064E0 4190718C 4045F948 41054C6C 4046DE2C 41217B70 412183D4 4103C8DC
Dec  3 16:58:05.601: %TCP-2-INVALIDTCB: Invalid TCB pointer: 0x517F7F70
-Process= "*Sched*", ipl= 0
-Traceback= 409F71E0

The switch is running IOS : 12.2(18)SXF11 and it is safe harbor certified. It looks to me an IOS bug. Does anyone know about any

known defect in this version.

Best Regards


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
sampusarkar Mon, 12/28/2009 - 11:45

Hello Joe :

------------------ show version ------------------

Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF11, RELEASE SOFTWARE (fc1)
Technical Support:
Copyright (c) 1986-2007 by cisco Systems, Inc.
Compiled Fri 14-Sep-07 21:50 by kellythw
Image text-base: 0x40101040, data-base: 0x42DBB870

ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF11, RELEASE SOFTWARE (fc1)

6500-Aix-nominal uptime is 2 weeks, 5 days, 21 hours, 41 minutes
Time since 6500-Aix-nominal switched to active is 2 weeks, 5 days, 21 hours, 40 minutes
System returned to ROM by  power cycle at 16:58:49 MET Thu Dec 3 2009 (SP by power on)
System restarted at 17:01:29 MET Thu Dec 3 2009
System image file is "disk0:s72033-ipservicesk9_wan-mz.122-18.SXF11.bin"

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

If you require further assistance please contact us by sending email to
[email protected].

cisco WS-C6513 (R7000) processor (revision 1.0) with 458720K/65536K bytes of memory.
Processor board ID SAL09232JXN
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
65 Virtual Ethernet/IEEE 802.3 interfaces
152 Gigabit Ethernet/IEEE 802.3 interfaces
1 Ten Gigabit Ethernet/IEEE 802.3 interface
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102



Joe Clarke Mon, 12/28/2009 - 12:23

Sorry, I pasted the wrong info.  While that bug is possible given your version of code, the more likely candidate is CSCsv66827 which is fixed in 12.2(18)SXF16.  This bug relates to clearing an SSH session from a VTY.

However, it would be a good idea to contact TAC to have them more thoroughly analyze the crashinfo file.


This Discussion