pschnack@uci.edu (Peter Schnack) (10/12/90)
I am having trouble configuring a FastPath and a NetBridge using the
atalkad from CAP.
The question:
How do I configure the atalkatab to show the the zone on the otherside of
the NetBridge?
The problem:
------- -------
Zone B | net | Zone A | FP4 | Lots-o-Zones
---------|bridge|---------| |-------
-------- -------
From a Chooser on Zone B you see Zone A and Zone B.
From a Chooser on Zone A you will alternately approx every 10 seconds see
just Zone A and Zone B: Then you will see Lots-o-Zones, Zone A and I think
Zone B though you cannot see the services on the Lots-o-Zones side.
If you turn off the NetBridge everything works fine (except of course the
Zone B is isolated :-)
Background and other information:
Shiva were the ones that suggested adding the Zone information for Zone B
to the atalkatab, but could not help me with how.
We have about 9 FP's connected around campus through a TCP/IP only
backbone with the atalkad, this is the first time I have had a multi-zone
LocalTalk network on the LocalTalk side of the FP.
Thanks
pschnack@orion.oac.uci.edumorgan@JESSICA.STANFORD.EDU (RL "Bob" Morgan) (10/12/90)
> ------- ------- > Zone B | net | Zone A | FP4 | Lots-o-Zones > ---------|bridge|---------| |------- > -------- ------- > > How do I configure the atalkatab to show the the zone on the otherside of > the NetBridge? There are two things that have to work to make this setup functional. First, the NetBridge has to find out about the big world to the right of the FP4, including all its network numbers and zone names. Second, the big world to the right of the FP4 has to find out about the network number and zone name of the net to the left of the NB, and that there is a route to this net through the FP4. The NB is supposed to find out what it needs by hearing RTMP broadcasts from the FP4 on the LocalTalk labelled Zone A. If, as you say, > From a Chooser on Zone B you see Zone A and Zone B. > From a Chooser on Zone A you will alternately approx every 10 seconds see > just Zone A and Zone B: Then you will see Lots-o-Zones, Zone A and I think > Zone B then it sounds like the NB isn't doing the right thing, and the whole thing is doomed. The Mac in the Zone A net is getting the zone list alternately from the FP4 and the NB, and not the merged list that the boxes should cooperate to create. I seem to recall that some versions of the NB wouldn't work with some versions of the FP for various bizarre reasons. The other side of this now probably less interesting problem is how all the FPs, etc in the big world find out about the Zone B net. There are two ways. One is to identify one or more FPs in your atalkatab as "KC" rather than "K". This will cause the FPs to start exchanging their dynamically-discovered routing information, which, if things were working correctly, would include the info about the Zone B net that FP4 got from hearing the NB's RTMP broadcasts. The other way is to put the info for the Zone B net (its network number and zone) into an "E" line in your atalkatab, also including the IP address of FP4. This tells the big world that there is a net with this number and zone name and that FP4 can get packets to that net. This approach makes this info much more static than with the method in the paragraph above, but should have the same result. - RL "Bob" Morgan Networking Systems Stanford University -------