SUMMARY ADDENDUM: Seen as secondary name instead of primary.

From: Bugs (bb1@humboldt.edu)
Date: Thu Sep 12 2002 - 12:58:55 EDT


Thanks to "Davis, Alan" <Davis@tessco.com> for correcting
me as to the proper location of the ifconfig command.

Although it works where I placed it in an /sbin/rc3.d/S...
file, it should really be placed in /etc/inet.local.
Bugs

Bugs Brouillard Unix system administrator
Humboldt State Univ. Information Technology Services
Arcata, Calif.

email bb1@humboldt.edu

---------- Forwarded message ----------
Date: Thu, 12 Sep 2002 08:36:06 -0700 (PDT)
From: Bugs <bb1@humboldt.edu>
To: Tru64-UNIX-Managers <tru64-unix-managers@ornl.gov>
Followup-To: poster
Subject: SUMMARY: Seen as secondary name instead of primary.

I finally resolved this problem. Instead of entering IP aliases
in rc.config, I place "ifconfig" commands in our startup scripts.
Like this:
ifconfig tu1 alias 137.150.148.23/20

Now polaris sees oak as oak instead of oakfp.

Bugs Brouillard Unix system administrator
Humboldt State Univ. Information Technology Services
Arcata, Calif.

email bb1@humboldt.edu

==========================================================
My original problem:
Subject: Seen as secondary name instead of primary.

Hello,
        I manage 8 alpha's. A mixture of 4.0d, and 5.1a.
On one machine, "oak" I can connect to all but one called
"polaris", which is a 4.0d and is the campus nameserver.
oak is 5.1a. when I connect to all other alpha's from oak,
they all see oak as "oak", but when I connect to polaris, it
sees oak as oakfp, which is an aliases IP also on oak.
The connections only fail on the "r" commands such as rsh,
rcp, stuff like that because in .rhost files, oak is permitted
but not oakfp. It also cant mount polaris's nfs disk (for tripwire)

The question: why is polaris seeing oak as oakfp instead of oak
like all the other alphas.
Clue: The network folks took the campus to full dhcp (excluding
the alpha's). polaris is still on the backbone, but all other
alphas are on a different router.

Does this help?
(the 137.150.148.X are the alpha's)

Polaris:
tu1: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
     inet 137.150.17.5 netmask fffff000 broadcast 137.150.31.255 ipmtu 1500

Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.240.0

Route Tree for Protocol Family 2:
default 137.150.17.1 UGS 2 4133436 tu1
127.0.0.1 127.0.0.1 UH 1 128 lo0
137.150.16/20 137.150.17.5 U 1 4707632 tu1
137.150.146.30 137.150.16.9 UGHD 0 214 tu1
137.150.146.40 137.150.16.9 UGHD 0 1266 tu1
137.150.148.10 137.150.16.9 UGHD 2 1382283 tu1
137.150.148.16 137.150.16.9 UGHS 0 28 tu1
137.150.148.17 137.150.16.9 UGHD 0 10282 tu1
137.150.148.18 137.150.16.9 UGHD 4 93187 tu1
137.150.148.19 137.150.16.9 UGHD 0 35518 tu1
137.150.148.25 137.150.16.9 UGHD 0 1537 tu1
137.150.159.254 137.150.16.9 UGHD 0 100 tu1
137.150.186.23 137.150.16.9 UGHD 0 245 tu1
137.150.186.24 137.150.16.9 UGHD 0 166 tu1
===============================================================

Oak:
(oak's IP is 137.150.148.16)

tu1: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX>
     inet 137.150.145.23 netmask fffff000 broadcast 137.150.159.255 ipmtu 1500
     inet 137.150.148.16 netmask fffff000 broadcast 137.150.159.255 ipmtu 1500
     inet 137.150.148.16 netmask fffff000 broadcast 137.150.159.255 ipmtu 1500

Routing tables
Destination Gateway Flags Refs Use Interface

Route Tree for Protocol Family 26:

Route Tree for Protocol Family 2:
default 137.150.145.10 UGS 2 450299 tu1
127.0.0.1 127.0.0.1 UHL 5 3783 lo0
137.150.144/20 137.150.148.16 U 20 7950356 tu1
137.150.145.23 137.150.145.23 UGHS 0 0 tu1
137.150.148.16 137.150.148.16 UHL 0 548 tu1

Any help is appreciated. Thanks.

Bugs Brouillard Unix system administrator
Humboldt State Univ. Information Technology Services
Arcata, Calif.

email bb1@humboldt.edu



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:53 EDT