CUSTEAD@sask.usask.ca (01/19/89)
We have a net full of fastpath 3's and fastpath 4's, with an Appletalk
Bridge (Shiva) connected as shown:
==================== Ethernet ===================================
| | |
| | |
FastPath X Fastpath 3 Fastpath 4
|
| (localtalk)
|
SHIVA
NetBridge
|
| ZONEC
The Shiva Bridge publishes its own zone. (call it ZONEC) This zone
is not known to the atalkad daemon that manages all of the fastpaths.
If Fastpath X is a fastpath 3, then all of the other 3's acquire ZONEC,
but none of the 4's know about it.
If Fastpath X is a fastpath 4, then all of the other 4's acquire ZONEC,
but none of the 3's know about it.
Each Fastpath seems to share ZONEC with only its own kind!
Fastpath X was made a core gateway for each test.
(The 3's run KIP and the 4's run K-STAR.)
Is there a explanation for this incompatibility??
Larry R. Custead
Univ of Saskatchewan
internet: custead@sask.usask.ca
bitnet: custead@sask
usenet: alberta!dvinci!custeadjpm@sauna.cs.hut.fi (Jussi-Pekka Mantere) (01/21/89)
In article <Added.8XpB3Ty00Ui34Dr08D@andrew.cmu.edu>, CUSTEAD@sask writes: >We have a net full of fastpath 3's and fastpath 4's, with an Appletalk >Bridge (Shiva) connected as shown: > > [ network deleted... ] > >The Shiva Bridge publishes its own zone. (call it ZONEC) This zone >is not known to the atalkad daemon that manages all of the fastpaths. > >If Fastpath X is a fastpath 3, then all of the other 3's acquire ZONEC, >but none of the 4's know about it. >If Fastpath X is a fastpath 4, then all of the other 4's acquire ZONEC, >but none of the 3's know about it. > >Each Fastpath seems to share ZONEC with only its own kind! >Fastpath X was made a core gateway for each test. > >(The 3's run KIP and the 4's run K-STAR.) > >Is there a explanation for this incompatibility?? One promblem may be the "ddprangestart"-parameter in the atalkatab-file. If you use the "new & official" ddprange starting from 200, you will have problems because the current K-STAR version uses the old ddprange starting from 768. So, check your atalkatab-file and check if you have configured the KIP boxes to use the new ddprange: L0 L0 L0 L0 S0 S200 # ipother atnetet ddprangestart ^^^ this should be 0 or 768 If this is the case, change the "200" to "0" or "768". This may solve the problem, but then again, it may not... Hopefully Kinetics will come up with a new version of K-STAR, which will - use the new ddprange - provide filtering of AppleTalk objects (filtering of LaserWriters etc) - have "snmp" built in, as in the 0189 release of KIP from CMU (available from host lancaster.andrew.cmu.edu (128.2.13.21), in /pub) > Larry R. Custead Chape -- Jussi-Pekka Mantere jpm@cs.hut.fi Helsinki University of Technology, Finland jpm@finhutcs.bitnet Laboratory of Information Processing Science + 358 0 451 3231