I am trying to track down what I believe is a configuration error on a 6
node cluster running Tru64 5.1 with TruCluster.
We have two such clusters and only one exhibits the "odd" behavior.
I export a filesystem from the cluster and attempt to mount it (using the
cluster alias) from a 4.0f machine.
/etc/exports contains:
/var/opt/prdfs -root=0 -access=prd0db05
In this example prd0db05 has two interfaces, one set up on our internal
production network (xxx.xxx.122.29 prd0db05) the other to a backup network
(xxx.xxx.219.29 prd9db05). This machine is running routed and the default
router is xxx.xxx.122.29.
The mount command fails with permission denied. I then add the second
interface to /etc/exports.
/var/opt/prdfs -root=0 -access=prd0db05:prd9db05
This time the mount succeeds and a showmount command run on the cluster
shows the filesystem shared to prd9db05.
rcommands show the same behavior. Unless the backup interface is included
in the users .rhosts permission is denied.
Telnet also seems to use the backup network rather than routing over the
primary network.
When I telnet to the cluster alias from prd0db05 and get my tty name then
check who to see what machine this connected to it shows the backup
interface (prd9db05). On the other hand, if I bypass the cluster alias and
telnet directly to one of the hosts in the cluster it shows the connection
established from prd0db05 as we would expect to see.
the entries for prd0db05 are correct in /etc/hosts, yp hosts and dns. There
is only an entry for prd9db05 in nis. The cluster alias is in the
/etc/hosts and in yp hosts on the 4.0f machine as well as the dns tables.
I have been comparing configuration between the two clusters but am yet too
find a difference in implementation. We would be greatful for any clues as
to what I may be missing.
Thank You,
Allen
Received on Wed Jun 13 2001 - 19:38:53 NZST