Hello Managers,
Has anyone experienced problems while serving NFS over FDDI to an
ethernet client, where the NFS packets go through a Cisco 5000 Interface?
The server is a DEC 3000 M800 on FDDI, and other NFS clients on
FDDI work fine. We have some NFS clients which are on ethernet which talk
to the NFS server thru a Cisco 5000.
We've found that the ethernet clients will often get "NFS server
not responding" messages when the client wants to read lots of data over
a short time. Inserting an FDDI sniffer into the ring showed that large
NFS packets from the server were not being fragmented correctly - the
network experts guess that the Cisco 5000 is to blame. I'm told that
the method for breaking up large FDDI packets varies from vendor to
vendor, and that this could be the source of our problem.
(FYI - ethernet clients which get NFS which are _not_ routed thru
the Cisco always work fine.)
Anyway, we've found that a work-around is, on each problem client,
to NFS mount using small read and write buffer sizes (rsize=1536,
wsize=1536 worked). Instead of doing this for each problem client, I
was wondering if there was a way to configure the NFS server to limit the
NFS packet size. It seems that the rsize and wsize default can be set in
the NFS client's kernel configuration (how???), but no such mention is
made for the NFS server in the man pages.
Any comments are appreciated. Will summarize. Thanks!
Dave Wolinski Phone: (313) 936-6648 Fax: (313) 936-1817
University of Michigan / CDF
Received on Tue Nov 12 1996 - 02:44:12 NZDT