SUMMARY: PCNFS problems (fwd)

From: Ron.Madurski (ron@drd.com)
Date: Mon Feb 15 1993 - 01:46:14 CST


I am having the same problem as is described below. Except htat I only
have one sun. It is an IPX running 4.1.3. I have checked the sun
patches database and have not found anything that will help. I have
installed teh Jumbo PCNFS patch. I have redone the installation several
times. I have tried all of the suggestions mentioned in the old summary
(except one that I don't understand and changing the NIC since I don't
have any to swap out). Here is some of the info from my system. I am
getting desparate so even the most trivial suggestions would be
welcomed.

71 docucentric:/var/yp/docucentric% ifconfig -a
le0: flags=63<UP,BROADCAST,NOTRAILERS,RUNNING>
        inet 192.54.114.88 netmask ffffff00 broadcast 192.54.114.0
        ether 8:0:20:d:81:88
lo0: flags=69<UP,LOOPBACK,NOTRAILERS,RUNNING>
        inet 127.0.0.1 netmask ff000000

79 docucentric:/usr/SunSolve/bin% ypwhich
docucentric
80 docucentric:/usr/SunSolve/bin% rpcinfo -p docucentric
   program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100004 2 udp 662 ypserv
    100004 2 tcp 663 ypserv
    100004 1 udp 662 ypserv
    100004 1 tcp 663 ypserv
    100069 1 udp 664 ypxfrd
    100069 1 tcp 666 ypxfrd
    100007 2 tcp 1024 ypbind
    100007 2 udp 1027 ypbind
    100007 1 tcp 1024 ypbind
    100007 1 udp 1027 ypbind
    100028 1 tcp 668 ypupdated
    100028 1 udp 670 ypupdated
    100029 1 udp 668 keyserv
    100003 2 udp 2049 nfs
    100005 1 udp 714 mountd
    100005 2 udp 714 mountd
    100005 1 tcp 717 mountd
    100005 2 tcp 717 mountd
    100026 1 udp 729 bootparam
    150001 1 udp 735 pcnfsd
    150001 2 udp 735 pcnfsd
    150001 1 tcp 738 pcnfsd
    150001 2 tcp 738 pcnfsd
    100021 1 tcp 737 nlockmgr
    100024 1 udp 736 status
    100021 1 udp 1034 nlockmgr
    100024 1 tcp 739 status
    100021 3 tcp 742 nlockmgr
    100021 3 udp 1035 nlockmgr
    100020 1 udp 1036 llockmgr
    100020 1 tcp 747 llockmgr
    100021 2 tcp 750 nlockmgr
    100021 2 udp 1037 nlockmgr
 554766609 1 tcp 740
    100011 1 udp 1038 rquotad
    100001 2 udp 1039 rstatd
    100001 3 udp 1039 rstatd
    100001 4 udp 1039 rstatd
    100002 1 udp 1040 rusersd
    100002 2 udp 1040 rusersd
    100012 1 udp 1041 sprayd
    100008 1 udp 1042 walld
    100068 2 udp 1043
    100068 3 udp 1043
    100015 6 udp 789 selection_svc
1073741824 1 udp 987

81 docucentric:/usr/SunSolve/bin% netstat -i

81 docucentric:/usr/SunSolve/bin% netstat -i
Name Mtu Net/Dest Address Ipkts Ierrs Opkts Oerrs Collis Queue
le0 1500 192.54.114.0 docucentric 85 6 150 0 0 0
lo0 1536 loopback localhost 59951 0 59951 0 0 0

82 docucentric:/usr/SunSolve/bin% arp -a
pcframer (192.54.114.90) at 0:0:c0:2:9a:56

84 docucentric:/usr/SunSolve/bin% ypcat ethers
8:0:20:d:81:88 docucentric
0:0:c0:02:9a:56 pcframer

85 docucentric:/usr/SunSolve/bin% ypcat hosts
192.54.114.90 pcframer
192.54.114.89 route66
192.54.114.88 docucentric loghost mailhost
127.0.0.1 localhost

