ADSM-L

Re: ANR2716E Schedule prompter was not able to contact client

2006-11-16 21:36:29
Subject: Re: ANR2716E Schedule prompter was not able to contact client
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 16 Nov 2006 21:35:12 -0500
On Nov 16, 2006, at 9:15 PM, zareyna wrote:

Hi Dirk,

I have changed one of the clients to POLLING mode and the backup is
in the
pending state. There is no error stated in dsmerror.log.

For the port, there is no port listen on 1501 but when using the
backup
running on PROMPTED mode it will generate "11/16/2006 02:00:22
ANR2716E
Schedule prompter was not able to contact client PRDATMA using type 1
(10.200.209.11 1503). (SESSION: 82)".
Does it listen to port 1503 instead of 1501?

SErvername              TSM-213-18_SERVER1
COMMMethod              TCPip
TCPPort                 1500
TCPServeraddress        10.200.213.18
tcpclientaddress        10.200.209.11
Nodename                prdatma

passwordaccess          generate
schedmode               polling
tcpclientport           1501

If the Schedmode is Polling, there will not be a latent 1501 port
open; if Prompted, there will be a 1501 port listening. This can be
verified with the lsof command. At a minimum, use the ps command to
verify that the scheduler is running - and whether you are using
that, and not dsmcad. You can also use the telnet command, as
illustrated in ADSM QuickFacts, to verify the ability to connect. If
you can't, then a firewall may be preventing it. (You are using a
private, non-routed subnet there, which always tends to suggests
restrictions.) Also see the QuickFacts - and, authoritatively, the
TSM Problem Determination Guide - in pursuing scheduler problems.
Make sure no Restartable Restore is pending, which will block other
activities.

   Richard Sims