Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!mailrus!ncar!gatech!amdcad!diablo!phil From: phil@diablo.amd.com (Phil Ngai) Newsgroups: comp.dcom.lans Subject: Re: Ethernet terminal servers Message-ID: <24168@amdcad.AMD.COM> Date: 23 Jan 89 23:07:31 GMT References: <6556@fluke.COM> <13718@cup.portal.com> <14843@oberon.USC.EDU> Sender: news@amdcad.AMD.COM Reply-To: phil@diablo.AMD.COM (Phil Ngai) Organization: Advanced Micro Devices, Inc. Sunnyvale CA Lines: 17 | The third alternative, of using a port selector (aka data pbx) | shouldn't be ignored. (We use micoms here at usc, mostly 6600s, When my company adds a host on one of our Ethernets in California, Texas, or Japan, my Ethernet terminal server in California can instantly talk to it, without getting new Micom ports and hooking them up to the new host, without ordering new long lines, and without worrying about running out of Micom ports on the host. Data PBXs are for people who do small networks. Such situations never seem to last. Either they find themselves out of a job, or working on a large network. -- Phil Ngai, phil@diablo.amd.com {uunet,decwrl,ucbvax}!amdcad!phil "In Texas, they run the red light after it turns red." "In Taiwan, they run the red light before it turns green."