I would start at the bottom and work my way up.
So where is the bottom?
Check physical and network layer type stuff. You mention no physical changes, but you have moved to layer 3, so it is a safe bet the problem is in there somewhere.
Duplex mismatching maybe?
Run netdiag -v on your filer and it will give you a pretty good analysis from the filer perspective.
Check switches/routers for dropped packets, overflowing buffers and/or packet shaping.
If you want to get down to the lowest layer and are good with packet headers/tcpdump, then do a packet trace on the filer (pktt) to a known good host and then to a known bad host (i.e. your ls hanging machine).
I am betting netdiag or you switches/routers turn up something.
If nothing shows there, work your way up to NFS/CIFS analysis.
Thanks, Aaron
-----Original Message----- From: pdunkin@lucent.com [mailto:pdunkin@lucent.com] Sent: Wednesday, April 02, 2003 2:39 PM To: toasters@mathworks.com Subject: post-migration: sloooow response
The next (final??) phase of our network migration is almost complete. The server room and the users' offices have been moved from a Layer 2 network to a Layer 3 network, and everything has a new IP address. There have supposedly been no physical changes -- the same switches and servers and clients are involved as last week.
One of the problems we're encountering is intermittent slow response time in interaction with the NetApps. Example: I'm on the PC in my office. It has a session open with a Solaris server that automounts my home directory from a filer. If I cd to my home directory, it may take a countable number of seconds before the prompt comes back. If I try to ls my directory, it may take even longer. Running ls in /home (where *all* the home directories are, hundreds of them) takes so long that I've been giving up before I get any output.
The slowness isn't consistent. Some of the Solaris servers haven't had much trouble at all. Some are pretty frustrating. It wasn't this way last week before the migration.
Any ideas what may be wrong? Where are the likely places to start troubleshooting?
Thanks!