Ref: 03250437
Title: NCS/150 Limits & /AT Upgrade to Support TCP v.20000
Date: 3/31/88

Copyright 3Com Corporation, 1991.  All rights reserved.

With the release of TCP v.20000 for CommServers, the NCS/150 is
no longer able to support all combinations of 25 devices of two
different types, as our literature stated in the past.  It may be
necessary to upgrade to the NCS/AT.

The following example should help you calculate whether you will
need to upgrade to an NCS/AT at time of conversion to TCP 20000.

REQUIRED

Blks

 13      file & directory info
  8      /btsvrdata
  1      /passwd
  1      /DEV
  1      /BIN
272      /BIN/ncs150t
  2      /CONFIGS
  1      /CONFIGS/cfg.ncs
 10      /CONFIGS/shared
  1      /GLOBALS
  1      /GLOBALS/gbl.ncs
 68      /macros           (128 defined, as claimed)
 50      /nsnames  (500 names,    "    "   )
-------------------------------
429      SubTotal

Then, add two CS images:

2 Server Types - LS/1 and CS/200

 478      /BIN/cs1t
 476      /BIN/cs200t
  22      /BIN/sio16driver (or sio16.xxxxx)
   8      /BIN/sio16diag
--------------------------------
1413     Subtotal (including the 'required' 429 blocks above)

With a capacity of 1386 blocks, you are out of room, even prior
to adding the support files:

 40        /CONFIGS/cfg.XXXXXXXX(5 LS/1 x 4 blks, 20 CS/200)
 25        /GLOBALS/gbl.XXXXXXXX
 25        /GLOBALS/ipadr.XXXXXXXX

Note that config files take one block for every 16 ports
specified in the bind command (default is 32 ports, thus two
blocks) so you may conserve space by specifying only 10 ports
when binding CS/200s.

Also, one block per binding is needed for globals, and one per
binding for IP address storage (but LS/1s can have 64 port IP
addresses as a result of this new file, which also stores
Internet Server addresses and rotary IP addresses).  Be advised
that the latter file (ipadr...) is not created at the time of
binding, but rather when the CS boots.
