Installing and Configuring the Single-System Architecture

The installation utility starts and displays a list of Java interpreters found on your system. You are then prompted to specify a path to an interpreter:

0) I want to specify a path to an interpreter.
1) Use /bin/java
2) Use /bin/jre
3) Use /usr/bin/java
4) Use /usr/bin/jre
5) Use /bin/java
6) Use /bin/jre
7) Use /usr/bin/java
8) Use /usr/bin/jre
9) Terminate this installation.
Select a choice [0-9]:

Step 3 Enter a number that corresponds to the interpreter that you want to use.

For example, if your Java interpreter is in the /bin/java directory, enter 1.

The Welcome screen appears.

Figure 4-1: The Welcome Screen

Step 4 Click Next.

A dialog box appears and you are asked whether you are upgrading Cisco Info Center. The following message appears on the screen:

ONLY upgrade from CIC 1.1 to 1.2 is supported. Features that you
have customized or added other than additional fields added to
Object Server in your CIC 1.1 installation may not be upgraded to
1.2. Before upgrading make sure that you have a backup.

Step 5 If you are upgrading from CIC 1.1 to 1.2, ensure that you have backed up your 1.1 installation. For detailed instructions on the upgrade procedure refer to one of the following sections in "Upgrade Procedures."

If you are upgrading an installation using the single-system architecture, see "Upgrade Procedure for the Single-System Architecture" in Chapter 5.
If you are upgrading an installation using the multi-system architecture, see "Upgrade Procedures for the Multi-System Architecture" in Chapter 5.

The installation utility checks to make sure that your system is running the proper version of the Sun operating system.

If your system runs a supported version, the following message appears:

Verifying OS:
Supported OS. Click Next to continue.

Step 6 Click Next.

The system checks that your user ID is valid. If you have the correct user ID, the following message appears:

Checking User Id:
OK. Click Next to continue.

Step 7 Click Next.

The utility displays the README file for the software.

Step 8 Click Next.

You are prompted to accept the license agreement

Figure 4-2: Software License Agreement Screen

Step 9 Click on the check box to accept the terms of the license.

Step 10 Click Next.

The system displays the default installation directory (/opt/Omnibus).

Figure 4-3: Choosing the Destination Directory

Step 11 Do one of the following:

To accept the default destination directory, click Next.
If you want to change the destination directory, enter the path and name for the new installation directory.

If the specified destination directory does not exist, the following message appears:

The specified destination directory,
<directory name> does not exist. Would you like to
create this directory.

Step 12 Do one of the following:

If the directory shown in the message is the correct directory, click Yes.
If the directory shown in the message is not correct, click No and then re-enter the destination directory.

The system checks the specified directory for an existing version of Cisco Info Center. If an existing version is detected, the following message appears:

Legacy version exists
/opt/Omnibus/RELEASE_ID. Click cancel to exit
installation

Step 13 If there is an existing version of Info Center, click OK and then click Cancel to exit the installation program.

The system verifies that the existing directory is empty:

Step 14 Click Next.

The system checks for the common component and the following message appears:

Checking for Common component.
Common component not found. Click Next to continue.

Step 15 Click Next.

The system displays a dialog box that prompts you for the components that you want to install:

Figure 4-4: Choosing the Info Center Components to Install

Step 16 Click the check box for All Components.

Step 17 Click Next.

A message appears asking if you want to overwrite any existing packages:

Figure 4-5: Overwrite Existing Package Prompt

Step 18 Do one of the following:

If you want to overwrite a previous installation, click Yes.
If there is no previous installation, click No.

Step 19 Click Install.

The installation program installs the selected packages. After the installation is complete, the system prompts you to finish the installation procedure.

Step 20 Click Finish.

The installation process is now complete.

Single-System - Configuring the Cisco Info Server

After installation, you must configure the Cisco Info Center Components.

Step 1 If you are not root, change your UID to root.

Step 2 Set the OMNIHOME environment for ksh and sh shell:

host# OMNIHOME=/opt/Omnibus
host# export OMNIHOME
 
or for csh shell:
 
host# setenv OMNIHOME /opt/Omnibus

Step 3 Change to the following directory:

host# cd /opt/Omnibus/install

