Xref: utzoo comp.protocols.nfs:1534 alt.sys.sun:2063
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!apple!amdcad!sun!exodus!cs@Eng.Sun.COM
From: cs@Eng.Sun.COM (Carl Smith)
Newsgroups: comp.protocols.nfs,alt.sys.sun
Subject: Re: how do I find the swap traffic in the output of NFSWATCH?
Keywords: nfs nfswatch swap tcp udp
Message-ID: <2884@exodus.Eng.Sun.COM>
Date: 15 Nov 90 21:42:53 GMT
References: <706@keele.keele.ac.uk>
Sender: news@exodus.Eng.Sun.COM
Reply-To: cs@Eng.Sun.COM
Followup-To: comp.protocols.nfs
Organization: Sun Microsystems, Inc.
Lines: 21

In article <706@keele.keele.ac.uk>, cca13@seq1.keele.ac.uk (G.D. Pratt) writes:
> I am trying to determine the load on our ethernet - 16 3/[5|6]0s
> running SunOS 4.1 on a 3/180 server. Before the upgrade from SunOS
> 3.5 the "nd" swap traffic was obvious from the output from nfswatch;
> now it is not so clear to me. The packets are mostly TCP(25%) and
> UDP(75%) - is this the NFS verses SWAP division? 

	It's difficult to tell how much traffic to attribute to swapping over
NFS because the only difference between that and any other NFS I/O is the file
on which I/O is being done.
	Depending on how well-organized your file servers are, nfswatch may be
able to tell you what you need to know.  It understands the format of some
vendors file handles and can therefore often tell you what file system is the
target of the I/O.  If a given file system on the server contains only swap
files, you can be confident that any NFS traffic to that file system is attrib-
utable to swapping.
	For the truly desparate, you may be able to convince a server to tell
you what the file handles are for its swap files.  It would then be simple to
modify nfswatch to monitor an explicit list of file handles.

			Carl