cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4031
Views
0
Helpful
5
Replies

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

sampusarkar
Level 1
Level 1

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

Arjun

5 Replies 5

Joe Clarke
Cisco Employee
Cisco Employee

Post the full show ver output from this switch.

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: http://www.cisco.com/techsupport
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:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to
export@cisco.com.

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

Regards

Arjun

This looks like CSCeh35980, which is fixed in 12.2(18)SXF12.


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.

Hi Joe,

 

I'm running into a similar issue generating TCP-4-INVALIDTCB: Invalid TCB pointer:

 

%TCP-4-INVALIDTCB: Invalid TCB pointer: 0x112B80C0 -Process= "Tcl Serv - tty705", ipl= 0, pid= 425
-Traceback= 2402F42z 2403106z 2445CE5z 17242DFz 17219D7z 1708471z 1708341z 170A6A4z 1709218z 1980EF0z 19AD1D2z 19AC796z 198B6E5z 198A8D7z 19E0376z 19CD224z

 

https://quickview.cloudapps.cisco.com/quickview/bug/CSCud05458

 

We believe the problem is related to a tcl script we are running on cisco IR829 routers via a kron policy

 

when these error messages pop up the logic check in the tcl script fails.  We are using a tcl script to test our cellular backup link on a time interval to ensure that the cell connection is working and then shuts the link down and sends a log message to our log server.  Any ideas what may be causing this?

 

tcl script below

 

#
#
# Verify Tu23 is not up already.
# Bring up Tu23
# Verify EIGRP comes up on Tu23
# Verify EIGRP is still up on Tu24/25
# Shut Tu23
#
#

set _tu23_pre_neighbor_result [exec "show ip eigrp neighbors | include Tu23" ]

if {[regexp {Tu23} $_tu23_pre_neighbor_result ] == 1 } {

exec "send log 6 Cell Backup Test - SUCCESS"
ios_config "kron occurrence CELL_TEST in 7:0:0 recurring"
break
} else {

ios_config "interface Tu23" "no shutdown"

}

after 30000

set _tu23_neighbor_result [exec "show ip eigrp neighbors | include Tu23" ]

if {[regexp {Tu23} $_tu23_neighbor_result ] == 1 } {

exec "send log 6 Cell Backup Test - SUCCESS"
ios_config "kron occurrence CELL_TEST in 7:0:0 recurring"

} else {

exec "send log 6 Cell Backup Test - FAIL"
ios_config "kron occurrence CELL_TEST in 1:0:0 recurring"
}

after 5000

set _post_default_result [exec "show ip eigrp neighbors | exclude Tu23" ]

if {[regexp {Tu2*} $_post_default_result ] == 1 } {

ios_config "interface Tu23" "shutdown"

} else {

}


show ver
Cisco IOS Software, ir800 Software (ir800-UNIVERSALK9-M), Version 15.7(3)M2, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2018 by Cisco Systems, Inc.
Compiled Wed 28-Mar-18 05:07 by prod_rel_team

sh run | sec kron
kron occurrence CELL_TEST in 7:0:0 recurring
policy-list CELL_TEST
kron occurrence CELL_DEACTIVATE in 30:0:0 recurring
policy-list CELL_DEACTIVATE
kron policy-list CELL_TEST
cli tclsh flash:/scripts/cell_test.tcl
kron policy-list CELL_DEACTIVATE
cli tclsh flash:/scripts/cell_deactivate.tcl

opened a TAC case but they say tcl and eem are not supported by TAC so I thought i would try here

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco