Installing and Configuring CiscoWorks

After completing the tasks outlined in "Preparing to Install CiscoWorks," you are ready to install and configure the product. This chapter shows you how to install and configure CiscoWorks.

Process Overview for Installation and Configuration

The following general tasks must be performed to install and configure CiscoWorks.The rest of this chapter provides detailed instructions on these steps.

Make sure you have completed the Installation and Configuration Worksheets found in the "Blank Worksheets" appendix (see the "Preparing to Install CiscoWorks" chapter for details on completing the worksheets). The information you gather with these worksheets will be used to answer the questions prompted by the installation and configuration scripts.

Install CiscoWorks by invoking the /usr/etc/extract_unbundled script. The extract_unbundled script provides an interactive prompt and response dialog interface that guides you through the installation process. For general information on the extract_unbundled script, refer to the man pages on extract_unbundled. After you run the script, reboot your workstation to ensure that the Sybase changes to the kernel are put into effect.

If you are installing for the first time, see "Installing CiscoWorks Release 1.0 for the First Time" or "Installing CiscoWorks Release 1.0(3) for the First Time."
If you are upgrading from NetCentral 1.3 to CiscoWorks, see "Performing a NetCentral 1.3 to CiscoWorks 1.0 Upgrade" or "Performing a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade."
If you are upgrading from CiscoWorks 1.0 or 1.0(2) to CiscoWorks 1.0(3), see "Performing a CiscoWorks Release 1.0 or 1.0(2) to Release 1.0(3) Upgrade."

Configure CiscoWorks by invoking the ncsconfigure script in the /usr/tmp/unbundled directory. When you run the configuration script ncsconfigure, it makes the following changes: adds an entry to /etc/password for Sybase and CiscoWorks; adds an entry to /etc/group for the CiscoWorks group; and adds CiscoWorks startup commands to /etc/rc.local. Furthermore, if you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files: /usr/tmp/CW.group; /usr/tmp/CW.prod; and /usr/tmp/CW.sybase. After completing the CiscoWorks configuration, use the information in these files to update your NIS server.

If you are configuring CiscoWorks for the first time, see "Configuring CiscoWorks Release 1.0" or "Configuring CiscoWorks Release 1.0(3)."
If you are upgrading from NetCentral 1.3 to CiscoWorks, see "Performing a NetCentral 1.3 to CiscoWorks 1.0 Upgrade" or "Performing a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade."
If you are upgrading from CiscoWorks 1.0 or 1.0(2) to CiscoWorks 1.0(3), see "Performing a CiscoWorks Release 1.0 or 1.0(2) to Release 1.0(3) Upgrade."

Remove log files (optional). See "Cleaning Up Log Files."

Note: If you are upgrading from NetCentral 1.3 to CiscoWorks 1.0, you might have shut down the Sybase files before backing up the files on your system. Make sure that Sybase is open before installing CiscoWorks 1.0 on your system. For instructions on opening the Sybase files and using the nmstartup command, refer to the "Preparing to Install CiscoWorks" chapter.

If you encounter problems during installation or configuration, see the sections entitled "Troubleshooting Installation and Configuration Problems" and "CiscoWorks Release 1.0(x) Installation and Configuration Caveats." For a partial listing of error messages, see the "Error Messages" appendix. For an additional listing of error messages and CiscoWorks caveats, see the CiscoWorks User Guide.

Installing CiscoWorks Release 1.0 for the First Time

CiscoWorks 1.0 software is distributed on two cartridge tapes titled "CiscoWorks" and "Sybase Database & Server." The CiscoWorks tape contains CiscoWorks 1.0 software; the Sybase tape contains the Sybase software. You can install CiscoWorks 1.0 from a local tape drive attached to your system or from a tape drive attached to a remote system.

The installation script extract_unbundled prompts you to supply the device name of the local or the remote tape drive or the name of the remote system and the device name of the remote tape drive.

You install CiscoWorks by invoking and running the extract_unbundled script on your system. The extract_unbundled script provides an interactive prompt and response dialog interface that guides you through the installation process. For general information on the extract_unbundled script, refer to the man pages on extract_unbundled.

The installation and configuration process takes approximately 20 to 30 minutes, although the amount of time can vary depending on your system performance and installation method. An installation from a tape drive attached to a remote device may take longer.

Note: You can exit the installation script at any time by typing ControlC (^C) to return to the UNIX environment. The responses you have made up to the point you exit will be recorded for use as the defaults the next time you start the installation process.

If you plan to use a tape drive attached to a remote system, CiscoWorks does not require any disk space on the remote system. The software is copied across the network to the local workstation.

The root's .rhosts file on the remote system must contain your system's local hostname and your username. Otherwise, you will not be able to access the remote system to download software from the remote system's tape drive. For more information, refer to the man pages on rhosts.

If you use a local tape drive, the CiscoWorks software is installed directly on your system.

Detailed Procedure for a New Installation of CiscoWorks 1.0

This section provides a detailed procedure that shows you how to install CiscoWorks 1.0 either from a local tape drive or a remote tape drive. Follow this procedure if you want an explanation of the commands and information you need to provide during the installation process. For a quick overview of the installation script, see "Sample New Installation Script for CiscoWorks 1.0."

Before beginning your CiscoWorks 1.0 installation, be certain of the following:

You have filled out the Installation Worksheet with the appropriate information. See the "Blank Worksheets" appendix and the "Installation Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
The CiscoWorks tapes are readily available for insertion into the tape drive connected to your local system or a remote system.
You are logged in as a super user. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The following are the values and Sun system used for the installation procedure and script in this section:

/usr/nms is the name of the directory where the CiscoWorks software is being installed.
zen is the name of the system where CiscoWorks is being installed
/dev/rst0 is the name of the remote tape drive where the CiscoWorks tape is inserted.
enterprise is the name of the remote system to which the remote tape drive is attached.
The Sun SPARCstation uses Sun4c architecture.

Substitute the appropriate names and directory path names when you install the software.

Note: Some of the output displayed by the actual installation script is not included. Ellipses (...) in the example script indicate that some output is not displayed. A bracketed item ([ ]) after a prompt denotes the default response that will be accepted if you press Return. To select something other than the default, type your response and press Return. If a bracketed item appears without any input next to it, the default value has been accepted.

To perform the CiscoWorks 1.0 installation, complete the following steps:

Step 1: Insert the CiscoWorks 1.0 tape in a tape drive attached to either your local system or to a remote system on your network and fasten the latch of the tape drive.

Step 2: To extract the CiscoWorks software and begin the installation script, enter the following command at the UNIX prompt:

zen# /usr/etc/extract_unbundled

The extract_unbundled script is a script for Sun workstations that allows you to install software on your system.

Step 3: Specify whether you are installing from a local tape drive or from a tape drive attached to a remote system:

Enter media drive location [local | remote] : remote

If you are installing the CiscoWorks software from a local drive, enter local. Otherwise, enter remote.

Step 4: Specify the host name of the system to which the tape drive is attached:

Enter hostname of remote drive: enterprise

Step 5: Specify the name of the device from which you are installing the software:

Enter Device Name (e.g. rst0, rmt0, rfd0c) : /dev/rst0

Complete the syntax of the command by specifying the device name. For example, if your device name is rst0, enter st0 at the /dev/r prompt.

Step 6: Press Return if you have already inserted the tape in the tape drive as described in step 1.

**Please mount the release media if you haven't done so already.**        
Press return when ready:

Step 7: To continue installing the software, enter y.

The following product will be installed        
1+0 records in
1+0 records out
******************************************************
                CiscoWorks Version 1.0
     Copyright (c) 1986-1992 by Cisco Systems, Inc.
                All rights reserved
******************************************************
Do you want to continue [y|n]? y

A series of installation scripts are extracted:

/usr/etc/extract_unbundled : Extracting Installation Scripts        
x ./install_unbundled, 1059 bytes, 3 tape blocks
x ./1.0_CiscoWorks, 15676 bytes, 31 tape blocks
x ./ncsconfigure, 48768 bytes, 96 tape blocks
x ./ncskernel, 7019 bytes, 14 tape blocks

x ./.install/config.defs, 429 bytes, 1 tape blocks
x ./.install/nmcopyout, 4218 bytes, 9 tape blocks
x ./.install/exclude.sun4, 0 bytes, 0 tape blocks
x ./.install/find.sun4, 8683 bytes, 17 tape blocks
x ./.install/include.install, 224 bytes, 1 tape blocks
x ./.install/upgrade_nms, 12990 bytes, 26 tape blocks
x ./.install/variables, 176 bytes, 1 tape blocks
/usr/etc/extract_unbundled : Extracting Installation Scripts
/usr/etc/extract_unbundled : Begin Install Script Execution
Starting installation script /usr/tmp/unbundled/1.0_CiscoWorks
************ CiscoWorks 1.0 INSTALLATION *************
INSTALLATION SETUP - This section of the CiscoWorks 1.0 
installation will ask you to specify the type of installation (new 
or upgrade) and the directory path for the product installation.  
Existing NetCentral data will be saved if this is an upgrade, and 
the new directory structure will be setup.

Step 8: Specify whether this is a new installation or an upgrade. If you are installing CiscoWorks for the first time, this is a new installation. Enter n for a new installation.

Is this a new installation of CiscoWorks 1.0 installation,or an 
upgrade of an existing CiscoWorks 1.0 or NetCentral 1.3 
installation?        
Enter type of installation as (n)ew or (u)pgrade: [new]

Step 9: Specify the directory where you want CiscoWorks installed. The default directory is /usr/nms.If this directory does not exist on your system, the installation script can create it for you.

What directory will CiscoWorks be installed in? [/usr/nms]

Press Return to accept the displayed directory or enter the complete path for the directory where you want the software installed.

Step 10: If the directory does not exist on your system, confirm that you want the directory to be created. Press Return to enable the creation of the directory.

Directory /usr/nms does not exist! Create it? (y/n) [y]        
Directory /usr/nms has been created

Step 11: Confirm the information you specified earlier.

Installation type : new        
Destination Directory : /usr/nms
Remote host ----------------> enterprise
Are these values correct [y]

If your installation is of a different type or you wish to install the software in a different directory, enter n. You are returned to the beginning of the extract_unbundled script. Otherwise, press Return to continue.

The CiscoWorks software is copied onto your system. It takes approximately 20 minutes for the files to be copied to your system. While the files are being copied, you will see output similar to the following:

Tape ready...        
Forwarding...
Reading TAPE 1...
TAPE INSTALLATION - This section of the CiscoWorks 1.0

installation will load files from the installation tapes

into the /usr/nms directory.
CiscoWorks 1.0 tape installation will take approximately

20 minutes.
Checking tape ...
Forwarding tape ...
Reading TAPE 1...
dd if=/dev/nrst0 bs=126b | uncompress | tar vpxBbf 126

- 2>&1 | tee /var/tmp/unbundled/.install/tar.log | cat -u
x ./snm/agents/cisco.schema, 86288 bytes, 169 tape blocks
x ./snm/struct/cisco-elements.schema, 4212 bytes, 9 tape blocks
x ./snm/icons/AGS.icon, 622 bytes, 2 tape blocks
x ./snm/icons/AGS.iconmask, 622 bytes, 2 tape blocks
x ./snm/icons/MGS.icon, 622 bytes, 2 tape blocks
......................................................
x ./bin/nmadd, 712704 bytes, 1392 tape blocks
x ./bin/nmcontacts, 346000 bytes, 676 tape blocks
x ./bin/nmdevman_adr, 419728 bytes, 820 tape blocks
x ./bin/nmdevman_adm, 436112 bytes, 852 tape blocks
x ./bin/nmdevman_dev, 460688 bytes, 900 tape blocks
......................................................
x ./contrib/devices.rpt, 11525 bytes, 23 tape blocks
x ./contrib/totals.rpt, 18703 bytes, 37 tape blocks
x ./contrib/utilization.rpt, 13985 bytes, 28 tape blocks
x ./contrib/tcpdump, 262144 bytes, 512 tape blocks

Ignore the pauses that occur briefly while the files are being copied.

Step 12: When you are prompted to insert the Sybase Database & Server tape, remove the CiscoWorks tape, insert the second tape, fasten the tape drive's latch, and press Return.

Finished Reading TAPE 1        
Rewinding tape...
Please insert TAPE 2 - Sybase Database & Server
Press return when ready:
Checking Tape...

The Sybase files are copied to your system. Ignore the pauses that occur briefly while the files are being copied. After the files are copied you will see the following message:

Finished reading TAPE 2        
Rewinding tape ...
Verifying tape read...
TAPE installation completed - CiscoWorks 1.0 files

loaded correctly.

CiscoWorks installation and configuration requires that information about Sybase be added to your system configuration file in the /sys/ARCH/conf directory (where ARCH could be sun4, sun4c, or sun4m) and that a new configuration file called SYBASE be created.

Step 13: If you already have Sybase Version 4.8 installed on your system, or you are reinstalling CiscoWorks, or you prefer to edit the configuration file manually, or you have installed Sybase on a different system, enter n to the question on kernel modifications. Otherwise, press Return.

KERNEL MODIFICATIONS - This section of the CiscoWorks 

1.0 installation will make sybase modifications to your 

system kernel. You will be prompted for an existing 

kernel configuration file to use as a base for the new 

system kernel; the default is your current kernel 

configuration. After this script has completed 

successfully, you must reboot your system for the kernel 

modifications to take effect.        
You may decide to skip this section of the installation if:
1.  Your kernel has already been modified for Sybase 4.8,
2.  You wish to modify and rebuild your kernel manually, or
3.  Sybase will not be running on this system.
OK to continue with kernel modifications (y/n)? [y]

If you accepted or entered the name of your system configuration file, the installation script will create a new system configuration file called SYBASE and save the old configuration file as /vmunix.syb_inst. In addition, the new SYBASE kernel will be installed as /vmunix. The ncskernel.log file will contain information about the kernel rebuild process.

The base kernel configuration file is: /sys/sun4c/conf/GENERIC        
The new kernel configuration file will be: /sys/sun4c/conf/SYBASE
The old kernel will be saved as: /vmunix.syb_inst
The new SYBASE kernel will be installed as: /vmunix
The kernel rebuild will be logged in: /usr/tmp/unbundled/

ncskernel.log

Step 14: Confirm that the values for the system configuration file are correct by accepting the default.

Are these values correct (y/n) [y]

Press Return to accept the displayed values. Your system's old kernel is saved as /vmunix.syb_inst and a new configuration file called SYBASE is created from the existing configuration file on your system. The new configuration file SYBASE is configured and it is used to install a new kernel on your system.

Saving old kernel as /vmunix.syb_inst ...        
Creating /sys/sun4c/conf/SYBASE from /sys/sun4c/conf/GENERIC
Configuring /sys/sun4c/conf/SYBASE
Building SYBASE kernel from /sys/sun4c/conf/SYBASE
Installing new system kernel...
Sybase kernel modifications completed-Reboot your 

system to use the new kernel before you proceed with 

CiscoWorks 1.0 configuration.

REBOOT NOW!
CiscoWorks 1.0 Installation completed - continue with 

CiscoWorks 1.0 configuration by starting /usr/tmp/

unbundled/ncsconfigure.

After the old kernel is saved and the new kernel is created with the Sybase changes, you are returned to the UNIX prompt.

Step 15: At the UNIX prompt, enter the reboot command to reboot your system and ensure that the new kernel is used.

zen# reboot

Your system reboots and a series of system messages are displayed.

Step 16: After the reboot process is completed, log into your system as a super user.

login: root        
password:

The installation is complete. Next, configure the CiscoWorks 1.0 software as described in the section "Configuring CiscoWorks Release 1.0."

Sample New Installation Script for CiscoWorks 1.0

This section provides a CiscoWorks installation script dialog for an installation from a remote tape drive. If you are installing from a local tape drive, the installation script prompts you to supply only the device name.

This installation dialog gives you a quick overview of the type of information displayed or requested by the installation script.

If you want detailed instructions on how to answer the questions posed by the script during the installation process, refer to the section "Detailed Procedure for a New Installation of CiscoWorks 1.0."

Before beginning your CiscoWorks 1.0 installation, be certain of the following:

You have filled out the Installation Worksheet with the appropriate information. See the "Blank Worksheets" appendix and the "Installation Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
You have the CiscoWorks tapes readily available for insertion into the local tape drive connected to your system or a remote system.
You are logged in as a super user. See the "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The following are the values and Sun system used for the installation procedure and script in this section:

/usr/nms is the name of the directory where the CiscoWorks software is being installed.
zen is the name of the system where CiscoWorks is being installed.
/dev/rst0 is the name of the remote tape drive where the CiscoWorks tape is inserted.
enterprise is the name of the remote system to which the remote tape drive is attached.
The Sun SPARCstation is using Sun4c architecture.

Substitute the appropriate names and directory pathnames when you install the software.

        zen# /usr/etc/extract_unbundled
Enter media drive location [local | remote]: remote
Enter hostname of remote drive: enterprise
Enter Device Name (e.g. rst0, rmt0, rfd0c) : /dev/rst0
**Please mount the release media if you haven't done so already.**
Press return when ready:
The following product will be installed:
1+0 records in
1+0 records out
****************************************************************************
      CiscoWorks Version 1.0
      Copyright (c) 1986-1992 by Cisco Systems, Inc.
       All rights reserved
****************************************************************************
Do you want to continue [y|n]? y
/usr/etc/extract_unbundled : Extracting Installation Scripts
x ./install_unbundled, 1059 bytes, 3 tape blocks
x ./1.0_CiscoWorks, 15676 bytes, 31 tape blocks
x ./ncsconfigure, 48768 bytes, 96 tape blocks
x ./ncskernel, 7019 bytes, 14 tape blocks

x ./.install/config.defs, 429 bytes, 1 tape blocks
x ./.install/nmcopyout, 4218 bytes, 9 tape blocks
x ./.install/exclude.sun4, 0 bytes, 0 tape blocks
x ./.install/find.sun4, 8683 bytes, 17 tape blocks
x ./.install/include.install, 224 bytes, 1 tape blocks
x ./.install/upgrade_nms, 12990 bytes, 26 tape blocks
x ./.install/variables, 176 bytes, 1 tape blocks
/usr/etc/extract_unbundled : Extracting Installation Scripts
/usr/etc/extract_unbundled : Begin Install Script Execution
Starting installation script /usr/tmp/unbundled/1.0_CiscoWorks
********************** CiscoWorks 1.0 INSTALLATION **********************
INSTALLATION SETUP - This section of the CiscoWorks 1.0 installation
will ask you to specify the type of installation (new or upgrade) and
the directory path for the product installation.  Existing NetCentral
data will be saved if this is an upgrade, and the new directory
structure will be setup.
Is this a new installation of CiscoWorks 1.0 installation,or an upgrade of an 
existing NetCentral 1.3 installation? [new]
Enter type of installation as (n)ew or (u)pgrade: [new]n
   
