pigeon@ndcheg.cheg.nd.edu (Rich Pigeon) (06/07/89)
After much dismay and frustration in the attempt to "upgrade" from a FastPath 3 to a FastPath 4, I have finally come up with a scheme that is working very well.
Our setup:
Sun 3/50 as a file server (4.2 BSD - Release 3.5)
(129.74.6.8 ndcheg.cheg.nd.edu)
CAP 5.0 (AUFS, lwsrv, papif)
KIP 06/88 (atalkad -- reading /etc/atalkatab)
K-STAR Download (v5.0.3) on FastPath 4 (129.74.6.193 / PROM 4.1)
LaserWriter located on appletalk side
Many of the symptoms encountered during the upgrade typically involve atlook notbeing able to see any hosts on the appletalk side. Telenet services work fine
but AppleShare services do not. Other symptoms include services appearing
intermittently, or possibly having AUFS and Telnet functioning but not being
able to locate devices (such as printers) on the appletalk side.
My /etc/atalkatab
55.6 N1 129.74.6.0 Ethernet #ms ob
56.1 K 129.74.6.193 apple-cheg #chem.eng.appletalk
I129.74.6.193 I129.74.6.8 #ipbroad ipname
I129.74.6.8 L0 #ipdebug ipfile
L0 L0 L0 L0 S0 S0 #ipother unused ddprangestart
LX0 S6 S10 #flags ipstatic ipdynamic
S56.1 S55.6 "Ethernet" #atneta atnete zonea
NOTE: K-STAR v5.0.3 and earlier were implemented using the old UDP port
numbers (starting at 768), while in April 1988, NIC assigned UDP port
numbers ranging from 200 to 328 to be used by KIP. This has been
a major source of configuration problems. Since we are using K-STAR
v5.0.3, our ddpstartrange has been set to S0 (i.e., 768 by default).
Kinetics has now released K-STAR v7.0 which allows the newer
ddpstartrange of 200. Call Kinetics technical support at
1-415-947-0998.
Additionally, recall that CAP 5.0 allows the use of the newer port
range by installing entries in /etc/services for use by the getservent.
Be sure to remove these entries if configuring with a version of K-STAR
5.0.3 or older.
My /etc/atalk.local
# mynet mynode myzone
55.6 8 Ethernet
# bridgenet bridgenode bridgeIP
55.6 193 129.74.6.193
FastPath 4 Configuration: (using FastPath Manager II v4.1)
----------------------------------------------------------------------------
Download File: K-STAR v5.0.3
Configuration: K-STAR
LocalTalk Side
AppleTalk Zone Name apple-cheg
AppleTalk Net Number 14337
AppleTalk Node Number 220 #dynamically assigned
Ethernet Side
AppleTalk Zone Name Ethernet
AppleTalk Net Number 14081 #NOTICE: This 16-bit number
should actually be 14086. More
on this later.
AppleTalk Node Number 230 #dynamically assigned
IP Information
IP Address of FastPath Box 129.74.6.193
IP Subnetwork Mask 255.255.255.0
IP Broadcast Address 0.0.0.0
IP Address of Default Router 0.0.0.0
Administrator
IP Address of Administrator Host 129.74.6.8
UDP Side
AppleTalk Zone Name *
AppleTalk Network Number 0
AppleTalk Node Number 193
Servers
IP Address of Name Server 0.0.0.0
IP Address of File Server 0.0.0.0
Local Parameters
Parameter #1 0.0.0.0
Parameter #2 0.0.0.0
Parameter #3 0.0.0.0
Parameter #4 0.0.0.0
Option Flags: None are set.
Switches
Auto Config No
Remote Boot Yes
Table Sizes
Dynamic Addresses 10
Static Addresses 6
-------------------------------------------------------------------------------
When we tried to specify the UDP side with the same inforamtion as the Ethernet
side, AUFS worked fine, along with Telnet, but we could not print from Ethernet
to the LocalTalk LaserWriters.
Putting in the IP Broadcast Address caused
problems on the LocalTalk side that weren't readily apparent. Although all
LaserWriters would appear in the chooser, an NEC SilentWriter would not print
on a regular basis. It would signal that it was processing the document, but
no file would would actually print. (We have had other problems with this
LaserWriter in the past -- seems to be very sensitive to problems in the
network.)
When the "correct" AppeTalk Net Number (Ethernet Side) is used (i.e., 14086
for our case), atlook can no longer locate hosts on the localtalk side!!
LaserWriter services are no longer functional when attempting to print from
Ethernet to a LocalTalk LaserWriter. Although AUFS and Telnet work good.
I have tried numerous combinations in the attempt to get all desired services
working -- the final configuration that finally worked was obtained more by
persistance and chance, rather than anything that makes sense.
For our functional configuration, the following occurs:
Running look on the LocalTalk side, gives an "incorrect" AppleTalk internet
connectivity as reflected by the RTMP packets:
00 12 01 01 01 38 01 08 DC 38 01 00 37 01 00 37 06 00
trans: 0 18 1 1 1 56 1 8 220 56.1 0 55.1 0 55.6 0
The incorrect packets are the set of three that are second from the
last (37 01 00). These resulted from the the AppleTalk Node Number
on the Ethernet side being specified as 14081 instead of the "correct"
value of 14086. When we do use 14086, the RTMP packets reflect
AppleTalk internet connectivity as it should theoretically be, but
as I mentioned previously, this did not work for us.
Listed below are some attempts that failed:
1. SetUp:
FP Manger (v2.0)
gw.srec
prompt.config (with correct ethernet address)
ddpstartrange = 200
Result: All services show up, but localtalk side especially
intermittent. Effects all localtalk hosts, including localtalk TOPS
servers and clients.
2. SetUp:
Same as 1, but ddpstartrange = 768
Result: essentially the same as 1. (This setup has been reported to
work for others, but did was not satisfactory in our case.)
3. SetUp:
FP Manager II (v4.1)
gw.srec
promt.config
Result: No localtalk laserwriters even appear in the chooser. Other
services available but intermittent.
Hope this gives some useful insight.
Richard Pigeon
pigeon@ndcheg.cheg.nd.edu
University of Notre Dame
Dept. of Chemical Engineering
Notre Dame, IN 46556 minshall@kinetics.UUCP (Greg Minshall) (06/08/89)
From article <673@ndcheg.cheg.nd.edu>, by pigeon@ndcheg.cheg.nd.edu (Rich Pigeon): ... > My /etc/atalkatab > > 55.6 N1 129.74.6.0 Ethernet #ms ob > 56.1 K 129.74.6.193 apple-cheg #chem.eng.appletalk > I129.74.6.193 I129.74.6.8 #ipbroad ipname > I129.74.6.8 L0 #ipdebug ipfile > L0 L0 L0 L0 S0 S0 #ipother unused ddprangestart > LX0 S6 S10 #flags ipstatic ipdynamic > S56.1 S55.6 "Ethernet" #atneta atnete zonea I don't understand why you have "I129.74.6.193" set as the IP broadcast address. I would expect a number (from your subnet mask in the K-STAR data) like I129.74.6.255 (or I129.74.6.0, if your CAP host is a 4.2 machine). > > FastPath 4 Configuration: (using FastPath Manager II v4.1) ... I always suggest that people using atalkad (ie: specifying the IP address of the administrator host) leave everything "blank" ("*"s for zone names, 0's for network numbers) except the IP address of the KFPS AND the IP address of the administrator host (host running atalkad). [Plus whatever options, including the all-important option 4; plus turning on the Remote Boot switch.] ... > > When we tried to specify the UDP side with the same inforamtion as the Ethernet > side, AUFS worked fine, along with Telnet, but we could not print from Ethernet > to the LocalTalk LaserWriters. OK. When you are using "IP talk" (ie: Appletalk encapsulated in UDP in IP), your fastpath has 3 *separate* DDP networks. The first runs over LocalTalk. The second runs over EtherTalk (though FastPath manager calls it "Ethernet side"). The third runs over IPtalk (though the FastPath manager calls it "UDP Side" or some such thing). THESE ARE THREE SEPARATE NETWORKS! They need to be configured with three separate (distinct) network numbers! If you don't do it, it doesn't work right. (Again, my standard apology for the state of the current Kinetics' documentation, and a sincere acknowledgement that I don't wonder why everyone DOESN'T know this - I more wonder how anyone ever figured it out - it just isn't well documented.) So, if network number X is set for the EtherTalk network, you may not use network number X for the IP talk network. (Some of the confusion here revolves around the question "what is a network?" After all, the IP talk network and the EtherTalk network run on the same cable; aren't they, therefore, the same network? My partial answer is that, for a broadcast network, a network is the union of all machines that receive and understand a particular node's broadcast packets.) One additional point, the "atnete" entry in "atalkatab" relates to the IP talk network, NOT the EtherTalk network. > Putting in the IP Broadcast Address caused > problems on the LocalTalk side that weren't readily apparent. Although all > LaserWriters would appear in the chooser, an NEC SilentWriter would not print > on a regular basis. It would signal that it was processing the document, but > no file would would actually print. (We have had other problems with this > LaserWriter in the past -- seems to be very sensitive to problems in the > network.) The above puzzles me, but I wonder what value for "IP Broadcast Address" you used. I hope this helps a bit. Greg Minshall 1-415-947-0998 minshall@kinetics.com Kinetics, a division of Excelan, Inc.