Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
Hello, I've never used so far the DEChub, but I'm involved in a deal whose objective (among many other things) is to connect 43 remote sites to a "data center". I'm trying to understand whether DEChub can be a Trojan horse for us. Each remote site has only a bunch of PCs which currently use telephone lines (low speed switched lines: 2400 baud) to establish a connection to central hosts (old Philips P4700s we wish to replace with ALPHA systems). To date, the number of PCs per site is by all means less than 8, and are served by a multiplexer (at each site). My very naive questions are: 1)we want to replace the MUXs, as well as the Philips P4700. Can we effectively use e.g. a (standalone) DECserver 90TL at each site to "concentrate" the PCs? What do I need (hw. + sw) to build such a star configuration? Do I also need a router (if TCP/IP is not required) in the DEChub? 2)if I remember well, a DECserver 90TL can be loaded by a PC with Pathworks/DOS. Can you confirm? 3)suppose I want to use the Internet suite of protocols. I need a TCP router, I gather. Is our current offer limited to the Wanrouter 90? 4)would you please give me some more info. on DEChub900 , DEChub900MS, and explain in a few words the differences between these hubs and the DEChub 90? Is the MS model capable of doing port switching? And what about management? Can we do anything more than turning ports off/on through SNMP directives? The reason for this question is that I want to assess which model is best suited for the customer's requirements. Thanks in advance for your replies Fabio
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
152.1 | dechub900/MS | RTOIC::CQ386::wrieger | This Note�s for You ! | Thu Feb 18 1993 05:51 | 24 |
Hello Fabio, If you wish to integrate 43 locations with each 8 PC you have to use 1.) Pathworks for DOS (on each PC the whole Software H-Kit as disks) to get best access to the ALPHA (VMS) 2.) install in one PC the ETHERworks router (only a board) to get X.25 connection to the ALPHA 3.) use DECrepeater 90T to integrate all PC's that's it. DEChub900/900MS DEChub900 "big brother" of DEChub90 with internal 2 Thinethernet, 2 TokenRing, 1 FDDI and 1 flexible Channel. Modules will be available for all this Topologies in a couple of month. Chouse between E-net 1/2, TokenRing 1/2 to seperate your LAN trafic. Finde infofiles on EMDS::Management get infos from EMDS::SEAVER (Bill Seaver)??!! DEChub900 MS has 12 flexible channels which can define as E-Net, TokenRing, FDDI, in future ATM or others. Wolfgang | |||||
152.2 | Remote Office Program developing DEChub 90 modules | MEMIT::FORREST | Thu Feb 18 1993 12:32 | 15 | |
Fabio, you didn't say what protocol is being used between the PCs and the Phillips machine. Is it X.25, as suggested in .1, or is it perhaps Telnet or LAT? Depending upon when the equipment has to be deployed, you may want to check into the products that are being developed by CSS in Australia for just such remote connectivity problems. Contact Peter Ambrose at SNOC01::AMBROSEP. And CSS in Annecy is developing something for ISDN. These all will play in the DEChub 90, or standalone. Contact Phillipe Roussin-Moynier @AEO. jack | |||||
152.3 | ROM01::CENCI | sono dolce come un toblerone | Fri Feb 19 1993 06:02 | 16 | |
Thanks a lot Wolfgang & Jack. Your replies are very interesting and so are your pointers. Re. Jack: I think the customer will foster X25 to connect the remote sites. I'll post a note when we're given the green light Best regards Fabio |