AH!!! Many thanks to all of you who responded, this is just the information I need!
(Couldn't survive without this list!) -----Original Message----- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Friday, July 11, 2003 1:17 PM To: [EMAIL PROTECTED] Subject: Re: TSM/AIX problem or AIX/TSM problem??!? Yes, do a "man tsm" at AIX prompt. David Longo >>> [EMAIL PROTECTED] 07/11/03 01:12PM >>> Wrong 'tsm'. tsm is the module in AIX (SYSV) that is the login broker (it does getty, and login). The messages below indicate that something is getting a 'password: ' prompt but not typing anything or hitting enter before a timeout value. You are not looking at a TSM (ADSM, WDSF...) problem here, you are looking at a AIX thing. Look to see if you have some type of monitoring set up that trys to log in to the machine at an interval to see if it is responding. bob On Fri, Jul 11, 2003 at 01:02:23PM -0400, Prather, Wanda wrote: > Need some help from you AIX wizards out there. > > I have a new TSM environment; there are 4 p-series servers, all at AIX 5.1 > in 32bit mode. > > One is a dedicated TSM server, with the unimaginative hostname of "TSM". > (OK, so we're not creative - that's why we have the techie jobs...) > > The other 3 servers have hostnames like P6xxxx. > > The TSM server is 5.1.6.3; the TSM clients are all 5.1.6.something. > The P6xxxx severs back up (incremental) to the TSM server nightly, on a > POLLING schedule. > Incrementals are all done by 2am. > The clients contact the server every 8 hours for work (queryschedperiod 8). > >From their dsmsched.log files, everything seems to be working fine. > > Here's the problem: > On each of the P6xxxx hosts, (but not the TSM server), the syslog shows LOTS > of records like the ones below, coming every 20 minutes to an hour apart, > every day. > > It appears that the TSM server is trying to contact them on some sort of > virtual terminal session? > There is no TELNET or FTP scheduled between the servers, and since nothing > is broke, I don't know what to look for to fix. There is no process on any > machine named "TSM". Rebooting the TSM server doesn't stop it. > > Can anybody tell me what these records represent? Thanks! > > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Jul 9 14:07:29 p6xxxx tsm: /dev/pts/31: 3004-031 Password read timed out -- > possible noise on port > Jul 9 14:07:29 p6xxxx tsm: /dev/pts/31: 3004-031 Password read timed out > -- possible noise on port > Jul 9 14:08:20 p6xxxx tsm: /dev/pts/34: 3004-031 Password read timed out > -- possible noise on port > etc > etc ############################################################## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##############################################################
