I agree on adding the actual IP address for the TCPCLIENTADDRESS option.
This is necessary in machines with more than one network card as well.  I
usually query the activity log and search for the node to see what IP it's
actually using to connect to the TSM server.  Then I ask the administrator
to use that IP in their dsm.sys.

Also, if you are connecting over firewalls, ports 1500 and 1501 must be
open bi-directional for communication to take place.

Greg A. Garrison
Account Storage Manager
IBM Global Services, Service Delivery Center - West
9022 S. Rita Road, Rm 2785, Tucson, AZ 85744
Phone (520) 799-5429  Internal 321-5429
Pager 800-946-4646 PIN 6034139
e-mail: [EMAIL PROTECTED]



                      "Garrison, Tony"
                      <Anthony.Garrison        To:       [EMAIL PROTECTED]
                      @USAA.COM>               cc:
                      Sent by: "ADSM:          Subject:  Re: ANR2716E Schedule 
prompter was not able to contact client...W HY?
                      Dist Stor
                      Manager"
                      <[EMAIL PROTECTED]
                      .EDU>


                      07/08/2002 12:25
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"





I have had this problem with several servers.  I solved the problem on
several by utilizing the IP address in the dsm.opt as the TCPCLIENTADDRESS
instead of the node name.


Tony Garrison
I/T Sr. Systems Programmer
USAA
210-913-9836



-----Original Message-----
From: Villegas, Beatrice [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 08, 2002 1:59 PM
To: [EMAIL PROTECTED]
Subject: ANR2716E Schedule prompter was not able to contact
client...WHY?


Hi all,

We are running into an issue with several of our AIX servers. Every 1 to 2
days, one of the client servers incremental backup is "missed" or fails
because of:

ANR2716E Schedule prompter was not able to contact client SY using type 1
(10.160.97.213 1501).

I have checked all the obvious:

1.  dsmc sched is running.
2. There are no apparent network problems.

It seems to me that the process: dsmc sched just hangs.
Once I kill it and re-start it, the backup runs fine.

These are my levels: Server: AIX 4.3.3 ML10 TSM 4.2.1.7
                           Client: AIX 4.3.3 ML8 TSM Client 4.2.0.0

Anyone has any ideas of what could be wrong? Is this a known problem?

Thanks in advance,

Beatriz

Reply via email to