Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

dlsw protocol does not work in router 1941.

hello, dlsw protocol router does not work in 1941. enable the temporary license and a% TCP-2-INVALIDTCPENCAPS error occurs. the peer "not connet" and is "DISCONN"

**license boot module c1900 technology-package datak9**

Cisco IOS Software, C1900 Software (C1900-UNIVERSALK9-M), Version 15.4(1)T1, REL
EASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Wed 12-Feb-14 04:27 by prod_rel_team

ROM: System Bootstrap, Version 15.0(1r)M16, RELEASE SOFTWARE (fc1)

ATM9296_PRUEBA uptime is 3 hours, 4 minutes
System returned to ROM by reload at 13:51:38 UTC Tue Jun 24 2014
System image file is "flash0:c1900-universalk9-mz.SPA.154-1.T1.bin"
Last reload type: Normal Reload
Last reload reason: Reload Command

 

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 CISCO1941/K9 (revision 1.0) with 487424K/36864K bytes of memory.
Processor board ID FTX181881BJ
6 Gigabit Ethernet interfaces
1 Serial(sync/async) interface
1 terminal line
1 Virtual Private Network (VPN) Module
DRAM configuration is 64 bits wide with parity disabled.
255K bytes of non-volatile configuration memory.
250880K bytes of ATA System CompactFlash 0 (Read/Write)


License Info:

License UDI:

-------------------------------------------------
Device#   PID                   SN
-------------------------------------------------
*1        CISCO1941/K9          FTX181881BJ

 

Technology Package License Information for Module:'c1900'

------------------------------------------------------------------------
Technology    Technology-package                  Technology-package
              Current              Type           Next reboot
------------------------------------------------------------------------
ipbase        ipbasek9             Permanent      ipbasek9
security      securityk9           Permanent      securityk9
data          datak9               Permanent      datak9
NtwkEss       None                 None           None

Configuration register is 0x2102

*Jun 24 16:24:59.259: %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x2B6
682A4 -Process= "DLSw Background", ipl= 0, pid= 257
-Traceback= 23457A4Cz 2214700Cz 22102014z 261B40F8z 261B4188z 22100B58z 220F9880
z 22111978z 241156A8z 2411568Cz

ATM9296_PRUEBA# sh dl pe
Peers:                state     pkts_rx   pkts_tx  type  drops ckts TCP   uptime
 TCP 167.28.62.9     PCONN_WT         2         2  conf      0    0   -        -
 TCP 167.28.61.214   DISCONN          0         0  conf      0    0   -        -
Total number of connected peers: 0
Total number of connections:     0

ATM9296_PRUEBA#
*Jun 24 16:53:36.183: DLSw: START-TPFSM (peer 167.28.62.9(2065)): event:ADMIN-OP
EN CONNECTION state:DISCONN
*Jun 24 16:53:36.183: DLSw: dtp_action_a() attempting to connect peer 167.28.62.
9(2065)
*Jun 24 16:53:36.183: DLSw: END-TPFSM (peer 167.28.62.9(2065)): state:DISCONN->W
AIT_WR

*Jun 24 16:53:36.183: DLSw: Async Open Callback 167.28.62.9(2065) -> 13087
*Jun 24 16:53:36.183: DLSw: START-TPFSM (peer 167.28.62.9(2065)): event:TCP-WR P
IPE OPENED state:WAIT_WR
*Jun 24 16:53:36.183: DLSw: dtp_action_f() start read open timer for peer 167.28
.62.9(2065)
*Jun 24 16:53:36.183: DLSw: END-TPFSM (peer 167.28.62.9(2065)): state:WAIT_WR->W
AIT_RD

*Jun 24 16:53:36.187: DLSW: dlsw_access_check(): sport=1074 dport=2065 vrf_table
id=0x0 vrf_string =
*Jun 24 16:53:36.187: DLSw: passive open 167.28.62.9(1074) -> 2065
*Jun 24 16:53:36.187: DLSw: START-TPFSM (peer 167.28.62.9(2065)): event:TCP-RD P
IPE OPENED state:WAIT_RD
*Jun 24 16:53:36.187: DLSw: dtp_action_g() read pipe opened for peer 167.28.62.9
(2065)
*Jun 24 16:53:36.187: DLSw: CapExId Msg sent to peer 167.28.62.9(2065)
*Jun 24 16:53:36.187: DLSw: END-TPFSM (peer 167.28.62.9(2065)): state:WAIT_RD->W
AIT_CAP

