>> But that's essentially what we have now -- if you can trigger the
>> NMBCLUSTER usage (I don't know how, which is just fine...), the
>> machine will fall off the network, and, as far as I can tell,
>> does not recover.

Der Mouse wrote:
> Then it may be interesting to know that there is something
> architecture-specific, or perhaps machine-specific, involved in causing
> it.  My main home machine is a SPARC IPX, and occasionally when
> switching windows (which causes a big but brief spike of network
> traffic, much internal to the machine but some off-machine) I'll get
> the NMBCLUSTERS gripe...but aside from that there is no visible effect;
> the machine certainly doesn't "fall off the network".

Alpha-specific?  Tulip driver-specific?  Has anyone else on this list
experienced this?  Does your system come back up on the network after an
NMBCLUSTERS error?


Tom Haapanen
tomh@motorsport.com