Hi Stefan! Thanks for your reply! net.ipv4.tcp_window_scaling = 1 seems to be the default on Linux, I checked on the host and it is already set to 1... So indeed there must be another parameter which limits the size to 224 apparently, but I cannot find any clear instruction on where these limits are set... Kind regards, Eric van Loon Air France/KLM Storage Engineering
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Stefan Folkerts Sent: donderdag 6 juli 2017 9:13 To: ADSM-L@VM.MARIST.EDU Subject: Re: Best Practices/Best Performance SP/TSM B/A Client Settings ? Hi Eric, I think some Linux sysctl tuning might be required to raise the Linux OS tcp window limit from 224. with scaling the system can adjust it if needed, that might work for the TSM client as well. net.ipv4.tcp_window_scaling = 1 Regards, Stefan On Wed, Jul 5, 2017 at 4:30 PM, Loon, Eric van (ITOPT3) - KLM < eric-van.l...@klm.com> wrote: > Hi Del! > Because of your mail down below I implemented TCPWINDOWSIZE 512 on the > (LINUX) clients on our new TSM server with a directory containerpool, > but the client logs are now filled with the following messages: > > ANS5246W TCPWINDOWSIZE 512 is specified, but exceeds the maximum value > allowed by the operating system. TCPWINDOWSIZE 244 will be used instead. > > What is you recommendation, from a performance perspective, in this > situation? > Thanks again for your help! > Kind regards, > Eric van Loon > Air France/KLM Storage Engineering > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf > Of Del Hoobler > Sent: dinsdag 21 maart 2017 2:11 > To: ADSM-L@VM.MARIST.EDU > Subject: Re: Best Practices/Best Performance SP/TSM B/A Client Settings ? > > Hi Ben, > > Here are some items to get you started: > > > Backup-Archive client with limited, high latency network (WAN backups): > =============================== > TCPWINDOWSIZE 512 > RESOURCEUTILIZATION 4 > COMPRESSION Yes > DEDUPLICATION Yes > ENABLEDEDUPCACHE Yes > > Tip: Do not use the client deduplication caching for applications > that use the IBM Spectrum Protect API. Refer to section 1.2.3.2.1 for > additional details. > > > Backup/Archive client or Client API with limited network (Gigabit LAN > backups): > =============================== > TCPWINDOWSIZE 512 > RESOURCEUTILIZATION 10 > COMPRESSION Yes > DEDUPLICATION Yes > ENABLEDEDUPCACHE No > > > Backup/Archive client or Client API with high speed network (10 > Gigabit + LAN backups) =============================== > TCPWINDOWSIZE 512 > RESOURCEUTILIZATION 10 > COMPRESSION No > DEDUPLICATION No > ENABLEDEDUPCACHE No > > > Tip: For optimal data reduction, avoid the following client option > combination: > > COMPRESSION Yes > DEDUPLICATION No > > > > > Del > > ---------------------------------------------------- > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 03/15/2017 > 02:39:04 PM: > > > From: "Alford, Ben" <balf...@utk.edu> > > To: ADSM-L@VM.MARIST.EDU > > Date: 03/15/2017 02:39 PM > > Subject: Best Practices/Best Performance SP/TSM B/A Client Settings ? > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > I've looked at the IBM Blueprint documents but may have missed what > > I was looking for - the Best Practices for Best Performance for TSM > > B/A client settings. As we move from 6.4 to 7.x or 8.x clients > > before the 6.4 EOL, we are looking to test with the current client > > settings optimized for things like TCPBUFFSIZE, TCPWINDOWSIZE, > > TXNBYTLIMIT, etc., etc. > > Thanks! > > > > Ben Alford > > IT Manager, Office of Information Technology > > Systems: Shared Services > > > > The University of Tennessee > > > ******************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. 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. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch > Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > ******************************************************** > ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. 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. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************