HP3000-L Archives

March 1997, Week 1

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:
Joe Geiser <[log in to unmask]>
Reply To:
[log in to unmask][log in to unmask]> at ~INTERNET
Date: 3/4/97 7:51 PM

Hi,
I just found out about this group and will be joining in the fun. Please
excuse any transgressions until I get my feet suitably wet. Any suggestions
for a new person would be welcomed. [...]45_6Mar199708:49:[log in to unmask]
Date:
Fri, 7 Mar 1997 17:07:58 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (83 lines)
----------
> From: Chuck Duncan. <[log in to unmask]>
> To: [log in to unmask]
> Subject: Frame Relay issues
> Date: Friday, March 07, 1997 10:03 AM
>
> We are considering converting our HP3000 56Kb and fractional T1 (4
DSO's) to
> frame relay.  Our current Hardware configuration typically is Codex 3500
DSU,
> HP Router ER or FR, 56Kb DDS, DSU, Router, and HP DTC 2345A with an
Advance
> Stack Hub or two.  We are using WRQ 3000 connection for DOS (requirement
of
> client server DOS program from third party vendor) via TCP/IP.  System
> config's include 979's and 992 with 5.5.
>
> Does anyone know of any issues or have suggestions?

Chuck,

I once put up a complete frame relay network including WAN connections and
one link to the 'net.  Depending who the carrier is, it can be quite
painless.

Here's what you need to think about...

1.  You'll be routing, not bridging.  All DTC traffic, with the exception
of those DTC's which can be routed via TCP/IP (the DTC16RX/72RX) will be
bridged (so bridging will need to be turned on for the routers).

2.  Netware networks at each location should have different Net numbers on
a routed network.

3.  Plan. Plan. Plan!  Each location should either have their own Class C
IP Space, or subnet an existing Class C.  If you plan on a net connection
- get registered IPs.  It's a good idea anyway - and do it now, as
InterNIC is planning to start charging some hefty fees for IP Addresses in
the not too distant future, if what I;m reading is correct.

4.  Also under planning --- which site can see which other site?  Make a
network map --- and start planning as to which site can have access to
each other site.  Will there be a "hub" site --- a site which all other
sites come through?  Can this hub site handle the other traffic?  Can the
Router handle all of the traffic?

5.  Lastly, but most important --- pick a carrier who has experience with
Frame Relay.  Of these, I've been able to recommend:

   - CompuServe Network Services (they've been doing frame relay since
before people knew about it :-)
   - Bell Atlantic (if you're in the Northeast)
   - AT&T (although pricey now, it might come down with competition with
the Local Bells)
   - MCI  (has been doing frame relay for about 5-7 years)

   (CompuServe Network Services is NOT the Information Service --- it's a
totally separate division)

   - Advantis (This net is run by, ahem, IBM, and carries Prodigy.  The
net is a good one - I won't say much about Prodigy though)

Good Luck --- you'll find that you should see some nice performance under
Frame Relay.  One last thing to remember is that Frame Relay is good when
your sites are far away, not around the corner.  The further away the
site, the lower the cost.  Yes --- this is true.  The basic premise is
that the "long distance" portion is the private frame relay network
provided by the carrier, and you're not paying long distance prices ---
just for the throughput, bandwidth, etc.  The only "line" you will be
paying for is the local loop on each end from the POP to the site.

Joe Geiser

----------------------------------------------------------------------
Joe Geiser
CSI Business Solutions
140 Bristol-Oxford Valley Road, Suite 102
Langhorne, PA 19047-3083
Toll Free (US/Canada): (888) 956-9812
[log in to unmask] (at work)
[log in to unmask] (at play)
----------------------------------------------------------------------

ATOM RSS1 RSS2