Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site amdcad.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!amdcad!phil
From: phil@amdcad.UUCP (Phil Ngai)
Newsgroups: net.dcom
Subject: Re: info on micom dataswitches???
Message-ID: <1518@amdcad.UUCP>
Date: Wed, 5-Jun-85 00:28:17 EDT
Article-I.D.: amdcad.1518
Posted: Wed Jun  5 00:28:17 1985
Date-Received: Thu, 6-Jun-85 08:11:02 EDT
References: <1359@amd.UUCP> <2872@fritz.UUCP>
Reply-To: phil@amdcad.UUCP (Phil Ngai)
Organization: AMD, Sunnyvale, California
Lines: 24

In article <2872@fritz.UUCP> zemon@fritz.UUCP (Art Zemon) writes:
>The M600 is the "heart" of Micom's local area non-Ethernet
>network.  Micom makes a large number of multiplexors (both
>time-division and statistical) ranging from 4 to 128 lines.
>Most of these are available either as standalone units or as
>cards for the M600.

Yes, and if you have to use stat muxes your cost per line goes way up.
My main point is that the Instatrunk system is neat BUT you have to
be able to lay 1.5Mbaud copper. If you can't, things get more expensive.

Also, when configuring an Instatrunk (or stat mux, for that matter)
remember that each bay only holds a certain number of "virtual" cards,
whether or not you actually have a particular number of physical cards.
One instatrunk module can eat up a whole bay all by itself...

How about some comments on the competition? Like Equinox or Gandalf?
Or even ATTIS ISN (is that what they're calling datakit these days?)
-- 
 People do what management inspects, not what management expects.

 Phil Ngai (408) 749-5720
 UUCP: {ucbvax,decwrl,ihnp4,allegra}!amdcad!phil
 ARPA: amdcad!phil@decwrl.ARPA