HP3000-L Archives

August 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Tue, 27 Aug 2002 12:57:02 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Review your network settings in NMMGR, comparing the new box with the old.

I believe that your new box comes "untuned". That is, assuming that all
network traffic is local (just like all politics are local), and your
network small and simple. So, for instance, timeouts are assumed to be
relatively short, and retries few.

Also, in spite of any memory upgrades you may have ordered, the OS is tuned
for the base memory, and inbound and outbound buffers are still set to their
default amounts.

A good first approximation for your network timeouts in NMMGR are whatever
you have on the older box. You can also try its values for inbound and
outbound buffers, although another rule of thumb is to multiply them by the
same factor that you have for total memory above the base configuration.
IOW, if you have twice as much memory as the base configuration, double the
buffer pools.

I'm trying to remember, can the 3000 be told to communicate half-duplex
instead of full duplex?

The great thing about network issues is, your mileage will vary.

Greg Stigers
http://www.cgiusa.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2