topic Re: Multinet IP Change Problem in Operating System - OpenVMS

Multinet IP Change Problem

PreZ — Tue, 03 Aug 2010 09:53:54 GMT

Hi,

Recently we changed ip in our server with version,
MultiNet V4.4 Rev A-X, AlphaServer 4100 5/533 4MB, OpenVMS AXP V7.2-2.
The server is resolving in DNS and also I can telnet and login to the system.
But when I try to ping the host from same host , it is giving me the old ip.

Example :
If i have changed the ip from x.x.x.x to y.y.y.y
Server1$telnet server1.ser.com

I am able to login.

But,
If i try to ping the server with fqdn,
server1$multinet ping server1.ser.com
PING Server1.ser.com (x.x.x.x): 56 data bytes
It is trying to get the old ip address.

If i try to ping the server without fqdn,
server1$multinet ping server1
Ping Server1.ser.com (y.y.y.y) : 56 data bytes
64 bytes from y.y.y.y: icmp_seq=0 time=0 ms
It is reachable.

I have checked the multinet:hosts.local file entry also. It is not there.

Kindly please let me know how could i resolve this problem.
Also how could i release port in multinet.
i want to release the connection in port 1521

Thanks,
Prem

Re: Multinet IP Change Problem

PreZ — Tue, 03 Aug 2010 10:24:02 GMT

also how to flush the cache in multinet.

It is not pinging only if i use in Capital letter for hosts.
SERVER1.SER.COM

Re: Multinet IP Change Problem

Richard Whalen — Tue, 03 Aug 2010 12:13:34 GMT

It sounds like you may have changed the IP address with MultiNet Configure/Network (good) and the name server (NAMED_SERVER) is getting the right information because its configuration files have been updated.

I suspect that PING is using the old HOSTS.TXT though. Update MULTINET:HOSTS.TXT with the new address, then recompile it with
$multinet host compile
and install the new tables with
$@multinet:install_databases

Re: Multinet IP Change Problem

PreZ — Tue, 03 Aug 2010 12:37:45 GMT

Hi Richard,
Thanks.
I checked the Multinet:Hosts.txt file.
There were no entries at all.

Re: Multinet IP Change Problem

Richard Whalen — Tue, 03 Aug 2010 13:52:11 GMT

There is no way to flush the cache of the name server, but you can restart it:
$ multinet netc/host=127.0.0.1 domainname shutdown
$ multinet netc/host=127.0.0.1 domainname start

You'll want to check your name server configuration and where it eventually gets its answers from for hosts in your domain.

Re: Multinet IP Change Problem

Joewee — Tue, 03 Aug 2010 14:39:24 GMT

Hi Richard,

Sorry to pop in here.

Im working with Prem here on the same problem.

I jus tried the command you have give above and please find the out put below.

AAAAA_SYSTEM> multinet netc/host=127.0.0.1 domainname start
Connected to NETCONTROL server on "127.0.0.1"
< AAAAA.MERCK.COM Network Control V4.4(10) at Tue 3-Aug-2010 11:09AM-EDT
Error: Service "domainname" not found

Please suggest.

Re: Multinet IP Change Problem

Richard Whalen — Tue, 03 Aug 2010 16:48:08 GMT

That would imply that the name service isn't running on this system. To see what MultiNet services can be controlled from the netcontrol application do the following:
$ multinet netc/host=127.0.0.1 netc list

To see the address of the name server that the system using:
$ show log multinet_nameservers