ADSM-L

Re: ANS1017E on NT 4.0 - TSM 5.1.5.2

2003-03-31 11:24:14
Subject: Re: ANS1017E on NT 4.0 - TSM 5.1.5.2
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 31 Mar 2003 09:23:35 -0700
I don't know why this is happening, but as the messages suggest, it is
probably a network-related issue. Since your note suggests that other
clients ran successfully, can we assume that the TSM server is up and
running?

Some other things to try:

1) From an OS prompt, change into the directory where the TSM executables
are located (i.e. C:\Program Files\Tivoli\TSM\baclient), then try this:

   dsmc q se

Can a session be established? If not, check your dsm.opt file. What is the
TCPSERVERADDRESS set to? Can you ping that address?

2) If the above test works, veryify the dsm.opt file that is being used by
the scheduler service:


   dsmcutil list
   dsmcutil query /name:tsmservicename

where "tsmservicename" is the name of the TSM scheduler service as
reported by the "dsmcutil list" command.

What options file does the "dsmcutil query" command show? If different
than the one from test #1 above, then retry test #1 but point to the
scheduler service options file:

   dsmc q se -optfile=optfilename

where "optfilename" is the options file used by the scheduler service.

Can a session be established? If not what is the TCPSERVERADDRESS in the
scheduler service options file? Can you ping that address?

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Kelli Jones <JONESK AT CO.CHESTERFIELD.VA DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/31/2003 08:43
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        ANS1017E on NT 4.0 - TSM 5.1.5.2



Backups for one of our NT 4.0 servers running TSM 5 Release 1 Level 5.2
(Server running 5.1.6.0 on AIX 5) missed this weekend...after stopping and
restarting the service,  the same ANS1017E message is reported in the log
and a session cannot be established...

Here is a part of the log from before it happened.

03/29/2003 01:02:58 --- SCHEDULEREC STATUS BEGIN
03/29/2003 01:02:58 Total number of objects inspected:   59,688
03/29/2003 01:02:58 Total number of objects backed up:      121
03/29/2003 01:02:58 Total number of objects updated:          0
03/29/2003 01:02:58 Total number of objects rebound:          0
03/29/2003 01:02:58 Total number of objects deleted:          0
03/29/2003 01:02:58 Total number of objects expired:          0
03/29/2003 01:02:58 Total number of objects failed:           0
03/29/2003 01:02:58 Total number of bytes transferred: 369.16 MB
03/29/2003 01:02:58 Data transfer time:                   37.75 sec
03/29/2003 01:02:58 Network data transfer rate:        10,011.59 KB/sec
03/29/2003 01:02:58 Aggregate data transfer rate:      2,060.09 KB/sec
03/29/2003 01:02:58 Objects compressed by:                    0%
03/29/2003 01:02:58 Elapsed processing time:           00:03:03
03/29/2003 01:02:58 --- SCHEDULEREC STATUS END
03/29/2003 01:02:58 --- SCHEDULEREC OBJECT END CDISBATCH_SCH 03/29/2003
01:00:00
03/29/2003 01:02:58 Scheduled event 'CDISBATCH_SCH' completed
successfully.
03/29/2003 01:02:58 Sending results for scheduled event 'CDISBATCH_SCH'.
03/29/2003 01:02:58 Results sent to server for scheduled event
'CDISBATCH_SCH'.

03/29/2003 01:02:58 ANS1483I Schedule log pruning started.
03/29/2003 01:02:58 Schedule Log Prune: 3233 lines processed.  273 lines
pruned.
03/29/2003 01:02:58 ANS1484I Schedule log pruning finished successfully.
03/29/2003 01:02:58 Querying server for next scheduled event.
03/29/2003 01:02:58 Node Name: CDISBATCH
03/29/2003 01:02:58 ANS1017E Session rejected: TCP/IP connection failure
03/29/2003 01:02:58 Will attempt to get schedule from server again in 20
minutes.
03/29/2003 01:22:58 Querying server for next scheduled event.
03/29/2003 01:22:58 Node Name: CDISBATCH
03/29/2003 01:22:59 Session established with server ADSM: AIX-RS/6000
03/29/2003 01:22:59   Server Version 5, Release 1, Level 6.0
03/29/2003 01:22:59   Data compression forced off by the server
03/29/2003 01:22:59   Server date/time: 03/29/2003 01:23:39  Last access:
03/29/2003 01:00:34

