hodson@hwee.UUCP (Ian Hodson) (02/23/91)
Im having a few problems setting up the departments apollo network We just got 6 DN4500's. The main problem is the gateway onto the department ethernet. One node is set up as a gateway, but when I run tcp/ip on the apollo ethernet, the system seems to communicate in only one direction ie I can rwho, and all the department node respond, but rlogin hangs with no response. When I only run tcp on the gateway I can rlogin to the remote net fine, however the rest of the apollo's dont see the remote network... Any ideas? Another minor thing is the crp program seems to hang after a few commands! It then needs to be killed to clear the connection. Help would be welcome, as these machines are new to me, and I seem to be going round in circles :-) Yours Ian. config is 6 x Dn4500 (16Meg 330Meg disks) ethernet Domain/OS 10.2 rest of the department is a mix of suns,hp's,dec's and other misc unix boxes. _______________________________________________________________________________ | Ian Hodson , Electrical Engineering | hodson@uk.ac.hw.ee (best) | | Heriot-Watt University, Mountbatten Bldg | eeeidh@uk.ac.hw.clust (worst) | | Grassmarket , Edinburgh , Scotland , UK | hodson@UUCP.hwee (ok) | -------------------------------------------------------------------------------
thompson@pan.ssec.honeywell.com (John Thompson) (02/25/91)
Ian (et.al.) -- > <<forwarded message>> (text re-ordered for clarity) > Im having a few problems setting up the departments apollo network > We just got 6 DN4500's. Config is 6 x Dn4500 (16Meg 330Meg disks) > ethernet Domain/OS 10.2. The rest of the department is a mix of > suns,hp's,dec's and other misc unix boxes. > The main problem is the gateway onto the department > ethernet. One node is set up as a gateway, but when I run tcp/ip on the > apollo ethernet, the system seems to communicate in only one direction > ie I can rwho, and all the department node respond, but rlogin hangs > with no response. When I only run tcp on the gateway I can rlogin to > the remote net fine, however the rest of the apollo's dont see the remote > network... Any ideas? When I first read this, I said 'subnets -- no question.' When I got to the end and noticed the configuration, it changed to 'question.' You say that the Apollo's are gateway-ed onto the main department ethernet. Does this mean that they're on a separate piece of cable? If not, then there's no reason to have the gateway, and I suspect that your problem is being caused by having the nodes think they need to go through somebody who doesn't think they need to go through him. More likely, you have a second piece of wire, and your gateway node has 2 controllers, and is on 2 ethernets. If this is true, the likely problem is subnets. (In case you aren't familiar w/ it, subnets are simply a means of breaking up your one local tcp/ip network address into several sub-networks. The outside world treats them all as one network, but inside, you treat it as several. For instance, honeywell.com has a class B network address of 129.30.x.y. From the outside world, the "x.y" combinations give a potential of ~ 65000 systems on the same network. Since Honeywell is not all in one building (and because nobody wants 65000 nodes on one network!), it has been sub-netted. The 3rd byte (the 'x' one) is used to designate which sub network the host 'y' is on. Routing proceeds from the node to the gateway(s) to the recipient, and then back again. The most important thing to note in this is that _all_ hosts (Apollo and otherwise) on the 129.30 net must agree to use the same subnetting scheme. Otherwise, some recipients will think that the message came from their own network, and will not look for a gateway to send through. I suspect that either you don't have subnetting set up (in which case no packets are going across the gateway) or subnetting is set up only on the Apollo side (in which case packets go across, but the reply never gets routed back to your node). > Another minor thing is the crp program seems to hang after a few > commands! It then needs to be killed to clear the connection. No explanation for that one. I have had (almost) no problems w/ crp. The first thing to check out would be the patch tapes. Keep in mind that 'crp' uses the mailbox routines (mbx_helper) and the server_process_manager (spm) to get things set up. -- jt -- John Thompson Honeywell, SSEC Plymouth, MN 55441 thompson@pan.ssec.honeywell.com Me? Represent Honeywell? You've GOT to be kidding!!!
nazgul@alphalpha.com (Kee Hinckley) (02/27/91)
In article <895@hwee.UUCP> hodson@hwee.UUCP (Ian Hodson) writes: >Another minor thing is the crp program seems to hang after a few >commands! It then needs to be killed to clear the connection. If you're using ksh with crp, don't. -- Alfalfa Software, Inc. | Poste: The EMail for Unix nazgul@alfalfa.com | Send Anything... Anywhere 617/646-7703 (voice/fax) | info@alfalfa.com I'm not sure which upsets me more; that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's.
vinoski@apollo.HP.COM (Stephen Vinoski) (03/01/91)
In article <1991Feb26.170351.4759@alphalpha.com> nazgul@alphalpha.com (Kee Hinckley) writes: >In article <895@hwee.UUCP> hodson@hwee.UUCP (Ian Hodson) writes: >>Another minor thing is the crp program seems to hang after a few >>commands! It then needs to be killed to clear the connection. >If you're using ksh with crp, don't. Works fine for me on sr10.3. -steve | Steve Vinoski (508)256-0176 x5904 | Internet: vinoski@apollo.hp.com | | HP Apollo Division, Chelmsford, MA 01824 | UUCP: ...!apollo!vinoski | | "The price of knowledge is learning how little of it you yourself harbor." | | - Tom Christiansen |
root@ttsi.lonestar.org (System) (03/05/91)
In article <50163020.20b6d@apollo.HP.COM> vinoski@apollo.HP.COM (Stephen Vinoski) writes: >In article <1991Feb26.170351.4759@alphalpha.com> nazgul@alphalpha.com (Kee Hinckley) writes: >>In article <895@hwee.UUCP> hodson@hwee.UUCP (Ian Hodson) writes: >>>Another minor thing is the crp program seems to hang after a few >>>commands! It then needs to be killed to clear the connection. >>If you're using ksh with crp, don't. > >Works fine for me on sr10.3. > Much to my dismay, ksh does occassionally lock up when used with crp on sr10.3. /bsd4.3/bin/ls is especially prone to lock up in this configuration. Can anyone explain why? -- Mark S. Evans Tandem Telecommunications Systems Inc. Phone: 214-516-6201 850 E. Central Parkway Fax: 214-516-6801 Plano, TX 75074 Mail: mse@ttsi.lonestar.org