paul@aucs.UUCP (Paul Steele) (09/10/88)
I have a small Appletalk net set up which has 2 KPFS 4's bridged to
our Ethernet backbone. I am attempting to install atalkad on our Sun-4
and would like to know if the KStar package that comes with the gateway
is adequate or should I use the KIP stuff that comes with CAP. I was
told that KIP only runs on KFPS 2 and 3, but there is no mention of
KStar in the KIP/CAP documentation. Any info would be appreciate.
--
Paul H. Steele USENET: {uunet|watmath|utai|garfield}!dalcs!aucs!Paul
Acadia University BITNET: Paul@Acadia
Wolfville, NS Internet: Paul%Acadia.BITNET@CUNYVM.CUNY.EDU
CANADA B0P 1X0 (902) 542-2201x587davef@Jessica.stanford.edu (David Finkelstein) (09/14/88)
In article <1248@aucs.UUCP> paul@aucs.UUCP (Paul Steele) writes: >I have a small Appletalk net set up which has 2 KPFS 4's bridged to >our Ethernet backbone. I am attempting to install atalkad on our Sun-4 >and would like to know if the KStar package that comes with the gateway >is adequate or should I use the KIP stuff that comes with CAP. I was >told that KIP only runs on KFPS 2 and 3, but there is no mention of >KStar in the KIP/CAP documentation. Any info would be appreciate. Well, as I understand it, the current implementation of KIP will not run on a Fastpath-4. But I expect that Bill Croft will have a new version out sometime soon. KStar, however, will use atalkad if you want it to, so you can make entries for your KFPS-4's in your existing atalkatab (or, in your case, you can just start running KIP and have the kboxes boot from your Sun). Be careful, though -- we have been unable to get two KFPS-4's in the same zone to work. When the second box is booted, both boxes refuse to give out IP addresss (we are running KIP). We're expecting new PROMs from Kinetics today (and a new version of KStar too) so I hope that solves our problem. If you have problems with two boxes and not one (and you've sure you've configured correctly) you might give Kinetics a call. ------ David Finkelstein Academic Information Resources Stanford University davef@jessica.stanford.edu
moyman@DEGREE.ECN.PURDUE.EDU (J Michael "Mac" Moya) (09/14/88)
> In article <1248@aucs.UUCP> paul@aucs.UUCP (Paul Steele) writes: > >I have a small Appletalk net set up which has 2 KPFS 4's bridged to > >our Ethernet backbone. I am attempting to install atalkad on our Sun-4 > >and would like to know if the KStar package that comes with the gateway > >is adequate or should I use the KIP stuff that comes with CAP. I was > >told that KIP only runs on KFPS 2 and 3, but there is no mention of > >KStar in the KIP/CAP documentation. Any info would be appreciate. and dave replies(parts): > From: Portia!Jessica!davef@labrea.stanford.edu (David Finkelstein) > version out sometime soon. KStar, however, will use atalkad if you > want it to, so you can make entries for your KFPS-4's in your existing > atalkatab (or, in your case, you can just start running KIP and have > the kboxes boot from your Sun). You can make entries in the current atalkatab and atalkad will boot up upon KFPS-4 startup, no problem here. > Be careful, though -- we have been unable to get two KFPS-4's in the > same zone to work. As I said in an earlier letter to the net, I have been unable to get ONE KFPS-4 to work for longer than a minute or two before it pukes its guts out. > that solves our problem. If you have problems with two boxes and not > one (and you've sure you've configured correctly) you might give > Kinetics a call. ^^^^^^^^^^^^^^^ Be patient...I called last week no less than 7 times(tuesday-wednesday-thursday leaving a message each time) before I got through to somebody on friday (and somebody even returned one of my previous calls an hour later!). I have sent them diagnostic and set-up data but still am starting from square one (still waiting for them to get back to me, heavy sigh...only four calls and messages this week). I did notice and alerted them to the fact that if you "print configuration" in the FastPath Manager. On the LaserWriter output, the listed address for the "IP address of Administrater host" will be the same as the "IP Subnetwork Mask" (try it), I REALLY hope that it's just a print routine problem. J Michael Moya Software Support Specialist Engineering Computer Network Purdue University
minshall@kinetics.UUCP (Greg Minshall) (09/17/88)
From article <3647@Portia.Stanford.EDU>, by davef@Jessica.stanford.edu (David Finkelstein): >... > Be careful, though -- we have been unable to get two KFPS-4's in the > same zone to work. When the second box is booted, both boxes refuse > to give out IP addresss (we are running KIP). We're expecting new > PROMs from Kinetics today (and a new version of KStar too) so I hope > that solves our problem. If you have problems with two boxes and not > one (and you've sure you've configured correctly) you might give > Kinetics a call. There is one bad "real" bug in K-STAR and one bad "theoretical" bug in K-STAR (K-STAR being the download module supplied with Kinetics' FastPath 4). The bad "real" bug is the one Dave Finkelstein mentions above: it is impossible to have more than one K-STAR (or one K-STAR and one KIP) box "in the same zone" (which is to say: connected to LocalTalk networks which are in the same zone). The workaround for this bug is, clearly, to keep the LocalTalk zones unique. We recognize that this workaround is not possible in all environments, and *I* (having produced the bug) sincerely apologize for the inconvenience (and confusion) this bug has caused. The bad "theoretical" bug is that K-STAR may, in certain environments, reply to the wrong DDP address when responding to "=:IPADDRESS@*" or "=:IPGATEWAY@*" NBP Lookups. What happens is that K-STAR responds to the source address in the incoming DDP packet; what it should do is respond to the address in the NBP-tuple in the incoming DDP packet. The reason this is a "theoretical" bug is that, in most cases, the two addresses are the same (for an obscure reason having to do with how AppleTalk bridges have traditionally dealt with NBP Broadcast Requests). However, it has come up with one customer testing K-STAR with their own, in-house developed, AppleTalk bridge (which deals with NBP Broadcast Requests in a slightly different, and likely more conformant, manner than many current AppleTalk bridges). Anyone adversely affected by either of the two bugs mentioned above should contact Kinetics technical support at (415) 947-0998 to get in the queue for a fix. Again, apologies for the bugs. Greg Minshall Kinetics, a division of Excelan Inc. (415) 947-0998 2540 Camino Diablo Walnut Creek, CA 94596