Client sessions won't disappear on server

Hi everybody,

While investigating a network issue, I came across the following on
our TSM server. The situation is that some TSM clients have trouble
with their TCP connections to the TSM server. Sessions are lost and
automatically reopened, and generally have very low throughput. At the
moment, our suspicion lies with the network.

However, on the TSM server, there are two client sessions 'stuck' in
Run-state:

  Sess Comm.  Sess     Wait   Bytes   Bytes Sess  Platform Client Name
Number Method State    Time    Sent   Recvd Type
------ ------ ------ ------ ------- ------- ----- -------- --------------------
 1,687 Tcp/Ip Run      0 S    2.7 K 173.9 K Node  WinNT    TRIASDC1
 2,420 Tcp/Ip Run      0 S      342   1.3 K Node  Linux86  TRIINFRA
 2,815 HTTP   Run      0 S        0       0 Admin WebBrow- JOSKAM
                                                   ser

The first session is in that state for about 35 hours now, and the second
session for about 8 hours. On both clients, no dsmc processes are running.

These sessions were part of a group that were affected by the network
problem described above. Due to those problems, these sessions took
much longer than normal, and extended past the regular backup window.
Because of that, I cancelled all those sessions with "cancel sess <x>".
That worked on all sessions, except those two above. Even now, a "cancel
sess 1687" results in:

ANR0490I Canceling session 1687 for node TRIASDC1 (WinNT) .

... but the session remains. In the log, this appears:

03/21/03 16:31:14     ANR0407I Session 2819 started for administrator JOSKAM
                       (WebBrowser) (HTTP 172.17.0.1(1128)).
03/21/03 16:31:14     ANR2017I Administrator JOSKAM issued command: CANCEL
                       SESSION 1687
03/21/03 16:31:14     ANR0490I Canceling session 1687 for node TRIASDC1 (WinNT)
                       .
03/21/03 16:31:14     ANR0405I Session 2819 ended for administrator JOSKAM
                       (WebBrowser).

Nothing about a failure of the "cancel session" command.



Is this a known phenomenon? Did this happen to anyone else before? Our TSM
server is at 5.1.6.2 (AIX 4.3.3 ML10), the client TRIASDC1 is at 5.1.5.15
(W2K) and TRIINFRA (RedHat Linux AS) is at 4.2.3.3.

Thanks,

--
Jurjen Oskam

PGP Key available at http://www.stupendous.org/