Thanks for the tip. I'll set it in the option file to 63.
Geert
Check out the TSM performance and tuning guide. It has specific
recommendations for all of those types of values. TCPWindowsize should
be
set to 63 on Linux.
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp
Hi all,
We were checking the throughput on our new tsm server (5.3 on suse sles9)
and
I encountered the following in the serveroptions:
TCPWindowsize 64512
The manual states the maximum value is 2048 (which is 2mb).
Should I set it to 2048 in my dsmserv.opt or leave it as is?
Thanks,
Geert
Check out the TSM performance and tuning guide. It has specific
recommendations for all of those types of values. TCPWindowsize should be
set to 63 on Linux.
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/com.ibm.itsmm.doc/sc32-9101-03.htm
== On Tue, 27 Dec 2005 11:03:59 -0600, John Monahan [EMAIL PROTECTED] said:
Check out the TSM performance and tuning guide. It has specific
recommendations for all of those types of values. TCPWindowsize should be
set to 63 on Linux.
Keep in the back of your mind that you might need
we're running AIX 4.3.3 server and clients. server is TSM V4.2.2, clients
are generally 4.2 as well.
what should we have our tcpwindowsize and tcpbuffsize set to? i know the
suggested size is 64 and 32 respectively, but the book mentions increasing
them if the resources are available. i have
Hi,
here is an excerpt of the knowledge base article
Description of Windows 2000 TCP Features (Q224829).
As I understand, the maximum value IS 64 UNLESS the
RFC1323 option is used. I'm not a network expert, but
why should I set the TCPWINDOWSIZE option to 63?
The receive window size
, 2002 11:42 AM
To: [EMAIL PROTECTED]
Subject: Re: optimising tcpwindowsize and tcpbuffsizes
I refer to our position as on the perf site. that is what I consider
official as those are the recommendations of the perf team based on real
tests. as I wrote in the other post.
I'll quote again:
TCP/IP
Hi,
Does any one know a calculation or method for setting/optimising tcpwindowsize and
tcpbuffsize on Windows 2K machines?
I have currently set them to :
TCPBUFFSIZE 32
TCPWINDOWSIZE61
But am still getting very slow speeds. Named pipes on the server gives me about 13M a
second
Chris,
TCPWINDOWSIZE should be set to 63 on Win2k.
apart from that ,have you tried
TxnGroupMax 256
TxnByteLimit 2097152(for BU direct to LTO or DLT)
TcpNoDelay yes
and maybe you can take an instr_client_detail trace and take a look at the
DataVerb figure, see if it's
]
ABRUECK.DE cc:
Sent by: ADSM: Dist Subject: Re: optimising
tcpwindowsize and tcpbuffsizes
Stor Manager
[EMAIL PROTECTED]
10/07/2002 12:41
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gianluca Mariani1
TCPWINDOWSIZE should be set to 63 on Win2k.
Cordiali saluti
Gianluca Mariani
Tivoli TSM Global Response Team, Roma
You need to check your documentation. Windows 2K machines should have
TCPWINDOWSIZE set
Hi,
TCPWINDOWSIZE should be set to 63 on Win2k.
No, that's the recommendation for WinNT4. The maximum
value for Win2k is 64 (see the MS knowledge base article
Q224829).
After we set the values for TCPWINDOWSIZE to 64 and the
TCPBUFFSIZE to 512 the throughput of our Win2k clients
has been
I refer to our position as on the perf site. that is what I consider
official as those are the recommendations of the perf team based on real
tests. as I wrote in the other post.
I'll quote again:
TCP/IP Window Size
Use the Tivoli Storage Manager option TcpWindowSize 63 on both the Tivoli
Hi i am wondering about TCPWINDOWSIZE, regarding perfomance tuning.
This senario has WINNT TSM Server
Tivoli Recomends this option in dsmserv.opt
TCPWINDOWSIZE 2048
But the info cleary sates that only WIN2K has the option to have so large
window.
WIN2K 1-2048
WIN9X,NT,ME
To: [EMAIL PROTECTED]
Subject: TCPWINDOWSIZE
Hi i am wondering about TCPWINDOWSIZE, regarding perfomance tuning.
This senario has WINNT TSM Server
Tivoli Recomends this option in dsmserv.opt
TCPWINDOWSIZE 2048
But the info cleary sates that only WIN2K has the option to have so
:02
To: [EMAIL PROTECTED]
Subject: Re: TCPWINDOWSIZE
Petur,
If you set the windowsize to 2048 TSM defaults to 63. We upgraded recently
from ADSM 3.1 where our window size was 64. We left this setting in our
option file for TSM, but in the error log, it was saying the size was too
big
-
Von: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 13. Dezember 2001 01:57
An: [EMAIL PROTECTED]
Betreff: Re: Question Regarding TCPWindowsize on W2K
That was the limit on NT 4.0. With W2K I usually set it to 128.
--
Joshua S. Bassi
Independent IT Consultant
My Win2k servers have the following parameters and it works !!!
TCPBUFFSIZE 512 * max allowed
TXNBytelimit 10240* KB (= 2 GB)
TCPWindowSize 2048 * max W2K:2048, max NT4:63
rv
Steven Chaba [EMAIL PROTECTED]@VM.MARIST.EDU on 12/12/2001 05:19:23
PM
Please respond
To my knowledge 63 is the limit.
-Original Message-
From: Steven Chaba [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 12, 2001 11:19 AM
To: [EMAIL PROTECTED]
Subject: Question Regarding TCPWindowsize on W2K
From one of my WinTel gurus:
- Forwarded by Steven Chaba/RGE on 12
: please post to ADSM.org
I run TSM 4.1 on an AIX server with NT and 2000 clients.
I have a question regarding TCPWindowSize on Windows 2000 Server.
I was advised to set this parameter to 128 on Windows 2000 machines.
When I do that, this shows up in the dsmerror.log:
The TCP window size 128K
connection speed when you are using your home PC and those internet
speed enhancers.
-Original Message-
From: Seay, Paul [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 12, 2001 11:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Question Regarding TCPWindowsize on W2K
To my knowledge 63
I am using the same settings for TCPBUFFSIZE and TCPWindowSize and it works
for me too.
Although, this is what I see in a sniffer capture (Ethereal) during a backup
(Win2k server):
TSM Server -- TSM Client TCP window size is 17162
TSM Client -- TSM Server TCP window
:[EMAIL PROTECTED]] On Behalf Of
Seay, Paul
Sent: Wednesday, December 12, 2001 8:35 AM
To: [EMAIL PROTECTED]
Subject: Re: Question Regarding TCPWindowsize on W2K
To my knowledge 63 is the limit.
-Original Message-
From: Steven Chaba [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 12
expecting it to work.
I have not actually done this but there are many references to changing
the TCP windowsize in W2k for larger packet size networks. My suggestion
is to go to google and search for windows 2000 tcpwindowsize rfc1323.
There are microsoft knowledgebase articles discussing
Hi Ruud,
in ADSM V3 tcpwindowsize must be indicated in KB boundary.
I don't know if this is still valid ...
Best regards
Valeriano Bassi [EMAIL PROTECTED]
"Van Ruler, Ruud R SSI-ISES-32" [EMAIL PROTECTED] on 15/01/2001
17.09.12
Please respond to "ADSM: Dist Stor
Hi,
From memory, I do not think that TCPWINDOWSIZE can be specified for an OS390
server,
This sort of parameter is handled elsewher in the OS390 system.
TCPNODELAY is a client option
"Van Ruler, Ruud R SSI-ISES-32" [EMAIL PROTECTED] on 01/15/2001
04:09:12 PM
Please respond to &
Lg
In TSM reference the following is stated:
"To improve backup performance, increase the TCPWINDOWSIZE on the server."
We have installed TSM4.1 Level0.0 on a S/390 Server. But during startup we
get the following messages:
ANR0902W Unsupported keyword found in file dsmserv.opt
Shouldn't that be in dsm.opt ?
about it? Changing the value of
TCPWINDOWSIZE in DSM.SYS has no affect.
Since you did not mention your operating system, *sm level ( which is not
needed in this case : ), we can not help you :)
Ok. Since I have seen this... I assume it is AIX, and I assume you did not
change your default network
Some of my clients get this message:
16.10.2000 16:30:21 TcpOpen(): Warning. The TCP window size defined to ADSM is
not supported by your
system.
It will be to set default size - 131070
What does it mean and what can I do about it? Changing the value of
TCPWINDOWSIZE in DSM.SYS has
Using the above, supported client(s), coded TCPWINDOWSIZE 128 in DSM.SYS.
It complains that a TCPWINDOWSIZE of 131072 is invalid and is defaulting to
131070
Went through ADSM.ORG archives and saw some references to TCPWINDOWSIZE and
other UNIX platforms. There were suggestions to code
It complains that a TCPWINDOWSIZE of 131072 is invalid and is defaulting to
131070
In the B/A client manual on the option:
Note: Depending on the operating system communication settings, your
system might not accept all values in the range of values.
That is, the value
32 matches
Mail list logo
