Jerry,
Sounds like you'll be using either Compaq Proliant 4500's or 1500's.
We've got some Proliant Servers connected into an Etherswitch but they're
running Netware 4.1 and are also going thru a router to get to a 3172 so the
thruput numbers that we see aren't relevant since you're saying your 3172
Ethernet connection will be hooked into the Etherswitch also. However, we
do have some Proliant 4500's running NT Advanced Server (mostly Token Ring,
some using Ethernet) using the ADSM V2 client. Our thruput numbers have
been excellent even without playing around with the TCP Windowing and
buffering in the DSM.OPT file.
Tim Pittson
pittson1 AT bwmail1.hcc DOT com
---------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: Re: ADSM hardware examples
Date: Thursday, February 15, 1996 11:40AM
---------------------------- Forwarded with Changes
---------------------------
From: INTERNET.OWNERAD at SNADGATE
Date: 2/15/96 8:32AM
To: Jerry Lawson at TISDMAIL
*To: Multiple recipients of list ADSM-L at SNADGATE
Subject: Re: ADSM hardware examples
----------------------------------------------------------------------------
---
-
A question based on your response below.....
We are considering a special setup for some high capacity servers. The
machines will be Compaq's with a 20G RAID array - there will be 10 of them.
(I have forgotten the model name - they are the twin CPU models with 133Mhz
Pentiums.) We of course want to run the ADSM V2 NT client; our server will
be
MVS ADSM V2 by the time the configuration is in place. These machines will
be
in our data center, and we do not want them on the backbone with our
routers.
Therefore, we are installing a separate Ethernet circuit for them, using
switched Ethernet. As I understand it, this means that each machine will
appear to have a 10Mb network of his own. The ethernet will go directly to
a
3172 - again I am missing the model number, but they are the new Pentium
based
90Mhz machines. Attachment to the Mainframe is via 4.5MB copper cables
(ESCON
could be done, but is not directly available.)
Would you care to speculate on what kind of throughput we might see on this
configuration?
Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Re: ADSM hardware examples
02-15-96 08:32 AM
Hi,
For Novell servers attached to the same 16 Mb Token Ring as one of our
3172-3's, the best thruput we've been able to attain is about 1.2 GB per
hour. However, those are servers with larger average file sizes. More
typical is 500-800 MB per hour for servers with smaller average file sizes.
Restores are typically a little slower.. again, best we've been able to do
is about 800 MB an hour on a restore.
By the way, I haven't noticed any difference in thruput between 10 Mb
Ethernet and 16 Mb Token Ring (we have both attachments into 3172-3s).
From seeing the configuration you've documented, one thing you might
want to check is the TCP/IP configuration on your Novell servers. By
default, Novell will set the maximum segment size (MSS) to 536 bytes when
it's sending TCP/IP packets thru a router or non local segment. In Netware
3.12 and 4.x, it is possible to force TCP/IP to set it's MSS equal to the
outbound interface MTU by adding the following line to sys:\etc\tcpip.cfg
TcpMSSinternetlimit off
This is documented in Novell TID # 1004825. This change seems to have
helped some of our Netware clients who have to go thru routers to get to a
3172-3.
Might also want to consider upgrading to the latest client level
(2.1.02)... there are supposed to be some performance enhancements for the
client (i.e. TCPIP buffering, etc.)
Good luck !!!
Tim Pittson
pittson1 AT bwmail1.hcc DOT com
----------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Date: Wednesday, February 14, 1996 10:11AM
<<File Attachment: WINMAIL.DAT>>
What I am looking for are examples of ADSM specific hardware
implementations. For example, what hardware are you using for the server
and tape drives. How you have configured your media transport, including
topology, if dedicated specifcally for ADSM only and if you pass data across
routers and bridges.
Currently we are using our exsisting network to pass data from the
client(Netware) to the server(IBM9121 MVS) using TCPIP. The data passes
over ethernet thru a Cisco router, to FDDI to another Cisco router, to
ethernet into a IBM 8232. In this configuration it take at least 10 hours
to do a full server restore, about 4 gigs of data. We are in the process of
setting up a dedicate token ring from the clients to a IBM3172. Is there a
better solution? I read about 200 client setups, but our initial 4 client
setup is a non workable solutions.
Server version: v1.r2.level 8 connection states 1.1.13
Client version: 1.02r NLM
|
