Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!uunet!brunix!pjd
From: pjd@cs.brown.edu (Peter J. DiCamillo)
Newsgroups: comp.protocols.appletalk
Subject: Atalkad: ZIP table too large
Keywords: atalkad ZIP K-Star
Message-ID: <62474@brunix.UUCP>
Date: 24 Jan 91 23:43:45 GMT
Sender: news@brunix.UUCP
Reply-To: cmsmaint@brownvm.brown.edu (Peter J. DiCamillo)
Organization: Brown University CIS
Lines: 15

We have a network consisting of over 20 FastPath 4 gateways which we con-
figure using atalkad.  The gateways have version 4.1 ROMs and run K-Star
8.0. The version of atalkad is from the 6/88 distribution of KIP.  After 
adding the most recent new zone, atalkad generated the message "buildzones:
ZIP table size 512 approaching maximum of 512".  It is evident from the
source code for atalkad that when we add the next zone we will get the
messages "buildzones: ZIP table too large" and "buildzones: don't worry
if you are using a KIP later than 1/88".  I have two questions about this:

1) Does K-Star 8.0 qualify as "a KIP later than 1/88"?

2) If not, what options do I have for supporting more zones?

Peter DiCamillo
cmsmaint@brownvm.brown.edu