HP3000-L Archives

October 1996, 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:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Fri, 25 Oct 1996 23:52:42 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Jeff Sullivan wrote:
> Has anyone installed more than one ThinLAN card(802.3) in their
> HP3000?  If so, why?  Would this, or could this improve the response
> time for systems that have 300+ users accessing the system, or
> would this be used for segmented networks?  When I open the back
> door to our HP3000, and know we have 400 users accessing our
> data through one twisted pair cable, it is quite amazing.

The original 3000/9xx systems (930 and 950) initially *required* two
LANICs if you wanted network services - one services DTC traffic and one
for TCP/IP traffic.  It was only later that I leared that the two could
be combined on one.

We initially had them on separate LAN segments to isolate the DTC
traffic from the campus LAN, but no longer after installing a telnet
card in a DTC.  It was *very* handy when we changed TCP/IP addresses; we
simply cranked up TCP on the DTC link with the old address, put the new
address on the TCP LANIC, and restarted the network.  After everyone had
changed their addresses, we just deactivated TCP on the DTC LANIC.  If
the LANIC fails on TCP, you can quickly switch it to the other LANIC.
You can't switch the DTC LANICs without a restart, however [AFAIK].

Not sure what gains you'd get running the two on the same ethernet
segment.  It won't do load-sharing automatically (they must have unique
TCP addresses, and you have to figure out how to split the load).

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2