We have a minimum of 150 concurrent NS/VT connections during normal
business hours, only one 100Base-TX NIC, and no current performance
problems. However, in the past I had a similar problem, maybe a year
ago. The problem seemed to come-an-go. I have software support with
Beechglen, and they told me about this command:

linkcontrol @;status=all

This command showed me that our 100Base NIC was working in HALF-DUPLEX
mode. The explanation was; The NIC was configured to 'auto sense' the
link.

So sometimes it would 'auto sense' to be HALF-DUPLEX, other times
FULL-DUPLEX. In FULL-DUPLEX everything worded great. The problem was
that the network usually started up in HALF-DUPLEX. The solution is the
change 'Link Auto Sensed" to "NO", and 'Link Duplex" to "FULL"

I don't recall the command syntax to make these changes, I am sure
someone on the list will recall, but it did take care of our problem.


--
Michael Anderson
Spring Independent School District
16717 Ella Boulevard
Houston, Texas 77090-4299
office: 281.586.1105
fax: 281.586.1187
-

>>> NTC John Pitman <[log in to unmask]> 06/05/02 09:11AM >>>
We are getting significant pauses in traffic over devices on our network
-
terminal just hangs for 5-10 seconds periodically. Altogether we have ~
150
terms, many local to the system are serial, many are virtual
connections.
These are all hanging off 1 NIC (N series, 220Mhz). Is it likely we will
get
an improvement if we add another NIC? We are thinking along the lines of
1
NIC for local head office DTCs, and another to handle the lines going
out to
remote offices.

Any experience out there please?

Thanks,

John Pitman
NTC Riyadh
01) 477 4710 X 1104
056447214

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

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