Re: WAN design -- MIDRANGE-L

I have used the IBM 2210 for similair functionality.  The 2210s
support Dlsw which sends the SNA frames over TCP/IP.  An additional
advantage is that on the host end you only need an Ethernet or
Token-ring no SDLC serial lines to the router from the AS/400.  Dlsw
routes the frames to the AS/400 vie the LAN on the host end, so the
AS/400 thinks the router is on the LAN when it is actually on a standard
SDLC serial line.  Your basic 2210 with serial two ports (One for the
frame and one for the 53/5494) + Enet is pretty cheap too.

  This solution also minimizes SNA timeouts and traffic over the Frame
as do the Vanguards.

  Larry Bolhuis
  Arbor Solutions, Inc
  lbolhui@ibm.net

Carl Galgano wrote:
> 
> Dave:
> I have done the connectivity to FR 2 ways.
> 1.  Total TCP/IP, using the Ethernet port on the AS400, Cisco routers and
> MCI FR.  This has worked very well, but the support was only for PCs
> connected, no dumb terminals.  I guess you could use a 5494 that connected
> ethernet to the router  and then hang some dumb tubes off the twinax ports.
> 
> 2.  SNA over RF using Motorola Vangurad family MP routers.  V35 connection
> to the Vanguard, supporting dumb tubes hung off a 5494.
> 
> Both solutions work well.  The SNA over FR is more complicated to set up,
> but once in place works well.  I guess the bottom line is how much SNA
> traffic do you need to handle.  If you are only doin IP, I'd go for #1.  The
> cost of the Vanguard routers may offset the savings of using the green
> screens. If I were you, I'd keep it the same for each location, either all
> TCP/IP or all SNA over FR.
> 
> Just my opinions, let me know if you have any specific questions.
> 
> Carl
> 
> Carl Galgano
> EDI Consulting Services, Inc.
> http://cgalgano.home.mindspring.com
> mailto://cgalgano@ediconsulting.com
> (770) 422-2995
> 
> -----Original Message-----
> From: BORING, David <dboring@shl.com>
> To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com>
> Date: Friday, October 02, 1998 8:31 PM
> Subject: WAN design
> 
> |I've got a project coming up where I will have the ability to completely
> |renovate a client's LAN and WAN. I would like to get some input from all
> |of you who may be using some of these topologies to see what seems to
> |work best with the AS/400.
> |
> |First off, we will try to go TCP/IP over Ethernet as much as possible,
> |replacing most green-screen terminals with PC's, but we will probably
> |end up with a couple small sites using twinax terminals (1 terminal and
> |1 printer that get used 15 minutes every other day is not what we want
> |to try to support as a PC). My first thought is to put everything onto
> |frame relay and use some routers to connect all the sites. Most sites,
> |except the small ones, would probably get connected with a T1 line into
> |the frame relay network. Could any of you shed some light on your WAN's
> |and how you have them set up? Especially in regards to the routers (I'm
> |green on them) and how you handle sending SDLC traffic across the frame
> |relay network; I've read here about problems some of you have had in the
> |past with SDLC over frame relay and I'm curious what solved the problem.
> |
> |We are also considering printing options. We currently have
> |twinax-connected laser printers and a 6252 printer in place. We are
> |thinking of replacing the twinax-connected laser printers with HP
> |LaserJet 8000's with a MPI Blue Kit IPDS chip and a JetDirect card. We
> |are also considering replacing the 6252 with something faster, such as a
> |6262. What are you doing for printing to the laser printers? Should I
> |use the MPI twinax cards as well or stick with a pure Ethernet
> |environment? What are all of you doing for your high speed impact
> |printing? Especially in a TCP/IP Ethernet environment.
> |
> |Sorry for the long post and all the questions, but I would appreciate
> |any information anybody could provide. Please feel free to E-mail me
> |directly at: dboring@shl.com .
> |
> |Thanks in advance!
> |
> |David Boring
> |Systems Engineer
> |MCI Systemhouse
> |Direct: (562) 809-5460
> |E-mail: dboring@shl.com
> |
> |+---
> || This is the Midrange System Mailing List!
> || To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> || To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> || To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> || Questions should be directed to the list owner/operator:
> david@midrange.com
> |+---
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---