Step 4 Run the configuration script:

host# ./nco_config

The following Configuration menu is displayed:

#################################################################
               Cisco Info Center Configuration Menu
##################################################################
 
           1.  Configure Info Server         
 
           2.  Configure CWM Mediators       
 
           3.  Configure Info Admin Desktop  
 
           4.  Configure All                 
 
           5.  Help                          
 
           6.  Quit                          
 
Select one of the above options :

Step 5 Select option 4 from the Configuration menu.

You have Selected the following Info Center Components to be configured 
 
        Info Server, Info Admin Desktop, CWM Mediators
 
Do you want to continue (y/n) ? [y]:

Step 6 Press Return to continue or specify n, then press Return to go back to the previous menu.

If you continue with the configuration process and the current installation directory is not /opt/Omnibus, the script automatically links the Cisco Info Center install directory to /opt/Omnibus.

However, if /opt/Omnibus is not the current installation directory and /opt/Omnibus already exists, either as a directory, file, or a link on the system, the following error message is displayed:

........ ...... 
*** Info Center Requires Installation in /opt/Omnibus*** 
*** /opt/Omnibus already exists, ***
*** Create a link to /opt/Omnibus from the <install directory> ***
*** at the end of this configuration script ***

The configuration utility now takes you through the steps to configure the each component of the Cisco Info Center System. These steps are described in the following sections:

Single-System - Configuring Cisco Info Server Properties

Complete these steps to configure the Info Server properties.

Step 1 Observe the following prompt.

*** Name for the Info Server must be alphanumeric beginning ***
*** With a letter and up to 11 characters long ***
Name for the Info Server [INFOSERVER]

Step 2 Do one of the following:

To accept the default name, INFOSERVER, press <Return>.
To specify a different name for the Info Server, enter an alphanumeric string of up to eleven characters, beginning with a letter.

The script converts any lowercase characters that you enter to uppercase and informs you of the converted Cisco Info Server name.

After you enter a valid Cisco Info Server name the following prompt appears:

Enter the Port Number for the Info Server [4100]:

Step 3 Do one of the following:

To accept the default port, press Return.
To change the port number, enter the number of an an unused port .

The script validates the availability of the port and informs you when the port number you specified is already in use or is a reserved port. This process may take a few seconds. When the port number is in use or reserved, the following message is displayed:

Checking Port Availability Please Wait...
Port Number [4100] is already in use...Checking Port Number 4101
Enter the Port Number for the Info Server [4101]

The script automatically increments the port number and checks for port availability. It continues to do so until a free port is available and prompts you to accept this new port number.

Step 4 Press Return to accept the unused port number.

You are now ready to continue with the configuration of the Process Control properties.

Single-System - Configuring Process Control Agent Properties

Complete these steps to configure the Process Control Agent properties.

Step 1 Observe the following prompt:

*** Name for the Process Agent must be alphanumeric beginning with ***
*** a letter, must NOT exceed 11 characters and must end with _PA ***
Name for the Info Server Process Agent [NCO_PA]

Step 2 Do one of the following:

To accept the default name, NCO_PA, press Return.
To specify another name, enter an alphanumeric string of up to eleven characters, beginning with a letter and ending with _PA.

The script validates the Process Control name and prompts you to specify the port number for the Process Control:

*** Port Number for the Process Agent must not be ***
*** the same as the Info Server Port Number [4100] ***
Enter the Port Number for the Info Server Process Agent [4200]:

Step 3 Do one of the following:

Press Return to accept the default port
Enter an unused port number.

The script validates the availability of the port number and also ensures the specified port number is not the port number selected for the Cisco Info Server. When the port number is in use or reserved, the following text is displayed:

Checking Port Availability Please Wait...
Port Number [4200] is already in use...Checking Port Number 4201
Enter the Port Number for the Info Server Process Agent [4201]

The script automatically increments the port number and checks for port availability. It continues to do so until a free port is available and prompts you to accept the new port number.

Step 4 Press Return to accept the unused port number. The following text is displayed:

Creating the new Process Agent NCO_PA
Adding its entry to omni.dat ... done
Creating the new Info Server INFOSERVER
Adding its entry to omni.dat... done
Generating the database files... Info Server INFOSERVER created
Updating /etc/services file ...done
Adding Info Server entry to /etc/services. . . done

