Hi Richard,

In the past we had multiple TSM server instances per box. This lead to
TCPPORT numbers starting at 1500, and going up by 5.

Locally, TCPADMINPORT is left to the default (which is to use the value of
TCPPORT). It is hard to argue that the default isn't good practice.

Thanks,
[RC]





From:
Richard Sims <rbs AT BU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
02/16/2011 05:18 AM
Subject:
Re: [ADSM-L] SQLLiteSpeed backups hanging when moved to TSM server on
RHEL5.
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



On Feb 15, 2011, at 5:06 PM, Robert Clark wrote:

> 16:01:18.507558 IP 192.168.1.116.1505 > 10.1.1.235.2735: F 2235:2235(0)
> ack 38543 win 61320

Robert -

One thing I'd check into is port definitions for the TSM server and what
the client is configured to think it should be accessing at the server. In
the tcpdump, it shows port 1505 for the server: that's commonly the
TCPADMINPort number, whereas the server port for backup/archive client
access (TCPPort) is conventionally 1500. Just something to check out in
your site configs.

    Richard Sims



U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



---------------------------------------------------------------------