Hi Ruomiao!
What's in the clients error log at the time of error?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Ruomiao Wang [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 17:45
To: [EMAIL PROTECTED]
Subject: Session lost after upgrade to TSM 3.7.2.17


We upgrade a TSM client from ADSM 3.016 to TSM v. 3.7.2.17. Ever since
the upgrade, the client has been experiencing session lost:

This is from the dsmsched.log:
07/18/2001 08:18:50 TcpRead(): recv(): errno = 10058
07/18/2001 08:18:50 sessRecvVerb: Error -50 from call to 'readRtn'.
07/18/2001 08:18:50 ANS1809E Session is lost; initializing session
reopen procedure.

It seems that the sessions will lose when files larger than 79MB was
being backed up.

This did not happen when we used ADSM 3.1.06.

We modified the dsm.opt during our upgrade to use all-local, instead of
specifying the domains. The current include-exclude file acutally
exclude few files.

The network throughput was also different before and after the
upgrate:

Before upgrade: 07/01/2001 06:44:34 Network data transfer rate:   48.04
KB/sec
07/01/2001 06:44:34 Aggregate data transfer rate:   154.44 KB/sec

After upgrade:

07/13/2001 14:10:02 Network data transfer rate:      28.74 KB/sec
07/13/2001 14:10:02 Aggregate data transfer rate        130.99 KB/sec

Any suggestions ?


**********************************************************************
This e-mail and any attachment may contain confidential and privileged material 
intended for the addressee only. If you are not the addressee, you are notified that 
no part of the e-mail or any attachment may be disclosed, copied or distributed, and 
that any other action related to this e-mail or attachment is strictly prohibited, and 
may be unlawful. If you have received this e-mail by error, please notify the sender 
immediately by return e-mail, and delete this message. Koninklijke Luchtvaart 
Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for 
the incorrect or incomplete transmission of this e-mail or any attachments, nor 
responsible for any delay in receipt.
**********************************************************************

Reply via email to