You are now ready to configure the CWM Mediator for the single-system configuration.

Single-System - Configuring the CWM Mediator

After completing the Info Server configuration, the installation script prompts you for information required to configure the CWM Mediator. Complete these steps to configure the CWM Mediator.

Step 1 Observe the following prompt:

************************************
Info Mediators configuration menu
************************************
 
        1. Trap Receiver, NNM and Syslog Mediators
        2. Trap Receiver and NNM Mediators
        3. Syslog Mediator only
 
Select one of the above options :

Step 2 Enter the number that corresponds to the combination of Info Mediators that you want to install.

If you select option 3, the following message appears:

*** Configuring Syslog Mediator ***
 
Syslog Mediator configured
Configuring Process Control for CWM Mediators...done
Running nco_igen...

Step 3 If you selected option 1 or 2 from the Info Mediators configuration menu, complete these steps.

(a) Answer the following prompts:

***************************************************************
Info Center rules configuration for NNM and rttrapd Mediators
***************************************************************
 
The CWM installation on host "<hostname>" is version 9.1
Is the CWM installation on host <hostname> greater than or equal to 9.1.0.9 (y/n) [n] 
 
CIC 1.2 will be configured to support the following:
 
        :-CWM 9.1 on host "<hostname>"
 
Is this correct? (y/n)? [y] y

(b) Do one of the following:

If the configuration shown in the prompt is correct, enter y.
If the configuration is not correct, enter n.

: If you respond by entering n, you are prompted once again to enter the rules file information.

You are now prompted for the IP address of the CWM machine:

IP address of the CWM machine [171.71.28.116]:

Step 4 Do one of the following:

To accept the IP address displayed with the prompt, press Return.
To specify another IP address, enter the new address.

You are prompted for the port number:

Port Number to run the Info Center Trap Receiver [4000]: 
Checking Port Availability Please Wait... done

Step 5 Do one of the following:

To accept the default port number (port 4000), press Return.
To specify another port number, enter the port number.

Step 6 You are prompted for the name of the database:

Name for the CWM Informix Database [stratacom]:

Step 7 Enter the name of your Informix database.

Step 8 The following messages appear:

Configuring CWM Mediators...
 
        Configuring nnm5 mediator...
        Configuring rttrapd mediator...
 
CWM Mediators Configured
 
Generating Lookup Files for the CWM Mediators
 
Generating empty files for the Info Mediators
Generating Node IP Address Lookup File... 
Generating Node Platform Lookup File... 
Generating Node Release Lookup File... 
Generating Node NetId Lookup File... 
Generating Node Model Lookup file... 
Generating NetId NetworkName Lookup File...
 
Generating SV+ Version Lookup File...

The following prompt appears:

Do you wish to configure automatic startup upon system boot? (y/n) [y]

Step 9 Press Return if you wish to configure automatic startup when the system is booted or n if you do not want this option.

If you respond y to the prompt, the following message appears:

Automatic Startup Scripts Installed

Manually Installing Cisco Info Center Components

This section describes the installation and configuration of components used to enhance the installed and configured multi- or single-system architecture, or to install Cisco Info Center and manually configure the components.

Communication Protocol

Cisco Info Center uses client/server technology, therefore, all of the components can be installed either on one workstation or on separate workstations and platforms, communicating over a TCP/IP network.

Components installed on different workstations use the Cisco Info Center communications protocol to communicate with the Cisco Info Center software. This relationship is configured in the interfaces file.

Installation on Solaris 2.x Platform

This section describes how to install the Cisco Info Center system on a Solaris 2.x platform. The following assumptions are made:

the installer is logged in as user root
the system is loaded with all of the components for the architecture of the target workstation
licensing will be installed
the CD-ROM drive is attached to the local system.

When the installer does not have root access (or at least write access to /opt), other users can run the Cisco Info Admin Desktop. (When only the Cisco Info Admin Desktop is being installed, root access is not necessary.)

The installation procedure covers the following steps:

1. Mount the CD-ROM.

2. Start the installation.

3. Select the target directory.

4. Select the components for the system.

5. Set the environment variables.

