thanks, but ...
"upda subscribers" does not exists,
and i did exactly as you said but it doesent work.
thanks again ...
----- Original Message -----
From: "Ben Bullock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 30, 2004 4:25 PM
Subject: Re: SERVER 2 SERVER
I've had this happen before. Here are the notes I jotted down
for the next time it happens:
________________________
Troubleshooting problems.
The servers communicate to eachother through an encrypted password.
Sometimes, if the TSM password is corrupted or if someone pokes around
in the wrong place in the Web GUI, it cross-server communications can
get messed up. Here are the steps to get it working again.
NOTE: This does not work with TSMDMZ1, as the firewall will not pass
this traffic. You must still change your TSM password on the DMZ host
individually.
Log onto MASTER TSMHOST and do a "q server" to see who he "manages".
Check to see if they are still communicating.
q subscriber
On MASTER TSMHOST update the cross-server password to whatever you like
on all the servers on the list.
update server SERVERNAME serverpassword=NEWPASSWORD
Tell all the "managed" servers what MASTER TSMHOST's new password is.
all: update server tsmserv1 serverpassword=NEWPASSWORD
Get the managed servers to try to communicate.
update subscribers
Check in a minute to see if it is now communicating properly.
q subscriber
Additional hints:
One of the most helpful screens when troubleshooting cross-server
communications is found in this help file. Learn it and it will save you
some headaches.
tsm: TSMSERV1A>help ANR0454E
------------------------------------------------------------------------
-------
ANR0454E Session rejected by server server name, reason:
rejection reason.
Explanation: The server has attempted to open a session with the
shown
server. The session was rejected for the indicated reason.
System Action: The operation fails.
User Response: Check both the servers for any additional
messages that might
further describe the reason the session was rejected. For a
reason of
AUTHENTICATION FAILURE, ensure that all passwords have been set
correctly on
both servers. The password for the server (set by SET
SERVERPASSWORD on
server X) and the password in the server definition (set by
DEFINE or UPDATE
SERVER X SERVERPASSWORD=) are the same password. For a reason of
VERIFICATION FAILURE, use the QUERY SERVER command to determine
that the
HLADDRESS and LLADDRESS of the target server are correct. If
they are not,
correct them with the UPDATE SERVER command. If they are
correct,
resynchronize with the target server by issuing the UPDATE
SERVER
FORCESYNC=YES. For a reason of COMMUNICATION FAILURE ensure that
the target
server is available and that TCPIP is available on both servers.
For a
reason of NO RESOURCE, ensure that the receiving server is
enabled, has
sufficient DB, LOG, and memory resource to support the source
server
session. For a reason of INTERNAL ERROR, use the messages on the
target
server to determine the problem and contact your service
representative.
Retry the failing operation.
______________________
Ben
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
goc
Sent: Thursday, September 30, 2004 8:04 AM
To: [EMAIL PROTECTED]
Subject: SERVER 2 SERVER
hi all, please help
i changed something and "notify subscribers" doesnt work anymore i
changed all the passwords into "password" and still no good, i'm i
missing something ? obviously yes ... but what ...i did this once or
twice before with success but now ... i dont know ...
from TSM01 as configuration manager
ANR3092I NOTIFY SUBSCRIBERS: Subscriber notification processing has
begun. ANR0454E Session rejected by server TSM02, reason: Authentication
Failure. ANR0454E Session rejected by server TSM03, reason:
Authentication Failure. ANR0454E Session rejected by server TSM04,
reason: Authentication Failure. ANR0454E Session rejected by server
TSMIBLER, reason: Authentication Failure. ANR0454E Session rejected by
server TSM_TEST, reason: Authentication Failure. ANR0454E Session
rejected by server ZSBACKUP02, reason: Authentication Failure.
on TSM02
ANR0408I Session 11087 started for server TSM01 (AIX-RS/6000) (Tcp/Ip)
for configuration management. ANR0451W Session 11087 for server TSM01
(AIX-RS/6000) refused - invalid password submitted. ANR0409I Session
11087 ended for server TSM01 (AIX-RS/6000).
on TSM03 the same
ANR0408I Session 11087 started for server TSM01 (AIX-RS/6000) (Tcp/Ip)
for configuration management. ANR0451W Session 11087 for server TSM01
(AIX-RS/6000) refused - invalid password submitted. ANR0409I Session
11087 ended for server TSM01 (AIX-RS/6000). . . . in Network view -
Other servers all servers are in the list, and all direct links to their
url's are working fine.
all TSM's are AIX5.2 version 5.2.3.1 except on in Win which is 5.2.3.2
thanks in advance.
---------------------------------
goran konjic
AIX,TSM,HPOV,ISP admin
vipnet
---------------------------------
