3Com 3031 Command Reference Manual page 442

442 C 5: N P
HAPTER ETWORK ROTOCOL
Description
Using the debugging tcp event command, you can enable TCP events debugging.
And using the undo debugging tcp event command, you can disable TCP events
debugging.
There is limitation for the number of debugging switches enabled, that is, only a
fixed number of debugging switches can be enabled at one time (combination of
task ID and socket ID). In addition, when TCP is enabled to receive connection
request reactively, a new socket will be created to establish that connection, and
some programs will create a new task to process the connection, like Telnet server.
So to view information about connection, such parameters as task_id and
socket_id cannot be used for filtering.
Example
Enable debugging of TCP events.
<3Com> debugging tcp event
*0.630270-SOCKET-8-TCP EVENT:
1043494683: task = Co0(2), socketid = 0,
TCPCB 0x02c6fd74 created
*0.630270-SOCKET-8-TCP EVENT:
1043494683: task = Co0(2), socketid = 1,
state CLOSED changed to SYN_SENT
*0.630270-SOCKET-8-TCP EVENT:
1043494683: task = Co0(2), socketid = 1,
sending SYN, seq = 74249530,
LA = 127.0.0.1:1025, FA = 1.1.1.1:23
*0.630270-SOCKET-8-TCP EVENT:
1043494683: task = Co0(2), socketid = 1,
advertising MSS = 512,
LA = 127.0.0.1:1025, FA = 1.1.1.1:23
*0.630270-SOCKET-8-TCP EVENT:
1043494683: task = VTYD(9), socketid = 0,
received MSS = 512,
LA = 1.1.1.1:23, FA = 127.0.0.1:1025
*0.50959090-SOCKET-8-TCP EVENT:
733759463: sending RST to 2.2.2.1:11022
*0.1293330-SOCKET-8-TCP EVENT:
1043495346: task = Co0(2), socketid = 1,
connection refused because remote sent RST!
LA = 1.1.1.1:1026, FA = 1.1.1.2:21
<3Com> display debugging
TCP:
TCP event debugging is on for task any socket any
debugging tcp md5 Syntax
debugging tcp md5
undo debugging tcp md5