What directory will CiscoWorks 1.0 be installed in?  [/usr/nms]
Directory /usr/nms does not exist! Create it (y/n) [y]
Directory /usr/nms has been created
Installation type :new
Destination Directory :/usr/nms
Are these values correct  [y]  y
Tape ready..
Forwarding...
Reading TAPE 1...
TAPE INSTALLATION - This section of the CiscoWorks 1.0 installation
will load files from the installation tapes into the /usr/nms
directory.
Checking Tape ...
Forwarding tape ...
Reading TAPE 1...
rsh -n enterprise dd if=/dev/nrst0 bs=126b | uncompress | tar vpxBbf 126 - 2>&1\
| tee /share/var/tmp/unbundled/.install/tar.log | cat -u
x ./snm/agents/cisco.schema, 86288 bytes, 169 tape blocks
x ./snm/struct/cisco-elements.schema, 4212 bytes, 9 tape blocks
x ./snm/icons/AGS.icon, 622 bytes, 2 tape blocks
x ./snm/icons/AGS.iconmask, 622 bytes, 2 tape blocks
x ./snm/icons/MGS.icon, 622 bytes, 2 tape blocks
......................................................................
x ./bin/nmadd, 712704 bytes, 1392 tape blocks
x ./bin/nmcontacts, 346000 bytes, 676 tape blocks
x ./bin/nmdevman_adr, 419728 bytes, 820 tape blocks

x ./bin/nmdevman_adm, 436112 bytes, 852 tape blocks
x ./bin/nmdevman_dev, 460688 bytes, 900 tape blocks
......................................................................
x ./contrib/devices.rpt, 11525 bytes, 23 tape blocks
x ./contrib/totals.rpt, 18703 bytes, 37 tape blocks
x ./contrib/utilization.rpt, 13985 bytes, 28 tape blocks
x ./contrib/tcpdump, 262144 bytes, 512 tape blocks
Finished Reading TAPE 1
Please insert TAPE 2 - Sybase Database & Server
Press return when ready:
Checking Tape...
0+1 records in
0+1 records out
Reading TAPE 2...
rsh -n enterprise dd if=/dev/nrst0 bs=126b | uncompress | tar vpxBbf 126 - 2>&1\
 | tee /share/var/tmp/unbundled/.install/tar.log | cat -u
x ./sybase/bin/bcp, 327680 bytes, 640 tape blocks
x ./sybase/bin/bcptrans, 286720 bytes, 560 tape blocks
x ./sybase/bin/buildmaster, 884736 bytes, 1728 tape blocks
x ./sybase/bin/charset, 417792 bytes, 816 tape blocks
......................................................................
x ./sybase/termdef/a/avt, 1578 bytes, 4 tape blocks
x ./sybase/termdef/a/avt-w, 1591 bytes, 4 tape blocks
x ./sybase/termdef/c/cit101, 1383 bytes, 3 tape blocks
x ./sybase/termdef/c/cit101-w, 1422 bytes, 3 tape blocks
......................................................................
Finished Reading TAPE 2
Verifying tape read...
TAPE installation complete - CiscoWorks 1.0 files loaded correctly.
KERNEL MODIFICATIONS - This section of the CiscoWorks 1.0 installation
will make sybase modifications to your system kernel. You will be
prompted for an existing kernel configuration file to use as a base for
the new system kernel; the default is your current kernel configuration. 
After this script has completed successfully, you must reboot your
system for the kernel modifications to take effect.
You may decide to skip this section of the installation if:
1.  Your kernel has already been modified for Sybase 4.8,
2.  You wish to modify and rebuild your kernel manually, or
3.  Sybase will not be running on this system.
OK to continue with kernel modifications (y/n)? [y]
Please enter System Configuration file or (q)uit: [GENERIC]
The base kernel configuration file is      : /sys/sun4c/conf/GENERIC
The new kernel configuration file will be  : /sys/sun4c/conf/SYBASE
The old kernel will be saved as            : /vmunix.syb_inst
The new SYBASE kernel will be installed as : /vmunix
The kernel rebuild will be logged in       : /usr/tmp/unbundled/ncskernel.log
Are these values correct [y/n]? [y]
Saving old kernel as /vmunix.syb_inst ...

Creating /sys/sun4c/conf/SYBASE from /sys/sun4c/conf/GENERIC
Configuring /sys/sun4c/conf/SYBASE
Building SYBASE kernel from /sys/sun4c/conf/SYBASE
Installing new system kernel...
SYBASE kernel modifications completed - Reboot your system to use
the new kernel before you proceed with CiscoWorks 1.0 configuration.
REBOOT NOW!
CiscoWorks 1.0 Installation completed - continue with CiscoWorks 1.0
configuration by starting /usr/tmp/unbundled/ncsconfigure.
zen# reboot

The installation is complete. When the workstation has rebooted, you are ready to configure the CiscoWorks 1.0 software as described in the section, "Configuring CiscoWorks Release 1.0."

Configuring CiscoWorks Release 1.0

This section provides a detailed procedure and a sample configuration script that explain how to respond to the questions posed by the configuration script. If you want a quick overview of the configuration process refer to the section "Sample New Configuration Dialog for CiscoWorks 1.0." For a detailed explanation, refer to the section "Detailed Procedure for a New Configuration of CiscoWorks 1.0."

After installing CiscoWorks 1.0 and rebooting your system, you must configure CiscoWorks to fit your particular environment. The interactive configuration script will first prompt you to enter all the required information, then ask you to confirm your choices before any actual changes are made to your system.

When you run the configuration script ncsconfigure, it performs the following actions:

Adds an entry to /etc/password for Sybase
Adds an entry to /etc/group for the CiscoWorks group
Adds CiscoWorks startup commands to /etc/rc.local

Note: At any time before you confirm the configuration, you can abort the process by typing Control-C (^C) to return to the UNIX command environment. The responses you made up to the point you exit will be recorded for use as the defaults the next time the configuration script is run. Once you have confirmed your configuration choices and the actual configuration process has begun, ^C is disabled. If you want to change your choices, rerun the script.

Detailed Procedure for a New Configuration of CiscoWorks 1.0

This detailed procedure shows you how to configure CiscoWorks 1.0. Follow this procedure if you want an explanation of the information you need to provide during the configuration process.

Before beginning the CiscoWorks 1.0 configuration, make sure of the following:

You have filled out the Configuration Worksheet with the appropriate information. The configuration script will prompt you for this information. See the "Blank Worksheets" appendix and the "Configuration Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
SunNet Manager (SNM) is installed on your system. The configuration script attempts to find SNM files. If it fails to find them, the configuration process is aborted.
You are logged in as a super user. If you are not logged in as a super user, CiscoWorks will be unable to complete the configuration. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The example configuration script that follows uses a directory named /usr/nms on a system called zen. Substitute the appropriate names and paths where necessary.

Note: Some of the output displayed by the actual configuration script is not included. Ellipses (...) in the example script indicate that some output is not displayed. A bracketed item ([ ]) after a prompt denotes the default response that will be accepted if you press Return. To select something other than the default, type your response and press Return. If a bracketed item appears without any input next to it, the default value has been accepted.

To configure CiscoWorks 1.0, perform the following steps:

Step 1: After rebooting your system and logging in as a super user, enter the following command and press Return to begin the CiscoWorks configuration process.

hostname# /usr/tmp/unbundled/ncsconfigure

Step 2: Specify that you are configuring a new installation of CiscoWorks. Enter n.

Is this a new installation of CiscoWorks 1.0, or an 

upgrade of an existing CiscoWorks 1.0 or NetCentral 1.3 

installation?        
Verify type of installation as (n)ew or (u)upgrade:[new] n

Step 3: Confirm the directory where the CiscoWorks software will be configured.

Verify the directory path for the CiscoWorks 1.0 

software:[/usr/nms]

Press Return to accept the displayed directory. This is the same directory where you installed CiscoWorks.

Step 4: Confirm the type of installation and directory where CiscoWorks will be configured:

Installation type          :  new        
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]

Step 5: Specify a name for the CiscoWorks group. Later you will add users to this group, and they will have login IDs that will enable them to access the system that is running CiscoWorks and the CiscoWorks software. The default name for the group is CscWorks.

GROUPS AND USERS - This section of the CiscoWorks 1.0 

configuration will set up a UNIX group and users for the 

installed software.  You will be asked for a group name, 

group id, and a list of group users.  Next, you will be 

asked to specify user information for ownership of the 

CiscoWorks 1.0 files followed by user information for 

ownership of the Sybase database files.  The users for 

CiscoWorks 1.0 and Sybase will be added to the group 

automatically.        
Refer to your system and CiscoWorks 1.0 documentation 

for instructions on adding/modifying groups and users 

after configuration is complete.
What would you like to call the CiscoWorks 1.0 group?  [CscWorks]

Press Return to accept the default option or enter a name of your choice. The installation script adds the CiscoWorks group name to the /etc/group file.

Step 6: Press Return to accept the group ID number for the CscWorks group or specify a unique group ID number. The group ID number you accept or specify is added to the /etc/group file on your system.

Group id for the CiscoWorks 1.0 group? [55]

Step 7: Add users to the CiscoWorks group. These users can access CiscoWorks provided they already have login accounts on the system where you are installing CiscoWorks. If these users do not have login accounts, you can create the login accounts after configuring CiscoWorks. Later, you will also be able to assign specific permissions for each user in this group by using the CiscoWorks Security Manager application, described in the CiscoWorks User Guide.

Enter CiscoWorks group user names one line at a time.        
Terminate the list with an empty line.
Input users name >cthomas
Input users name >rpoling
Input users name > kwilson
Input users name > tjones
Input users name > blytton
Input users name >

When you have finished adding all the usernames, confirm the values by pressing Return.

Step 8: Confirm the values you entered earlier.

Using the following values for the CiscoWorks 1.0 group        
CiscoWorks 1.0 Group Name ----> CscWorks
CiscoWorks 1.0 Group ID ------> 55
CiscoWorks 1.0 Group Users ---> cthomas, rpoling, 

kwilson, tjones, blytton
Are these values correct? [yes]

To accept the displayed values, press Return.If you wish to change any values at this time, enter n and press Return. You are returned to the beginning of the configuration script.

Step 9: Specify a username for CiscoWorks.

What would you like to call the CiscoWorks 1.0 user name? 
[cscworks]

Press Return to accept the default username cscworks or enter a username of your choice.

Step 10: Specify a unique user ID number for CiscoWorks or accept the default user ID that is displayed.

User ID for CiscoWorks 1.0 login? [100]

Press Return to accept the default user ID or enter a unique user ID number.

Step 11: Specify the full name for the CiscoWorks username.

Full name for CiscoWorks 1.0 user? [CiscoWorks]

Press Return to accept the default name.

Step 12: Specify the shell that will be used by CiscoWorks.

Shell for CiscoWorks 1.0 login? [/bin/csh]

Press Return to accept the default C-Shell or enter a shell name of your choice.

Step 13: Confirm the values you chose for CiscoWorks.

Using the following values for the CiscoWorks 1.0 user:        
CiscoWorks 1.0 User Name          : cscworks
CiscoWorks 1.0 User ID            : 100
CiscoWorks 1.0 Group ID           : 55
CiscoWorks 1.0 Full Name          : CiscoWorks
CiscoWorks 1.0 Home Directory     : /usr/nms
CiscoWorks 1.0 Shell              : /bin/csh
Are these values correct?  [yes]

Press Return to accept the displayed values. If you enter n, you are asked to specify the values again.

Step 14: Press Return to accept the Sybase username. Cisco recommends that you accept the default username sybase.

What would you like to call the Sybase username? [sybase]

This username is used to access Sybase.

Step 15: Specify a user ID for the Sybase login.

User ID for Sybase login? [101]

Press Return to accept the default user ID for the the Sybase login or specify a unique user ID for the Sybase login.

Step 16: Specify the full name for Sybase.

Full name for Sybase user? [Sybase]

Cisco recommends that you use the default full name Sybase. Press Return to accept the default username.

Step 17: Press Return to accept the /bin/csh shell for Sybase login, or if you prefer, specify a different shell.

Shell for Sybase login? [/bin/csh]

Step 18: Confirm whether the Sybase values are correct.

Using the following values for the Sybase user        
Sybase User Name          : sybase
Sybase User ID            : 101
Sybase Group ID           : 55
Sybase Full Name          : Sybase
Sybase Home Directory     : /usr/nms/sybase
Sybase Shell              : /bin/csh
Are these values correct? [yes]

Press Return to accept the values and continue. If you enter n, you are asked to specify the values again.

The /etc/passwd and /etc/group files are updated with the information you specified for CiscoWorks and Sybase.

Adding CscWorks:*:55:cthomas,rpoling,kwilson, tjones, 

blytton,cscworks,sybase to /etc/group ...        
Adding cscworks:*:100:55:CiscoWorks:/usr/nms/bin/csh 

to /etc/passwd ...
Adding sybase:*:101:55:Sybase:/usr/nms/sybase:/bin/csh 

to /etc/passwd ...

The configuration script also sets the owner and group permissions for CiscoWorks files.

FILE OWNERSHIP AND PERMISSIONS  -  The ownership of the 

CiscoWorks 1.0 files will be changed to the selected 

users and groups.  Permissions of specific files will 

be modified to enable execution and read/write capabilities.        
Setting the owner and group for CiscoWorks 1.0 software ...
chown -R cscworks.CscWorks /usr/nms/.
chown -R sybase /usr/nms/sybase
chown root /usr/nms/bin/nmsummary
chown root /usr/nms/bin/nmpoll
chown root /usr/nms/bin/nmproc
chown root /usr/nms/bin/nmpath
chown root /usr/nms/contrib/tcpdump
Setting the permissions for CiscoWorks 1.0 software ...
chmod -R 750 /usr/nms
chmod 4750 /usr/nms/bin/nmsummary
chmod 4750 /usr/nms/bin/nmpoll
chmod 4750 /usr/nms/bin/nmproc
chmod 4750 /usr/nms/bin/nmpath
chmod 4750 /usr/nms/contrib/tcpdump
chmod 660 /usr/nms/etc/ncspwd
chmod 660 /usr/nms/log

Step 19: To enable the addition of Cisco schema files to the SNM schema files, specify the complete path for the directory where you installed SNM.

SUNNET MANAGER MODIFICATIONS  -  A set of Cisco schema 

files must be added to the SunNet Manager schema files 

to enable SunNet Manager to to integrate CiscoWorks 1.0 

functionality.  You need to specify the directory path 

for the SunNet Manager schema files.        
Directory path for SunNet Manager schema files? [/usr/snm]

Press Return if SNM was installed in the /usr/snm directory. Otherwise, enter the correct directory path for SNM.

The Cisco schema files are added to the SNM schema files.