Then the errors begin:

03/30/2003 00:59:48 The Scheduler is under the control of the TSM
Scheduler Daemon
03/30/2003 00:59:48 Scheduler has been started by Dsmcad.
03/30/2003 00:59:48 Querying server for next scheduled event.
03/30/2003 00:59:48 Node Name: CDISBATCH
03/30/2003 00:59:49 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 00:59:49 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 01:19:49 Querying server for next scheduled event.
03/30/2003 01:19:49 Node Name: CDISBATCH
03/30/2003 01:19:49 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 01:19:49 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 01:39:49 Querying server for next scheduled event.
03/30/2003 01:39:49 Node Name: CDISBATCH
03/30/2003 01:39:50 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 01:39:50 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 01:59:50 Querying server for next scheduled event.
03/30/2003 01:59:50 Node Name: CDISBATCH
03/30/2003 01:59:50 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 01:59:50 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 02:19:50 Querying server for next scheduled event.
03/30/2003 02:19:50 Node Name: CDISBATCH
03/30/2003 02:19:51 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 02:19:51 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 02:39:51 Querying server for next scheduled event.
03/30/2003 02:39:51 Node Name: CDISBATCH
03/30/2003 02:39:51 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 02:39:51 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 02:59:51 Querying server for next scheduled event.
03/30/2003 02:59:51 Node Name: CDISBATCH
03/30/2003 02:59:52 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 02:59:52 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 03:19:52 Querying server for next scheduled event.
03/30/2003 03:19:52 Node Name: CDISBATCH
03/30/2003 03:19:52 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 03:19:52 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 03:39:52 Querying server for next scheduled event.
03/30/2003 03:39:52 Node Name: CDISBATCH
03/30/2003 03:39:53 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 03:39:53 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 03:59:53 Querying server for next scheduled event.
03/30/2003 03:59:53 Node Name: CDISBATCH
03/30/2003 03:59:54 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 03:59:54 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 04:19:54 Querying server for next scheduled event.
03/30/2003 04:19:54 Node Name: CDISBATCH
03/30/2003 04:19:54 ANS1017E Session rejected: TCP/IP connection failure
03/30/2003 04:19:54 Will attempt to get schedule from server again in 20
minutes.
03/30/2003 04:39:54 Querying server for next scheduled event.
03/30/2003 04:39:54 Node Name: CDISBATCH

Then after stopping/restarting service:

Restarted Service:

03/31/2003 09:01:00 The Scheduler is under the control of the TSM
Scheduler Daemon
03/31/2003 09:01:00 Scheduler has been started by Dsmcad.
03/31/2003 09:01:00 Querying server for next scheduled event.
03/31/2003 09:01:00 Node Name: CDISBATCH
03/31/2003 09:01:00 ANS1017E Session rejected: TCP/IP connection failure
03/31/2003 09:01:00 Will attempt to get schedule from server again in 20
minutes.

Restarted Service:

03/31/2003 09:15:06 The Scheduler is under the control of the TSM
Scheduler Daemon
03/31/2003 09:15:06 Scheduler has been started by Dsmcad.
03/31/2003 09:15:06 Querying server for next scheduled event.
03/31/2003 09:15:06 Node Name: CDISBATCH
03/31/2003 09:15:07 ANS1017E Session rejected: TCP/IP connection failure
03/31/2003 09:15:07 Will attempt to get schedule from server again in 20
minutes.

Any ideas on why this is happening?  This appears to be totally out of the
blue....

Thanks,
K. Jones
jonesk AT chesterfield DOT gov
804-748-1951
Chesterfield County, Va

<Prev in Thread] Current Thread [Next in Thread>