6. Install licensing.

Manual Installation - Mounting the CD-ROM

This section describes how to mount the CD-ROM on a Solaris 2.x platform.

Before you begin, you must have write access to /opt installation directory.

Step 1 The CD-ROM should mount automatically if you are running the Solaris Volume daemon (vold) as /cdrom/infocenter. If this daemon is not running, issue the following command to mount the CD-ROM:

host# mount -o ro -F hsfs </dev/dsk/device> /cdrom

where </dev/dsk/device> is the CD-ROM drive device entry.

Manual Installation - Running the Installation Program

Complete these steps to run the Cisco Info Center installation program.

Step 1 Change directory to the directory where you mounted the CD-ROM.

For example, if the CD-ROM is mounted in the /cdrom/infocenter directory, specify the following command:

host# cd /cdrom/infocenter

Step 2 Enter the following to start the Info Center installation script.

host# ./setup.sh

The installation utility starts and displays a list of Java interpreters found on your system. You are then prompted to specify a path to an interpreter:

0) I want to specify a path to an interpreter.
1) Use /bin/java
2) Use /bin/jre
3) Use /usr/bin/java
4) Use /usr/bin/jre
5) Use /bin/java
6) Use /bin/jre
7) Use /usr/bin/java
8) Use /usr/bin/jre
9) Terminate this installation.
Select a choice [0-9]:

Step 3 Enter a number that corresponds to the interpreter that you want to use.

For example, if your Java interpreter is in the /bin/java directory, enter 1.

The Welcome screen appears.

Figure 4-6: The Welcome Screen

Step 4 Click Next.

A dialog box appears and you are asked whether you are upgrading Cisco Info Center. The following message appears on the screen:

ONLY upgrade from CIC 1.1 to 1.2 is supported. Features that you
have customized or added other than additional fields added to
Object Server in your CIC 1.1 installation may not be upgraded to
1.2. Before upgrading make sure that you have a backup.

If you are upgrading an installation using the single-system architecture, see "Upgrade Procedure for the Single-System Architecture" in Chapter 5.
If you are upgrading an installation using the multi-system architecture, see "Upgrade Procedures for the Multi-System Architecture" in Chapter 5.

The installation utility checks to make sure that your system is running the proper version of the Sun operating system.

If your system runs a supported version, the following message appears:

Verifying OS:
Supported OS. Click Next to continue.

Step 6 Click Next.

The system checks that your user ID is valid. If you have the correct user ID, the following message appears:

Checking User Id:
OK. Click Next to continue.

Step 7 Click Next.

The utility displays the README file for the software.

Step 8 Click Next.

You are prompted to accept the license agreement.

Figure 4-7: Software License Agreement Screen

Step 9 Click on the check box to accept the terms of the license.

Step 10 Click Next.

The system displays the default installation directory (/opt/Omnibus).

Figure 4-8: Choosing the Destination Directory

Step 11 Do one of the following:

To accept the default destination directory, click Next.
If you want to change the destination directory, enter the path and name for the new installation directory.

If the specified destination directory does not exist, the following message appears:

The specified destination directory,
<directory name> does not exist. Would you like to
create this directory.

Step 12 Do one of the following:

If the directory shown in the message is the correct directory, click Yes.
If the directory shown in the message is not correct, click No and then re-enter the destination directory.

The system checks the specified directory for an existing version of Cisco Info Center. If an existing version is detected, the following message appears:

Legacy version exists
/opt/Omnibus/RELEASE_ID. Click cancel to exit
installation

Step 13 If there is an existing version of Info Center, click OK and then click Cancel to exit the installation program.

The system verifies that the existing directory is empty:

Step 14 Click Next.

The system checks for the common component and the following message appears:

Checking for Common component.
Common component not found. Click Next to continue.

Step 15 Click Next.

The system displays a dialog box that prompts you for the components that you want to install:

Figure 4-9: Choosing the Info Center Components to Install

Step 16 Click the check boxes for the components that you want to install.

Step 17 Click Next.

A message appears asking if you want to overwrite any existing packages:

Figure 4-10: Overwrite Existing Package Prompt

Step 18 Do one of the following:

If you want to overwrite a previous installation, click Yes.
If there is no previous installation, click No.

