Is the machine part of a cluster ? This can happen when the cluster fails over and the cluster node connects to the TSM server with a new active node and hence a new IP address and GUID.
I have also seen this with multi-honed machines. Ie more than one NIC. Sometimes, if the routing has changed and the node has established a connection through a different NIC and hence a different IP address. Failing this, somebody could have established a connection to the TSM server using the nodename KULDB21P but not from the machine that is normally associated with the nodename KULDB21P. I find that the above happens when somebody copies the dsm.opt/dsm.sys file from another machine but forgets to change the nodename. HTH Leigh -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dksh Cssc Sent: 11 January 2006 05:03 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] ANR1639I Hi all, 1. Could anyone enligthen me the attributes of some of the nodes that were changed automatically without human intervention? 2. Checked from the TSM messages information that this message will not bring any harm but would like to know why it happened and what are the things that could affect it from happening? 01/11/06 10:10:54 ANR1639I Attributes changed for node KULDB21P: TCP Address from to 10.208.14.26. (SESSION: 249836) This message repeated for a few days, not only on this particular node but other nodes also. Thanks and Warmest Regards,