86 docucentric:/usr/SunSolve/bin% psg rpc
USER PID %CPU %MEM SZ RSS TT STAT START TIME COMMAND
root 67 0.0 0.0 40 0 ? IW 14:45 0:00 rpc.ypupdated
root 112 0.0 0.0 56 0 ? IW 14:45 0:00 rpc.mountd -n
root 128 0.0 0.0 52 0 ? IW 14:45 0:00 rpc.bootparamd
root 134 0.0 0.0 52 0 ? IW 14:45 0:00 rpc.statd
root 133 0.0 0.0 48 0 ? IW 14:45 0:00 /usr/etc/rpc.pcnfsd
root 135 0.0 0.0 84 0 ? IW 14:45 0:00 rpc.lockd

: The master NIS server is intermittently available and unavailable. One
: second I can ping and mount drives from it and the next second its as if
: it has disappeared off the face of the earth.
:
:
: Solution:
: __________
:
:
: Changing the server that the PCs bind to seemed to do the trick. I don't know
: why this solved the problem, the server that the PCs were binding to was not
: under a particularly heavy load and other PCs in the dept could bind to
: "problem" server with no problem.
:
: However, the patch 100075 was applied around the same time and may have had a
: hand in the solution. However this patch is for file locking and I don't really
: see how that would relate to PCNFS booting, unless it had something to do
: with the way rpc calls are handled.
:
: Thanks,
:
:
:
: Larry Chin {larry@cch.com} CCH Canadian Ltd.
: System Administrator 6 Garamond Court
: Research and Development Don Mills, Ontario.
: (416) 441-4001 ext. 349 M3C 1Z5
:
: Rule 46, Oxford Union Society, London:
: Any member introducing a dog into the Society's premises shall
: be liable to a fine of one pound. Any animal leading a blind
: person shall be deemed to be a cat.
:
:
:
:
: Replies:
: _________
:
: ------------------------------------------------------
:
: > "Andrew Luebker" <aahvdl@eye.psych.umn.edu> suggested:
: > setting an appropriate NETMASK for the PC-NFS microcomputers, using "net
: > subnet 255.255.255.0" during bootup and making sure that the "pcnfsd" daemon
: > is automatically started whenever your server reboots.
:
: > Eckhard.Rueggeberg@ts.go.dlr.de suggested:
: > Rebooting the PC helps, perhaps multiple times.
:
: > nagel@post.inf-wiss.ivp.uni-konstanz.de
: > use the $NISSERVER and $HOME feature for mounting drives, from the master.
: > this feature works only with the real master and not with the slaves.
I

I don't understand this...:
: ** this is interesting because the PCs were trying to bind to the master **
:
: ----------------------------------------------------
:
: > Richard Elling <Richard.Elling@eng.auburn.edu>
: > take a close look at your
: > addresses. In particular, make sure you don't have duplicate IP
: > addresses for any PCs. Second, check to see if you have entries in
: > the ethers NIS map for any PCs. Make sure these match exactly. You
: > can also use the arp command on the Suns to see what the Suns think
: > the mapping is from IP address to ethernet address.
:
: > What will happen is as a machine comes up it will send an arp packet
: > which tells everyone what its IP address is. This will set up an arp
: > table entry on the Suns so that the Sun will know which ethernet address
: > to send packets destined for the corresponding IP address. If another
: > machine speaks up and claims the IP or ethernet address, then the first
: > machine will seem to disappear.
:
: > There was some talk a while back about some Asian ethernet clone cards
: > which used the same ethernet address. So be sure and check each PC
: > out.
:
: ---------------------------------------------------
:
: > Mike Raffety <miker@sbcoc.com>
: > Are there blank lines in any of your NIS maps????
:
: ----------------------------------------------------
:
: > birger@vest.sdata.no (Birger A. Wathne)
: > try turning off the SQE heartbeat on the transceiver
:
: ----------------------------------------------------
: > ldavis!ken@snowbird.Central.Sun.COM (Ken Cox)
: > upgrading the drivers for the PC ethernet controllers and in some cases
: > replacing the PC ethernet controller. The SS2 have VERY fast ethernet
: > performance and it seems that some PC controllers just cannot keep up with
: > the data.
:
:
: Thanks also to:
:
: geertj@ica.philips.nl (Geert Jan de Groot)
:
:

-- 
ron@DRD.Com           ||   Death, Taxes, and running out of disk space. ||
uunet!drd!ron         ||   3 things you can count on in life.           ||



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:28 CDT