Update NAME_SERVICE IP Addresses in TCPIP
-
Topic author - Active Contributor
- Posts: 39
- Joined: Fri Jun 28, 2019 10:29 am
- Reputation: 0
- Location: Gary, Indiana
- Status: Offline
Update NAME_SERVICE IP Addresses in TCPIP
I have multiple legacy OpenVMS nodes that require an update to the IP addresses in NAME_SERVICE in TCP/IP.
I am not sure if TCP/IP has to be stopped and started after change.
Can this be done dynamically?
Is a reboot required?
I am not sure of how to implement the change of IP addresses.
To facilitate the change do you use:
$ @TCPIP$CONFIG.COM;
or
$ TCPIP
TCPIP>
Nodes involved are:
DS-25/OpenVMS V7.3-1/Compaq TCP/IP Services for OpenVMS Alpha Version V5.3
rx3600/OpenVMS V8.4/HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 1
Appreciate your assistance.
Vince
I am not sure if TCP/IP has to be stopped and started after change.
Can this be done dynamically?
Is a reboot required?
I am not sure of how to implement the change of IP addresses.
To facilitate the change do you use:
$ @TCPIP$CONFIG.COM;
or
$ TCPIP
TCPIP>
Nodes involved are:
DS-25/OpenVMS V7.3-1/Compaq TCP/IP Services for OpenVMS Alpha Version V5.3
rx3600/OpenVMS V8.4/HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 1
Appreciate your assistance.
Vince
-
- Master
- Posts: 201
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: Update NAME_SERVICE IP Addresses in TCPIP
Vince,
do you want to change the IP address of an OpenVMS node ?
For TCPIP V5.7 and above, this may help:
https://support.hpe.com/hpesc/public/d ... ale=en_US
For older versions of TCPIP, it's more work - try this:
$ TCPIP SET CONFIG NOINT name-of-interface
$ TCPIP SET NOHOST host-name or "hostname"
$ @TCPIP$CONFIG
1 - Core environment
2 - Interfaces
and define the new IP address
You'll probably have to reboot the OpenVMS system after this change, because shutting down TCPIP and starting it again in the running system may not be cleanly possible.
Volker.
do you want to change the IP address of an OpenVMS node ?
For TCPIP V5.7 and above, this may help:
https://support.hpe.com/hpesc/public/d ... ale=en_US
For older versions of TCPIP, it's more work - try this:
$ TCPIP SET CONFIG NOINT name-of-interface
$ TCPIP SET NOHOST host-name or "hostname"
$ @TCPIP$CONFIG
1 - Core environment
2 - Interfaces
and define the new IP address
You'll probably have to reboot the OpenVMS system after this change, because shutting down TCPIP and starting it again in the running system may not be cleanly possible.
Volker.
-
Topic author - Active Contributor
- Posts: 39
- Joined: Fri Jun 28, 2019 10:29 am
- Reputation: 0
- Location: Gary, Indiana
- Status: Offline
Re: Update NAME_SERVICE IP Addresses in TCPIP
Hi Volker,
Thanks for reply.
No, I do not want to change the ip address for the interface, IE0, but to the name_service
as identified in TCPIP, the DNS server ip addresses.
Just need to update one of the DNS server ip addresses.
Thanks for reply.
No, I do not want to change the ip address for the interface, IE0, but to the name_service
as identified in TCPIP, the DNS server ip addresses.
Just need to update one of the DNS server ip addresses.
-
- Master
- Posts: 201
- Joined: Fri Aug 14, 2020 11:31 am
- Reputation: 0
- Status: Offline
Re: Update NAME_SERVICE IP Addresses in TCPIP
Vince,
$ TCPIP SHOW CONF NAME ! to look at current config
$ TCPIP SET CONF NAME/SERVER=(IP-address-of-new-DNS-server) ! define in config
$ TCPIP SET NAME/SYSTEM/SERVER=(IP-address-of-new-DNS-server) ! enable in running system
$ TCPIP SET CONF NAME/NOSERVER=(IP-address-of-old-server-to-be-removed) ! delete from config
$ TCPIP SET NAME/SYSTEM/NOSERVER=(IP-address-of-old-server-to-be-removed) ! delete from running system
No TCPIP restart necessary.
Volker.
$ TCPIP SHOW CONF NAME ! to look at current config
$ TCPIP SET CONF NAME/SERVER=(IP-address-of-new-DNS-server) ! define in config
$ TCPIP SET NAME/SYSTEM/SERVER=(IP-address-of-new-DNS-server) ! enable in running system
$ TCPIP SET CONF NAME/NOSERVER=(IP-address-of-old-server-to-be-removed) ! delete from config
$ TCPIP SET NAME/SYSTEM/NOSERVER=(IP-address-of-old-server-to-be-removed) ! delete from running system
No TCPIP restart necessary.
Volker.
-
Topic author - Active Contributor
- Posts: 39
- Joined: Fri Jun 28, 2019 10:29 am
- Reputation: 0
- Location: Gary, Indiana
- Status: Offline
Re: Update NAME_SERVICE IP Addresses in TCPIP
Hi Volker,
Thanks again for your prompt reply.
It is good to know, no restarts are required for this in TCPIP or system.
OpenVMS is very robust.
Appreciate your help.
Vince
Thanks again for your prompt reply.
It is good to know, no restarts are required for this in TCPIP or system.
OpenVMS is very robust.
Appreciate your help.
Vince
-
- Valued Contributor
- Posts: 79
- Joined: Thu Jun 06, 2019 6:57 am
- Reputation: 0
- Location: Brindisi (Italy)
- Status: Offline
- Contact:
Re: Update NAME_SERVICE IP Addresses in TCPIP
Try the below procedure :
If you need to change the order of the dns servers :
No need to restart ip stack or to reboot the system, the dns client configuration is valid and active. Of course, even on the next reboot of the server
/Maurizio
PS: after sending I realized that Volker had already replied; I apologize for this.
Code: Select all
$ TPCIP
TCPIP> sho name ! volatile db
BIND Resolver Parameters
Local domain: acme.org
System
State: Started, Enabled
Transport: UDP
Domain: acme.org
Retry: 2
Timeout: 5
Servers: 8.8.8.8, 8.8.4.4
Path: acme.org
Process
State: Enabled
Transport:
Domain:
Retry:
Timeout:
Servers:
TCPIP> sho conf name ! permanent db
BIND Resolver Configuration
Transport: UDP
Domain: acme.org
Retry: 2
Timeout: 5
Servers: 8.8.8.8, 8.8.4.4
Path: acme.org
TCPIP> set name /noserver=(8.8.4.4)/system ! volatile db
TCPIP> set name /server=(192.168.1.1)/system ! volatile db
TCPIP>!
TCPIP> set conf name /noserver=(8.8.4.4) ! permanent db
TCPIP> set conf name/server=(192.168.1.1) ! permanent db
TCPIP> sho name ! volatile db
BIND Resolver Parameters
Local domain: acme.org
System
State: Started, Enabled
Transport: UDP
Domain: acme.org
Retry: 2
Timeout: 5
Servers: 8.8.8.8, 192.168.1.1
Path: acme.org
Process
State: Enabled
Transport:
Domain:
Retry:
Timeout:
Servers:
TCPIP> sho conf name ! permanent db
BIND Resolver Configuration
Transport: UDP
Domain: acme.org
Retry: 2
Timeout: 5
Servers: 8.8.8.8, 192.168.1.1
Path: acme.org
If you need to change the order of the dns servers :
Code: Select all
TCPIP> set name /noserver=(8.8.8.8,8.8.4.4)/system ! volatile db
TCPIP> set name /server=(192.168.1.1,8.8.8.8)/system ! volatile db
TCPIP>!
TCPIP> set conf name /noserver=(8.8.8.8,8.8.4.4) ! permanent db
TCPIP> set conf name/server=(192.168.1.1,8.8.8.8) ! permanent db
TCPIP> sho name ! volatile db
BIND Resolver Parameters
Local domain: acme.org
System
State: Started, Enabled
Transport: UDP
Domain: acme.org
Retry: 2
Timeout: 5
Servers: 192.168.1.1, 8.8.8.8
Path: acme.org
Process
State: Enabled
Transport:
Domain:
Retry:
Timeout:
Servers:
TCPIP> sho conf name ! permanent db
BIND Resolver Configuration
Transport: UDP
Domain: acme.org
Retry: 2
Timeout: 5
Servers: 192.168.1.1, 8.8.8.8
Path: acme.org
No need to restart ip stack or to reboot the system, the dns client configuration is valid and active. Of course, even on the next reboot of the server
/Maurizio
PS: after sending I realized that Volker had already replied; I apologize for this.
Last edited by m_detommaso on Tue May 09, 2023 12:34 pm, edited 3 times in total.
-
Topic author - Active Contributor
- Posts: 39
- Joined: Fri Jun 28, 2019 10:29 am
- Reputation: 0
- Location: Gary, Indiana
- Status: Offline
Re: Update NAME_SERVICE IP Addresses in TCPIP
Hi Maurizio,
Appreciate you taking the time to reply.
Thanks for providing a detailed example.
Always helps.
Thanks.
Vince
Appreciate you taking the time to reply.
Thanks for providing a detailed example.
Always helps.
Thanks.
Vince