[rescue] tcpdump and nfs questions

[John Duksta]

At 08:52 PM 11/12/2001 -0500, Joshua D Boyd wrote:
>On Mon, Nov 12, 2001 at 08:38:40AM -0500, John Duksta wrote:
> > >00:02:24.863421 802.1d config 8000.08:00:02:1d:b9:02.800d root
> > >8000.08:00:02:1d:b9:02 pathcost 0 age 0 max 20 hello 2 fdelay 15
> >
> > This is a spanning tree announcement. This must be the 3Com LaxPlex.
>
>What in the world does that mean?

Spanning tree is the protocol by which bridges and switches
(which are just multiport bridges anyway) make sure that there
are no loops in the network. Not something you need to worry
about right now, seeing as you probably only have this one switch.

If you want to read about it, here's a decent overview at Cisco:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/sw_ntman/cwsimain/cwsi2/cwsiug2/vlan2/stpapp.htm

>
> > Things to try:
> >
> > - You might want to try taking the LanPlex out of the picture.
> >   Do you have a plain old hub that you could test with?
>
>Hmm.  That fixes it.  So, based on the fact that everything else functions
>perfectly through the lanplex 2500, I'm wondering if this might be a
>configuration problem with the lanplex?  Can anyone answer that?  I'm
>trying to look through the documentation now, but I have no clue what I'm
>looking for.
>
>A restore to factory default might do it...

Good place to start. If you still see the problem, you might
want to try putting the two machines on different ports
on the switch than you had them on before. Maybe you've got
flaky ports there?

One other thing you might try... if you've got the FDDI
interface on the LanPlex, but you're not using it, try
disabling it. Perhaps the switch might be messing with
the packet sizes if it thinks the FDDI interface is active.

Since I've never worked with one of these LanPlex beasties,
I'm kinda pulling these suggestions out of my a**, so YMMV.

-john