ief@geocub.UUCP (06/12/87)
In our lab, we have a TCP/IP Ethernet network and a Network System Corp. HyperchannelB network. Thus we are naturally leaded to imagine a gateway between them : this gateway seems a rather difficult problem. More precisely, people are interested in file transfer between their minicompiters and mainframes on Hyperchannel (IBM 3090 and Sperry 1100). Has anybody tried to have something work, or does anybody know of some experience elsewhere ? P.Garda
dpk@BRL.ARPA.UUCP (06/14/87)
I know of no gateway that one can plug in and run between a TCP/IP network and a Hyperchannel. If you can obtain TCP/IP for the IBM and/or the Sperry (they do exist), then you could make one minicomputer a gateway by giving it an interface on both the Hyperchannel and the other TCP/IP networks. Here at BRL, we have a Hyperchannel connecting our CRAY to a Gould PN6000 which is in turn connected to the building Ethernet. The Gould runs UTX2.0 (4.3BSD) and acts as the IP gateway between the Hyperchannel and the Ether. The key is getting the same protocol suite on both machines. -Doug-
mac@idacrd.UUCP (Bob McGwier) (06/17/87)
in article <153@geocub.UUCP>, ief@geocub.UUCP (Didier Demigny ) says: > > In our lab, we have a TCP/IP Ethernet network and a Network System Corp. > HyperchannelB network. Thus we are naturally leaded to imagine a gateway > between them : this gateway seems a rather difficult problem. > > More precisely, people are interested in file transfer between their > minicompiters and mainframes on Hyperchannel (IBM 3090 and Sperry 1100). > > Has anybody tried to have something work, or does anybody know of some > experience elsewhere ? > > P.Garda We use a sun3 as the gateway between the hyperchannel which talks to our Cray's and the "rest of our world" on our ethernet. We even have NFS running on all. This is meant as encouragement ONLY this software will never leave the building. Bob
woods@hao.UCAR.EDU (Greg Woods) (06/17/87)
In article <250@idacrd.UUCP> mac@idacrd.UUCP (Bob McGwier) writes: >in article <153@geocub.UUCP>, ief@geocub.UUCP (Didier Demigny ) says: >> >> In our lab, we have a TCP/IP Ethernet network and a Network System Corp. >> HyperchannelB network. Thus we are naturally leaded to imagine a gateway >> between them : this gateway seems a rather difficult problem. We have the same situation. I wrote a hyperchannel server that runs on the gateway VAX 750 (attached to both Ethernet and hyperchannel) for non- hyperchannel Ethernet machines to submit jobs to the CRAYs (on hyperchannel only, of course). I created a local "ntwk" port (in /etc/services) and the hyperchannel gateway server just listens on this port for a connection in the same manner as any other TCP server and handles submitting the job to the appropriate CRAY when it comes in. Such a server is not hard to write, I'd be glad to send you mine if you think it would help (but it might be easier to write your own; it was not written to be portable and does have some site-dependent code in it). It turns out that the problem of what to do with outputs coming back from the CRAY is a LOT harder. I had to modify our local hyperchannel software to check each returned output file to see if it belonged to a job that was submitted from an Ethernet host, and if so, connect to yet another server running on the submitting host (also fairly easy to write) and send the output across the Ethernet. The hyperchannel changes were by far the hardest part of this and are COMPLETELY implementation dependent and therefore useless to anyone else. However, a similar design could probably be used for those wishing a similar capability. >This is meant as encouragement ONLY this software >will never leave the building. I'd be happy to mail you any of my software, it is public domain. However, because it is implementation-dependent, it probably would be useful only as a guide in designing your own. --Greg -- UUCP: {hplabs, seismo, nbires, noao}!hao!woods CSNET: woods@ncar.csnet ARPA: woods%ncar@CSNET-RELAY.ARPA INTERNET: woods@hao.ucar.edu
vns@mhres.UUCP (Gertjan Vinkesteyn) (06/23/87)
In article <8706141434.aa06229@SEM.BRL.ARPA>, dpk@BRL.ARPA (Doug Kingston) writes: > I know of no gateway that one can plug in and run between > a TCP/IP network and a Hyperchannel. If you can obtain > TCP/IP for the IBM and/or the Sperry (they do exist), then > you could make one minicomputer a gateway by giving it an > interface on both the Hyperchannel and the other TCP/IP > networks..... Convex has TCP/IP and Hyperchannel, as well as DECNET in their machines. -- Real-Name: Gertjan Vinkesteyn UUCP and other network: ..!seismo!mcvax!mhres!vns This note does not necessarily represent the position of Multihouse NV Therefore no liability or responsibility for whatever will be accepted.
rroot@edm.UUCP (uucp) (06/30/87)
In article <8706141434.aa06229@SEM.BRL.ARPA>, dpk@BRL.ARPA (Doug Kingston) writes: > I know of no gateway that one can plug in and run between > a TCP/IP network and a Hyperchannel. If you can obtain > TCP/IP for the IBM and/or the Sperry (they do exist), then > you could make one minicomputer a gateway by giving it an > interface on both the Hyperchannel and the other TCP/IP .... There is currently some work at the University of Alberta computing services trying to build a hyperbus/TCP gateway box. I didn't see the original posting, so if somebody could mail me (a summary of) the original query, I could perhaps comment on how well the UofA work might answer the problem. ------------- Stephen Samuel Disclaimer: You betcha! {ihnp4,ubc-vision,seismo!mnetor,vax135}!alberta!edm!steve -- ------------- Stephen Samuel {ihnp4,ubc-vision,seismo!mnetor,vax135}!alberta!edm!ad!uad
lekash@ORVILLE.ARPA (John Lekashman) (07/03/87)
hi. There are things that will move IP packets between hyperchannels and other networks. vaxes running bsd. suns. Various vendors have mentioned the idea of building it into their gatways. Most that I have seen operate on hyperchannel A, the 50 mbit version. Porting to hyperchannel B should not be that hard. We just don't have any, because ethernets are so much cheaper. There is a spec from NSC on how to encapsulate IP over hyperchannel. It will likely occur as an RFC one day soon. The distribution hyperchannel driver on a BSD tape is broken, and doesn't follow this spec besides. I have drivers for: vaxes running 4.3 BSD. (4.2 is trivial from that) silicon graphics Irises, running 3.5 (or it may be 3.6 by now) you can have these for free. Wollongong has installed this driver on a VMS vax for us, you can probably give them some amount of money for it, but they shouldn't charge you much, because I gave it to them. Availability: public ftp from orville.arpa. I don't guarantee it is as up to date as whatever I last built. I'll probably copy the current version over next week. Upgrades include things to deal with special NSC hardware, so its no great need. john