Installing and Configuring the Single-System Architecture

In the single-system architecture, you install all of the required Cisco Info Center components on a single host. The procedure in this chapter describes the installation of the single-system architecture with Policy Manager.

Note For detailed information on other single-system configurations, refer to the "Single System (Centralized) Architecture" section.

Installing the Cisco Info Center components on a single system involves these steps:

mounting the CD ROM
running the installation script

Single-System Architecture---Mounting the CD-ROM

Complete these steps to mount the CD-ROM.

Step 1 Log in as user root.

Step 2 The CD-ROM should mount automatically if the host is running the Solaris Volume daemon (vold) as /cdrom/infocenter.

Step 3 If this daemon is not running, issue this 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.

Single-System---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# ./OINSTALL

The following message appears:

1. Discovering existing InfoCenter installations

If no existing Cisco Info Center installation exists, the following message appears:

No InfoCenter installations found, is this correct (y/n)? [y]

If an existing Cisco Info Center installation is found, a message similar to the following appears:

InfoCenter version 1.2 found in /opt/Omnibus

Step 3 Do one of the following:

If an existing Cisco Info Center installation was found, go to "Upgrading to Cisco Info Center 2.0" and follow the instructions in the "Upgrade Procedure" section.
If no existing Cisco Info Center installation was found, enter y to continue the installation process.

The main installation menu appears (shown in Figure 4-1). This menu allows you to choose the components that you want to install.

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

Step 4 If you want to change the default installation directory (/opt/Omnibus), enter C and then enter the directory path to where you want to install Cisco Info Center.

Step 5 Enter the number for each component for the multi-system architecture:

Enter 1 to select the Desktop component.
Enter 3 to select the Licensing component.
Enter 4 to select the Process Control component.
Enter 5 to select the Mediators component.
Enter 6 to select the Info Server component.
Enter 9 to select the Syslog Trap Generator component.
Enter 10 to select the Policy Manager component.

: The display indicates the components that you have selected:

1.  Desktop                SELECTED
2.  Gateway 
3.  Licensing              SELECTED
4.  Process Control        SELECTED
5.  Mediators              SELECTED
6.  InfoServer             SELECTED
7.  Java support 
8.  Wave 
9.  Syslog Trap Generator  SELECTED
10. Policy Manager         SELECTED

Step 6 Select optional components as follows:

If you have purchased a license for the Gateway component and want to install it on this host, enter 2 to select the Gateway component.
If you want to install the Java Event List component, enter 7 to select Java Support
If you want to install the Wave component, enter 8 to select it.

Step 7 If you make a mistake in selecting components, enter U to deselect all components and then re-enter the selection numbers for the components that you want to install.

Step 8 Enter I to install the selected components.

The installation program installs the selected packages. As the selected packages are installed, messages similar to the following appear:

Installation of <CICSrv> was successful.

The following message appears:

Component installation Complete
 
Press <Return> when ready...

Step 9 Press Return.

The following messages appear:

Finalizing install
Do you wish to configure the install now (y/n)? [y]

Step 10 Do one of the following:

If you want to configure the installed components at this time, enter y. For instructions on configuring the Info Server component, refer to the following sections.
If you want to wait and configure the installed components later, enter n.

The installation process is now complete.

Single-System Architecture---Configuring the Cisco Info Server

The configuration utility (nco_config) starts automatically if you respond y for "yes" when the installation program displays the following prompt:

Do you wish to configure the install now (y/n)? [y]

If you did not configure the Info Server component directly after installing it, you can start the configuration utility manually by entering the following commands:

host# setenv OMNIHOME /opt/Omnibus

host# cd /opt/Omnibus/install

host# ./nco_config

host# setenv IMPACT_HOME /opt/Omnibus/polmgr

After the configuration utility starts, complete these steps to configure the Info Server component.

Step 1 Observe the following menu:

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

Note Configuration options reflect only those configurable options installed on the host.

Step 2 Enter 4 to configure all components

The script displays the selected option and prompts you for confirmation.

You have Selected the following Info Center Components to be configured 
 
        Configure All
 
Do you want to continue (y/n)? [y]:

Step 3 Press Return to continue; or, specify N and 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 all of the installed components. These steps are described in the following sections:

Single-System---Configuring Process Control Agent and Info Server 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:

Enter the Port Number for the Process Agent [4200]:

Step 3 Do one of the following:

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

The following prompt appears:

*** 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 4 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 5 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 6 Press Return to accept the unused port number.

Step 7 The following messages appear:

Checking Port Availability Please Wait... done
Adding its entry to omni.dat.... done
Creating the new Info Server INFOSERVER
 
Generating the databases files... Info Server INFOSERVER created
Updating /etc/services file...

The following prompt appears:

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

Step 8 If you want the Info Server to start up automatically when the host system boots, enter y; otherwise enter n.

The following prompt appears:

Would you like to configure Policy Manager now?

Enter y.

The following prompt appears:

Please enter the name of the VPN Solutions Center host:

Step 9 Enter the hostname of the host that is running the Cisco MPLS VPN Solutions product.