Step 19 Click Install.

The installation program installs the selected packages. After the installation is complete, the system prompts you to finish the installation procedure.

Step 20 Click Finish.

The installation process is now complete.

Manual Installation - Set OMNIHOME and PATH Variables

From this point on in the installation, the OMNIHOME environment variable must be set. This variable should point to the directory (/opt/Omnibus) in which you installed Cisco Info Center.

Step 1 For csh users, specify the following command in the $HOME/.login file for each user:

setenv OMNIHOME /opt/Omnibus

For ksh and sh shell users, specify the following command in the $HOME/.profile file for each user:

OMNIHOME=/opt/Omnibus;export OMNIHOME

Step 2 Set the PATH environment variable as follows:

host% PATH=$PATH:$OMNIHOME/bin; export PATH for ksh and sh shell users

host% setenv PATH $PATH:$OMNIHOME/bin for csh users.

Manual Installation - Shared Libraries

The Cisco Info Center directory layout uses shared libraries, which contain rationalized common executables providing smaller executables and a smaller total distribution.

The run-time dynamic loader module automatically looks for shared libraries within the default /lib and /usr/lib directories. The libraries are installed in the default location specific to the platform. For example, the installation default location of the shared libraries for Solaris 2 is /opt/Omnibus/platform/solaris2/lib. When Cisco Info Center is started, the run-time dynamic loader searches this directory for the shared libraries, due to the default path being encoded within the header of the program.

When Cisco Info Center is not installed in the default directory, you must set the LD_LIBRARY_PATH system environment variable in order for the dynamic loader to find the required shared library.

Step 3 For csh users, when you installed Cisco Info Center in the /opt/Apps/Omnibus directory, specify the following command:

setenv LD_LIBRARY_PATH /opt/Apps/Omnibus/platform/solaris2/lib

For ksh and sh shell users, specify the following command:

LD_LIBRARY_PATH=/opt/Apps/Omnibus/platform/solaris2/lib;
export LD_LIBRARY_PATH

Manual Installation - Licensing

Step 4 You must set the NCO_ELMHOST environment variable to the host where the license daemon is located. For example, when the licenses are installed on the host muppet, using csh, specify:

host# setenv NCO_ELMHOST muppet

For ksh and sh shell users, specify the following command:

host$ NCO_ELMHOST=muppet; export NCO_ELMHOST

This command ensures that components search for licenses on the host muppet only. To search for licenses on multiple sources, prefix the host name with a @. For example, the following command (csh) ensures that components search for licenses on muppet, then on boomerang, before doing a network broadcast:

host# setenv NCO_ELMHOST=@muppet:boomerang:BROADCAST

For ksh and sh s hell users, the command is as follows:

host$ NCO_ELMHOST=@muppet:boomerang:BROADCAST; export NCO_ELMHOST

When you do not set the NCO_ELMHOST environment variable, components search for licenses by network broadcast only.

Manual Installation - Install License Keys

Step 5 The Cisco Info Center system is licensed on a component basis. Before you can bring up the system, you must supply license keys on the NCO_ELMHOST workstation. These licenses are installed in the Cisco Info Center license manager. To start the license manager, specify:

host# $OMNIHOME/install/nco_license

Step 6 Accept all of the default options. You are then supplied with a server code, which is generated from unique host information. Send the server code to support@MicroMuse.com (800-637-2665) to obtain your license keys.

Step 7 When you receive your license keys, run the license manager again and specify the keys when prompted to do so, or press Return to skip a key. The nco_license command automatically starts the license daemon. To run it manually, specify the command:

host# $OMNIHOME/bin/nco_start_license

Manual Installation - Configuring the System

This section describes how to configure the Cisco Info Center system.

The configuration procedure covers the following steps:

1. Create the interfaces file for Cisco Info Center communications.

2. Run a Cisco Info Server using the nco_objserv command. For details, see Chapter 1, "Cisco Info Server" in the Cisco Info Center Administrator Reference guide.

3. Configure the system to run under Process Control. For details, see Chapter 2, "Process Control" in the Cisco Info Center Administrator Reference guide.

4. Define users and groups (for Cisco Info Center, not UNIX).

Interfaces File

