Am I correct in assuming that you have the following configuration:

Interface Adapter CSR Address Flags/Vector
--------- ------- ----------- ------------
*se0 (Shared VMS Ethernet/FDDI) -NONE- -NONE- -NONE-
[TCP/IP: 10.161.32.59]
[VMS Device: EIA0, Link Level: Ethernet]

se1 (Shared VMS Ethernet/FDDI) -NONE- -NONE- -NONE-
[TCP/IP: current.ip.address.number]
[VMS Device: EWA0, Link Level: Ethernet]

Official Host Name: mcrc16.med.nyu.edu

Though SE0 has been deactivated, the code that selects the IP address to use selects the first interface that it finds. Since SE0 is still defined, its address is used.

I believe that things would get fixed if you disabled SE1 and MODIFIED SE0 to use EWA0 and the ip address that you want to use.

-----Original Message-----
From: Ross Smith [mailto:smithp01@med.nyu.edu]
Sent: Tuesday, October 24, 2006 3:56 PM
To: info-multinet@process.com
Subject: Odd logical definitions...


When I first got my IA64 box I had it in my office. But then it was
moved and given a new IP number.

I inactivated the slower Ethernet port and switched to using the GigE
port which was configured with the new IP.

On hunting down a problem with DNS I found logicals still pointing to
the old IP. The place they are coming from is

START_MULTINET.COM

where I see ...
...
$ Define/System/Exec/NoLog UCX$Inet_Host "mcrc16.med.nyu.edu"
$ Define/System/Exec/NoLog UCX$Inet_HostAddr "10.161.32.59"
$ Define/System/Exec/NoLog UCX$Device _BG0:
$ Define/System/Exec/NoLog UCX$Inet_Device _BG0:
$ Define/System/Exec/NoLog TCPIP$Inet_Host "mcrc16.med.nyu.edu"
$ Define/System/Exec/NoLog TCPIP$Inet_HostAddr "10.161.32.59"
...

Both the IPs are wrong.

I can edit this file and fix the errors. But I'd like to know where
they came from and how they escaped my (clearly inadequate) re-
configuration effort. (I had check with the menu-driven configuration
tool and these IPs don't appear anywhere).

-Ross-