The installation program pings the specified host. If the host is not reachable, you are prompted to re-enter the hostname for the Cisco MPLS VPN Solution host.

Step 10 If the host that you specified Step 7 was unreachable, enter the correct hostname for the host that is running the CIsco MPLS VPN Solution product.

After you have entered the correct hostname, the script continues and prompts you to configure the Info Mediators component. You are now ready to configure the Info Mediators component for the single-system architecture.

Single-System---Configuring the Info Mediators Component

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

Step 1 Observe the following prompt:

************************************
Info Mediators configuration menu
************************************
 
 1.   NNM probe
 2.   rttrapd probe
 3.   syslog probe
 
 
1-3. Toggle Component
S. Select All Components
U. Unselect All
I. Setup and Install Components
H. Help
Option:

Step 2 Enter 2 to select the RTtrapd Info Mediator.

The script indicates the selection that you have made:

************************************
Info Mediators configuration menu
************************************
 
 1.   NNM probe
 2.   rttrapd probe     SELECTED
 3.   syslog probe
 
 
1-3. Toggle Component
S. Select All Components
U. Unselect All
I. Setup and Install Components
H. Help
Option:

Step 3 Enter I to install and set up the RTtrapd Info Mediator.

The following message appears:

*** Configuring the rttrapd mediator to register with the RTM Proxy ***

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 the rttrapd mediator [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.

The following messages appear:

rttrapd Mediator Configured
 
CIC 2.0 has been succesfully configured

Configuration of the Info Mediator component is now complete.

Single System Architecture---Configuring the Syslog Trap Generator

After you have run the nco_config utility to configure the Cisco Info Center components for the single-system architecture with Policy Manager, you must complete two additional steps to configure the STG host to communicate with Policy Manager and the MPLS VPN Solution Center:

1. Edit the nodeinfo.dat file for the STG host. This step is described in the "Single-System ArchitectureEditing the nodeinfo.dat file for the STG" section

2. Configure the STG host to support Policy Manager. This is described in the "Single System ArchitectureConfiguring the STG Host to Support Policy Manager" section.

Single-System Architecture---Editing the nodeinfo.dat file for the STG

Complete these steps to edit the nodeinfo.dat file.

Step 1 Locate the nodeinfo.dat file in the /opt/Omnibus/stg/stg directory.

Step 2 Edit the file to add entries for each network note that you want the STG to monitor.

The nodeinfo.dat contains sample entries that have been inserted as comment lines to show you the format for node information entries. The sample entries show the format for entries for Cisco 3810 devices and for Route Processor Module (RPM) cards installed in MGX 8850 wide-area switches.

Example 4-1 shows the example entries that are provided in the file.

Example 4-1: Sample nodeinfo.dat Entries Provided with the STG

# Entry for a 3810.
#ipAddress=x.x.x.x nodeName=3810-11 iosVersion=12.05
 
# Entry for an RPM card
#ipAddress=x.x.x.x nodeName=RPM-12 ios

Example 4-2 shows an example of actual entries for each type of device.

Example 4-2: Edited nodeinfo.dat Entries

# An entry for a 3810.
ipAddress=209.165.000.224 nodeName=3810-11 iosVersion=12.05
 
# Entry for an RPM card
ipAddress=209.165.201.30 nodeName=RPM-12 iosVersion=12.05 parentNodeIPAddress=209.165.201.0 parentNodeName=MGX-12 parentSlotNum=3

Note The nodeName entry should not contain the domain name for the node. For example, RPM-12@acme.com is not allowed. If you specify a domain name, erroneous events will be generated.

Step 3 When you are done changing the file, save your changes.

Once you have configured the STG component, you can proceed to start the STG. For information on starting the STG, refer to the following section.

Single System Architecture---Configuring the STG Host to Support Policy Manager

After you have run the nco_config utility to configure Policy Manager and the Info Server running on the Policy Manager host, complete these steps to complete the configuration:

change permissions on the MPLS VPN Solution host
start the Policy Manager application
configure the STG host for Policy Manager support

Changing Permissions on the MPLS VPN Solution Host

Before you configure the STG host to support Policy Manager, complete these steps on the host that is running the MPLS VPN Solution product.

Step 1 Log in as the ORBIXADM user.

Step 2 Change directory to the ORBIXADM/bin directory.

Step 3 Enter the following command:

chmodit NS i+all

Step 4 Log in as the VPNADM user.

Step 5 Change directory to the ORBIXADM/bin directory.

Step 6 Enter the following command:

chmodit VpnInvServer i+all

Starting the Policy Manager Application

At the Policy Manager host, complete these steps to start the Policy Manager application.

Step 1 Enter the following commands to start the Info Server:

cd /opt/Omnibus/bin

./nco_pad

Step 2 Enter the following commands to start licensing for Policy Manager:

setenv IMPACT_HOME /opt/Omnibus/polmgr

cd /opt/Omnibus/polmgr/install

./nci_license

The nci_license utility runs and generates a server license code. This code appears on the console display.

Step 3 Email Micromuse Technical Support and include the server license code and hostname in your email.

The email address is as follows:

: support@micromuse.com

Micromuse Technical Support will email you a feature key and a license key.

Step 4 Press Return.

The following prompt appears:

Enter the feature code (press <Enter> to exit):

Step 5 Enter the feature key that you received in the email.

The following prompt appears:

Enter the license key:

Step 6 Enter the license key:

You can now start Policy Manager.

Step 7 Enter the following commands to start Policy Manager

cd /opt/Omnibus/plmgr/bin

./nci_server

Policy Manager starts.

Step 8 Issue the following command to verify that Policy Manager is running:

/usr/ucb/ps -auxwwwwww | grep nci

Configuring the STG Host for Policy Manager Support

Complete these steps to configure the STG host for Policy Manager support.

Step 1 Enter the following command to start up the Info Mediators.

./nco_pad -name SVHOSTn_PA

where n is the number of the PA process that you specified during Info Mediator configuration.

Step 2 At the STG host, enter the following commands to generate an MPLS lookup table:

cd /opt/Omnibus/utils/install/polmgr/bin

./run_mpls_lookup

The script generates an MPLS lookup table.

You have now completed configuration of the Policy Manager component.

Starting Licensing

To run the installed components, you must obtain license for each component and start licensing.

For detailed instructions on implementing licensing, refer to the following sections in "Overview of Installation and Configuration."

Starting the Info Center Components

After you have installed and configured the various Info Center components, complete these steps to start the components.

Step 1 Review the procedure described in "Licensing Cisco Info Center" section and make sure that you have obtained license keys correctly.

Step 2 Copy the license keys that you have received from Micromuse to the /opt/Omnibus/etc directory on the host where the Licensing component is installed.

Step 3 On the host where you have installed licensing enter the following commands to start the license server:

setenv OMNIHOME /opt/Omnibus

cd /opt/Omnibus/bin

./nco_start_license

Step 4 Enter /usr/bin/ps -ef | grep elmd to make sure that the license server is running

Step 5 Enter the following commands to set the environment variables for CIC.

setenv OMNIHOME /opt/Omnibus

cd /opt/Omnibus/bin

Step 6 Enter the following command to start the default Info Server:

./nco_pad

Step 7 Enter the following command to start up the Info Mediators.

./nco_pad -name SVHOSTn_PA

where n is the number of the PA process that you specified during Info Mediator

Step 8 Enter /usr/bin/ps -ef | grep nco to make sure that the processes shown in Table 4-1are running, if installed

Table 4-1: CIC Processes

CIC 2.0 Services Process Name

Object Server

/opt/Omnibus/bin/solaris2/nco_objserv

Process Control

/opt/Omnibus/bin/solaris2/nco_pad

CWM 9.2.04-9.2.05 Mediator

/opt/Omnibus/probes/solaris2/nco_p_rttrapd

HPOV Mediator

/opt/Omnibus/probes/solaris2/nco_p_nnm5

Syslog Mediator

/opt/Omnibus/probes/solaris2/nco_p_syslog

STG

/opt/Omnibus/stg/bin/cic_SNMPAgent

/opt/Omnibus/stg/bin/cic_snmpd

for STG

/opt/Omnibus/stg/bin/cic_RtmProxy -v -L2

/opt/Omnibus/stg/bin/cic_watch_rtmd

for STG

/opt/Omnibus/stg/bin/cic_stg_5.7 -s

/opt/Omnibus/stg/bin/cic_watch_stgd

CIC 2.0 Services	Process Name
Object Server	/opt/Omnibus/bin/solaris2/nco_objserv
Process Control	/opt/Omnibus/bin/solaris2/nco_pad
CWM 9.2.04-9.2.05 Mediator	/opt/Omnibus/probes/solaris2/nco_p_rttrapd
HPOV Mediator	/opt/Omnibus/probes/solaris2/nco_p_nnm5
Syslog Mediator	/opt/Omnibus/probes/solaris2/nco_p_syslog
STG	/opt/Omnibus/stg/bin/cic_SNMPAgent /opt/Omnibus/stg/bin/cic_snmpd
for STG	/opt/Omnibus/stg/bin/cic_RtmProxy -v -L2 /opt/Omnibus/stg/bin/cic_watch_rtmd
for STG	/opt/Omnibus/stg/bin/cic_stg_5.7 -s /opt/Omnibus/stg/bin/cic_watch_stgd

Starting Policy Manager

Complete these steps to start the Policy Manager application

Step 1 On the host where Policy Manager is installed, issue the following commands:

setenv IMPACT_HOME /opt/Omnibus/polmgr

cd /opt/Omnibus/polmgr/bin

Step 2 Enter the following command to start licensing for Policy Manager

./nci_license

Step 3 Issue the following commands to start Policy Manager

cd /opt/Omnibus/polmgr/bin

./nci_server

The Policy Manager application starts.

Step 4 At the Policy Manager host, complete these steps:

a. Change directory to the /utils/install/polmgr/bin directory.

b. Enter the following command:

: ./run_mplsdev.lookup

c. Enter the following command to restart the RTtrapd Info Mediator:

: kill -9 <pid of the nco_p_rttrapd process>

Table of Contents

Installing and Configuring the Single-System Architecture