Merging CiscoWorks 1.0 schemas with SunNet Manager ...        
cp /usr/nms/snm/agents/* /rpoling/snm/sun4/snm/agents/
cp /usr/nms/snm/struct/* /rpoling/snm/sun4/snm/struct/
cp /usr/nms/snm/icons/* /rpoling/snm/sun4/snm/icons/
chmod +r /rpoling/snm/sun4/snm/agents/cisco*
chmod +r /rpoling/snm/sun4/snm/struct/cisco*
chmod +r /rpoling/snm/sun4/snm/icons/*
Running /usr/snm/bin/build_oid ...
Parsing /usr/snm/agents/enterprises.oid

Parsing /usr/snm/agents/snmp.oid
Parsing /usr/snm/agents/cisco.asn1.oid
Parsing /usr/snm/agents/sun-snmp.oid
Parsing /usr/snm/agents/snmp-mibII.oid
Writing /var/adm/snm/oid.dbase
SunNet Manager modifications completed.

The configuration script also opens the TCP ports for the Sybase installation and changes the Sybase interface file.

TCP PORTS  -  An open set of tcp ports will be identified 

for this new Sybase installation. The ports will be defined 

in the Sybase interfaces file.        
Identifying open ports for Sybase ...
Using ports 8000 thru 8003
Defining ports in /usr/nms/sybase/interfaces file ...
/usr/nms/etc/setaddress 8000
Please wait...
Sybase interface file has been changed.

Step 20: Press Return to enable the configuration script to build and load the CiscoWorks database.

DATABASE STARTUP  -  This section of the CiscoWorks 1.0 

configuration will build and load the CiscoWorks 1.0 

database.  The Sybase dataserver and any daemons from 

previous installations will be halted.  Then, the new 

database will be built.  If this is an upgrade installation, 

data from database will be built.  If this is an upgrade 

installation, data from the previous installation will be 

reloaded into the new database. Certain operations will 

require you to provide the Sybase 'sa' (system admin) password. 

Use password 'NULL' if this is a new installation.        
OK to continue (y/n)? [y]

Step 21: Press Return to halt the Sybase dataserver.

Halting Sybase dataserver and CiscoWorks 1.0 daemons ...        
Sybase dataserver is running. If this is used by

CiscoWorks 1.0, it must be halted before continuing.
OK to halt Sybase dataserver (y/n) [y]
Running /usr/nms/etc/load_nms ...
**** Do not interrupt the execution of this script! ****
The load_nms script will create the Sybase master database 

and the nms database.  During database intensive operations, 

output may not be produced for several minutes. If problems occur, 

this script can be run manually from /usr/nms/etc/load_nms.
Creating master.dat database file ...
Starting Sybase dataserver ...

A series of messages appear, indicating that the Sybase database is being installed, loaded, and verified. A verification message appears, indicating that the database was installed without any errors.


No errors detected, the Database seems to be correctly installed.        
Resetting database and system logs ...

The log purge is completed.

Step 22: Press Return to halt the Sybase dataserver.

Sybase dataserver is running.  If this dataserver is 

used by CiscoWorks 1.0, it must be halted before continuing.        
OK to halt Sybase dataserver (y/n)? [y]

The Sybase dataserver is halted.

Step 23: Press Return to start the CiscoWorks processes and the database server.

Start the CiscoWorks 1.0 processes and database server? (y/n)? [y]        
Starting CiscoWorks 1.0. please wait...

The CiscoWorks processes and the Sybase database server are started.

The configuration script checks whether you set up TFTP on your system. If you plan to use CiscoWorks Configuration Management application, make sure that TFTP is configured as described in "Setting Up TFTP", in the "Preparing to Install CiscoWorks" chapter.

TFTP CHECK  -  The CiscoWorks 1.0 Configuration Management 

application uses TFTP for configuration upload and download 

of Cisco devices.        
Correct operation of this feature requires that TFTP service 

be enabled and that the TFTP directory have the correct access 

permissions.
Checking for correct TFTP service configuration ...

TFTP is correctly configured.

Step 24: Specify the name of the log file to be used to store messages from the UNIX syslogd process.

SYSLOG MODIFICATIONS  -  The CiscoWorks 1.0 Log Manager 

application uses a centralized log file which gets messages 

from the UNIX syslogd process.  You will need to specify the 

log file name and which syslog facility (local0-local7) to use.  

Use facility local7 if you want to log both CiscoWorks 1.0 

messages and Cisco device messages; use a different facility 

if you want to log only CiscoWorks 1.0 messages.        
Enter log file to use for CiscoWorks 1.0 messages:
[/var/log/nmslog]

Press Return to accept the default log file or enter the directory path name and filename.

Step 25: Specify the facility to be used with syslog for logging messages. To log both CiscoWorks messages and Cisco device messages, accept the default facility, local7. To log only CiscoWorks messages, enter a different facility within the range of local0 through local6.

Enter syslog facility to use for CiscoWorks 1.0 messages: [local7]

Press Return to accept local7 or enter a different facility name in the range of local0 through local6.

Step 26: If there are other applications that use the facility you chose, press Return to clear the facility for use by syslog.

OK to remove other syslog entries which use local7 (y/n) [y]

Step 27: Press Return to confirm the values you specified for the log file and the syslog facility.

The log file will be : /var/log/nmslog        
The syslog facility will be : local7
Remove other syslog entries which use local7 : y
Are these values correct (y/n)? [y]

The syslog modifications are completed.

Step 28: Press Return to enable the configuration script to install nmstartup and modify the /etc/rc.local file.

RC.LOCAL MODIFICATIONS  -  The Sybase dataserver and other 

CiscoWorks 1.0 daemons must be running as background processes 

for correct operation of CiscoWorks 1.0.  This section of 

the configuration will modify the file /etc/rc.local to 

include nmstartup which will start the Sybase dataserver 

and CiscoWorks 1.0 daemons during system reboot.        
Checking for nmstartup in /etc/rc.local ...
Install nmstartup for CiscoWorks 1.0 in /etc/rc.local (y/n)? [y]

Step 29: If you want the centralized log file syslog to be automatically purged and backed up every day, press Return. As a result, the CiscoWorks log purging utility is started automatically by the UNIX cron daemon. If you do not want the syslog file to be purged and backed up automatically every day, enter n. Refer to the CiscoWorks User Guide for information on customizing the log purge utility and editing the crontab file.

CRON MODIFICATIONS  -  The syslog file must be purged 

periodically to avoid running out of disk space.  This 

activity is automated by the CiscoWorks 1.0 log purge 

utility when scheduled by the UNIX cron daemon.        
This will purge syslog daily and maintain a seven day 

history of syslog files.
Schedule the CiscoWorks 1.0 log purge utility to run 

daily (y/n)? [y]

The crontab file is updated.

Make sure that you set up the environment variables and the paths by following the instructions in "Setting Up TFTP," in the "Preparing to Install CiscoWorks" chapter.


CONFIGURATION COMPLETE  -  Various environment variables 

must be defined for correct operation of CiscoWorks 1.0. 

You can append the following lines to the .login or .cshrc 

file of CiscoWorks 1.0 users so that required environment 

variables will be set correctly:

        
#   Set environment variables for CiscoWorks 1.0.
#   Set environment variables for CiscoWorks 1.0.
setenv SNMHOME /usr/snm
setenv NMSROOT /usr/nms
setenv SYBASE /usr/nms/sybase
#   Set path for CiscoWorks 1.0 man pages.
if (!($?MANPATH)) setenv MANPATH /usr/man
setenv MANPATH "$MANPATH":"$NMSROOT"/man
#   Set path for CiscoWorks 1.0 executables.
set path=($path /usr/nms/bin /usr/nms/etc)

You are returned to the UNIX prompt.

Note: Make sure you validate the CiscoWorks installation and configuration process by following the instructions in the "Validating CiscoWorks Installation" chapter. When you validate the CiscoWorks installation, you will be able to access CiscoWorks through SNM.

If you wish to remove the log files that were created when installing and configuring Cisco Works, see "Cleaning Up Log Files." Otherwise, proceed to the "Validating CiscoWorks Installation" chapter.

Sample New Configuration Dialog for CiscoWorks 1.0

This section provides an example of the CiscoWorks 1.0 configuration script. If you want detailed instructions on how to answer the questions posed by the script during the configuration process, refer to the section "Detailed Procedure for a New Configuration of CiscoWorks 1.0."

Before beginning the CiscoWorks 1.0 configuration, make sure of the following:

You have filled out the Configuration Worksheet with the appropriate information. The configuration script will prompt you for this information. See the "Blank Worksheets" appendix and the "Configuration Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
SunNet Manager (SNM) is installed on your system. The configuration script attempts to find SNM files. If it fails to find them, the configuration process is aborted.
You are logged in as a super user. If you are not logged in as a super user, CiscoWorks will be unable to complete the configuration. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The example configuration script that follows uses a directory named /usr/nms on a system called zen. Substitute the appropriate names and paths where necessary.

#zen /usr/tmp/unbundled/ncsconfigure        
********************** CiscoWorks 1.0 CONFIGURATION **********************
CONFIGURATION SETUP  -  This section of the CiscoWorks 1.0 configuration
will ask you to verify the type of installation (new or upgrade) and
the directory path where the product has been installed.
Is this a (new) installation of CiscoWorks 1.0, or an upgrade of an
existing NetCentral 1.3 installation?  [new] new
Verify type of installation as (n)ew or (u)pgrade: [new]
Verify the directory path for the CiscoWorks 1.0 software: [/usr/nms]
Installation type          :  new
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]
GROUPS AND USERS - This section of the CiscoWorks 1.0 configuration will
set up a UNIX group and users for the installed software.  You will be
asked for a group name, group id, and a list of group users.  Next,
you will be asked to specify user information for ownership of the
CiscoWorks 1.0 files followed by user information for ownership of the
Sybase database files.  The users for CiscoWorks 1.0 and Sybase will be
added to the group automatically.
Refer to your system and CiscoWorks 1.0 documentation for instructions
on adding/modifying groups and users after configuration is complete.
What would you like to call the CiscoWorks 1.0 group?  [CscWorks]
Group id for the CiscoWorks 1.0 group?   [55]
Enter CiscoWorks 1.0 group user names one line at a time.
Terminate the list with an empty line.

Input users name >cthomas
Input users name >rpoling
Input users name >kwilson
Input users name >tjones
Input users name >blytton
Input users name >
Using the following values for the CiscoWorks 1.0 group
CiscoWorks 1.0 Group Name ----> Cscworks
CiscoWorks 1.0 Group ID ------> 55
CiscoWorks 1.0 Group Users ---> cthomas,rpoling,kwilson, tjones, blytton
Are these values correct?  [yes]
What would you like to call the CiscoWorks 1.0 user name?  [cscworks]
User ID for CiscoWorks 1.0 login?  [100]
Full name for CiscoWorks 1.0 user?  [CiscoWorks]
Shell for CiscoWorks 1.0 login?  [/bin/csh]
Using the following values for the CiscoWorks 1.0 user:
CiscoWorks 1.0 User Name          : cscworks
CiscoWorks 1.0 User ID            : 100
CiscoWorks 1.0 Group ID           : 55
CiscoWorks 1.0 Full Name          : CiscoWorks
CiscoWorks 1.0 Home Directory     : /usr/nms
CiscoWorks 1.0 Shell              : /bin/csh
Are these values correct?  [yes] 
What would you like to call the Sybase user name?  [sybase]
User ID for Sybase login? [101]
Full name for Sybase user? [Sybase]
Shell for Sybase login? [/bin/csh]
Using the following values for the Sybase user:
Sybase User Name          : sybase
Sybase User ID            : 101
Sybase Group ID           : 55
Sybase Full Name          : Sybase
Sybase Home Directory     : /usr/nms/sybase
Sybase Shell              : /bin/csh
Are these values correct?  [yes]
Adding CscWorks:*:55:cthomas,rpoling,kwilson,tjones,blytton,cscworks,sybase to 

/etc/group
Adding cscworks:*:100:55:CiscoWorks:/usr/nms:/bin/csh to /etc/passwd ...
Adding sybase:*:101:55:Sybase:/usr/nms/sybase:/bin/csh to /etc/passwd ...
FILE OWNERSHIP AND PERMISSIONS  -  The ownership of the CiscoWorks 1.0
files will be changed to the selected users and groups.  Permissions
of specific files will be modified to enable execution and read/write
capabilities.

Setting the owner and group for CiscoWorks 1.0 software ...
chown -R cscworks.CscWorks /usr/nms
chown -R sybase /usr/nms/sybase
chown root /usr/nms/bin/nmsummary
chown root /usr/nms/bin/nmpoll
chown root /usr/nms/bin/nmproc
chown root /usr/nms/bin/nmpath
chown root /usr/nms/contrib/tcpdump
Setting the permissions for CiscoWorks 1.0 software...
chmod -R 750 /usr/nms
chmod 4750 /usr/nms/bin/nmsummary
chmod 4750 /usr/nms/bin/nmpoll
chmod 4750 /usr/nms/bin/nmproc
chmod 4750 /usr/nms/bin/nmpath
chmod 4750 /usr/nms/contrib/tcpdump
chmod 660 /usr/nms/etc/ncspwd
chmod 660 /usr/nms/log
SUNNET MANAGER MODIFICATIONS  -  A set of Cisco schema files must be
added to the SunNet Manager schema files to enable SunNet Manager to
integrate CiscoWorks 1.0 functionality.  You need to specify the
directory path for the SunNet Manager schema files.
Directory path for SunNet Manager schema files? [/usr/snm]
Merging CiscoWorks 1.0 schemas with SunNet Manager ...
cp /usr/nms/snm/agents/* /rpoling/snm/sun4/snm/agents/
cp /usr/nms/snm/struct/* /rpoling/snm/sun4/snm/struct/
cp /usr/nms/snm/icons/* /rpoling/snm/sun4/snm/icons/
chmod +r /rpoling/snm/sun4/snm/agents/*
chmod +r /rpoling/snm/sun4/snm/struct/*
chmod +r /rpoling/snm/sun4/snm/icons/*
Running /usr/snm/bin/build_oid ...
Parsing /usr/snm/agents/enterprises.oid
Parsing /usr/snm/agents/snmp.oid
Parsing /usr/snm/agents/cisco.asn1.oid
Parsing /usr/snm/agents/sun-snmp.oid
Parsing /usr/snm/agents/snmp-mibII.oid
Writing /var/adm/snm/oid.dbase
SunNet Manager modifications completed.
TCP PORTS  -  An open set of tcp ports will be identified for this
new Sybase installation. The ports will be defined in the Sybase
interfaces file.
Identifying open ports for Sybase ...
Using ports 8000 thru 8003
Defining ports in /usr/nms/sybase/interfaces file ...
/usr/nms/etc/setaddress 8000
Please wait...

Sybase interface file has been changed.
DATABASE STARTUP  -  This section of the CiscoWorks 1.0 configuration will
build and load the CiscoWorks 1.0 database.  The Sybase dataserver and
any daemons from previous installations will be halted.  Then, the new
database will be built.  If this is an upgrade installation, data from
the previous installation will be reloaded into the new database.
Certain operations will require you to provide the Sybase 'sa' (system
admin) password.  Use password 'NULL' if this is a new installation.
OK to continue (y/n)? [y]
Halting Sybase dataserver and CiscoWorks 1.0 daemons ...
Sybase dataservers is running. If this dataserver is used by
CiscoWorks 1.0, it must be halted before continuing.
OK to halt Sybase dataserver (y/n) [y]
Running /usr/nms/etc/load_nms ...
    **** Do not interrupt the execution of this script! ****
The load_nms script will create the Sybase master database and the
nms database.  During database intensive operations, output may not
be produced for several minutes. If problems occur, this script can
be run manually from /usr/nms/etc/load_nms.
Creating master.dat database file...
Starting Sybase dataserver...
Waiting for server to complete initialization ...
Loading master database schema ... (ignore message about sp_configure)
Loading master database ... (ignore message about unexpected EOF)
'Disk' device added.
(return status = 0)
DB-LIBRARY error:
        Unexpected EOF from SQL Server.
Restartng Sybase dataserver with new master database.
Creating new nms database ...
CREATE DATABASE: allocating 3072 pages on disk 'nms'
CREATE DATABASE: allocating 2048 pages on disk 'nms'
Loading nms database ... (ignore message about unexpected EOF)
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
Server SHUTDOWN by request.
The SQL Server is terminating this process.
DB-LIBRARY error:
        Unexpected EOF from SQL Server.

/usr/nms/sybase/install
Sybase database installation and load is complete.
Restart and verify the database ...
00: 92/10/12 08:50:11.96 kernel: SQL Server/4.8/EBF 984/Sun 4/SunOS 4.1.X/5/OPT/
Thu Aug 6 10:29:22 PDT 1992
00: 92/10/12 08:50:11.98 kernel: Sybase SMP SQL Server 4.8
00: 92/10/12 08:50:11.98 kernel: Confidential Property of Sybase, Inc.
00: 92/10/12 08:50:11.98 kernel: Copyright Sybase, Inc. 1987, 1992.
00: 92/10/12 08:50:11.98 kernel: All rights reserved.
......................................................
Database (null) is alive
Sybase is running.
No errors detected, the Database seems to be correctly installed.
Resetting database and system logs ...
log purg 1.0(0.25) starting:
Process id = 4821
Debugging: = Off
logpurg started at: Mon Oct 17 18:33:06 1992
logpurg completed
Halting Sybase dataserver
Sybase dataserver is running.  If this dataserver is used by
CiscoWorks 1.0, it must be halted before continuing.
OK to halt Sybase dataserver (y/n)? [y]
Server SHUTDOWN by request.
00: 92/10/12 08:51:32.39 server: SQL Server shutdown by request.
00: 92/10/12 08:51:32.42 kernel: ueshutdown: exiting
The SQL Server is terminating this process.
DB-LIBRARY error:
        Unexpected EOF from SQL Server.
Start the CiscoWorks 1.0 processes and database server (y/n)? [y]
Starting CiscoWorks 1.0.  Please wait ...
TFTP CHECK  -  The CiscoWorks 1.0 Configuration Management application
uses TFTP for configuration upload and download of Cisco devices.
Correct operation of this feature requires that TFTP service be enabled
and that the TFTP directory have the correct access permissions.
Checking for correct TFTP service configuration ...
TFTP is correctly configured.
SYSLOG MODIFICATIONS  -  The CiscoWorks 1.0 Log Manager application
uses a centralized log file which gets messages from the UNIX syslogd
process.  You will need to specify the log file name and which syslog
facility (local0-local7) to use.  Use facility local7 if you want to
log both CiscoWorks 1.0 messages and Cisco device messages; use a
different facility if you want to log only CiscoWorks 1.0 messages.
Enter log file to use for CiscoWorks 1.0 messages: [/var/log/nmslog]
Enter syslog facility to use for CiscoWorks 1.0 messages: [local7]
OK to remove other syslog entries which use local7 (y/n)? [y]

The log file will be                          : /var/log/nmslog
The syslog facility will be                   : local7
Remove other syslog entries which use local7  : y
Are these values correct (y/n)? [y]
Syslog modifications in progress ...
Syslog modifications completed.
RC.LOCAL MODIFICATIONS  -  The Sybase dataserver and other CiscoWorks 1.0
daemons must be running as background processes for correct operation
of CiscoWorks 1.0.  This section of the configuration will modify the file
/etc/rc.local to include nmstartup which will start the Sybase dataserver
and CiscoWorks 1.0 daemons during system reboot.
Checking for nmstartup in /etc/rc.local ...
Install nmstartup for CiscoWorks 1.0 in /etc/rc.local (y/n)? [y]
Adding nmstartup for CiscoWorks 1.0 to /etc/rc.local ...
/etc/rc.local modifications completed.
CRON MODIFICATIONS  -  The syslog file must be purged periodically
to avoid running out of disk space.  This activity is automated by the
CiscoWorks 1.0 log purge utility when scheduled by the UNIX cron daemon.
This will purge syslog daily and maintain a seven day history of syslog
files.
Schedule the CiscoWorks 1.0 log purge utility to run daily (y/n)? [y]
Adding line "0 2 * * * /usr/nms/bin/purge /usr/nms" to crontab ...
Cron modifications completed.
CONFIGURATION COMPLETE  -  Various environment variables must be defined
for correct operation of CiscoWorks 1.0. You can append the following lines
to the .login or .cshrc file of CiscoWorks 1.0 users so that required
environment variables will be set correctly:
#   Set environment variables for CiscoWorks 1.0.
setenv SNMHOME /usr/snm
setenv NMSROOT /usr/nms
setenv SYBASE /usr/nms/sybase
#   Set path for CiscoWorks 1.0 man pages.
if (!($?MANPATH)) setenv MANPATH /usr/man
setenv MANPATH "$MANPATH":"$NMSROOT"/man
#   Set path for CiscoWorks 1.0 executables.
set path=($path /usr/nms/bin /usr/nms/etc)
Refer to the CiscoWorks 1.0 Getting Started Guide for instructions on
validating your installation and configuration.
#zen

If you wish to remove the log files that were created when installing and configuring Cisco Works, see "Cleaning Up Log Files." Otherwise, proceed to the "Validating CiscoWorks Installation" chapter.

Performing a NetCentral 1.3 to CiscoWorks 1.0 Upgrade

This section provides CiscoWorks 1.0 installation and configuration script dialogs for a NetCentral 1.3 upgrade installation and configuration from a remote tape drive. If you are installing from a local tape drive, the installation script prompts you to supply only the device name.The "Sample Installation Dialog for a NetCentral 1.3 to CiscoWorks 1.0 Upgrade" section gives you a quick overview of the type of information displayed and requested by the installation script. The "Sample Configuration Dialog for a NetCentral 1.3 to CiscoWorks 1.0 Upgrade" section gives you a quick overview of the type of information displayed and requested by the configuration script.

If you plan to use a tape drive attached to a remote system, CiscoWorks does not require any disk space on the remote system. The software is copied across the network to the local workstation.

If you use a local tape drive, the CiscoWorks software is installed directly on your system.

When you run the configuration script ncsconfigure, it performs the following actions:

Adds an entry to /etc/password for Sybase
Adds an entry to /etc/group for the CiscoWorks group
Adds CiscoWorks startup commands to /etc/rc.local

Sample Installation Dialog for a NetCentral 1.3 to CiscoWorks 1.0 Upgrade

This section shows an example installation script dialog for upgrading NetCentral 3.1 to CiscoWorks 1.0.

Before beginning your CiscoWorks 1.0 installation, be certain of the following:

You have filled out the Installation Worksheet with the appropriate information. See the "Blank Worksheets" appendix and the "Installation Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
The CiscoWorks tapes are readily available for insertion into the local tape drive connected to your system or a remote system.
You are logged in as a super user. See the "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The following are the values and Sun system used for the installation procedure and script in this section:

/usr/nms is the name of the directory where the CiscoWorks software is being installed.
zen is the name of the system where CiscoWorks is being installed
/dev/rst0 is the name of the remote tape drive where the CiscoWorks tape is inserted.
enterprise is the name of the remote system to which the remote tape drive is attached.
The Sun SPARCstation uses Sun4c architecture.

Substitute the appropriate names and directory path names when you install the software.

#zen /usr/etc/extract_unbundled
Enter media drive location [local | remote]: remote
Enter hostname of remote drive: enterprise
Enter Device Name (e.g. rst0, rmt0, rfd0c) : /dev/rst0
**Please mount the release media if you haven't done so already.**
Press return when ready:
The following product will be installed:
1+0 records in
1+0 records out
****************************************************************************
CiscoWorks Version 1.0
Copyright (c) 1986-1992 by Cisco Systems, Inc.
All rights reserved
****************************************************************************
Do you want to continue [y|n]? y

/usr/tmp/extract_unbundled : Extracting Installation Scripts
x ./install_unbundled, 1059 bytes, 3 tape blocks
x ./1.0_CiscoWorks, 15676 bytes, 31 tape blocks
x ./ncsconfigure, 48768 bytes, 96 tape blocks
x ./ncskernel, 7019 bytes, 14 tape blocks
x ./.install/config.defs, 429 bytes, 1 tape blocks
x ./.install/nmcopyout, 4218 bytes, 9 tape blocks
x ./.install/exclude.sun4, 0 bytes, 0 tape blocks
x ./.install/find.sun4, 8683 bytes, 17 tape blocks
x ./.install/include.install, 224 bytes, 1 tape blocks
x ./.install/upgrade_nms, 12990 bytes, 26 tape blocks
x ./.install/variables, 176 bytes, 1 tape blocks
x ./.install/dbunload, 1553 bytes, 4 tape blocks
/usr/tmp/extract_unbundled : Begin Install Script Execution
Starting installation script /usr/tmp/unbundled/1.0_CiscoWorks
********************** CiscoWorks 1.0 INSTALLATION **********************
INSTALLATION SETUP - This section of the CiscoWorks 1.0 installation
will ask you to specify the type of installation (new or upgrade) and
the directory path for the product installation. Existing NetCentral
data will be saved if this is an upgrade, and the new directory
structure will be setup.
Is this a new installation of CiscoWorks 1.0, or an upgrade of an
existing CiscoWorks 1.0 or NetCentral 1.3 installation?
Enter type of installation as (n)ew or (u)pgrade: [new] u
What directory contains the existing installation? [/usr/nms]
Directory /usr/nms does not exist! Create it (y/n) [y]
Installation type : upgrade
Destination directory : /usr/nms
Are these values correct (y/n)? [y]
SYBASE UPGRADE - The following operations will be performed to
upgrade from NetCentral 1.3 to CiscoWorks 1.0:
* Currently running NetCentral 1.3 daemons will be halted.
* Consistency check will be run on the Sybase database; you must
provide the Sybase 'sa' (system admin) password for this operation.
* The database tables and data will be exported to files; the data
will be reloaded during CiscoWorks 1.0 configuration.
* Finally, the Sybase dataserver will be halted.
OK to continue (y/n)? [y]
Halting NetCentral 1.3 daemons ...
The 'sa' (system admin) password is required to perform
the consistency check on the database.
The consistency of the current database needs to be checked.
PLEASE enter DBMS password for 'sa':

Running the database consistency check. Please wait ...
Upgrading database version 1.3 to 1.3
Saving user data in database for upgrade ...
Running /usr/tmp/unbundled/.install/nmcopyout to save database data ...
database_name database_size
--------------------------------- ---------------------------
nms 8 MB
reserved data index_size unused
----------------- --------------- -------------------- ------
1952 KB 648 KB 78 KB 1226 KB
(return status = 0)
Use the data column above to estimate how much tmp space will be
required by this database unload procedure.
Where do you want the database data saved? [/usr/tmp]
Exporting database ...
Halting Sybase dataserver ...
TAPE INSTALLATION - This section of the CiscoWorks 1.0 installation
will load files from the installation tapes into the /usr/nms
directory.
CiscoWorks 1.0 tape installation will take approximately 20 minutes.
Checking Tape ...
Forwarding tape ...
Reading TAPE 1 ...
rsh -n enterprise dd if=/dev/nrst0 bs=126b | uncompress | tar vpxBbf 126 - 2>&1 | tee /usr/tmp/

unbundled/.install/tar.log | cat -u
x ./snm/agents/cisco.schema, 112289 bytes, 220 tape blocks
x ./snm/agents/cisco.asn1.oid, 19939 bytes, 39 tape blocks
x ./snm/agents/snmp-mibII.oid, 7655 bytes, 15 tape blocks
x ./snm/struct/cisco-elements.schema, 13726 bytes, 27 tape blocks
......................................................................
x ./bin/nmadd, 712704 bytes, 1392 tape blocks
x ./bin/nmcontacts, 346000 bytes, 676 tape blocks
x ./bin/nmdevman_adr, 419728 bytes, 820 tape blocks
x ./bin/nmdevman_adm, 436112 bytes, 852 tape blocks
x ./bin/nmdevman_dev, 460688 bytes, 900 tape blocks
......................................................................
x ./help/nmpath.hlp, 10257 bytes, 21 tape blocks
x ./help/nmproc.hlp, 3419 bytes, 7 tape blocks
x ./help/nmsync.hlp, 3081 bytes, 7 tape blocks
x ./help/nmhealth.hlp, 6507 bytes, 13 tape blocks
Finished reading TAPE 1
Please insert TAPE 2 - Sybase Database & Server
Press return when ready:
Checking Tape ...
0+1 records in
0+1 records out

Reading TAPE 2...
rsh -n enterprise dd if=/dev/nrst0 bs=126b | uncompress | tar vpxBbf 126 - 2>&1 | tee /usr/tmp/

unbundled/.install/tar.log | cat -u
x ./sybase/bin/apt.std, 1368064 bytes, 2672 tape blocks
x ./sybase/bin/apt, 508 bytes, 1 tape blocks
x ./sybase/bin/aptcompile, 344064 bytes, 672 tape blocks
.................................................
x ./sybase/termdef/xterm_c.hp, 1514 bytes, 3 tape blocks
x ./sybase/termdef/xterm_c.ncd, 1514 bytes, 3 tape blocks
x ./sybase/termdef/xterm_c.sun, 1602 bytes, 4 tape blocks
x ./sybase/interfaces.dist, 132 bytes, 1 tape blocks
Finished reading TAPE 2
Verifying tape read ...
TAPE installation completed - CiscoWorks 1.0 files loaded correctly.
KERNEL MODIFICATIONS - This section of the CiscoWorks 1.0 installation
will make sybase modifications to your system kernel. You will be
prompted for an existing kernel configuration file to use as a base for
the new system kernel; the default is your current kernel configuration.
After this script has completed successfully, you must reboot your
system for the kernel modifications to take effect.
You may decide to skip this section of the installation if:
1. Your kernel has already been modified for Sybase 4.8,
2. You wish to modify and rebuild your kernel manually, or
3. Sybase will not be running on this system.
OK to continue with kernel modifications (y/n)? [y]
Please enter System Configuration file or (q)uit: [GENERIC]
The base kernel configuration file is : /sys/sun4c/conf/GENERIC
The new kernel configuration file will be : /sys/sun4c/conf/SYBASE
The old kernel will be saved as : /vmunix.syb_inst
The new SYBASE kernel will be installed as : /vmunix
The kernel rebuild will be logged in : /usr/tmp/unbundled/ncskernel.log
Are these values correct (y/n)? [y]
Saving old kernel as /vmunix.syb_inst ...
Creating /sys/sun4c/conf/SYBASE from /sys/sun4c/conf/GENERIC ...
Configuring /sys/sun4c/conf/SYBASE ...
Building SYBASE kernel from /sys/sun4c/conf/SYBASE ...
Installing new system kernel ...
SYBASE kernel modifications completed - Reboot your system to use the
new kernel before you proceed with CiscoWorks 1.0 configuration.
REBOOT NOW!
CiscoWorks 1.0 Installation completed - continue with CiscoWorks 1.0
configuration by starting /usr/tmp/unbundled/ncsconfigure.
zen# reboot

The installation is complete. When the workstation has rebooted, you are ready to configure the CiscoWorks 1.0 software. For a sample upgrade configuration script, see "Sample Configuration Dialog for a NetCentral 1.3 to CiscoWorks 1.0 Upgrade."

Sample Configuration Dialog for a NetCentral 1.3 to CiscoWorks 1.0 Upgrade

This section shows an example configuration script dialog for upgrading NetCentral 3.1 to CiscoWorks 1.0.

Before beginning the CiscoWorks 1.0 configuration, make sure of the following:

You have filled out the Configuration Worksheet with the appropriate information. The configuration script will prompt you for this information. See the "Blank Worksheets" appendix and the "Configuration Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
SunNet Manager (SNM) is installed on your system. The configuration script attempts to find SNM files. If it fails to find them, the configuration process is aborted.
You are logged in as a super user. If you are not logged in as a super user, CiscoWorks will be unable to complete the configuration. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The example configuration script that follows uses a directory named /usr/nms on a system called zen. Substitute the appropriate names and paths where necessary.

%zen /usr/tmp/unbundled/ncsconfigure        
********************** CiscoWorks 1.0 CONFIGURATION **********************
CONFIGURATION SETUP  -  This section of the CiscoWorks 1.0 configuration
will ask you to verify the type of installation (new or upgrade) and
the directory path where the product has been installed.

Is this a new installation of CiscoWorks 1.0, or an upgrade of an
existing CiscoWorks 1.0 or NetCentral 1.3 installation?
Verify type of installation as (n)ew or (u)pgrade: [upgrade] upgrade
Verify the directory path for the CiscoWorks 1.0 software: [/usr/nms]
Installation type          :  upgrade
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]
GROUPS AND USERS - This section of the CiscoWorks 1.0 configuration will
set up a UNIX group and users for the installed software.  You will be
asked for a group name, group id, and a list of group users.  Next,
you will be asked to specify user information for ownership of the
CiscoWorks 1.0 files followed by user information for ownership of the
Sybase database files.  The users for CiscoWorks 1.0 and Sybase will be
added to the group automatically.
Refer to your system and CiscoWorks 1.0 documentation for instructions
on adding/modifying groups and users after configuration is complete.
What is the name of the existing CiscoWorks group? [NetCen]CscWorks
Group "Cscworks does not exist! Create it (y/n)? [y]
Group id for the CiscoWorks 1.0 group? [56]
Enter CiscoWorks 1.0 group user names one line at a time.
Terminate the list with an empty line.
Input users name >cthomas
Input users name >rpoling
Input users name >kwilson
Input users name >tjones
Input users name >blytton
Using the following values for the CiscoWorks 1.0 group
CiscoWorks 1.0 Group Name ----> CscWorks
CiscoWorks 1.0 Group ID ------> 55
CiscoWorks 1.0 Group Users ---> rpoling,cthomas, kwilson, tjones, blytton
Are these values correct?  [yes]
What is the name of the existing CiscoWorks 1.0 login? [cscworks]
Login "cscworks" does not exist
Would you like to create it? [yes]
User ID for CiscoWorks 1.0 login? [101]
Full name for CiscoWorks 1.0 user? [CiscoWorks]
Shell for CiscoWorks 1.0 login? [/bin/csh]
Using the following values for the CiscoWorks 1.0 user:
CiscoWorks 1.0 User Name          : cscworks
CiscoWorks 1.0 User ID            : 101

CiscoWorks 1.0 Group ID           : 56
CiscoWorks 1.0 Full Name          : CiscoWorks
CiscoWorks 1.0 Home Directory     : /usr/nms
CiscoWorks 1.0 Shell              : /bin/csh
Are these values correct?  [yes]
What is the name of existing Sybase login?  [sybase]
Using the following values for the Sybase user
Sybase User Name ---------> sybase
Sybase User ID -----------> 100
Sybase Group ID ----------> 55
Sybase Full Name ---------> Sybase
Sybase home directory ----> /usr/nms/sybase
Sybase Shell -------------> /bin/csh
Are these values correct?  [yes]
Adding CscWorks:*:56:cscworks,sybase to /etc/group ...
Adding cscworks:*:101:56:CiscoWorks:/usr/nms:/bin/csh to /etc/passwd ...
Adding sybase:*:101:55:Sybase:/usr/nms/sybase:/bin/csh to /etc/passwd ...
FILE OWNERSHIP AND PERMISSIONS  -  The ownership of the CiscoWorks 1.0
files will be changed to the selected users and groups.  Permissions
of specific files will be modified to enable execution and read/write
capabilities.
Setting the owner and group for CiscoWorks 1.0 software ...
chown -R cscworks.CscWorks /usr/nms/.
chown -R sybase /usr/nms/sybase
chown root /usr/nms/bin/nmsummary
chown root /usr/nms/bin/nmpoll
chown root /usr/nms/bin/nmproc
chown root /usr/nms/bin/nmpath
chown root /usr/nms/contrib/tcpdump
Setting the permissions for CiscoWorks 1.0 software ...
chmod -R 750 /usr/nms
chmod 4750 /usr/nms/bin/nmsummary
chmod 4750 /usr/nms/bin/nmpoll
chmod 4750 /usr/nms/bin/nmproc
chmod 4750 /usr/nms/bin/nmpath
chmod 4750 /usr/nms/contrib/tcpdump
chmod 660 /usr/nms/etc/ncspwd
chmod 660 /usr/nms/log
Do you wish to install the new MIB files? (y/n) [y]
Your previous MIb files will be saved in /usr/nms/etc/mibs.BAK
Do you want to replace the existing startup in
/etc/rc.local with the new version of CiscoWorks 1.0?  [yes]
SUNNET MANAGER MODIFICATIONS  -  A set of Cisco schema files must be

added to the SunNet Manager schema files to enable SunNet Manager to
integrate CiscoWorks 1.0 functionality.  You need to specify the
directory path for the SunNet Manager schema files.
Directory path for SunNet Manager schema files? [/usr/snm]
Merging CiscoWorks 1.0 schemas with SunNet Manager ...
cp /usr/nms/usr/nms/snm/agents/* /rpoling/snm/sun4/snm/agents/
cp /usr/nms/snm/struct/* /rpoling/snm/sun4/snm/struct/
cp /usr/nms/snm/icons/* /rpoling/snm/sun4/snm/icons/
chmod +r /rpoling/snm/sun4/snm/agents/cisco*
chmod +r /rpoling/snm/sun4/snm/struct/cisco*
chmod +r /rpoling/snm/sun4/snm/icons/*
Running /usr/snm/bin/build_oid ...
Parsing /usr/snm/agents/enterprises.oid
Parsing /usr/snm/agents/snmp.oid
Parsing /usr/snm/agents/cisco.asn1.oid
Parsing /usr/snm/agents/sun-snmp.oid
Parsing /usr/snm/agents/snmp-mibII.oid
Writing /var/adm/snm/oid.dbase
SunNet Manager modifications completed.
DATABASE STARTUP  -  This section of the CiscoWorks 1.0 configuration will
build and load the CiscoWorks 1.0 database.  The Sybase dataserver and
any daemons from previous installations will be halted. Then, the new
database will be built. If this is an upgrade installation, data from
the previous installation will be reloaded into the new database.
Certain operations will require you to provide the Sybase 'sa' (system
admin) password.  Use password 'NULL' if this is a new installation.
OK to continue (y/n)? [y]
Halting Sybase dataserver and CiscoWorks 1.0 daemons ...
Running /usr/nms/etc/load_nms ...
    **** Do not interrupt the execution of this script! ****
The load_nms script will create the Sybase master database and the
nms database.  During database intensive operations, output may not
be produced for several minutes.  If problems occur, this script can
be run manually from /usr/nms/etc/load_nms.
Creating master.dat database file ...
Starting Sybase dataserver ..
Waiting for server to complete initialization ...
Loading master database schema ... (ignore message about sp_configure)
Loading master database ... (ignore message about unexpected EOF)
'Disk' device added.
(return status = 0)
DB-LIBRARY error:
        Unexpected EOF from SQL Server.

Restartng Sybase dataserver with new master database.
Creating new nms database ...
CREATE DATABASE: allocating 3072 pages on disk 'nms'
CREATE DATABASE: allocating 2048 pages on disk 'nms'
Loading nms database ... (ignore message about unexpected EOF)
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
Server SHUTDOWN by request.
The SQL Server is terminating this process.
DB-LIBRARY error:
        Unexpected EOF from SQL Server.
/usr/nms/sybase/install
Sybase database installation and load is complete.
Upgrading database files ...
Start the new server on the old database ...
00: 92/Waiting for server to complete initialization ...
00: 92/10/12 08:50:11.96 kernel: SQL Server/4.8/EBF 984/Sun 4/SunOS 4.1.X/5/OPT/
Thu Aug 6 10:29:22 PDT 1992
00: 92/10/12 08:50:11.98 kernel: Sybase SMP SQL Server 4.8
00: 92/10/12 08:50:11.98 kernel: Confidential Property of Sybase, Inc.
...................................................
Loading database data from old server in new server ...
Where did you save the database data? [/usr/tmp/]
Creating table testpoll
Creating table nms_rev_history
(0 rows affected)
(1 row affected)
(2 rows affected)
Database (null) is alive
Sybase is running.
No errors detected, the Database seems to be correctly installed.
Resetting database and system logs ...
logspurg 1.0(0.25) 
Process id = 712
Debugging: = Off
logpurg started at: Mon Oct 19 8:14:05 1992
logpurg completed
Halting Sybase dataserver ...
Sybase dataserver is running.  If this dataserver is used by
CiscoWorks 1.0, it must be halted before continuing.
OK to halt Sybase dataserver (y/n)? [y]

Server SHUTDOWN by request.
00: 92/10/12 08:51:32.39 server: SQL Server shutdown by request.
00: 92/10/12 08:51:32.42 kernel: ueshutdown: exiting
The SQL Server is terminating this process.
DB-LIBRARY error:
        Unexpected EOF from SQL Server.
Start the CiscoWorks 1.0 processes and database server (y/n)? [y]
Starting CiscoWorks 1.0.  Please wait ...
TFTP CHECK - The CiscoWorks 1.0 Configuration Management application
uses TFTP for configuration upload and download of Cisco devices.
Correct operation of this feature requires that TFTP service be enabled
and that the TFTP directory have the correct access permissions.
Checking for correct TFTP service configuration ...
TFTP is correctly configured.
SYSLOG MODIFICATIONS  -  The CiscoWorks 1.0 Log Manager application
uses a centralized log file which gets messages from the UNIX syslogd
process.  You will need to specify the log file name and which syslog
facility (local0-local7) to use.  Use facility local7 if you want to
log both CiscoWorks 1.0 messages and Cisco device messages; use a
different facility if you want to log only CiscoWorks 1.0 messages.
Enter log file to use for CiscoWorks 1.0 messages: [/var/log/nmslog]
/var/log/nmslog already exists! Use this file anyway (y/n)? [y]
Do you want to overwrite this file (y/n)? [y]
Enter syslog facility to use for CiscoWorks 1.0 messages: [local7]
OK to remove other syslog entries which use local7 (y/n)? [y]
The log file will be                          : /var/log/nmslog
The syslog facility will be                   : local7
Remove other syslog entries which use local7  : y
Are these values correct (y/n)? [y]
Syslog modifications in progress ...
Syslog modifications completed.
RC.LOCAL MODIFICATIONS  -  The Sybase dataserver and other CiscoWorks 1.0
daemons must be running as background processes for correct operation
of CiscoWorks 1.0.  This section of the configuration will modify the file
/etc/rc.local to include nmstartup which will start the Sybase dataserver
and CiscoWorks 1.0 daemons during system reboot.
Checking for nmstartup in /etc/rc.local ...
Install nmstartup for CiscoWorks 1.0 in /etc/rc.local (y/n)? [y]
Adding nmstartup for CiscoWorks 1.0 to /etc/rc.local ...
/etc/rc.local modifications completed.

CRON MODIFICATIONS  -  The syslog file must be purged periodically
to avoid running out of disk space.  This activity is automated by the
CiscoWorks 1.0 log purge utility when scheduled by the UNIX cron daemon.
This will purge syslog daily and maintain a seven day history of syslog
files.
Schedule the CiscoWorks 1.0 log purge utility to run daily (y/n)? [y]
Adding line "0 2 * * * /usr/nms/bin/purge /usr/nms" to crontab ...
Cron modifications completed.
CONFIGURATION COMPLETE  -  Various environment variables must be defined
for correct operation of CiscoWorks 1.0. You can append the following lines
to the .login or .cshrc file of CiscoWorks 1.0 users so that required
environment variables will be set correctly:
#   Set environment variables for CiscoWorks 1.0.
#   Set environment variables for CiscoWorks 1.0.
setenv SNMHOME /usr/snm
setenv NMSROOT /usr/nms
setenv SYBASE /usr/nms/sybase
#   Set path for CiscoWorks 1.0 man pages.
if (!($?MANPATH)) setenv MANPATH /usr/man
setenv MANPATH "$MANPATH":"$NMSROOT"/man
#   Set path for CiscoWorks 1.0 executables.
set path=($path /usr/nms/bin /usr/nms/etc)
Refer to the CiscoWorks 1.0 Getting Started Guide for instructions on
validating your installation and configuration.
zen#

If you wish to remove the log files that were created when installing and configuring Cisco Works, see "Cleaning Up Log Files." Otherwise, proceed to the "Validating CiscoWorks Installation" chapter.

Installing CiscoWorks Release 1.0(3) for the First Time

CiscoWorks 1.0(3) software is distributed on CD-ROM. You install CiscoWorks by changing to the /cdrom directory and invoking and running the ./extract_unbundled script which is supplied on the CDROM. The ./extract_unbundled script provides an interactive prompt and response dialog interface that guides you through the installation process.

The installation and configuration process takes approximately 20 to 30 minutes, although the amount of time can vary depending on your system performance and installation method. Installation from a CDROM drive attached to a remote device can take longer.

Detailed Procedure for a New Installation of CiscoWorks 1.0(3)

This section provides a detailed explanation of the CiscoWorks installation script dialog for an installation from a CD-ROM drive.

Before beginning your CiscoWorks 1.0(3) installation, be certain of the following:

You have filled out the Installation Worksheet with the appropriate information. See the "Blank Worksheets" appendix and the "Installation Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
You have mounted the CD-ROM properly. See the section entitled "Installing from a Local or Remote CDROM," in the "Preparing to Install CiscoWorks" chapter.
You are logged in as a super user. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The following are the values and Sun system used for the installation procedure and script in this section:

/usr/nms is the name of the directory where the CiscoWorks software is being installed.
zen is the name of the system where CiscoWorks is being installed.
The Sun SPARCstation is using Sun4c architecture.

Substitute the appropriate names and directory path names when you install the software.

To perform the CiscoWorks 1.0(3) installation, complete the following steps:

Step 1: Change the directory to the /cdrom directory:

zen# cd /cdrom

Step 2: Enter the following command to begin the ./extract_unbundled installation dialog:

zen# ./extract_unbundled

Note: When invoking the ./extract_unbundled script, make sure you specify the complete syntax with the period (.) and the slash (/) to ensure that you run the correct version of this command.

The following message appears and asks you if you wish to continue:

./extract_unbundled: The following product will be installed:        
**************************************************************
                     CiscoWorks Version 1.0(3)
           Copyright (c) 1986-1993 by Cisco Systems, Inc.
                        All rights reserved
**************************************************************
Do you want to continue (y/n)?  [y]

Step 3: To begin the extraction of the installation scripts, press Return.

./extract_unbundled: Extracting installation scripts ...x ./

install_unbundled, 717 bytes, 2 tape blocks        
x ./1.0_CiscoWorks, 18774 bytes, 37 tape blocks
x ./ncsconfigure, 66695 bytes, 131 tape blocks
x ./ncskernel, 7953 bytes, 16 tape blocks

x ./.install/config.defs, 429 bytes, 1 tape blocks
...
x ./.install/dbunload, 3036 bytes, 6 tape blocks
./extract_unbundled: Starting installation process ...
./extract_unbundled: /usr/tmp/unbundled/install_unbundled 

-c/cdrom -f
/usr/tmp/unbundled/install_unbundled: Starting installation 

script /usr/tmp/unbundled/1.0_CiscoWorks ...
/usr/tmp/unbundled/install_unbundled: /usr/tmp/unbundled/

1.0_CiscoWorks -c/cdrom -f
^^^^^^^^^^^^^^^^^CiscoWorks 1.0 INSTALLATION*****************
INSTALLATION SETUP  -  This section of the CiscoWorks 1.0 

installation will ask you to specify the type of installation 

(new or upgrade) and the directory path for the product 

installation.  Existing NetCentral data will be saved if this 

is an upgrade, and the new directory structure will be set up.

Step 4: Specify that you are installing CiscoWorks for the first time by pressing Return to accept the default option.

Is this a new installation of CiscoWorks 1.0, or an upgrade 

of an existing CiscoWorks 1.0 or NetCentral 1.3 installation?         
Enter type of installation as (n)ew or (u)pgrade: [new]

Step 5: Specify the directory where you want CiscoWorks installed. The default directory is /usr/nms. If this directory does not exist on your system, the installation script can create it for you.

What directory will CiscoWorks 1.0 be installed in? [/usr/nms]

To accept the displayed directory, press Return. You can also enter the complete path for the directory where you want the software installed.

Step 6: If the directory does not exist on your system, confirm that you want the directory to be created. To create the directory, press Return.

Directory /usr/nms does not exist!  Create it (y/n)? [y]        
Directory /usr/nms has been created.

Step 7: Confirm the information you specified earlier:

Installation type          :  new        
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]
CDROM INSTALLATION - This section of the CiscoWorks 1.0 

installation will load files from the installation cdrom 

into the /usr/nms directory.

Step 8: If your installation is of a different type or if you wish to install the software in a different directory, enter n. You are returned to the beginning of the ./extract_unbundled script.

Otherwise, press Return to continue.

The CiscoWorks software is copied onto your system. It takes approximately 20 minutes for the files to be copied to your system. Ignore the pauses that occur briefly while the files are being copied. While the files are being copied, you will see output similar to the following:

CiscoWorks 1.0 installation will take approximately 20 minutes.        
Installing CiscoWorks 1.0 ...
uncompress -c /cdrom/ciscoworks/sun4.ncs.tar.Z | tar xvfpB 

- 2>&1 | tee /usr/tmp
/unbundled/.install/tar.log | cat -u
x ./snm/agents/cisco.schema, 113239 bytes, 222 tape blocks
x ./snm/agents/cisco.asn1.oid, 20825 bytes, 41 tape blocks
x ./snm/agents/snmp-mibII.oid, 8094 bytes, 16 tape blocks
...
x ./help/nmproc.hlp, 3419 bytes, 7 tape blocks
x ./help/nmsync.hlp, 3081 bytes, 7 tape blocks
x ./help/nmhealth.hlp, 6507 bytes, 13 tape blocks
Finished installing CiscoWorks 1.0.
Installing Sybase Database & Server ...
uncompress -c /cdrom/sybase/sybase.sun4.tar.Z | tar xvfpB 

- 2>&1 | tee /usr/tmp/
unbundled/.install/tar.log | cat -u
x ./sybase/bin/apt.std, 1630208 bytes, 3184 tape blocks
x ./sybase/bin/apt, 998 bytes, 2 tape blocks
x ./sybase/bin/aptcompile, 499712 bytes, 976 tape blocks
...
x ./sybase/termdef/xterm_c.ncd, 1514 bytes, 3 tape blocks
x ./sybase/termdef/xterm_c.sun, 1602 bytes, 4 tape blocks
x ./sybase/interfaces.dist, 132 bytes, 1 tape blocks
Finished installing Sybase Database & Server.
Verifying installed files ...
Installation verified - CiscoWorks 1.0 files loaded correctly.

Step 9: If any one of the following conditions is true, enter n to the question on kernel modifications:

You already have the new Sybase Version 4.9.1 installed on your system.
You are reinstalling CiscoWorks.
You prefer to edit the configuration file manually.
You have installed Sybase on a different system.

Otherwise, press Return to continue with kernel modifications.

KERNEL MODIFICATIONS  -  This section of the CiscoWorks 1.0 

installation will make sybase modifications to your system kernel. 

You will be prompted for an existing kernel configuration file 

to use as a base for the new system kernel; the default is your 

current kernel configuration.        
After this script has completed successfully, you must reboot 

your system for the kernel modifications to take effect.
You may decide to skip this section of the installation if:
1.  Your kernel has already been modified for Sybase 4.9.1,
2.  You wish to modify and rebuild your kernel manually, or
3.  Sybase will not be running on this system.
OK to continue with kernel modifications (y/n)? [y]

Step 10: If your configuration file name is GENERIC or if you enter the name of your system configuration file, the installation script creates a new system configuration file called SYBASE and saves the old configuration file as /vmunix.syb_inst. The new SYBASE kernel will be installed as /vmunix. The ncskernel.log file will contain information about the kernel rebuild process.

Please enter System Configuration file or (q)uit: [GENERIC]

If the name of your configuration file is GENERIC, press Return. Otherwise, enter the name of the configuration file of your system.

Step 11: Confirm that the values for the system configuration file are correct by pressing Return to accept the displayed values. Otherwise, enter n.

The base kernel configuration file is: /sys/sun4c/conf/GENERIC

The new kernel configuration file will be: /sys/sun4c/conf/SYBASE

The old kernel will be saved as: /vmunix.syb_inst        
The new SYBASE kernel will be installed as: /vmunix
The kernel rebuild will be logged in: /usr/tmp/unbundled/

ncskernel.log
Are these values correct [y/n]? [y]

The old kernel file is saved as syb_inst, and a new configuration file called SYBASE is created from the existing configuration file on your system. The SYBASE file is configured and is used to install a new kernel on your system.

Saving old kernel as /vmunix.syb_inst ...        
Creating /sys/sun4c/conf/SYBASE from /sys/sun4c/conf/GENERIC
Configuring /sys/sun4c/conf/SYBASE
Building SYBASE kernel from /sys/sun4c/conf/SYBASE
Installing new system kernel...
SYBASE kernel modifications completed - Reboot your system to 

use the new kernel before you proceed with CiscoWorks 1.0 

configuration.
REBOOT NOW!
CiscoWorks 1.0 Installation completed - continue with CiscoWorks 

1.0 configuration by starting /usr/tmp/unbundled/ncsconfigure.
zen#

After the old kernel is saved, and the new kernel is created with the Sybase changes, you are returned to the UNIX prompt.

Step 12: At the UNIX prompt, enter the following command to reboot your system and ensure that the new kernel is used.

zen# reboot

Step 13: After the reboot process is completed, log into your system as a superuser.

login: root        
password:

The installation is complete. Next, configure the CiscoWorks 1.0(3) software as described in the section, "Configuring CiscoWorks Release 1.0(3)."

Configuring CiscoWorks Release 1.0(3)

This section provides a detailed configuration procedure to help you respond to the questions posed by the configuration script.

After installing CiscoWorks and rebooting your system, you must configure CiscoWorks to fit your particular environment. The interactive configuration script will first prompt you to enter all of the required information, then ask you to confirm your choices before any actual changes are made to your system.

When you run the configuration script ncsconfigure, it performs the following actions:

Adds an entry to /etc/password for Sybase
Adds an entry to /etc/group for the CiscoWorks group
Adds CiscoWorks startup commands to /etc/rc.local

If you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files:

/usr/tmp/CW.group
/usr/tmp/CW.prod
/usr/tmp/CW.sybase

After completing the CiscoWorks configuration, use the information in these files to update your NIS server.

Detailed Procedure for New Configuration of CiscoWorks 1.0(3)

This detailed procedure describes how to configure CiscoWorks. Follow this procedure if you want an explanation of the information you need to provide during the configuration process.

Before beginning the CiscoWorks 1.0(3) configuration, make sure of the following:

You have filled out the Configuration Worksheet with the appropriate information. The configuration script will prompt you for this information. See the "Blank Worksheets" appendix and the "Configuration Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
You have SunNet Manager (SNM) installed on your system. The configuration script attempts to find SNM files. If it fails to find them, the configuration process is aborted.
You are logged in as a super user. If you are not logged in as a super user, CiscoWorks will be unable to complete the configuration. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.
Check your umask to ensure proper privileges. If your umask is set to 7 or 77, you need to change it to 022 in order for the ncsconfigure script to run correctly. To check your umask, enter umask at the UNIX prompt. To change your umask, enter umask 022 at the UNIX prompt. This is a temporary change since the umask is usually set in your .cshrc file and will revert back to the original setting.

Caution: If you do not check your umask setting, you may experience a failure in the ncsconfigure script. If you experience a configuration script failure, refer to the "Troubleshooting Installation and Configuration Problems" section for more detailed instructions.

The example configuration script that follows uses a directory named /usr/nms on a system called zen. Substitute the appropriate names and paths where necessary.

Step 1: After rebooting your system and logging in as a superuser, enter the following command and press Return to begin the CiscoWorks 1.0(3) configuration process:

zen# /usr/tmp/unbundled/ncsconfigure

Step 2: Specify that you are configuring a new installation of CiscoWorks by pressing Return to accept the default option.

******************CiscoWorks 1.0 CONFIGURATION**************        
CONFIGURATION SETUP  -  This section of the CiscoWorks 1.0 

configuration will ask you to verify the type of installation 

(new or upgrade) and the directory path where the product has 

been installed.
Is this a new installation of CiscoWorks 1.0, or an upgrade of 

an existing CiscoWorks 1.0 or NetCentral 1.3 installation?
Verify type of installation as (n)ew or (u)pgrade: [new]

Step 3: Confirm the directory where CiscoWorks software will be configured.

Verify the directory path for the CiscoWorks 1.0 software: 

[/usr/nms]

Press Return to accept the displayed directory. This is the same directory where you installed CiscoWorks.

Step 4: Confirm the type of installation and the directory where CiscoWorks will be configured.

Installation type          :  new        
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]

If you are using Network Information Service (NIS) at your site, the configuration script displays the following message:

*****************************************************************        
NIS CHECK - Your system appears to be running Network Information 
Service.
Your NIS Administrator should update your NIS server

with any new or modified groups and users. This

information is also added to your local host.
*****************************************************************

After completing CiscoWorks configuration, make sure that the NIS server is updated with the new or modified groups and users. If you are not using NIS, this NIS message will not appear.

GROUPS AND USERS - This section of the CiscoWorks 1.0 configuration 

will set up a UNIX group and users for the installed software.  

You will be asked for a group name, group id, and a list of 

group users.  Next, you will be asked to specify user information 

for ownership of the CiscoWorks 1.0 files followed by user 

information for ownership of the Sybase database files.  The 

users for CiscoWorks 1.0 and Sybase will be added to the group 

automatically.        
Refer to your system and CiscoWorks 1.0 documentation for 

instructions on adding/modifying groups and users after 

configuration is complete.
What would you like to call the CiscoWorks 1.0 group?  [CscWorks]

Press Return to accept the default option, or enter a name of your choice. The configuration script adds the group name to the /etc/group file.

Step 6: To accept the group ID number for the CscWorks group, press Return. Otherwise, specify a unique group ID number. The group ID number you accept or specify is added to the
/etc/group file on your system.

Group id for the CiscoWorks 1.0 group? [55]

Step 7: Add users to the CiscoWorks group. These users can access the CiscoWorks application if they already have login accounts on the system where you are installing the software. If these users do not have login accounts, you can create the login accounts after configuring CiscoWorks. Later, you also will be able to assign specific permissions for each user in this group by using the CiscoWorks Security Manager application, which is described in the CiscoWorks User Guide.

Enter CiscoWorks 1.0 group user names one line at a time.        
Terminate the list with an empty line.
Input users name>kwilson
Input users name>

Step 8: When you finish adding all the usernames, confirm the values by pressing Return.

Step 9: Confirm the values you entered earlier.

Using the following values for the CiscoWorks 1.0 group:        
CiscoWorks 1.0 Group Name     : CscWorks
CiscoWorks 1.0 Group ID       : 55
CiscoWorks 1.0 Group Users    : kwilson,cscworks,sybase
Are these values correct?  [yes]

To accept the displayed values, press Return. If you want to change any values at this time, enter n and press Return. You are returned to the beginning of the configuration script.

If you are using NIS at your site, the configuration script displays the following message:

****Please add this information to the NIS server:        
CscWorks:*:55:root, kwilson, cscworks, sybase
This information is saved to /usr/tmp/CW.group also

After completing CiscoWorks configuration, use the information in the /usr/tmp/CW.group file to update your NIS server.

Step 10: Specify a username for CiscoWorks.

What would you like to call the CiscoWorks 1.0 user name?  

[cscworks]

Press Return to accept the default username cscworks or enter a user name of your choice.

Step 11: Specify a unique user ID number for CiscoWorks or accept the default user ID that is displayed.

User ID for CiscoWorks 1.0 login? [100]

Press Return to accept the default user ID. Or enter a unique user ID number.

Step 12: Specify the full name for the CiscoWorks username.

Full name for CiscoWorks 1.0 user? [CiscoWorks]

Press Return to accept the default name.

Step 13: Specify the shell that will be used by CiscoWorks.

Shell for CiscoWorks 1.0 login? [/bin/csh]

Press Return to accept the default C-shell . Or enter a shell name of your choice.

Step 14: Confirm the values you chose for CiscoWorks.

Using the following values for the CiscoWorks 1.0 user:        
CiscoWorks 1.0 User Name          : cscworks
CiscoWorks 1.0 User ID            : 100
CiscoWorks 1.0 Group ID           : 55
CiscoWorks 1.0 Full Name          : CiscoWorks
CiscoWorks 1.0 Home Directory     : /usr/nms
CiscoWorks 1.0 Shell              : /bin/csh
Are these values correct? [yes]

Press Return to accept the displayed values. If you enter n, you are asked to specify the values again.

If you are using NIS at your site, the following message displays:

**** Please add this information to the NIS SERVER        
cscworks:*:100:55:CiscoWorks:/disk/cw1.0:/bin/csh
This information is saved to /usr/tmp/CW.prod also

After completing CiscoWorks configuration, use the information in the /usr/tmp/CW.prod file to update your NIS server.

Step 15: Specify a user ID for the Sybase login.

User ID for Sybase login? [101]

Press Return to accept the default user ID for the Sybase login, or specify a unique user ID.

Step 16: To accept the /bin/csh shell for Sybase login, press Return. Or specify a different shell.

Shell for Sybase login? [/bin/csh]

Step 17: Confirm whether the Sybase values are correct.

Using the following values for the Sybase user:        
Sybase User Name          : sybase
Sybase User ID            : 101
Sybase Group ID           : 55
Sybase Full Name          : Sybase
Sybase Home Directory     : /usr/nms/sybase
Sybase Shell              : /bin/csh
Are these values correct?  [yes]

To accept the values and continue, press Return. If you enter n, you are asked to specify the values again.

If you are using NIS at your site, the following message displays:

Please add this information to the NIS SERVER        
sybase:*:55:Sybase:/disk/cw1.0/sybase:/bin/csh
This information is saved to /usr/tmp/CW.sybase also.

After completing the CiscoWorks configuration, use the information in the /usr/tmp/CW.sybase file to update the information in your NIS server.

The /etc/passwd and /etc/group files are updated with the information you specified for CiscoWorks and Sybase.

Updating CscWorks group in /etc/group with kwilson,cscworks,

sybase ...

The configuration script also sets the owner and group permissions for CiscoWorks files.

FILE OWNERSHIP AND PERMISSIONS  -  The ownership of the 

CiscoWorks 1.0 files will be changed to the selected 

users and groups.  Permissions of specific files will be 

modified to enable execution and read/write capabilities.        
Setting the owner and group for CiscoWorks 1.0 software ...
chown -R cscworks.CscWorks /usr/nms/.
chown -R sybase /usr/nms/sybase
chown root /usr/nms/bin/nmsummary
...
Setting the permissions for CiscoWorks 1.0 software ...
chmod -R 750 /usr/nms
chmod 4750 /usr/nms/bin/nmsummary
...
chmod 770 /usr/nms/log

Step 18: To enable the addition of Cisco schema files to the SNM schema files, specify the complete path for the directory where you installed SNM.

SUNNET MANAGER MODIFICATIONS  -  A set of Cisco schema files must 

be added to the SunNet Manager schema files to enable SunNet 

Manager to to integrate CiscoWorks 1.0 functionality.  You need 

to specify the directory path for the SunNet Manager schema files.        
Directory path for SunNet Manager schema files? [/usr/snm]

If SNM was installed in the /usr/snm directory, press Return. Otherwise, enter the correct directory path for SNM.

The Cisco schema files are added to the SNM schema files.

Merging CiscoWorks 1.0 schemas with SunNet Manager ...        
cp /usr/nms/snm/agents/* /usr/snm/agents/
cp /usr/nms/snm/struct/* /usr/snm/struct/
cp /usr/nms/snm/icons/* /usr/snm/icons/
chmod +r /usr/snm/agents/*
chmod +r /usr/snm/struct/*
chmod +r /usr/snm/icons/*
Updating na.snmp.schemas in /etc/snm.conf ...
Running /usr/snm/bin/build_oid ...
Parsing /usr/snm/agents/enterprises.oid
Parsing /usr/snm/agents/snmp.oid
Parsing /usr/snm/agents/cisco.asn1.oid
Parsing /usr/snm/agents/sun-snmp.oid
Parsing /usr/snm/agents/snmp-mibII.oid
Writing /var/adm/snm/oid.dbase
SunNet Manager modifications completed.

The configuration script also opens the TCP ports for the Sybase installation and changes the Sybase interfaces file.

TCP PORTS  -  An open set of tcp ports will be identified for 

this new Sybase installation.  The ports will be defined in 

the Sybase interfaces file.        
Identifying open ports for Sybase ...
Using ports 8000 thru 8003
Defining ports in /usr/nms/sybase/interfaces file ...
/usr/nms/etc/setaddress 8000
Please wait...
Sybase interface file has been changed.

Step 19: To enable the configuration script to build and load the CiscoWorks database, press Return.

DATABASE STARTUP  -  This section of the CiscoWorks 1.0 

configuration will build and load the CiscoWorks 1.0 database.  

The Sybase dataserver and any daemons from previous 

installations will be halted.  Then, the new database will 

be built.  If this is an upgrade installation, data from 

the previous installation will be reloaded into the new 

database. Certain operations will require you to provide the 

Sybase 'sa' (system admin) password. Use password 'NULL' 

if this is a new installation.        
OK to continue (y/n)? [y]

Step 20: The Sybase dataserver must be halted before you continue with the CiscoWorks configuration. Press Return to halt the Sybase dataserver.


Halting Sybase dataserver and CiscoWorks 1.0 daemons ...        
Running /usr/nms/etc/load_nms ...
    **** Do not interrupt the execution of this script! ****
The load_nms script will create the Sybase master database 

and the nms database.  During database intensive operations, 

output may not be produced for several minutes.  If problems 

occur, this script can be run manually from /usr/nms/etc/load_nms.
Creating master.dat database file ...
Starting Sybase dataserver ...

Database (null) is alive        
Sybase is running.
No errors detected, the Database seems to be correctly installed.

The configuration script verifies that you set up TFTP on your system. If you plan to use the CiscoWorks Configuration Management application, and TFTP is not configured, complete the CiscoWorks configuration and then refer to the TFTP instructions in the section called "Setting Up TFTP," in the "Preparing to Install CiscoWorks" chapter.

TFTP CHECK  -  The CiscoWorks 1.0 Configuration Management 

application uses TFTP for configuration upload and download 

of Cisco devices.        
Correct operation of this feature requires that TFTP service 

be enabled and that the TFTP directory have the correct access 

permissions.
Checking for correct TFTP service configuration ...
TFTP is correctly configured.

Step 21: Specify the name of the log file to be used to store messages from the UNIX syslogd process.

SYSLOG MODIFICATIONS  -  The CiscoWorks 1.0 Log Manager application 

uses a centralized log file which gets messages from the UNIX 

syslogd process.  You will need to specify the log file name 

and which syslog facility (local0-local7) to use.  Use facility 

local7 if you want to log both CiscoWorks 1.0 messages and 

Cisco device messages; use a different facility if you want 

to log only CiscoWorks 1.0 messages.        
Enter log file to use for CiscoWorks 1.0 messages: 

[/var/log/nmslog]

Press Return to accept the default log file, or enter the directory path name and filename of your choice.

Step 22: Specify the facility to be used with syslog for logging messages. To log both CiscoWorks messages and Cisco device messages, accept the default facility, local7. To log only CiscoWorks messages, enter a different facility within the range of local0 through local6.

Enter syslog facility to use for CiscoWorks 1.0 messages: [local7]

To accept local7, press Return.

Step 23: If there are other applications that use the facility you chose, press Return to clear the facility for use by syslog.

OK to remove other syslog entries which use local7 (y/n)? [y]

Step 24: To confirm the values you specified for the log files and the syslog facility, press Return.

The log file will b        e : /var/log/nmslog
The syslog facility will be : local7
Remove other syslog entries which use local7 y
Are these values correct (y/n)? [y]

The syslog modifications are completed.

Step 25: To enable the configuration script to install nmstartup and modify the /etc/rc.local file, press Return.

RC.LOCAL MODIFICATIONS  -  The Sybase dataserver and other 

CiscoWorks 1.0 daemons must be running as background processes 

for correct operation of CiscoWorks 1.0.  This section of 

the configuration will modify the file /etc/rc.local to include 

nmstartup which will start the Sybase dataserver and CiscoWorks 1.0 

daemons during system reboot.        
Checking for nmstartup in /etc/rc.local ...
Install nmstartup for CiscoWorks 1.0 in /etc/rc.local (y/n)? [y]

Step 26: If you want the centralized log file syslog to be automatically purged and backed up every day, press Return. As a result, the CiscoWorks log purging utility is started automatically by the UNIX cron daemon. If you do not want the syslog file to be purged and backed up automatically every day, enter n. For information on customizing the log purge utility and editing the crontab file, refer to the CiscoWorks User Guide.

CRON MODIFICATIONS  -  The syslog file must be purged 

periodically to avoid running out of disk space.  This 

activity is automated by the CiscoWorks 1.0 log purge utility 

when scheduled by the UNIX cron daemon. This will purge 

syslog daily and maintain a seven day history of syslog files.        
Schedule the CiscoWorks 1.0 log purge utility to run daily (y/n)? 

[y]

If you pressed Return, the crontab file modifications are completed.

Make sure that you set up the environment variables and the paths by following the instructions in the section, "Defining Environment Variables and Search Paths" in the "Validating CiscoWorks Installation" chapter.

CONFIGURATION COMPLETE  -  Various environment variables must 

be defined for correct operation of CiscoWorks 1.0. You can 

append the following lines to the .login or .cshrc file of 

CiscoWorks 1.0 users so that required environment variables 

will be set correctly:        
#   Set environment variables for CiscoWorks 1.0.
setenv SNMHOME /usr/snm
setenv NMSROOT /usr/nms
setenv SYBASE /usr/nms/sybase
#   Set path for CiscoWorks 1.0 man pages.
if (!($?MANPATH)) setenv MANPATH /usr/man

setenv MANPATH "$MANPATH":"$NMSROOT"/man
#   Set path for CiscoWorks 1.0 executables.
set path=($path /usr/nms/bin /usr/nms/etc)
Refer to the CiscoWorks 1.0 Getting Started Guide for instructions 

on validating your installation and configuration.
zen#

The configuration is complete. To eject the CD-ROM enter the following commands:

hostname# cd /         
hostname# eject sr0

If you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files: /usr/tmp/CW.group, /usr/tmp/CW.prod, and /usr/tmp/CW.sybase. Use the information in these files to update your NIS server.

If you wish to remove the log files that were created when installing and configuring Cisco Works, see the section, "Cleaning Up Log Files." Otherwise, proceed to the "Validating CiscoWorks Installation" chapter.

Performing a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade

This section provides CiscoWorks Release 1.0(3) installation and configuration scripts for a NetCentral Release 1.3 upgrade installation and configuration. The "Sample Installation Dialog for a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade" section gives you a quick overview of the type of information displayed and requested by the installation script. The "Sample Configuration Dialog for a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade" section gives you a quick overview of the type of information displayed and requested by the configuration script.

CiscoWorks 1.0(3) software is distributed on a CD-ROM. You can install CiscoWorks from a CD-ROM drive attached to your system locally or from a CD-ROM drive attached to a remote system.

You install CiscoWorks 1.0(3) by invoking and running the ./extract_unbundled script supplied on the CD-ROM. The ./extract_unbundled script provides an interactive prompt and response dialog interface that guides you through the installation process.

Note: You can exit the installation script at any time by entering Control-C (^C) to return to the UNIX environment. The responses you make up to the point you exit will be recorded for use as the defaults the next time you start the installation process.

When you run the configuration script ncsconfigure, it performs the following actions:

Adds an entry to /etc/password for Sybase and CiscoWorks
Adds an entry to /etc/group for the CiscoWorks group
Adds CiscoWorks startup commands to /etc/rc.local

If you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files:

/usr/tmp/CW.group
/usr/tmp/CW.prod
/usr/tmp/CW.sybase

After completing the CiscoWorks configuration, use the information in these files to update your NIS server.

The installation and configuration process takes approximately 20 to 30 minutes, although the amount of time can vary depending on your system performance and installation method. An installation from a CDROM drive attached to a remote device might take longer.

Sample Installation Dialog for a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade

This section provides an example installation script dialog for upgrading NetCentral 1.3 to CiscoWorks Release 1.0(3).

Before beginning your CiscoWorks 1.0 installation, be certain of the following:

You have filled out the Installation Worksheet with the appropriate information. See the "Blank Worksheets" appendix and the "Installation Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
You have mounted the CD-ROM properly. See the section entitled "Installing from a Local or Remote CDROM," in the "Preparing to Install CiscoWorks" chapter.
You are logged in as a super user. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The following are the values and Sun system used for the installation procedure and script in this section:

/usr/nms is the name of the directory where the software is installed.
zen is the name of the system where CiscoWorks is being installed.
The Sun SPARCstation is using Sun4c architecture.

Substitute the appropriate names and directory path names when you install the software.

zen# cd /cdrom        
zen# ./extract_unbundled

Note: When invoking the ./extract_unbundled script, make sure you specify the complete syntax with the period (.) and the slash (/) to ensure that you run the correct version of this command.


./extract_unbundled: The following product will be installed:        
****************************************************************************
                          CiscoWorks Version 1.0(3)
                Copyright (c) 1986-1993 by Cisco Systems, Inc.
                             All rights reserved
****************************************************************************
Do you want to continue (y/n)?  [y]
./extract_unbundled: Extracting installation scripts ...
x ./install_unbundled, 717 bytes, 2 tape blocks
x ./1.0_CiscoWorks, 18774 bytes, 37 tape blocks
x ./ncsconfigure, 66695 bytes, 131 tape blocks
x ./ncskernel, 7953 bytes, 16 tape blocks
x ./.install/config.defs, 429 bytes, 1 tape blocks
x ./.install/nmcopyout, 4935 bytes, 10 tape blocks
x ./.install/exclude.sun4, 0 bytes, 0 tape blocks
x ./.install/find.sun4, 10081 bytes, 20 tape blocks
x ./.install/include.install, 244 bytes, 1 tape blocks
x ./.install/upgrade_nms, 13279 bytes, 26 tape blocks
x ./.install/variables, 176 bytes, 1 tape blocks
x ./.install/dbunload, 3036 bytes, 6 tape blocks
./extract_unbundled: Starting installation process ...
./extract_unbundled: /usr/tmp/unbundled/install_unbundled -c/cdrom -f
/usr/tmp/unbundled/install_unbundled: Starting installation script /usr/tmp/unbundled/

1.0_CiscoWorks ...
/usr/tmp/unbundled/install_unbundled: /usr/tmp/unbundled/1.0_CiscoWorks -c/cdrom -f
********************** CiscoWorks 1.0 INSTALLATION **********************
INSTALLATION SETUP  -  This section of the CiscoWorks 1.0 installation
will ask you to specify the type of installation (new or upgrade) and
the directory path for the product installation.  Existing NetCentral
data will be saved if this is an upgrade, and the new directory
structure will be setup.
Is this a new installation of CiscoWorks 1.0, or an upgrade of an
existing CiscoWorks 1.0 or NetCentral 1.3 installation?
Enter type of installation as (n)ew or (u)pgrade: [new] u
What directory contains the existing installation? [/usr/nms]
Installation type          :  upgrade
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]
CDROM INSTALLATION - This section of the CiscoWorks 1.0 installation
will load files from the installation cdrom into the /usr/nms directory.
CiscoWorks 1.0 installation will take approximately 20 minutes.
Installing CiscoWorks 1.0 ...

uncompress -c /cdrom/ciscoworks/sun4.ncs.tar.Z | tar xvfpB - 2>&1 | tee /disk/tmp

/unbundled/.install/tar.log | cat -u
x ./snm/agents/cisco.schema, 113239 bytes, 222 tape blocks
x ./snm/agents/cisco.asn1.oid, 20825 bytes, 41 tape blocks
x ./snm/agents/snmp-mibII.oid, 8094 bytes, 16 tape blocks
...
...
x ./help/nmhealth.hlp, 6507 bytes, 13 tape blocks
Finished installing CiscoWorks 1.0.
About to install upgrade to Sybase version 4.9.1
To upgrade your Sybase server you will need xxxxx Megabytes of free disk space
If you don't have enough space on the /usr/nms device,
you can enter a new path for the installation here,
otherwise press return to accept /usr/nms/syb491:
Installing Sybase Database & Server ...
uncompress -c /cdrom/sybase/sybase.sun4.tar.Z | tar xvfpB - 2>&1 | tee /disk/tmp
/unbundled/.install/tar.log | cat -u
x ./sybase/bin/apt.std, 1630208 bytes, 3184 tape blocks
x ./sybase/bin/apt, 998 bytes, 2 tape blocks
...
...
x ./sybase/interfaces.dist, 132 bytes, 1 tape blocks
Finished installing upgrade to sybase 4.9.1
Verifying installed files ...
Installation verified - CiscoWorks 1.0 files loaded correctly.
KERNEL MODIFICATIONS  -  This section of the CiscoWorks 1.0 installation
will make sybase modifications to your system kernel. You will be
prompted for an existing kernel configuration file to use as a base for
the new system kernel; the default is your current kernel configuration.
After this script has completed successfully, you must reboot your
system for the kernel modifications to take effect.
You may decide to skip this section of the installation if:
1.  Your kernel has already been modified for Sybase 4.9.1,
2.  You wish to modify and rebuild your kernel manually, or
3.  Sybase will not be running on this system.
OK to continue with kernel modifications (y/n)? [y]
Please enter System Configuration file or (q)uit: [GENERIC]
The base kernel configuration file is           : /sys/sun4c/conf/GENERIC
The new kernel configuration file will be       : /sys/sun4c/conf/SYBASE
The old kernel will be saved as                 : /vmunix.syb_inst
The new SYBASE kernel will be installed as:     : /usr/tmp/unbundled/ncskernel.log
Are these values correct (y/n) ? [y]
Saving old kernel as /vmunix.syb_inst ...
Creating /sys/sun4c/conf/SYBASE ...

Configuring /sys/sun4c/conf/SYBASE ...
Building SYBASE kernel from /sys/sun4c/conf/SYBASE ...
Installing new system kernel ...
SYBASE kernel modifications completed - Reboot your system to use the
new kernel before you proceed with CiscoWorks 1.0 configuration.
REBOOT NOW!
CiscoWorks 1.0 Installation completed - continue with CiscoWorks 1.0
configuration by starting /usr/tmp/unbundled/ncsconfigure.
zen# reboot

The installation is complete. When the workstation has rebooted, you are ready to configure the CiscoWorks 1.0(3) software. For a sample upgrade configuration script, see "Sample Configuration Dialog for a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade."

Sample Configuration Dialog for a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade

This section shows an example configuration script dialog for upgrading NetCentral 3.1 to CiscoWorks 1.0(3).

Before beginning the CiscoWorks 1.0(3) configuration, make sure of the following:

You have filled out the Configuration Worksheet with the appropriate information. The configuration script will prompt you for this information. See the "Blank Worksheets" appendix and the "Configuration Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
SunNet Manager (SNM) is installed on your system. The configuration script attempts to find SNM files. If it fails to find them, the configuration process is aborted.
You are logged in as a super user. If you are not logged in as a super user, CiscoWorks will be unable to complete the configuration. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.
Check your umask to ensure proper privileges. If your your umask is set to 7 or 77, you need to change it to 022 in order for the ncsconfigure script to run correctly. To check your umask, enter umask at the UNIX prompt. To change your umask, enter umask 022 at the UNIX prompt. This is a temporary change since the umask is usually set in your .cshrc file and will revert back to the original setting.

Caution: If you do not check your umask setting, you may experience a failure in the ncsconfigure script. If you experience a configuration script failure, refer to the "Troubleshooting Installation and Configuration Problems" section for more detailed instructions.

If you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files:

/usr/tmp/CW.group
/usr/tmp/CW.prod
/usr/tmp/CW.sybase

After completing the CiscoWorks configuration, use the information in these files to update your NIS server.

The example configuration script that follows uses a directory named /usr/nms on a system called zen. Substitute the appropriate names and paths where necessary.

        zen# /usr/tmp/unbundled/ncsconfigure
********************** CiscoWorks 1.0 CONFIGURATION **********************
CONFIGURATION SETUP  -  This section of the CiscoWorks 1.0 configuration
will ask you to verify the type of installation (new or upgrade) and
the directory path where the product has been installed.
Is this a new installation of CiscoWorks 1.0, or an upgrade of an
existing CiscoWorks 1.0 or NetCentral 1.3 installation?
Verify type of installation as (n)ew or (u)pgrade: [upgrade]
Verify the directory path for the CiscoWorks 1.0 software: [/usr/nms]
Installation type          :  upgrade
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]
*****************************************************************
NIS CHECK - Your system appears to be running Network Information

Service. Your NIS Administrator should update your NIS server
with any new or modified groups and users. This
information is also added to your local host.
*****************************************************************

Note: If you are not using NIS, the NIS-related information is not displayed by the configuration script.

GROUPS AND USERS - This section of the CiscoWorks 1.0 configuration will        
set up a UNIX group and users for the installed software.  You will be
asked for a group name, group id, and a list of group users.  Next,
you will be asked to specify user information for ownership of the
CiscoWorks 1.0 files followed by user information for ownership of the
Sybase database files.  The users for CiscoWorks 1.0 and Sybase will be
added to the group automatically.
Refer to your system and CiscoWorks 1.0 documentation for instructions
on adding/modifying groups and users after configuration is complete.
What is the name of the existing CiscoWorks 1.0 group?  [CscWorks]
Using the following values for the CiscoWorks 1.0 group:
CiscoWorks 1.0 Group Name     : CscWorks
CiscoWorks 1.0 Group ID       : 55
CiscoWorks 1.0 Group Users    : kwilson,cscworks,sybase
Are these values correct?  [yes]
****Please add this information to the NIS server:
CscWorks:*:55:root, kwilson, cscworks, sybase
This information is saved to /usr/tmp/CW.group also
What is the name of the existing CiscoWorks 1.0 login?  [cscworks]
Using the following values for the CiscoWorks 1.0 user:
CiscoWorks 1.0 User Name          : cscworks
CiscoWorks 1.0 User ID            : 100
CiscoWorks 1.0 Group ID           : 55
CiscoWorks 1.0 Full Name          : CiscoWorks
CiscoWorks 1.0 Home Directory     : /usr/nms
CiscoWorks 1.0 Shell              : /bin/csh
Are these values correct? [yes]
**** Please add this information to the NIS SERVER
cscworks:*:100:55:CiscoWorks:/disk/cw1.0:/bin/csh
This information is saved to /usr/tmp/CW.prod also
Using the following values for the Sybase user:
Sybase User Name          : sybase
Sybase User ID            : 101
Sybase Group ID           : 55
Sybase Full Name          : Sybase
Sybase Home Directory     : /usr/nms/sybase
Sybase Shell              : /bin/csh

Are these values correct?  [yes]
Please add this information to the NIS SERVER
sybase:*:55:Sybase:/disk/cw1.0/sybase:/bin/csh
This information is saved to /usr/tmp/CW.sybase also.
Updating CscWorks group in /etc/group with kwilson,cscworks,sybase ...
FILE OWNERSHIP AND PERMISSIONS  -  The ownership of the CiscoWorks 1.0
files will be changed to the selected users and groups.  Permissions
of specific files will be modified to enable execution and read/write
capabilities.
Setting the owner and group for CiscoWorks 1.0 software ...
chown -R cscworks.CscWorks /usr/nms/.
chown -R sybase /usr/nms/sybase
chown root /usr/nms/bin/nmsummary
chown root /usr/nms/bin/nmpoll
chown root /usr/nms/bin/nmproc
chown root /usr/nms/bin/nmpath
chown root /usr/nms/bin/nmdevmon
chown root /usr/nms/contrib/tcpdump
Setting the permissions for CiscoWorks 1.0 software ...
chmod -R 750 /usr/nms
chmod 4750 /usr/nms/bin/nmsummary
chmod 4750 /usr/nms/bin/nmpoll
chmod 4750 /usr/nms/bin/nmproc
chmod 4750 /usr/nms/bin/nmpath
chmod 4750 /usr/nms/bin/nmdevmon
chmod 4750 /usr/nms/contrib/tcpdump
chmod 660 /usr/nms/etc/ncspwd
chmod 770 /usr/nms/log
Do you wish to install the new MIB files? [yes]
SUNNET MANAGER MODIFICATIONS  -  A set of Cisco schema files must be
added to the SunNet Manager schema files to enable SunNet Manager
to integrate CiscoWorks 1.0 functionality.  You need to specify the
directory path for the SunNet Manager schema files.
Directory path for SunNet Manager schema files? [/usr/snm]
Merging CiscoWorks 1.0 schemas with SunNet Manager ...
cp /usr/nms/snm/agents/* /usr/snm/agents/
cp /usr/nms/snm/struct/* /usr/snm/struct/
cp /usr/nms/snm/icons/* /usr/snm/sun4/snm/icons/
cp /usr/nms/snm/traps/cisco.traps /var/adm/snm/
chmod +r /usr/snm/agents/*
chmod +r /usr/snm/struct/*
chmod +r /usr/snm/icons/*
chmod +r /var/adm/snm/*
Running /usr/snm/bin/build_oid ...

Parsing /usr/snm/agents/enterprises.oid
Parsing /usr/snm/agents/snmp.oid
Parsing /usr/snm/agents/sun-snmp.oid
Parsing /usr/snm/agents/cisco.asn1.oid
Parsing /usr/snm/agents/snmp-mibII.oid
Writing /var/adm/snm/oid.dbase
SunNet Manager modifications completed.
DATABASE STARTUP - This section of the CiscoWorks 1.0 configuration will
build and load the CiscoWorks 1.0 database. The Sybase dataserver and 
any daemons from previous installations will be halted. Then the new 
database will be built. If this is an upgrade installation, data from
the previous installation will be reloaded into the new database.
Certain operations will require you to provide the Sybase `sa' (system 
admin) password. Use password `NULL' if this is a new installation.
OK to continue (y/n)? [y]
Halting Sybase dataserver and CiscoWorks 1.0 daemons ...
Running /usr/nms/etc/load_nms ...
  **** Do not interrupt the execution of this script! ****
The load_nms script will create the Sybase master database and the
nms database. During database intensive operations, output may not 
be produced for several minutes. If problems occur, this script can
be run manually from /usr/nms/etc/load_nms.
Creating master.dat database file ...
Starting Sybase dataserver ...
Waiting for server to complete initialization...
Loading master database schema ... (ignore message about sp_configure)
Loading master database ... (ignore message about unexpected EOF)
`Disk' device added.
(return status = 0)
DB-LIBRARY error:
  Unexpected EOF from SQL Server.
Restarting Sybase dataserver with new master database.
Creating new nms database ...
CREATE DATABASE: allocating 3072 pages on disk `nms'
CREATE DATABASE: allocating 2048 pages on disk `nms'
Loading nms database ... (ignore message about unexpected EOF)
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
Run the CHECKPOINT command in the database that was changed.
(return status = 0)
Server SHUTDOWN by request.
The SQL Server is terminating this process.

DB-LIBRARY error:
  Unexpected EOF from SQL Server.
/usr/nms/sybase/install
Sybase database installation and load is complete.
Upgrading database files ...
Start the new server on the old database ...
00: 02/Waiting for server to complete initialization ...
00: 92/10/12 08:50:11.96 kernel:SQL Server/4.8/EBF 984/Sun 4/SunOS 4.1.X/55/OPT/
Thu Aug 6 10:29:22 PDT 1992
00: 92/10/12 08:50:11.98 kernel: Sybase SMP SQL Server 4.8
00: 92/10/12 08:50:11.98 kernel: Confidential Property of Sybase, Inc.
...................................................
Loading database data from old server in new server ...
Where did you save the database data? [/usr/tmp]
Creating table testpoll
Creating table nms_rev_history
(0 rows affected)
(1 row affected)
(2 rows affected)
Database (null) is alive
Sybase is running.
No errors detected, the Database seems to be correctly installed.
TFTP CHECK  -  The CiscoWorks 1.0 Configuration Management application
uses TFTP for configuration upload and download of Cisco devices.
Correct operation of this feature requires that TFTP service be enabled
and that the TFTP directory have the correct access permissions.
Checking for correct TFTP service configuration ...
TFTP is correctly configured.
SYSLOG MODIFICATIONS  -  The CiscoWorks 1.0 Log Manager application
uses a centralized log file which gets messages from the UNIX syslogd
process.  You will need to specify the log file name and which syslog
facility (local0-local7) to use.  Use facility local7 if you want to
log both CiscoWorks 1.0 messages and Cisco device messages; use a
different facility if you want to log only CiscoWorks 1.0 messages.
Enter log file to use for CiscoWorks 1.0 messages: [/var/log/nmslog]
/var/log/nmslog already exists!  Use this file anyway (y/n)? [y]
Enter syslog facility to use for CiscoWorks 1.0 messages: [local7]
OK to remove other syslog entries which use local7 (y/n)? [y]
The log file will be                          : /var/log/nmslog
The syslog facility will be                   : local7
Remove other syslog entries which use local7  : y
Are these values correct (y/n)? [y]
Syslog modifications in progress ...
NMSLOGFILE = /var/log/nmslog
INSTALL = upgrade

Resetting database and system logs ...
logpurg 1.0(2.8) Alpha starting:
        Process id = 842
        Debugging: = Off
logpurg started at: Fri Jul 23 17:19:21 1993
logpurg completed
Syslog modifications completed.
Start the CiscoWorks 1.0 processes and database server (y/n)? [y]
Starting CiscoWorks 1.0.  Please wait ...
RC.LOCAL MODIFICATIONS  -  The Sybase dataserver and other CiscoWorks 1.0

daemons must be running as background processes for correct operation

of CiscoWorks 1.0.  This section of the configuration will modify the file

/etc/rc.local to include nmstartup which will start the Sybase dataserver

and CiscoWorks 1.0 daemons during system reboot.
Checking for nmstartup in /etc/rc.local ...
Old version of nmstartup detected in /etc/rc.local!
Update existing nmstartup for CiscoWorks 1.0 in /etc/rc.local (y/n)? [y]
Updating nmstartup for CiscoWorks 1.0 in /etc/rc.local ...
/etc/rc.local modifications completed.
CRON MODIFICATIONS  -  The syslog file must be purged periodically
to avoid running out of disk space.  This activity is automated by the
CiscoWorks 1.0 log purge utility when scheduled by the UNIX cron daemon.
This will purge syslog daily and maintain a seven day history of syslog
files.
Schedule the CiscoWorks 1.0 log purge utility to run daily (y/n)? [y]
Adding line "0 2 * * * /usr/nms/bin/purge /usr/nms" to crontab 
...
Cron modifications completed.
CONFIGURATION COMPLETE  -  Various environment variables must be defined
for correct operation of CiscoWorks 1.0. You can append the following lines
to the .login or .cshrc file of CiscoWorks 1.0 users so that required
environment variables will be set correctly:
#   Set environment variables for CiscoWorks 1.0.
setenv SNMHOME /usr/snm
setenv NMSROOT /usr/nms
setenv SYBASE /usr/nms/sybase
#   Set path for CiscoWorks 1.0 man pages.
if (!($?MANPATH)) setenv MANPATH /usr/man
setenv MANPATH "$MANPATH":"$NMSROOT"/man
#   Set path for CiscoWorks 1.0 executables.
set path=($path /usr/nms/bin /usr/nms/etc)
Refer to the CiscoWorks 1.0 Getting Started Guide for instructions on
validating your installation and configuration.

The configuration is complete. To eject the CD-ROM enter the following commands:

hostname# cd /         
hostname# eject sr0

If you wish to remove the log files that were created when installing and configuring Cisco Works, see "Cleaning Up Log Files." Otherwise, proceed to the "Validating CiscoWorks Installation" chapter.

Performing a CiscoWorks Release 1.0 or 1.0(2) to Release 1.0(3) Upgrade

This section provides the CiscoWorks Release 1.0(3) installation and configuration scripts for a CiscoWorks Release 1.0 or 1.0(2) upgrade installation and configuration. Refer to this section if you are upgrading from CiscoWorks Release 1.0 or 1.0(2) to CiscoWorks Release 1.0(3).

Note: If you are upgrading from NetCentral Release 1.3 to CiscoWorks Release 1.0(3), refer to the section "Performing a NetCentral 1.3 to CiscoWorks 1.0(3) Upgrade."

Remember to backup your Sybase database before continuing with the upgrade.

CiscoWorks 1.0(3) software is distributed on CD-ROM. You can install CiscoWorks from a CD-ROM drive attached to your system or from a CD-ROM drive attached to a remote system.You install CiscoWorks by changing to the /cdrom directory and invoking and running the ./extract_unbundled script which is supplied on the CDROM. The ./extract_unbundled script provides an interactive prompt and response dialog interface that guides you through the installation process.

Note: You can exit the installation script at any time by entering Control-C (^C) to return to the UNIX environment. The responses you made up to the point you exit will be recorded for use as the defaults the next time you start the installation process.

When you run the configuration script ncsconfigure, it performs the following actions:

Adds an entry to /etc/password for Sybase and CiscoWorks
Adds an entry to /etc/group for the CiscoWorks group
Adds CiscoWorks startup commands to /etc/rc.local

If you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files:

/usr/tmp/CW.group
/usr/tmp/CW.prod
/usr/tmp/CW.sybase

After completing the CiscoWorks configuration, use the information in these files to update your NIS server.

The installation and configuration process takes 20 to 30 minutes, although the amount of time can vary depending on your system performance and installation method. An installation from a CD-ROM drive attached to a remote device might take longer.

Sample Installation Dialog for a CiscoWorks Release 1.0 Upgrade

This section provides an example installation script dialog for an upgrade installation of CiscoWorks Release 1.0 or 1.0(2) to Release 1.0(3).

Before beginning your CiscoWorks upgrade installation, be certain of the following:

You have filled out the Installation Worksheet with the appropriate information. See the "Blank Worksheets" appendix and the "Installation Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
You have mounted the CD-ROM properly. See the section entitled "Installing from a Local or Remote CDROM," in the "Preparing to Install CiscoWorks" chapter.
You are logged in as a super user. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.

The following are the values and Sun system used for the installation procedure and script in this section:

/usr/nms is the name of the directory where the software is installed.
zen is the name of the system where CiscoWorks is being installed.
The Sun SPARCstation is using Sun4c architecture.

Substitute the appropriate names and directory path names when you install the software.

zen# cd /cdrom        
zen# ./extract_unbundled

Note: When invoking the ./extract_unbundled script, make sure you specify the complete syntax with the period (.) and the slash (/) to ensure that you run the correct version of this command.


./extract_unbundled: The following product will be installed:        
****************************************************************************
                          CiscoWorks Version 1.0(3)
                Copyright (c) 1986-1993 by Cisco Systems, Inc.
                             All rights reserved
****************************************************************************
Do you want to continue (y/n)?  [y]
./extract_unbundled: Extracting installation scripts ...
x ./install_unbundled, 717 bytes, 2 tape blocks
x ./1.0_CiscoWorks, 18774 bytes, 37 tape blocks
x ./ncsconfigure, 66695 bytes, 131 tape blocks
x ./ncskernel, 7953 bytes, 16 tape blocks
x ./.install/config.defs, 429 bytes, 1 tape blocks
x ./.install/nmcopyout, 4935 bytes, 10 tape blocks
x ./.install/exclude.sun4, 0 bytes, 0 tape blocks
x ./.install/find.sun4, 10081 bytes, 20 tape blocks
x ./.install/include.install, 244 bytes, 1 tape blocks
x ./.install/upgrade_nms, 13279 bytes, 26 tape blocks
x ./.install/variables, 176 bytes, 1 tape blocks
x ./.install/dbunload, 3036 bytes, 6 tape blocks
./extract_unbundled: Starting installation process ...
./extract_unbundled: /usr/tmp/unbundled/install_unbundled -c/cdrom -f
/usr/tmp/unbundled/install_unbundled: Starting installation script /disk/tmp

/unbundled/1.0_CiscoWorks ...
/usr/tmp/unbundled/install_unbundled: /disk/tmp/unbundled/1.0_CiscoWorks 

-c/cdrom -f
********************** CiscoWorks 1.0 INSTALLATION **********************
INSTALLATION SETUP  -  This section of the CiscoWorks 1.0 installation
will ask you to specify the type of installation (new or upgrade) and
the directory path for the product installation.  Existing NetCentral
data will be saved if this is an upgrade, and the new directory
structure will be setup.
Is this a new installation of CiscoWorks 1.0, or an upgrade of an
existing CiscoWorks 1.0 or NetCentral 1.3 installation?
Enter type of installation as (n)ew or (u)pgrade: [new] u
What directory contains the existing installation? [/disk/netcentral]
Installation type          :  upgrade
Destination directory      :  /disk/netcentral
Destination directory      :  /disk/netcentral

Are these values correct (y/n)? [y]
CDROM INSTALLATION - This section of the CiscoWorks 1.0 installation
will load files from the installation cdrom into the /disk/netcentral
directory.
CiscoWorks 1.0 installation will take approximately 20 minutes.
Installing CiscoWorks 1.0 ...
uncompress -c /cdrom/ciscoworks/sun4.ncs.tar.Z | tar xvfpB - 2>&1 | tee /disk/tmp

/unbundled/.install/tar.log | cat -u
x ./snm/agents/cisco.schema, 113239 bytes, 222 tape blocks
x ./snm/agents/cisco.asn1.oid, 20825 bytes, 41 tape blocks
x ./snm/agents/snmp-mibII.oid, 8094 bytes, 16 tape blocks
x ./snm/struct/cisco-elements.schema, 14702 bytes, 29 tape blocks
x ./snm/icons/3000.icon, 622 bytes, 2 tape blocks
x ./snm/icons/3000.iconmask, 622 bytes, 2 tape blocks
x ./snm/icons/4000.icon, 622 bytes, 2 tape blocks
...
...
x ./help/nmsync.hlp, 3081 bytes, 7 tape blocks
x ./help/nmhealth.hlp, 6507 bytes, 13 tape blocks
Finished installing CiscoWorks 1.0.
About to install upgrade to Sybase version 4.9.1
To upgrade your Sybase server you will need 63.8135 Megabytes of free disk space
If you don't have enough space on the /disk/netcentral device,
you can enter a new path for the installation here,
otherwise press return to accept /disk/netcentral/syb491:
Installing Sybase Database & Server ...
uncompress -c /cdrom/sybase/sybase.sun4.tar.Z | tar xvfpB - 2>&1 | tee /disk/tmp

/unbundled/.install/tar.log | cat -u
x ./sybase/bin/apt.std, 1630208 bytes, 3184 tape blocks
x ./sybase/bin/apt, 998 bytes, 2 tape blocks
x ./sybase/bin/aptcompile, 499712 bytes, 976 tape blocks
x ./sybase/bin/apt.x11, 1654784 bytes, 3232 tape blocks
x ./sybase/bin/aptexec.std, 1056768 bytes, 2064 tape blocks
x ./sybase/bin/aptconv, 1081344 bytes, 2112 tape blocks
x ./sybase/bin/aptexec, 2718 bytes, 6 tape blocks
x ./sybase/bin/buildmaster, 860160 bytes, 1680 tape blocks
x ./sybase/bin/aptexec.x11, 1081344 bytes, 2112 tape blocks
x ./sybase/bin/aptmig, 1056768 bytes, 2064 tape blocks
...
...
x ./sybase/termdef/xterm_c.sun, 1602 bytes, 4 tape blocks
x ./sybase/interfaces.dist, 132 bytes, 1 tape blocks
Finished installing upgrade to sybase 4.9.1
Verifying installed files ...
Installation verified - CiscoWorks 1.0 files loaded correctly.
KERNEL MODIFICATIONS  -  This section of the CiscoWorks 1.0 installation

will make sybase modifications to your system kernel.  You will be
prompted for an existing kernel configuration file to use as a base for
the new system kernel; the default is your current kernel configuration.
After this script has completed successfully, you must reboot your
system for the kernel modifications to take effect.
You may decide to skip this section of the installation if:
1.  Your kernel has already been modified for Sybase 4.9.1,
2.  You wish to modify and rebuild your kernel manually, or
3.  Sybase will not be running on this system.
OK to continue with kernel modifications (y/n)? [y] n
****  Skipping kernel configuration ...
****  Kernel configuration not modified!
CiscoWorks 1.0 Installation completed - continue with CiscoWorks 1.0
configuration by starting /usr/tmp/unbundled/ncsconfigure.

The installation is complete. When the workstation has rebooted, you are ready to configure the CiscoWorks 1.0(3) software. For a sample upgrade configuration script , see "Sample Configuration Dialog for a CiscoWorks Release 1.0 Upgrade."

Sample Configuration Dialog for a CiscoWorks Release 1.0 Upgrade

This section provides an example configuration script dialog for an upgrade of CiscoWorks Release 1.0 or 1.0(2) to Release 1.0(3).

Before beginning the CiscoWorks 1.0(3) configuration, make sure of the following:

You have filled out the Configuration Worksheet with the appropriate information. The configuration script will prompt you for this information. See the "Blank Worksheets" appendix and the "Configuration Worksheet Items" section in the "Preparing to Install CiscoWorks" chapter.
SunNet Manager (SNM) is installed on your system. The configuration script attempts to find SNM files. If it fails to find them, the configuration process is aborted.
You are logged in as a super user. If you are not logged in as a super user, CiscoWorks will be unable to complete the configuration. See "Becoming a Super User," in the "Preparing to Install CiscoWorks" chapter.
Check your umask to ensure proper privileges. If your your umask is set to 7 or 77, you need to change it to 022 in order for the ncsconfigure script to run correctly. To check your umask, enter umask at the UNIX prompt. To change your umask, enter umask 022 at the UNIX prompt. This is a temporary change since the umask is usually set in your .cshrc file and will revert back to the original setting.

If you are using Network Information Service (NIS) at your site, the configuration script saves NIS-related information during the configuration to the following files:

/usr/tmp/CW.group
/usr/tmp/CW.prod
/usr/tmp/CW.sybase

After completing the CiscoWorks configuration, use the information in these files to update your NIS server.

The example configuration script that follows uses a directory named /usr/nms on a system called zen. Substitute the appropriate names and paths where necessary.

zen# /usr/tmp/unbundled/ncsconfigure        
********************** CiscoWorks 1.0 CONFIGURATION **********************
CONFIGURATION SETUP  -  This section of the CiscoWorks 1.0 configuration
will ask you to verify the type of installation (new or upgrade) and
the directory path where the product has been installed.
Is this a new installation of CiscoWorks 1.0, or an upgrade of an
existing CiscoWorks 1.0 or NetCentral 1.3 installation?

Verify type of installation as (n)ew or (u)pgrade: [upgrade]
Verify the directory path for the CiscoWorks 1.0 software: [/usr/nms]
Installation type          :  upgrade
Destination directory      :  /usr/nms
Are these values correct (y/n)? [y]
*****************************************************************
NIS CHECK - Your system appears to be running Network Information
Service. Your NIS Administrator should update your NIS server
with any new or modified groups and users. This
information is also added to your local host.
*****************************************************************
GROUPS AND USERS - This section of the CiscoWorks 1.0 configuration will
set up a UNIX group and users for the installed software.  You will be
asked for a group name, group id, and a list of group users.  Next,
you will be asked to specify user information for ownership of the
CiscoWorks 1.0 files followed by user information for ownership of the
Sybase database files.  The users for CiscoWorks 1.0 and Sybase will be
added to the group automatically.
Refer to your system and CiscoWorks 1.0 documentation for instructions
on adding/modifying groups and users after configuration is complete.
What is the name of the existing CiscoWorks 1.0 group?  [CscWorks]
Using the following values for the CiscoWorks 1.0 group:
CiscoWorks 1.0 Group Name     : CscWorks
CiscoWorks 1.0 Group ID       : 55
CiscoWorks 1.0 Group Users    : kwilson,cscworks,sybase
Are these values correct?  [yes]
****Please add this information to the NIS server:
CscWorks:*:55:root, kwilson, cscworks, sybase
This information is saved to /usr/tmp/CW.group also
What is the name of the existing CiscoWorks 1.0 login?  [cscworks]
Using the following values for the CiscoWorks 1.0 user:
CiscoWorks 1.0 User Name          : cscworks
CiscoWorks 1.0 User ID            : 100
CiscoWorks 1.0 Group ID           : 55
CiscoWorks 1.0 Full Name          : CiscoWorks
CiscoWorks 1.0 Home Directory     : /usr/nms
CiscoWorks 1.0 Shell              : /bin/csh
Are these values correct? [yes]
**** Please add this information to the NIS SERVER
cscworks:*:100:55:CiscoWorks:/disk/cw1.0:/bin/csh
This information is saved to /usr/tmp/CW.prod also
Updating CscWorks group in /etc/group with kwilson,cscworks,sybase ...
FILE OWNERSHIP AND PERMISSIONS  -  The ownership of the CiscoWorks 1.0

files will be changed to the selected users and groups.  Permissions
of specific files will be modified to enable execution and read/write
capabilities.
Setting the owner and group for CiscoWorks 1.0 software ...
chown -R cscworks.CscWorks /usr/nms/.
chown -R sybase /usr/nms/sybase
chown root /usr/nms/bin/nmsummary
chown root /usr/nms/bin/nmpoll
chown root /usr/nms/bin/nmproc
chown root /usr/nms/bin/nmpath
chown root /usr/nms/bin/nmdevmon
chown root /usr/nms/contrib/tcpdump
Setting the permissions for CiscoWorks 1.0 software ...
chmod -R 750 /usr/nms
chmod 4750 /usr/nms/bin/nmsummary
chmod 4750 /usr/nms/bin/nmpoll
chmod 4750 /usr/nms/bin/nmproc
chmod 4750 /usr/nms/bin/nmpath
chmod 4750 /usr/nms/bin/nmdevmon
chmod 4750 /usr/nms/contrib/tcpdump
chmod 660 /usr/nms/etc/ncspwd
chmod 770 /usr/nms/log
Do you wish to install the new MIB files? [yes]
SUNNET MANAGER MODIFICATIONS  -  A set of Cisco schema files must be
added to the SunNet Manager schema files to enable SunNet Manager
to integrate CiscoWorks 1.0 functionality.  You need to specify the
directory path for the SunNet Manager schema files.
Directory path for SunNet Manager schema files? [/usr/snm]
Merging CiscoWorks 1.0 schemas with SunNet Manager ...
cp /usr/nms/snm/agents/* /usr/snm/agents/
cp /usr/nms/snm/struct/* /usr/snm/struct/
chmod +r /usr/snm/agents/*
chmod +r /usr/snm/struct/*
chmod +r /usr/snm/icons/*
Running /usr/snm/bin/build_oid ...
Parsing /usr/snm/agents/enterprises.oid
Parsing /usr/snm/agents/snmp.oid
Parsing /usr/snm/agents/cisco.asn1.oid
Parsing /usr/snm/agents/sun-snmp.oid
Parsing /usr/snm/agents/snmp-mibII.oid
Writing /var/adm/snm/oid.dbase
SunNet Manager modifications completed.
Halting Sybase dataserver and CiscoWorks 1.0 daemons ...
Starting sybase server for upgrade ...
Waiting for server to complete initialization ...

Upgrading CiscoWorks 1.0 Database ...
Please enter DBMS password for nmsuper:
Database SYBASE is alive
Upgrading 102 database to 103
This will take about 10 minutes ...
Enter directory where you installed the sybase upgrade [usr/nms/sybase]
[1] 735
Server SHUTDOWN by request.
The SQL Server is terminating this process.
DB-LIBRARY error:
  Unexpected EOF from SQL Server.
Finished 102 to 103 upgrade 
Upgrading sample reports ... Done
TFTP CHECK  -  The CiscoWorks 1.0 Configuration Management application
uses TFTP for configuration upload and download of Cisco devices.
Correct operation of this feature requires that TFTP service be enabled
and that the TFTP directory have the correct access permissions.
Checking for correct TFTP service configuration ...
TFTP is correctly configured.
SYSLOG MODIFICATIONS  -  The CiscoWorks 1.0 Log Manager application
uses a centralized log file which gets messages from the UNIX syslogd
process.  You will need to specify the log file name and which syslog
facility (local0-local7) to use.  Use facility local7 if you want to
log both CiscoWorks 1.0 messages and Cisco device messages; use a
different facility if you want to log only CiscoWorks 1.0 messages.
Enter log file to use for CiscoWorks 1.0 messages: [/var/log/nmslog]
/var/log/nmslog already exists!  Use this file anyway (y/n)? [y]
Enter syslog facility to use for CiscoWorks 1.0 messages: [local7]
OK to remove other syslog entries which use local7 (y/n)? [y]
The log file will be                          : /var/log/nmslog
The syslog facility will be                   : local7
Remove other syslog entries which use local7  : y
Are these values correct (y/n)? [y]
Syslog modifications in progress ...
NMSLOGFILE = /var/log/nmslog
INSTALL = upgrade
Resetting database and system logs ...
logpurg 2.0 Experimental starting:
        Process id = 618
        Debugging: = Off
logpurg started at: Thu Feb 18 17:53:47 1993
logpurg completed
Syslog modifications completed.
Start the CiscoWorks 1.0 processes and database server (y/n)? [y]

Starting CiscoWorks 1.0.  Please wait ...
RC.LOCAL MODIFICATIONS  -  The Sybase dataserver and other CiscoWorks 1.0
daemons must be running as background processes for correct operation
of CiscoWorks 1.0.  This section of the configuration will modify the file
/etc/rc.local to include nmstartup which will start the Sybase dataserver
and CiscoWorks 1.0 daemons during system reboot.
Checking for nmstartup in /etc/rc.local ...
Old version of nmstartup detected in /etc/rc.local!
Update existing nmstartup for CiscoWorks 1.0 in /etc/rc.local (y/n)? [y]
Updating nmstartup for CiscoWorks 1.0 in /etc/rc.local ...
/etc/rc.local modifications completed.
CRON MODIFICATIONS  -  The syslog file must be purged periodically
to avoid running out of disk space.  This activity is automated by the
CiscoWorks 1.0 log purge utility when scheduled by the UNIX cron daemon.
This will purge syslog daily and maintain a seven day history of syslog
files.
Schedule the CiscoWorks 1.0 log purge utility to run daily (y/n)? [y]
Adding line "0 2 * * * /usr/nms/bin/purge /usr/nms" to crontab 
...
Cron modifications completed.
CONFIGURATION COMPLETE  -  Various environment variables must be defined
for correct operation of CiscoWorks 1.0. You can append the following lines
to the .login or .cshrc file of CiscoWorks 1.0 users so that required
environment variables will be set correctly:
#   Set environment variables for CiscoWorks 1.0.
setenv SNMHOME /usr/snm
setenv NMSROOT /usr/nms
setenv SYBASE /usr/nms/sybase
#   Set path for CiscoWorks 1.0 man pages.
if (!($?MANPATH)) setenv MANPATH /usr/man
setenv MANPATH "$MANPATH":"$NMSROOT"/man
#   Set path for CiscoWorks 1.0 executables.
set path=($path /usr/nms/bin /usr/nms/etc)
Refer to the CiscoWorks 1.0 Getting Started Guide for instructions on
validating your installation and configuration.

The configuration is complete. To eject the CD-ROM enter the following commands:

hostname# cd /         
hostname# eject sr0

Review the section entitled "Enabling Better Use of Disk Space by Device Polling" to see if you need to take steps to optimize the use of your disk space by the Device Polling application. If you wish to remove the log files that were created when installing and configuring Cisco Works, see "Cleaning Up Log Files." Otherwise, proceed to the "Validating CiscoWorks Installation" chapter.

Enabling Better Use of Disk Space by Device Polling

If you are upgrading from CiscoWorks Release 1.0 to Release 1.0(3), perform the following procedures in order to optimize the use of your disk space by the Device Polling application. If you have already upgraded to CiscoWorks Release 1.0(2) and you have performed this procedure, it is not necessary to perfom it again when upgrading to Release 1.0(3).

The storage of polling data was changed in CiscoWorks Release 1.0(2) and 1.0(3). When a poll table is specified in the Device Polling window for a poll group, the inst column in the database field stores the instance value of the MIB table you use. The size of the inst column was 255 bytes in CiscoWorks Release 1.0. However, some instance values are smaller in size and do not require the use of 255 bytes in the inst column. As a result, database polling tables created in CiscoWorks Release 1.0 used more disk space than necessary.

CiscoWorks Release 1.0(3) software uses a variable size for the inst column with a maximum of 255 characters. For example, if the instance value of a MIB table is 3 bytes, the inst column field uses only 3 bytes to store the instance value. As a result, the amount of disk space used is significantly lower.

Although you can obtain an estimate of required disk space by multiplying the disk space consumption by the length of time you plan to poll, your calculations might not be 100 percent accurate. The Device Polling application is unaware of which device interfaces are up or down and whether or not MIB values returned by a device are sent in one or more packets. Therefore, you should occasionally check the database to determine the actual consumption rate.

The CiscoWorks Release 1.0(3) software includes two scripts that address the size of the inst column used to store the instance value of a MIB variable:

$NMSROOT/etc/fixpolls enables you to change the size of the inst column for all polling tables created after upgrading from CiscoWorks Release 1.0 to 1.0(3). Run this script once after upgrading to CiscoWorks Release 1.0(3).
$NMSROOT/etc/fixpolltable enables you to change the size of the inst column for an existing poll table from a fixed size of 255 bytes to a variable size with a maximum limit of 255 bytes. Run this script for each poll table you created using CiscoWorks Release 1.0.

Note: Use the $NMSROOT/etc/fixpolltable and $NMSROOT/etc/fixpolls scripts only if you are upgrading from CiscoWorks Release 1.0.x to 1.0(3). If you are upgrading from NetCentral Release 1.3 to CiscoWorks Release 1.0 or installing CiscoWorks Release 1.0(3) for the first time, you need not run these scripts.

Running the $NMSROOT/etc/fixpolls Script

To run the $NMSROOT/etc/fixpolls script after upgrading from CiscoWorks Release 1.0 to 1.0(3), perform the following steps:

Step 1: Make sure you know the password for nmsuper or the password of a CiscoWorks Release 1.0 user. Do not use the Sybase SA password.

Step 2: Enter the following command at the UNIX prompt (%):

% $NMSROOT/etc/fixpolls -U        user -Ppassword

For example, if your user name is kwilson and your password is casey2, you would enter the following command:

% $NMSROOT/etc/fixpolls -Ukwilson -Pcasey2

Output similar to the following will appear:

Fixing poll template table... Done.

Running the $NMSROOT/etc/fixpolltable Script

To run the $NMSROOT/etc/fixpolltable script for each polling table, perform the following steps:

Step 1: To identify the names of the polling tables, select the Tools menu on the SNM console and pull down to Device Polling.

The Device Polling window appears.

Step 2: Select the Poll Group field and pull down the pick menu to display the existing poll group names for polling tables.

Step 3: Note the names of the polling tables.

Step 4: Make sure you know the password for nmsuper or the password of a CiscoWorks user. Do not use the Sybase SA password.

Step 5: Enter the following command at the UNIX prompt, substituting the name of the polling table:

% $NMSROOT/etc/fixpolltable -Uuser         -Ppassword polling_table_name

For example, if your user name is kwilson, your password is casey2, and the name of the polling table is sample, you would enter the following command:

% $NMSROOT/etc/fixpolltable -Ukwilson -Pcasey2 sample

Output similar to the following will display:

Fixing poll table sample

All done fixing test1

Step 6: Repeat step 5 for each polling group.

Cleaning Up Log Files

During the installation process, several log files are created to track the installation process and provide diagnostic information if a problem arises. Once you are satisfied that CiscoWorks is properly installed and operating, you can remove these files. To remove these files from your system, enter the following command:

hostname# rm /usr/tmp/unbundled/.install/*.log

After installing and configuring CiscoWorks, proceed to the "Validating CiscoWorks Installation" chapter to validate the CiscoWorks installation and configuration.

Troubleshooting Installation and Configuration Problems

If you experience any installation or configuration problems, refer to the "Error Messages" appendix in this Guide. Also refer to the section entitled "CiscoWorks Release 1.0(x) Installation and Configuration Caveats," in this chapter. A more comprehensive list of error messages and caveats is given in the CiscoWorks User Guide.

CiscoWorks Release 1.0(x) Installation and Configuration Caveats

Review this section if you encounter problems with installing or configuring CiscoWorks 1.0(3). This section lists notes and restrictions that apply to CiscoWorks Release 1.0(3) Installation and Configuration. If a caveat applies only to CiscoWorks Release 1.0 or 1.0(2), it is noted in the description of the caveat.

Note: For your reference, identification numbers follow the description of the caveat. For example, [CSCdi00001]. If you need to contact Technical Support about one of the following caveats, refer to the identification number to speed up the resolution of any questions or situations you might encounter.

Altering the Interface File

When you install the Sybase software, either separately or by using the Sybase software supplied with CiscoWorks Release 1.0(3), the network interface on your system must be present before you install Sybase. For example, a system might have an Ethernet network interface.

When you install the CiscoWorks and Sybase software by running the ./extract_unbundled script, an interfaces file is created. This file specifies the network interface used by your system.

Avoid editing the interfaces file manually before configuring the CiscoWorks software. If you change this interfaces file before configuring CiscoWorks, the Sybase dataserver is not activated. To avoid this problem, make sure that you do not manually change the interfaces file while you are installing the CiscoWorks and the Sybase software. [CSCdi08816]

Problem with Root umask in Configuration Script

If you run ncsconfigure and receive the message, "FIFO_config: Permission denied," your installation fails. The root umask setting on your system has caused the configuration script to not allow other users, in this case the Sybase user, to read the configuration files. To remove the files with the incorrect privileges and rerun the installation correctly, perform the following steps:

Note: Remove the following files using the remove (rm) command by entering the following. All the following steps should be run as root, and in sequence, without logging out or changing to superuser, or the umask setting (from the umask command) will be lost.

Step 1: As root, remove the following files using the remove (rm) command:

# rm /tmp/interfaces        
# rm $SYBASE/install/FIFO_config
# rm $SYBASE/interfaces
# umask 0

This allows you to rerun ncsconfigure and get the correct file permissions.

Step 2: Rerun ncsconfigure as a superuser.

# /usr/tmp/unbundled/ncsconfigure

The configuration should run correctly. If you have further problems, refer to the "Error Messages" appendix in this Guide. For a more comprehensive list of error messages and caveats, see the CiscoWorks User Guide.[CSCdi12809]

SPARC10 Installation Problem

The installation of CiscoWorks Release 1.0(3) on a SPARC10 might fail if you are installing CiscoWorks on a Sun4m class machine, such as a Sparc10. This occurs when CiscoWorks tries to rebuild the kernel for Sybase and finds that ranlib has not been run on libprom.a. To determine why CiscoWorks failed, look in the ncskernel.log file. This file should tell you to run ranlib by entering the following command:

ranlib /usr/sys/sun4m/libprom.a

After you run ranlib, restart the CiscoWorks installation by using the following command:

/usr/tmp/unbundled/ncskernel

This command will rebuild the kernel appropriately. [CSCdi12538]

Resolution of CiscoWorks Release 1.0(2) Caveats

The following section includes modifications to CiscoWorks Release 1.0(3) that resolve installation and configuration related caveats associated with CiscoWorks Release 1.0(2). For a more comprehensive list of resolved caveats, see the CiscoWorks User Guide.

CiscoWorks Release 1.0(3) Modifications

Installation now displays a warning message if OpenWindows 2.0 is running instead of the required OpenWindows Version 3.0. [CSCdi09410]
CiscoWorks upgrade installation no longer fails. [CSCdi11200]
For new installations, the cisco.traps file is now loaded during the installation. [CSCdi11795]
During CiscoWorks installation, Polling Summary now checks to ensure that it is being run as setuid root. If it is not run as setuid root, an error message is generated. [CSCdi11512]
If you are running a non-CiscoWorks Sybase server when you attempt to install CiscoWorks Release 1.0(3), the installation no longer fails. [CSCdi11513]
The installation script now checks for the proper Sun OS (Version 4.1.2 or later) before proceeding with the installation of CiscoWorks. [CSCdi08687]
During the CiscoWorks Release 1.0(3) upgrade installation, if the Sybase user is other than "sybase," the installation script no longer fails to create the master database. [CSCdi11797]

Table of Contents