All,

Thanks for this info.  We'll patch our AIX box and report the results.

I'm curious about one thing though.  If it's an AIX problem, why does shutting 
down the TSM server (not AIX) and restarting it fix the problem?

Mark


--
Mark Ferraretto
Unix Systems Administrator
Deutsche Bank Hong Kong
w: +852 2203 6362        m: +852 9558 8032        f: +852 2203 6971
mark.ferraretto AT db DOT com



                      deehre01@LOUISVIL
                      LE.EDU                   To:       ADSM-L AT VM.MARIST 
DOT EDU
                      Sent by:                 cc:
                      [email protected].        Subject:  Re: TSM Scheduler not 
contacting clients
                      EDU


                      03/10/2003 00:45
                      Please respond to
                      ADSM-L






There was a major bug in Aix 5.1 64 bit mode tcp that caused major
slowdowns in backups.  It was apar IY36925 fixed in bos.net.tcp.client
5.1.0.37.  The receive buffer problem occurred with that fix already in
place.

David Ehresman

>>> r.post AT SARA DOT NL 10/2/2003 12:27:02 PM >>>
On Thu, 2 Oct 2003 09:56:38 -0400
David E Ehresman <deehre01 AT LOUISVILLE DOT EDU> wrote:

Now this makes some bells ring over here. IIRC there was some bug in
the AIX
5.1 TCP code, which in particular would shouw on TSM servers. I don't
know
what it was any more, nor what the fix is (It was just smalltalk with
some
engeneer once). You might want to check the APAR DB....


> I had that problem and it was a aix tcp tuning issue.  Do a
>    netstat -v ent1 | grep "Receive Pool Buffer"
> where ent1 is the adaptor that your tsm traffic runs on.  If your
"No
> Receive Pool Buffer Errors:" line is greater than zero you have the
same
> problem I had.  We raised our receive pool buffer size up to 2048
and
> that fixed our problem.
>
> The ethernet adaptor has to be down to change the setting.  The
command
> is:
>   chdev -l ent"x" -a rxbuf_pool_size=2048
> where x is the adaptor name.
>
> David Ehresman
> University of Louisville
>
>
> >>> mark.ferraretto AT DB DOT COM 10/1/2003 8:21:01 PM >>>
> All,
>
> I am running TSM 5.1.6.1  on AIX 5.1ML3.  In the last few weeks it's
> started exhibiting a rather strange problem where the scheduler
seems
> not to contact the clients to start the backup schedule.
>
> Halting TSM and restarting it seems to fix it for a few days and
then
> it will start again.
>
> Checking the actlog, I stop seeing 'Schedule prompter contacting...'
> messages.  And, of course, the following day I see a whole stack of
> 'Missed' backups.  Sometimes the prompter may contact one or two (out
of
> about 100) systems before stopping altogether.  We have 100 Nodes -
50
> Unix (Solaris/Linux/AIX) and 50 NT/2000 systems.  All are running
> file-based backups.   We also have a single Notes server (NT) that's
> backed up using TDP.  All are in prompted mode.
>
> I haven't been able to find any error messages in the TSM log.  Just
an
> absence of prompter messages like I said before.
>
> Can anyone help?
>
> Mark
>
>
> --
> Mark Ferraretto
> Unix Systems Administrator
> Deutsche Bank Hong Kong
> w: +852 2203 6362        m: +852 9558 8032        f: +852 2203 6971
> mark.ferraretto AT db DOT com
>
>
> --
>
> This e-mail may contain confidential and/or privileged information.
If
> you are not the intended recipient (or have received this e-mail in
> error) please notify the sender immediately and destroy this e-mail.
Any
> unauthorized copying, disclosure or distribution of the material in
this
> e-mail is strictly forbidden.


--
Met vriendelijke groeten,

Remco Post

SARA - Reken- en Netwerkdiensten
http://www.sara.nl
High Performance Computing  Tel. +31 20 592 8008    Fax. +31 20 668
3167

"I really didn't foresee the Internet. But then, neither did the
computer
industry. Not that that tells us very much of course - the computer
industry
didn't even foresee that the century was going to end." -- Douglas
Adams





--

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden.