ADSM-L

Renaming a W2K node

2003-03-05 19:00:49
Subject: Renaming a W2K node
From: Todd Lundstedt <Todd_Lundstedt AT VIA-CHRISTI DOT ORG>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 5 Mar 2003 18:00:28 -0600
AIX 4.3.3 running TSM Server 4.2.1.7.

I have a few client nodes that are W2K servers.  Oddly, they are named
after our NT servers (NT-ServerA, NT-ServerB, etc..).  The dsm.opt file
contains the NT machine name as the NodeName.  I would like to change the
NodeName to W2K-ServerA, but not rename the machine name.
... I stopped the scheduler service on the client node.
... I modified the name in dsm.opt, and saved the file
... I renamed the node on the TSM Server ("rename node nt-servera
w2k-servera", or whatever the command is... I actually used the web admin
GUI to do it).
... I entered "dsmc query session" at the command line of the client node.
... ... it indicated it was node W2K-ServerA, requested the user ID, and
password.. I entered (defaulted) the ID, and keyed in the password for that
node.  The information was returned as expected.
... I entered "dsmc query session" at the command line of the client node,
again.
... ... The information was returned as expected, without ID and password
being required (by the way, the opt file does have passwordaccess
generate), still indicating it was the new nodename, W2K-ServerA.
... I started the service up... it started and quietly failed (no GUI
messages on the screen).  I checked the dsmsched.log file, and it appeared
that it attempted to connect using NT-ServerA instead of W2K-ServerA.

Baffled.. so
... I checked to properties on the service.. I didn't see anything that
indicated NT-ServerA.
... I started the Backup/Archive GUI (vers 5.1.x) and checked the
preferences there.  Everything was as I would have expected it to be based
on the values in the dsm.opt file, including the node name being
W2K-ServerA

After much searching of documentation and scratching of head, I punted and
changed everything (dsm.opt, nodename on TSM server, etc.) back to
NT-ServerA and the service started up and stayed up.

What am I missing to change the node name?  Something is still using the
old node name when it attempts to contact the TSM server, and of course,
that nodename no longer exists on the TSM server.  I did do some looking
around in that quickFaQ that Richard links to all the time... didn't find
anything in there that jumped out at me.  Same with the last 3 months of
ADSM.org archives, and IBM's horridly slow and completely non-user-friendly
support pages.

I am lost...

Thanks in advance
Todd

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