On Sep 7, 2005, at 3:28 AM, Large, M (Matthew) wrote:
Hi SMers,
I picked up this message last night after a scheduled event failed,
but
I was not expecting to read what I read:
06-09-2005 17:43:33 ANR1639I Attributes changed for node CHEETAH: TCP
Address from 172.17.40.228 to 172.17.44.56. (SES
Ah, I think I'm looking for an 'official' answer - the node was
contacted using the Server Prompted option, TSM found a new TCP address,
at this point I would have expected TSM to record the new TCP address
against the node, and to use the new address in future contacts, not the
old one.
The back
May be it tries to read/checks the client option file ( dsm.opt or what
ever u have specified)associated to schedular while defining tsm client
schedular , it may have kept those entries in database,
despite of this message I feel that urs backup was successful..
-Original Message-
From:
Hi Sandeep,
We don't use accounting at the moment so we are not affected by that.
My question is why, if TSM updated the attributes after it noticed they
had changed, did it not attempt to communicate to the client over the
new TCP address? If it had it might not have failed to perform the
backup
Hi matthew,
ANR1639I indicates that the TSM server found that the client
node connected to the TSM server with a different IP address than it did
before. This does not affect operation, however it may affect accounting
depending on how accounting is performed for this node.
Do u have
