Node Name Change

[Robert Atkinson]

When we migrated from 8200's to ES40's, I used different node names for the new machines, so that I could run them in parallel.

One of the boxes, GAMMA, is still left with an old name of GAMNEW.

My question is simple - can anyone give me a fairly difinitive list of the areas I need to check to change the name back to GAMMA.

I already know quite a few of them, such as DECNET, License Database, etc, but if anyone has a document that covers the rest, I'd be grateful.

Cheers, Rob.

[Mobeen_1]

Rob,
Here are the things that need to be carried out to accomplish the node change. Technically speaking you can have different node names each for your TCPIP and DECnet.

1. Change the SCSNODE parameter to GAMMA
2. Shutdown your system
3. Have your DNS administrator delete
GAMMANEW and add GAMMA
4. Boot your system up MIN
5. Make sure that SCSNODE name reflects the
new name which is GAMMA
6. Now run your TCPIP config (if you are
using process ware's TCPWare product,
the command is @tcpware:cnfnet menu)
Configure your ethernet to GAMMA
7. Make changes in the license database
8. Reboot your system

All folks out there, please append to this list, if i have left out anything :)

regards
Mobeen

[Antoniov.]

Hi Rob,
other areas of name are (furtehermore the good prior post):
a) DecNet (executor node);
b) TCP/IP (localhost, pop3 if use it, etc);
c) LAT service (could be automatic after SCSI and/or decnet change, but it's better check);
d) Proxy database, if you use it;
e) DCL procedures that use devices (may be not change but it's better check); perahps, for DCL commands you could search "GAMMA" in all *.COM files, then edit individually to see details.
You might make some change also on other machine of network, for example in proxy database (if you use) or in decnet if you have stored list of nodes.

H.T.H.
@Antoniov

[Antoniov.]

ABout officila documentation I've found only this:
http://h71000.www7.hp.com/wizard/faq/vmsfaq_006.html

Regards
@Antoniov

[Ian Miller.]

queues refer to the SCSNODE name. Layered products may also contain configuration information related to the node name. Apart from externally visable things like dns and decnet you may consider if its worth the hassle resulting from changing SCSNODE name.

[Martin P.J. Zinser]

One thing "out of the box", any clients that do refer to GAMNEW by name need to change their
config to point to GAMMA (or you need to keep GAMNEW around as an alias for GAMMA).

Possbile cases where this can crop in range from terminal emulation setups to Webserver addresses.

Also Oracle is running its own "DNS" with SQL*net and would need to be changed most probably.

Greetings, Martin

[Willem Grooters · Accepted solution]

Rob,

the list is fairly complete, but I wouldn't recommend it. I tried this once, almost ended up in re-installing VMS (it was still an empty machine without real function so it was an alternative to think about).So I won't try it again...Like the others also pointed out: you're bound to forget something. What you _will_ have to redo:

* redefine DECNet stuff. SYS$NODE will change

* Whatever relies on rightsidentifier SYS$NODE_ will no longer work. The system will create anew rights identifier but whatever is linked to the old one, needs to be re-done.

I'm not certain whether other layered products will encounter problems, but surely there is more.

If you _really_ require a new name, but only for TCPIP, that's a less complicated story...

Willem

[Lokesh_2]

Hi Rob,

Why you want to change node name ? If you wish to access system with name GAMMA , then define the alias for it .

Best regards,
Lokesh Jain

[Mike Naime]

Maybe he is tired of seeing GAMNEW when he logs in.

I would make sure that you have handy what your old IP configuration was so that you can re-create it. I would take the approach that you are building a new root and re-do everything just to be safe.

Modparams.dat (Then Autogen)
@net$configure
@utc$time_setup
MCR DECNET_REGISTER
@tcpip$config (Or other IP stack)
Que manger? (Not sure how you handle your queues)

That list covers it for me when I do a new clone)

[Robert Atkinson]

Additional info - I.P. settings were never changed from Gamma so is not an issue.

[Mike Naime]

Robert:

I used to think that changing the node name was not a big issue. This is because I came from a DECNET Phase 4 on VAX world. I changed it all the time by just changing the SCSNODE value and doing a Autogen reboot.

When I went to change my nodename on an Alpha running TCPIP, I found out that after I did my AUTOGEN with REBOOT.... I no longer had a system that was on the network! Changing the SCSNODE setting blew away the TCPIP settings. (And several others that are linked to SCSNODE)

Mike Naime