We have an alphaserver 400 that was at DU4.0D which we recently updated
to DU4.0F with most recent patches.
Prior to the update, the host had its IP in /etc/hosts and
/etc/rc.config, and ifconfig showed the interface to be at that IP.
It also had an additional IP that was added to /etc/hosts by
developers with root access before my time. This additional IP
could be used to telnet to the box but was not represented in
/etc/rc.config or in ifconfig output. (I don't understand why
this worked, but it did)
Since the upgrade, nothing has changed in /etc/hosts, or in
/etc/rc.config (or in /etc/inet.local, which we do use but
which does not contain an entry for this mysterious additional IP)
but ifconfig reports that the interface is answering as this
additional IP. Both IPs work to get to the box, so the first
one didn't stop working.
Here's contents of files, and ifconfig, changed to protect us:
/etc/hosts
127.0.0.1 localhost
111.22.33.44 primary.hostname.org
111.22.33.55 additional.hostname.org
/etc/rc.config
NUM_NETCONFIG="2"
NETDEV_0="tu0"
NETDEV_1="le0" <-----------------------------------This is the interface
IFCONFIG_0="111.22.99.44 netmask 255.255.255.0" in question
IFCONFIG_1="111.22.33.44 netmask 255.255.255.0" <- defined as
primary.hostname.org
# ifconfig -a
le0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 111.22.33.55 netmask ffffff00 broadcast 111.22.33.255 ipmtu 1500
^^^^^^^^^^^^
Interface is defined as "additional.hostname.org" ????
tu0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
inet 111.22.99.44 netmask ffffff00 broadcast 111.22.99.255 ipmtu 1500
Can anyone explain this behavior??
TIA...
--
Judith Reed
jreed_at_appliedtheory.com
(315) 453-2912 x5835
Received on Fri Sep 22 2000 - 13:42:09 NZST