Ref: 11620001
Title: Documentation for CS_INSTALL Utility on NCS/AT
date: 8-30-89

Copyright 3Com Corporation, 1991.  All rights reserved.

This article explains how to use CS_INSTALL, an undocumented
utility on the NCS/AT utilities screen.  CS_INSTALL extracts the
existing name, global parameters, macros, and per port
configuration databases from a disk-based Communications Server
running XNS or TCP and installs them onto the NCS/AT.


PREREQUISITES

Two Communications Servers are required to use CS_INSTALL.  Both
must be operational on the network.  At least one must be booted
from and bound to the NCS.  The bound CS must have at least as
many ports as the other (disk-based) CS.  Also, the bound CS
should not be used by any users while CS_INSTALL is being run.

The shared configuration files term.asyn and host.asyn must exist
on the local NCS configuration database.


HOW CS_INSTALL WORKS

CS_INSTALL binds the disk-based Communications Server to the NCS
by automatically issuing the following command:

        BIND <ethernet_address> <address> <bootfilename> nports

If the BIND command detects any errors, they will be reported in
the command log file /tmp/cs.xxxxxxxx.

Then the shared configurations are extracted from the disk-based
CS.  The second CS redefines them and saves them on the NCS/AT
using the SAVE command.


COMMAND FORMAT

The command format for CS_INSTALL is as follows:

        CS_INSTALL address address_bound filename nports

<address>          address of the disk-based CS.  (Can be
                   an IP address or name server name.)

<address bound>    address of a second CS that is booted
                   from and bound to the NCS.  (Can be an IP
                   address or name server name.)

<filename>         configuration file to be moved

<nports>           number of ports on the disk-based CS


FILES

In the following files, xxxxxxxx is the Internet address in
hexadecimal of the disk-based CS.  yyyyyyyy is the Internet
address in hexadecimal of the bound server.

    /tmp/cs.xxxxxxxx
            output file, a command log file

    /usr/ncs/config.std/host.asyn,term.asyn
            input file, internal form of the shared
            configuration "host.asyn" and "term.asyn"

    /usr/NCS/CONFIGS/shared
            input file, NCS shared configuration file

    /usr/NCS/CONFIGS/cfg.xxxxxxxx
            output file, per port configs for the disk-based CS

    /usr/NCS/CONFIGS/cfg.yyyyyyyy
            input file, per port configs for the bound server

    /usr/NCS/GLOBALS/gbl.xxxxxxxx
            output file, global data for the disk based server

    /usr/NCS/GLOBALS/gbl.yyyyyyyy
            input file, global data for the bound sserver


LIMITATIONS

CS_INSTALL can extract only asynchronous port configurations.

It is best to use CS_INSTALL when the network is not busy.
CS_INSTALL uses the REMOTE command to gather most of the
information from servers across the network.  On heavily loaded
networks, the REMOTE command may time out, causing CS_INSTALL to
time out also.
