ADSM-L

Re: [ADSM-L] Odd ANR2716E messages

2017-10-19 03:17:51
Subject: Re: [ADSM-L] Odd ANR2716E messages
From: Dwight Cook <cookde AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 19 Oct 2017 02:16:27 -0500
Well, all that code is out of date but other than that... make sure 
SCHEDMODE PROMPT is in the client's dsm.opt file.
Also if you are running only a scheduler, look at switching over to the 
CAD and letting it drive the scheduler.
If your backup network is set to use jumbo frames (MTU 9000) check to make 
sure this specific client's interface is set for that and not regular 
frames (MTU 1500), a mismatch will allow some traffic but as soon as a 
jumbo frame comes across, it can cause communications to fail.


Dwight E. Cook
Senior Architect
TSM Delivery, IBM Cloud
(918) 493-4678



From:   Thomas Denier <Thomas.Denier AT JEFFERSON DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   10/13/2017 12:25 PM
Subject:        Odd ANR2716E messages
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



One of our Windows client backups has had a minor but very puzzling 
problem on three of the last four days. On each of the three days the 
following sequence of events occurred:

1.The TSM server displayed the message "ANR2716E Schedule prompter was not 
able to contact client TJVDPMHD using type 1" three minutes and ten or 
eleven seconds after the nominal starting time for the backup.
2.The contact attempt was retried successfully thirty seconds after the 
error message.
3.The backup ran successfully and with no further sign of network 
communication issues.

The client system has a network interface dedicated to TSM traffic. This 
interface is on the same subnet as one of the network interfaces on the 
system hosting the TSM server. There are 24 other client systems on the 
subnet. None of the 24 have shown any recent signs of network 
communications issues.

A "query node" command reports that the client system is running 64 bit 
Windows 7 and using TSM 6.2.4.0 client code.

The TSM server code is at level 6.3.5.0 and is running under zSeries 
Linux. I checked the various log files in /var/log and found no sign of 
network errors within the last few days.

Does anyone know of an explanation for the odd combination of consistent 
behavior on a 24 hour time scale and inconsistent behavior on a 30 second 
time scale?

Thomas Denier,
Thomas Jefferson University
The information contained in this transmission contains privileged and 
confidential information. It is intended only for the use of the person 
named above. If you are not the intended recipient, you are hereby 
notified that any review, dissemination, distribution or duplication of 
this communication is strictly prohibited. If you are not the intended 
recipient, please contact the sender by reply email and destroy all copies 
of the original message.

CAUTION: Intended recipients should NOT use email communication for 
emergent or urgent health care matters.

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

ADSM.ORG Privacy and Data Security by KimLaw, PLLC