For communications to be established between the components of Cisco Info Center, you must create an interfaces file.

The interfaces file contains information about:

which hosts run Cisco Info Server and how to connect to those hosts
which hosts run Info Gateways and how to connect to those hosts
entries for each host being managed by the Process Control system.

When Cisco Info Center components are started, they search for the $OMNIHOME/etc/interfaces.solaris2 file.

You can also use the nco_igen command's -java parameter to generate the interfaces file used specifically for Java support.

Without an appropriate interfaces file, the software looks for a file named $OMNIHOME/etc/interfaces and uses that as the interfaces file.

When that file does not exist, the programs are unable to contact any Cisco Info Servers and they fail to run .

Figure 4-11: Server Editor Window

Step 1 To create the interfaces file, use the Server Editor window, shown in Figure 4-11. To open the Server Editor window, specify:

host# $OMNIHOME/bin/nco_xigen

The Server Editor window may display an empty list or display the list of Cisco Info Servers, Info Gateways, or Process Control that may have been configured, along with the host name and the TCP port to which they are allocated. The list of servers is stored in the $OMNIHOME/etc/omni.dat file and any changes you make in the Server Editor window are saved in this file.

Note, although it is possible to edit the $OMNIHOME/etc/omni.dat file directly, it is recommended you use the Server Editor window to edit the list of servers. However, there may be occasions when you want to edit the connections data file. For more information about how to edit this file, see Section, "Editing the Connections Data File", in Appendix B, in the Cisco Info Center Administrator Reference guide.

To change the host name:

(a) Click on the server name to select it.

(b) Specify the name of the host machine in the Host field.

(d) Click on the Apply button. The interfaces file for the local platform is generated. A separate interfaces file for Java support is also generated automatically.

Add a Backup Server

Cisco Info Center allows you to specify backup hosts for each server defined. This ensures that when a server, for example, NCOMS, fails on the first host, Cisco Info Center attempts to connect to NCOMS on the backup host.

For example, to specify a backup host for NCOMS:

1. Click on the CISCO server in the main list.

2. Specify a different host name in the Host field.

3. Click on the Add button.

In Figure 4-12, the NCOMS server shows two backup hosts: muppet and darkstar.

Figure 4-12: Backup Servers in the Server Editor Window

Change the Priority of the Servers

To change the priority of the server in the list:

1. Click on the server name to select it.

2. Click on either the Raise or Lower buttons to move the server up or down the list, respectively.

Add a New Server

To add a new server to the interfaces file:

1. Specify the name of the server into the Name field.

2. Specify the name of the host machine in the Host field.

3. Specify the port number into the Port field.

4. Click on the Add button to add the new server.

5. Click on the Apply button to apply the changes.

Change the Server Details

To change a primary server:

1. Click on the server name to select it, or specify the server name in the Name field.

2. Edit the Name, Host, or Port fields, as required.

3. Click on the Update button.

4. Click on the Apply button to apply the changes.

Delete a Server

To delete a primary server:

1. Click on the server name to select it.

2. Click on the Remove button.

3. Click on the Apply button to apply the changes.

Test the Server

To test the server, click the Test button. A window is displayed providing the results of the test command.

Distributing Interfaces Information to Multiple Platforms

By default, the Server Editor window generates the $OMNIHOME/etc/interfaces.solaris2 interfaces file for use on Solaris 2.

You can then copy this file to the $OMNIHOME/etc directory on each of the participating Cisco Info Center machines.

Starting the Cisco Info Center Components

This section describes how to install the start-up scripts and configure the login procedure. The multi- and single-system installation processes automatically add the automatic start-up procedures to the /etc/init.d/nco file.

To manually start the installed Cisco Info Center components, execute the following command:

: host# /opt/Omnibus/bin/nco_pa_start

To manually shut down the running Cisco Info Center components, execute the following command:

: host# opt/Omnibus/bin/nco_pa_shutdown

The Login window is displayed when you start the Desktop tools. To modify the Server button on the Login window, use a skip filter file. This filter is an external file that comprises regular expression statements to define the servers that will not appear in the Login window.

To use this skip file, create the $OMNIHOME/etc/skip-filter file.

Table of Contents

Installing and Configuring the Single-System Architecture