Hello managers,
   We recently added some ip aliases to our nfs server by adding
ifconfig ee0 alias 1.2.3.4
ifconfig ee0 alias 1.2.3.5
ifconfig ee0 alias 1.2.3.6
to our /etc/inet.local file.  Each alias has a corresponding dns entry 
which resolves forward and reverse as expected.
   We are having an issue with nfs mounted file systems when the file 
system is mounted via one of these aliases.  It seems rpc.lockd and 
rpc.statd bind only to the first ip on a given interface.  So in the 
case above if the interface ee0 has 1.2.3.3 and the above aliases 
rpc.lockd and rpc.statd only listen on 1.2.3.3 and not the above 
aliases.
   rpcinfo -p shows me the ports that these two services are listening 
on, and netstat -na shows which interfaces these ports are listening on.
rpcinfo -p |grep -E "stat|lock"
     100001    2   udp   2080  rstatd
     100001    3   udp   2080  rstatd
     100001    4   udp   2080  rstatd
     100024    1   udp   1650  status
     100024    1   tcp   2550  status
     100021    1   tcp   2551  nlockmgr
     100021    2   tcp   2551  nlockmgr
     100021    3   tcp   2551  nlockmgr
     100021    4   tcp   2551  nlockmgr
     100020    3   tcp   2551  llockmgr
     100021    1   udp   1651  nlockmgr
     100021    2   udp   1651  nlockmgr
     100021    3   udp   1651  nlockmgr
     100021    4   udp   1651  nlockmgr
     100020    3   udp   1651  llockmgr
netstat -na | grep for ports from above list
tcp        0      0  127.0.0.1.2551            *.*                      
  LISTEN
tcp        0      0  1.2.3.3.2551       *.*                       LISTEN
tcp        0      0  127.0.0.1.2550            *.*                      
  LISTEN
tcp        0      0  1.2.3.3.2550       *.*                       LISTEN
udp        0      0  *.2080                    *.*
udp        0      0  127.0.0.1.1651            *.*
udp        0      0  1.2.3.3.1651       *.*
 From this list rstatd (not nfs related, services rup requests) is 
listening on all interfaces, but all remaining ports(rpc.statd & 
rpc.lockd) are listening only on localhost and the first interface.
I can start a second rpc.lockd with that -b argument and a hostname or 
ip address, but I cannot start a statd.  My NFS clients are having 
locking issues that are preventing them from functioning.
I know the easy fix is to tell my NFS clients to mount via the primary 
IP instead of the aliases, but I am seeking an alternative solution for 
various reasons.
Thanks,
--
Jay R. Wren
Systems Programmer
Oakland University
Rochester, Michigan
Received on Mon Nov 11 2002 - 18:21:56 NZDT