*Jun 24 16:53:36.187: DLSw: START-TPFSM (peer 167.28.62.9(2065)): event:SSP-CAP
MSG RCVD state:WAIT_CAP
*Jun 24 16:53:36.187: DLSw: dtp_action_j() cap msg rcvd from peer 167.28.62.9(20
65)
*Jun 24 16:53:36.187: DLSw: Recv CapExId Msg from peer 167.28.62.9(2065)
*Jun 24 16:53:36.187: DLSw: Pos CapExResp sent to peer 167.28.62.9(2065)
*Jun 24 16:53:36.187: DLSw: END-TPFSM (peer 167.28.62.9(2065)): state:WAIT_CAP->
WAIT_CAP

*Jun 24 16:53:36.187: DLSw: START-TPFSM (peer 167.28.62.9(2065)): event:SSP-CAP
MSG RCVD state:WAIT_CAP
*Jun 24 16:53:36.187: DLSw: dtp_action_j() cap msg rcvd from peer 167.28.62.9(20
65)
*Jun 24 16:53:36.187: DLSw: Recv CapExPosRsp Msg from peer 167.28.62.9(2065)
*Jun 24 16:53:36.187: DLSw: END-TPFSM (peer 167.28.62.9(2065)): state:WAIT_CAP->
WAIT_CAP

*Jun 24 16:53:36.191: DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev st
ate:WAIT_CAP
*Jun 24 16:53:36.191: DLSw: START-TPFSM (peer 167.28.62.9(2065)): event:SSP-CAP
EXCHANGED state:WAIT_CAP
*Jun 24 16:53:36.191: DLSw: dtp_action_k() cap xchged for peer 167.28.62.9(2065)
*Jun 24 16:53:36.191: DLSw: END-TPFSM (peer 167.28.62.9(2065)): state:WAIT_CAP->
PCONN_WT
no deb all
All possible debugging has been turned off
ATM9296_PRUEBA#
ATM9296_PRUEBA# sh dl pe
Peers:                state     pkts_rx   pkts_tx  type  drops ckts TCP   uptime
 TCP 167.28.62.9     PCONN_WT         2         2  conf      0    0   -        -
 TCP 167.28.61.214   DISCONN          0         0  conf      0    0   -        -
Total number of connected peers: 0
Total number of connections:     0

ATM9296_PRUEBA#
*Jun 24 16:53:51.207: %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x2B6
682A4 -Process= "DLSw Background", ipl= 0, pid= 257
-Traceback= 23457A4Cz 2214700Cz 22102014z 261B40F8z 261B4188z 22100B58z 220F9880
z 22111978z 241156A8z 2411568Cz
*Jun 24 16:53:51.207: %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x2B6
682A4 -Process= "DLSw Background", ipl= 0, pid= 257
-Traceback= 23457A84z 22147024z 22102014z 261B40F8z 261B4188z 22100B58z 220F9880
z 22111978z 241156A8z 2411568Cz
*Jun 24 16:53:51.207: %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x2B6
682A4 -Process= "DLSw Background", ipl= 0, pid= 257
-Traceback= 23457C84z 22103C68z 22103D74z 220F035Cz 2210201Cz 261B40F8z 261B4188
z 22100B58z 220F9880z 22111978z 241156A8z 2411568Cz
*Jun 24 16:53:51.207: %TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x2B6
682A4 -Process= "DLSw Background", ipl= 0, pid= 257
-Traceback= 23457CE4z 22103C7Cz 22103D74z 220F035Cz 2210201Cz 261B40F8z 261B4188
z 22100B58z 220F9880z 22111978z 241156A8z 2411568Cz

 

Everyone's tags (4)
1 REPLY

Hi,There was a caveat for the

Hi,

There was a caveat for the old IOS versions. You can make use of the work around option to solve. But am not sure if the same exist for your IOS version.

CSCdt17920

You may receive the following information every day after upgrading Cisco IOS Release 11.3 to Release 12.0(13):

%TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer:

0x0

-Process= "IP Input", ipl= 0, pid= 12

-Traceback= 60382C2C 60383F14 60A56FF0 60A583F8 60A569E4 60A46840 60A4E58C

60382B78 602EAE00 602ECB84 603233D4 6030BD04 6030A200 6030A2FC 6030A470 6

02973AC

This situation is specific to a data-link switching (DLSw) border peer network. It does not happen in a standard DLSw environment with only configured or promiscuous DLSw peers. There is no workaround.

 

HTH

 

Regards

Karthik

196
Views
0
Helpful
1
Replies
CreatePlease login to create content