jeffl@SPECTRUM.CS.UNSW.OZ.AU (Jeff Lee) (04/11/91)
Hi:
I have been trying to install CAP6.0 on SUN SPARC 1+ with SHIVA FastPath4 box
on the network. The installation of CAP seemed OK, and the FasPath box seemed
OK because I am able to do ftp using SUMac/IP. (I think the FastPath box is OK..)
However on the CAP end, I do not have much joy. When I tested out using atlook,
I do not see anything.
My questions are:
(a) How do you set atalk.local file ? (I think I may made an error
here.
(b) I may have missed out something, but what ?
My configuration are as follows:
My atalk.local file is:
81 1 "syscon_iptalk"
81 24 129.94.168.24
81 1
the configuration of the network is as follows:
129.94.128.249 129.94.168.1 129.94.168.24
_____________________ ______________________________________________
| | |
------------------------ -----------------
| SUN Sparc running CAP| | Fastpath4 |
------------------------- ----------------
The SUN has 2 ethernet channels, le0 with IP address 129.94.128.249 and
le1 with 129.94.168.1 (the name is syscon). The fasthpath is on
the network 129.94.168.0 and the address for the fastpath is 129.94.168.24
We install CAP, and tested out using atlook. We are not able to see the
appletalk devices on the network. So we did a etherfind to see what is going
on. Etherfind gives us the following information:
short DDP from 193.1 to broadcast.1 RTMP of 21 data bytes
UDP from syscon.sc.ee.unsw.OZ.AU.route to 129.94.168.0.route 512 bytes
UDP from syscon.sc.ee.unsw.OZ.AU.route to 129.94.168.0.route 512 bytes
UDP from syscon.sc.ee.unsw.OZ.AU.route to 129.94.168.0.route 512 bytes
UDP from syscon.sc.ee.unsw.OZ.AU.route to 129.94.168.0.route 412 bytes
short DDP from 193.1 to broadcast.1 RTMP of 21 data bytes
short DDP from 193.1 to broadcast.1 RTMP of 21 data bytes
This seems to indicate that the fastpath box is running, and the SUN
is able to see the appletalk packets.
The fastpath box is configured as follows:
LOCALTALK Interface:
Appletalk Zone Name: syscon_appletalk
Appletalk Net Number: 80
Appletalk Node Number: 220
EtherTalk Phase 1:
Appletalk Zone Name: syscon_etalk1
Appletalk Net Number: 82
Appletalk Node Number: 193
EtherTalk Phase 2:
Range Start: 0 Range End: 0
ETalk 2.0 Net Number : 0
IP Information:
IP Address of FastPath Box: 129.94.168.24
IP Subnetwork Mask : 255.255.248.0
IP Broadcast Address : 0.0.0.0
IP Address of Default Router: 129.94.168.1
Administrator:
IP Address of Administrator Host: 0.0.0.0
IPTalk Interface:
Appletalk Zone Name: syscon_iptalk
Appletalk Network Number: 81
Appletalk Node Number: 24
Number of IP Clients:
Dynamic: 16
Static: 0
Servers:
IP Address of Name Server: 129.94.128.12
IP Address of File Server: 129.94.168.1
Local Parameters:
Parameters #1 to #4 are 0.0.0.0
Option Flags:
Flags set: 6, 11, 17 and 18
LOG Messages from Fastpath Mamager on the box:
KFPS AT* 199 ET* 193 PROM REV 4.1 (88/10/07) STATE=DOWNLOAD VALID
HW STATUS=0
K-STAR FastPath AT node 199, ET node 193, ET2.0 net 0, ET2.0 node 0,
84 buffers (30 for ethernet), revision 8.0, Option Flags: 6, 11, 17 and 18.
NOTE: Flags 17, 18 are set, so EtherTalk Phase 1 only is used.
Questions:
Your help will be very much appreciated.
regards,
-jeff Lee (jeffl@spectrum.cs.unsw.oz.au)rapatel@khnphwzhn.njin.net ( Rakesh Patel) (04/12/91)
You seem to have set up everything properly, but you didn't mention whether you started up atis or not. You need to start up atis first, give it a few seconds, then you should be able to use any of the CAP clients. Rakesh Patel.
alanlevy@ux1.cso.uiuc.edu (Alan Levy) (04/12/91)
rapatel@khnphwzhn.njin.net ( Rakesh Patel) writes: >You seem to have set up everything properly, but you didn't mention >whether you started up atis or not. You need to start up atis first, >give it a few seconds, then you should be able to use any of the CAP >clients. atis does not have to be running in order to utilize all of CAP's clients. It is not needed for atlook (looking for AT devices) or getzones (looking for AT zones). atis IS needed is you want to use aufs or lwsrv (the server or laserwriter spooler). But for atlook and getzones, atis does not have to be running. Alan LEvy alevy@uiuc.edu
rapatel@khnphwzhn.njin.net ( Rakesh Patel) (04/13/91)
In article <1991Apr12.052732.1896@ux1.cso.uiuc.edu> alanlevy@ux1.cso.uiuc.edu (Alan Levy) writes: > atis does not have to be running in order to utilize all of CAP's clients. > It is not needed for atlook (looking for AT devices) or getzones (looking > for AT zones). > > atis IS needed is you want to use aufs or lwsrv (the server or laserwriter > spooler). > > But for atlook and getzones, atis does not have to be running. > > Alan LEvy > alevy@uiuc.edu Not quite. He is running under CAP 6.0, which has some changes. All the cap clients require etalk.local to be created and updated apropriately, and atis ensures that that is done - even under IPTalk. You can manually create the file if you want, then atis is not required, but most sites tend to want to use one of aufs or lwsrv, or at least have snitch running to indicate the unix machine is on the appletalk network. It would just be simple enough to start up atis, then run atlook initially to make sure the CAP 6.0 installation works. Rakesh Patel.
rapatel@pilot.njin.net ( Rakesh Patel) (04/14/91)
In article <Apr.12.15.53.48.1991.488@khnphwzhn.njin.net> rapatel@khnphwzhn.njin.net ( Rakesh Patel) writes: > All the cap clients require etalk.local to be created and updated apropriately, > and atis ensures that that is done - even under IPTalk. > > Rakesh Patel. Sorry, but I was totally incorrect on this one. The IPTalk based version does not use etalk.local, and atis is not required to be run in order for atlook and getzones to work. Rakesh Patel.