Cisco Info Center Installation and Configuration Guide, 3.6 - Installing and Configuring the Single-System Architecture [Cisco Info Center]

Table Of Contents

Installing and Configuring the Single-System Architecture

System Requirements

Minimum Configuration

Additional Requirements for Webtop

Additional Requirements for Virtual Operator

Recommended Configuration for Managing Large Networks

Operating System Requirements

Preliminary Steps

If You Are Installing the Cisco Transport Manager Info Mediator

If You Are Using Cisco CNS Notification Engine As a Data Source

If You Are Using CiscoWorks2000 As a Data Source

If You Are Using Mobile Wireless Fault Manager as a Data Source

If You Are Using CNS-PE as a Data Source

Installation Procedure

Mounting the CD-ROM

Running the Installation Program

Configuring the Installation

Specifying Remote Info Mediator Information

Specifying the Desktop Configuration

Licensing the Cisco Info Server Components

Obtaining License Keys for the Info Center Components

Installing License Keys for the Cisco Info Server Components

Setting Licensing Information on Info Center Component Hosts

Starting Cisco Info Center

Stopping the Cisco Info Center Processes

Starting Cisco Info Center in Installations with Cisco CNS Notification Engine or Cisco WAN Manager

Stopping Cisco Info Server

Installing and Configuring the Single-System Architecture

This chapter describes installation of Cisco Info Center with all of the Cisco Info Center components on a single host. In this configuration, the following Cisco Info Center components are installed on one host:

•the Info Mediators component

•the Info Desktop component or the Webtop component

•the Cisco Info Server component

•the Licensing component

•the Process Control component

In addition, you can select the following components for installation:

•The Gateways component

•The Virtual Operator component

Note This chapter documents the installation if Cisco Info Server without failover. If you plan to enable failover, refer to "Configuring Failover."

Note This chapter describes the procedure for an initial installation of Cisco Info Center. For information on adding components after an initial installation, refer to "Adding or Deleting Components After an Initial Installation."

This chapter contains the following sections:

•"System Requirements"

•"Preliminary Steps"

•"Installation Procedure"

•"Configuring the Installation"

•"Licensing the Cisco Info Server Components"

•"Starting Cisco Info Center"

System Requirements

Minimum Configuration

This section indicates the minimum system requirements for Cisco Info Center.

•Cisco Info Server— Sun Blade 150 workstation or Sun Fire V120 server with a minimum of 512 MB RAM, and a 512-MB hard drive

Note This does not include additional NMS or add-on requirements. Please read the Release Notes or installation manual for the NMS you will use with each Info Mediator.

•Info Mediators—Sun Ultra 2 or higher workstation with a minimum of 64-MB RAM and a minimum 100 MB hard drive, per Info Mediator

•Info Admin Desktop—Sun Workstations with a minimum of 48-MB RAM and a minimum of 75-MB hard drive

Additional Requirements for Webtop

If you will install the Webtop component in the single-system architecture, note the following additional requirements:

•A full installation of Webtop requires an additional 120 MB of disk space.

•UNIX hosts or PCs that will monitor events relayed by the Webtop Web server must run one of the following browsers:

–Internet Explorer 5.x or 6.0

–Netscape Navigator 4.7 or 6.0

Note The browser must be configured to accept all cookies.

Additional Requirements for Virtual Operator

The Virtual Operator component must be installed on a host running Solaris 8. If you will install the Virtual Operator component in a single-system architecture, also note the following additional requirements.

•Virtual Operator requires an additional 55 MB of free disk space

•Virtual Operator requires an additional 80 MB of free space in the /tmp directory

•Perl 5 must be installed or linked from /bin/perl or /usr/local/bin/perl

•Your Solaris operating system must be at the level recommended for the Java Runtime Environment 1.3.1, which is bundled with Virtual Operator

See the Sun Microsystems SunSolv Web page at the following URL for a list of patches that might be required:

http://sunsolve.sun.com

Recommended Configuration for Managing Large Networks

This section indicates the minimum system requirements for in a large installation.

•Cisco Info Server—Sun Fire 280R or Netra 20 server or higher with a minimum of 1 GB of RAM and a 512-MB hard drive disk storage per Info Mediator

Note This does not include additional NMS or add-on requirements. Please read the Release Notes or installation manual for the NMS you will use with each Info Mediator.

•Info Mediators—Sun Ultra 2 or higher workstation with a minimum of 64-MB RAM and a minimum 100 MB hard drive, per Info Mediator

•Info Admin Desktops—Sun Workstations with a minimum of 48-MB RAM and of 75-MB hard drive

Operating System Requirements

The Sun system must have Solaris 7 or 8 with Motif 1.2 or the Common Desktop Environment (CDE) installed.

If you want to access the Cisco Info Center documentation on Cisco Connection Online from the Info Desktop, then your system must have a browser installed on it.

Preliminary Steps

Before you can use Cisco Info Center to monitor event sources, the applications that forward events to Cisco Info Server must be installed on one or more hosts.

In some cases, the applications can be installed on the host running the Cisco Info Center. In other cases, the application must run on separate hosts, however, the Info Mediators that receive events for Cisco Info Center can be installed on the host running the Cisco Info Center.

Table 4-1 lists some of the NMS applications that can be monitored using Cisco Info Center in the single-system architecture, and indicates where they may be installed.

Table 4-1 Installation Location of NMS Applications Used with Cisco Info Center

NMS Application

Monitored Devices/Event Sources

Application Installed on

Associated Info Mediators

Cisco WAN Manager (CWM)

Events from Cisco wide-area switches

Remote host or on host running Cisco Info Server

Rttrapd Info Mediator—Choose CWM from the Device Configuration menu.

Cisco Transport Manager (CTM)

Events from Cisco ONS 15327, 15454, 15800, 15801, 15808 devices

Remote host or on host running Cisco Info Server

Cisco Transport Manager Info Mediator—Choose CTM from the Device Configuration menu.

Cisco CNS Notification Engine

IOS Syslog events via SNMP or CNS Integration Bus, plus SNMP traps

Remote host or on host running Cisco Info Server

Rttrapd or Tibco Info Mediator—Choose CNS-NOTE using SNMP or CNS-NOTE using TIBCO from the Device Configuration menu.

Mobile Wireless Fault Manager (MWFM)

MWFM events

Remote host or host running Cisco Info Center

MTTrapd Info Mediator—Choose MWFM from the Device Configuration menu.

CiscoWorks2000 (CW2K)

Device Fault Manager (DFM) and/or Voice Health Monitor (VHM) events

Remote host or host running Cisco Info Server

MTTrapd Info Mediator—Choose CW2K from the Device Configuration menu.

Cisco CNS Performance Engine

CNS-PE events

Remote host or host running Cisco Info Server

Tibco Info Mediator—Choose CNS-PE using TIBCO from the Device Configuration menu.

Cisco Element Manager System-based applications

Northbound Event Interface (NEI) events from various Element Managers

Remote host or host running Cisco Info Server

MTTrapd Info Mediator—Choose Cisco Element Manager (NEI) from the Device Configuration menu.

Note The CEMF Info Mediator and the Cisco WAN Manager Info Mediator should be installed in a multi-system architecture. The CEMF Info Mediator is installed on a host running CEMF and the Cisco WAN Manager Info Mediator on a host running Cisco WAN Manager.

If You Are Installing the Cisco Transport Manager Info Mediator

If you have purchased a license for the Cisco Transport Manager Info Mediator, then before you can use the Cisco Transport Manager Info Mediator to monitor Cisco Transport Manager events, you must complete these steps:

Step 1 Ensure Cisco Transport Manager is installed on an appropriate host.

For information on installing Cisco Transport Manager, refer to the Cisco Transport Manager Installation Guide for the appropriate Cisco Transport Manager release.

Step 2 Complete these steps to start the Cisco Transport Manager Gateway/TL1 application:

a. On the Cisco Transport Manager host, log in to the Cisco Transport Manager client with administrator privileges.

b. In the Domain Explorer window, choose Administration > Server Control Panel.

c. On the Cisco Transport Manager Server tree, click the GW icon for the GateWay/TL1 Service property sheet.

d. Click the Global tab. In the Status area, click the Start button to start GateWay/TL1. Notice the service status toggles to Running.

e. Click the OSS Clients tab and the OSS Client Properties subtab.

f. Enter the following OSS client information:

•Password—Enter cic123.

•OSS Profile Name—Enter cic.

•OSS IP Address—Enter the IP address or host name of the host running the Cisco Info Server.

•EFD Name—Select All Pass.

g. Click Save to save your changes.

Step 3 From the machine that is running the Cisco Info Server, enter the following command to test connectivity to the Cisco Transport Manager machine:

ping <CTM_IP_address>

where <CTM_IP_address> is the IP address of the host running Cisco Transport Manager.

If You Are Using Cisco CNS Notification Engine As a Data Source

If you are using the Cisco Networking Services Notification Engine Info Mediator to monitor Cisco CNS Notification Engine events, install the Cisco CNS Notification Engine 2.0 or 3.0 on an appropriate host and then configure the Cisco Info Server to communicate with Cisco CNS Notification Engine. For information on installing Cisco CNS Notification Engine, refer to the Cisco CNS Notification Engine Installation and Configuration Guide.

Cisco CNS Notification Engine includes event monitoring for devices used with Cisco's Global Long Distance Solution as well as Cisco IP + Optical Solution.

When you configure monitoring for events relayed by the Cisco CNS Notification Engine product, you can choose to monitor SNMP events or CNS events forwarded by the Tibco Info Mediator. For information on configuring the Cisco Info Server component to communicate with one or more Cisco CNS Notification Engine hosts, refer to the "Configuring the Installation" section.

If You Are Using CiscoWorks2000 As a Data Source

If you are using the CiscoWorks2000 product as a data source for Cisco Info Center, install the Cisco Device Fault Manager (DFM) product on an appropriate UNIX or Windows 2000 host and configure the product(s) to communicate with Cisco Info Center. Or install the VHM product on a Windows 2000 host.

For information on configuring DFM to forward messages to Cisco Info Center (or another network management system), refer to the "Using the GUI to Configure the SNMP Trap Adapter to Forward Traps" section in the "Getting Started" section of the Installing and Setting Up Device Fault Manager on Solaris manual or the Installing and Setting Up Device Fault Manager on Windows 2000 manual.

For information on configuring VHM to forward events to Cisco Info Center, refer to the "Enabling VHM to Send Event Notifications to NMSs" section in the Installing and Setting Up Voice Health Monitor on Windows 2000 manual.

Note that VHM requires Java Plug-in 1.3 (HP-UX uses Java Plug-in 1.2.2). For additional details, refer to the "Client Requirements" section of the Installing and Setting Up Device Fault Manager on Windows 2000 manual.

If You Are Using Mobile Wireless Fault Manager as a Data Source

If you are using Mobile Wireless Fault Manager (MWFM) as a data source, ensure the application is installed and configured to forward events to Cisco Info Center. For information on configuring MWFM, refer to the MWFM documentation.

If You Are Using CNS-PE as a Data Source

If you are using the Cisco CNS Performance Engine product as a data source for Cisco Info Center, install the CNS-PE product on an appropriate host. For installation instructions, refer to the Cisco CNS Performance Engine User's Guide.

Installation Procedure

Installing the Cisco Info Center components on a single host involves the following steps:

•mounting the CD-ROM

•running the installation program

Mounting the CD-ROM

Complete these steps to mount the CD-ROM.

Step 1 Log in as user root.

Step 2 Insert the CD-ROM into your computer's CD-ROM drive.

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

host# /etc/init.d/volmgt start
Or, mount the CD-ROM with the following command:

host# mount -o ro -F hsfs </dev/dsk/device> /cdrom
where </dev/dsk/device> is the CD-ROM drive device entry.

Running the Installation Program

Complete these steps to run the Cisco Info Center installation program to install Cisco Info Server with a single system architecture.

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

Several prompts appear asking you to confirm the location of the Cisco Info Center installation media.

Step 3 Confirm the location of the installation media as prompted.

The following messages appear:
Copying files from CIC distribution in /<directory_name>...
Install Cisco Info Center, add components, delete existing components, or upgrade a 
previous installation to release 3.6.
Do you want to proceed (y or n) [default y]
Step 4 To proceed, press Return; otherwise, enter n.

The following messages appear:
INFO: a log file can be reviewed at /tmp/cic_install.log
Press <Return> to continue....
Step 5 Press Return.

The installation utility checks whether you have an existing installation of Cisco Info Center.

If you have an existing installation, you are prompted to upgrade the existing installation.

If you do not have an existing installation, the following messages appear:
Your system does not have an existing CIC installation.
Proceeding with an initial installation...
Do you want to install to the OMNIHOME directory (/opt/Omnibus) (y or n) [default n] 
Step 6 Do one of the following:

•To use the default installation directory (/opt/Omnibus) press Return.

•If you want to install Cisco Info Center in another directory, enter the directory path and name where you want to install Cisco Info Center.

The following prompt appears:
Do you want to select components now (y or n) [default y] 
Step 7 Press Return.

The Component Selection screen appears, shown in Figure 4-1. This screen allows you to choose the components you want to install.

Figure 4-1 The Component Selection Screen

Step 8 On the Component Selection screen, choose the components for a single system installation:

•Mediators

•Desktop or Webtop

•Cisco Info Server

•Licensing

•Process Control

To select a component, use the up and down arrow keys to position the cursor on a component you want to install. Then press the space bar to select the component. When the components are selected, an X appears next to the component.

To deselect a component, press the space bar.

Figure 4-2 shows the Component Selection screen with the full set of components for a single system installation selected.

Figure 4-2 Component Selection for Single System Installation

Note If required, you can also install the Gateways and/or the Virtual Operator component on this hosts.

Step 9 If you make a mistake in selecting components, highlight the component and press the space bar to deselect it.

Step 10 Press the tab key until Continue is highlighted.

Step 11 Press Return to verify your selections.

A window appears listing the selected components.

You are prompted several times to confirm your selections.

Step 12 Confirm your selection when prompted.

The installation program installs the selected packages. As the selected packages are installed, messages similar to the following appear:
Installing CIC packages for CIC 3.6
Installed pkg <CICcom>
Installed pkg <CICutl>
Installed CIC Packages for CIC 3.6
The following message appears:
Do you want to continue to configure components (y/n)? [y] 
The installation process is now complete. You are now ready to configure the Cisco Info Center components. The following section, the "Configuring the Installation" section, describes the configuration procedure.

Configuring the Installation

The configuration utility (nco_config) starts automatically if you press Return 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 Mediator 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
After the configuration utility starts, complete these steps to configure the Cisco Info Server components.

Step 1 Observe the following message:
Configure Info Server failover on primary Info Server?  (y/n)? [n] 
Step 2 Do one of the following:

•If you do not want to use the Cisco Info Server failover feature, press Return.

•If you want to use the Cisco Info Server failover feature, enter y.

Note If you choose to configure Cisco Info Server failover, go to the "Configuring Info Server Failover" section of "Configuring Failover," for detailed instructions.

The following prompt appears:
Configure Mediator failover on primary Mediator?  (y/n)? [n]
Step 3 Do one of the following:

•If you do not want to use the Info Mediator failover feature, press Return.

•If you want to use the Info Mediator failover feature, enter y.

Note If you choose to configure Info Mediator failover, go to the "Configuring Info Mediator Failover" section of "Configuring Failover," for detailed instructions.

The Cisco Info Center configuration menu appears:
##################################################################
               Cisco Info Center Configuration Menu
##################################################################
           1.  Configure Info Server         
           2.  Configure Mediators           
           3.  Configure Info Admin Desktop  
           4.  Configure All                 
           5.  Help                          
           6.  Quit 
           7.  Start Configuration
Select one of the above options : 
Note Configuration options reflect only those configurable options installed on the host.

Step 4 Enter 4 to configure all components.

Step 5 Enter 7 to start configuration.

The script displays the selected option and prompts you for confirmation.
You have Selected the following Info Center Components to be configured 
        Start Configuration
Do you want to continue (y/n)? [y]:
Step 6 Press Return to continue

A series of configuration prompts appear.

Answer the prompts as indicated in the following table.
Prompt

Response
INFO: The Process Control Agent name must 
be a single word no more than 11 
characters long, made up of uppercase 
alphanumeric letters.
The name must begin with a letter and end 
with _PA.
Enter Process Control Agent name [NCO_PA]
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 selection you make determines the name of a script that is used to start the Info Center processes on this host. This script is stored in the /opt/Omnibus/bin directory.
Enter Process Control Agent port number 
[4200]:
Do one of the following:

•To accept the default port, press Return.

•To specify an unused port number, enter the port number.

The script validates the availability of the port number. If the port number is in use or reserved, you are prompted to enter an unused port number.
Cisco Info Center will by default 
configure your Process Agent Daemon (PAD) 
to bind to the IP address that your 
hostname resolves to
If the host that the PAD will run on has 
multiple IP addresses, choose the IP 
address you would like the Process Agent 
Daemon (PAD) to bind to:
1. Do one of the following:

•If the host has multiple IP addresses defined in the /etc/hosts file, enter the IP address you want the Info Mediator host to use to bind to the remote Cisco Info Server.

•If there is only one IP address defined for the remote host, press Return.

If you press Return and only one IP address is found in the /etc/hosts file, the following message appears:
The configuration utility has found a 
unique IP for the host [<hostname>]
in the /etc/hosts file. This is 
[nnn.nnn.nnn.nnn]
Is the IP above the correct one to use? 
(y/n)? [y] 
2. Do one of the following:

•To accept the IP address indicated by [nnn.nnn.nnn.nnn] in the prompt, press Return.

•To specify another IP address, enter n and then specify the different IP address when prompted.

If you press Return, the following message appears:
Using address/hostname 
[nnn.nnn.nnn.nnn].....
where [nnn.nnn.nnn.nnn] is the IP address found in the /etc/hosts file.
Enter the Info Server name [INFOSERVER]: 
Do one of the following

•To accept the default name, INFOSERVER, press Return.

•To specify a different name for the Cisco Info Server, enter an alphanumeric string of up to eleven characters, beginning with a letter.
Enter the Port Number for the Info Server 
[4100]:
1. Do one of the following:

•To accept the default port, press Return.

•To change the port number, enter the number of an unused port.

Make a note of the port you configure in this step. You will need to enter this port number later during remote Info Mediator configuration.

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. If the port number is in use or reserved, you are prompted to enter another port number.

If there is an existing configuration for a Cisco Info Server with the specified name, the following prompt appears:
An Info Server named <servername> 
already exists.
Do you want to keep the existing data?: 
(y/n)? [y]
2. If this prompt appears and you want to keep the existing configuration, enter y; otherwise enter n.
Do you wish to configure automatic startup 
upon system boot? (y/n)? [y]:
If you want the Info Center components to start automatically when the host is booted, press Return; otherwise enter n.

If you press Return, then the Cisco Info Server components you install will start automatically when the host is started.

If you enter n when prompted to configure automatic startup, then a startup script is created in the /etc/init.d/ directory. You can then start the Cisco Info Server components (including the License server) by entering the command /etc/init/d/nco start.
The Device Configuration menu appears:
************************************
Device configuration menu
************************************
 1.   MWFM
 2.   CW2K (include DFM and VHM)
 3.   CTM
 4.   CWM
 5.   CEMF
 6.   NNM
 7.   CNS-NOTE using SNMP
 8.   CNS-NOTE using TIBCO
 9.   Syslog
 10.  SNMP Generic Traps 
 11.  CNS-PE using TIBCO
 12.  Cisco Element Manager (NEI)
1-11. Toggle Component
S. Select All Components
U. Unselect All
I. Setup and Install Components
H. Help
Q. Quit
Option: 
Step 7 Enter the numbers that correspond to the combination of devices or software applications you want to install.

Select one or more of the components depending on the type of software and hardware you will use Cisco Info Center to monitor:

•1. MWFM. Choose this option to monitor events from the Cisco Mobile Wireless Fault Mediator (MWFM) application.

•2. CW2K. Choose this option to monitor events from the CiscoWorks2000 product.

•3. CTM. Choose this option to monitor events from Cisco Transport Manager (CTM).

•4. CWM. Choose this option to monitor events from Cisco WAN Manager.

•5. CEMF. This Info Mediator component must be installed on a remote host running CEMF.

•6. NNM. This is used to monitor messages from the HP Network Node Manager application.

•7. CNS-NOTE using SNMP. If you have purchased the Cisco CNS Notification Engine product, choose this option to monitor SNMP-based events from the Cisco CNS Notification Engine product forwarded through the RTTrapd Info Mediator.

•8. CNS-NOTE using TIBCO. If you have purchased the Cisco CNS Notification Engine product, choose this option to monitor Cisco Networking Service (CNS)-based events through the Tibco Info Mediator.

•9. Syslog. Choose this option if you are not using the Cisco CNS Notification Engine product to receive Syslog messages and want to monitor some syslog events.

•10. SNMP Generic Traps. Choose this option if you want to monitor SNMP events.

•11. CNS-PE using TIBCO. Choose this option to receive events from the Cisco CNS Performance Engine product using the Tibco Info Mediator.

•12. Cisco Element Manager (NEI). Choose this option to receive Northbound Event Interface (NEI) events from an Element Manager running under the Cisco Element Manager System, for example NEI events from Cisco Media Gateway Node Manager (CMNM) or Cisco Media Gateway Manager (CMGM).

As you choose components, they are marked as SELECTED.

Step 8 When you are done selecting components, enter i to install the selected Info Mediators.

Depending on which Info Mediator components you selected, some or all of the following messages and prompts appear:

Step 9 If you selected option 3 (CTM) from the Device Configuration menu, complete the following steps:

a. Observe the following prompt:
IMPORTANT: An OSS user profile must have been created in the CTM server
Otherwise /opt/Omnibus/install/nco_config must be rerun after creating 
the OSS user profile in the CTM server
b. If you have not created a user profile in the Cisco Transport Manager, exit the installation procedure. Go to the "If You Are Installing the Cisco Transport Manager Info Mediator" section and follow the instructions for entering OSS client information. Then start the nco_config utility to reconfigure the Info Mediators component.

The following prompt appears:
Enter the hostname [or IPAddress] of the CTM server:
c. Enter the hostname or IP address of the Cisco Transport Manager server.

The following prompt appears:
Enter the username for the CTM server [cic]: 
d. Enter the username that was specified when the client profile was set up on the Cisco Transport Manager host.

The following prompt appears:
Enter the password for the CTM user [cic123]: 
e. Enter the password that was specified for the client profile on the Cisco Transport Manager host.

The following prompt appears:
Enter the version of the CTM server [2.2]: 
f. Enter the Cisco Transport Manager version you are using:

–To accept the default value (2.2), press Return.

–If you are using a later version of Cisco Transport Manager (3.0, 3.1, or 3.2) enter that version.

The following messages appear:
Generating CTM lookup table
Info Mediator ctm Configured
Press <Return> when ready... 
g. Press Return.

If you selected options 1, 2, 10, or 12 from the Device Configuration Menu, the following message appears:
Info Mediator mttrapd Configured
Press <Return> when ready... 
Step 10 Press Return if this message appears.

Step 11 If you are installing an Info Mediator to monitor Cisco WAN Manager events—you selected option 4 (CWM) from the Device Configuration menu—complete these steps:
***************************************************************
InfoCenter rules configuration for CWM.  You will now be asked
a series of questions to determine the version of CWM and the 
appropriate software versions to include.
***************************************************************
Please choose the version of CWM you are using.
Press <Return> when ready... 
	1. CWM 10.5 or higher
	2. CWM 10.4.X
	3. CWM 9.2 
	4. Quit
Version: 
a. Enter the number the corresponds to the Cisco WAN Manager version you are monitoring.

A message similar to the following indicating the selected version appears:
The CWM installation on host "<hostname>" is equal or higher than 10.5 version.
A series of prompts appears asking you to specify the Cisco WAN Manager version and SWSW version that is running on the wide-area switches the Info Mediator will monitor.

b. Indicate the requested information when prompted.

Messages similar to the following appear:
Cisco Info Center will be configured to support the following:
	:-CWM 10.5 on host "<hostname>"
	:-MGX 8850 or Firmware 5.0 on at least one MGX
The following prompt appears:
Is this correct? (y/n)? [y] 
c. If the version information is correct, press Return; otherwise enter n.

If you enter n, you are again prompted for Cisco WAN Manager software version information.

Messages similar to the following appear:
Linking /opt/Omnibus/probes/solaris2/cisco.includes/generictraps/enterprises -> 
/opt/Omnibus/probes/solaris2/cisco.includes/generictraps/enterprises_cwm92sw92fw50
Linking /opt/Omnibus/probes/solaris2/cisco.includes/generictraps/enterprises/traps to 
/opt/Omnibus/probes/solaris2/cisco.includes/generictraps/enterprises/traps_cwm92sw92fw
50
Configuring the CWM InfoMediator to register with the RTM Proxy for CWM.
You will be prompted for the IP address and port number to use for the 
Info Mediator.  The default values will be the current host.
Press <Return> when ready... 
d. Press Return.

You are prompted for the IP address of the Cisco WAN Manager host:
IP address of CWM InfoMediator host machine [xxx.xxx.xxx.xxx]: 
e. Do one of the following:

•If the indicated IP address is correct, press Return.

•If the indicated IP address is different, enter the address of the Cisco WAN Manager host.

You are prompted for the port number for the Cisco WAN Manager Info Mediator to use:
Port Number CWM InfoMediator will use [4000]:
f. Do one of the following:

•To accept the default port number (4000) press Return.

•To use another port number, enter that port number.

Messages similar to the following appear:
Port Number CWM InfoMediator will use [4000]: 4102
Checking Port Availability Please Wait... done
......................................................................................
........................................
Generating 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 CWM Version Lookup File...
Info Mediator cwm Configured
Press <Return> when ready... 
Step 12 Press Return if this message appears.

Step 13 If you selected option 7 (CNS-NOTE using SNMP), complete these steps.

a. Observe the following prompt:
Configuring the CNS-NOTE InfoMediator to register with the RTM Proxy for CNS-NOTE.
You will be prompted for the CNS-NOTE hostname and port number to use to 
communicate with CNS-NOTE.  The default hostname will be the current host,
and the default port will be 4000.
Press <Return> when ready... 
b. Press Return

The following prompt appears:
Hostname of the CNS-NOTE Host [<hostname>]: 
c. Do one of the following:

•If the indicated hostname is correct, press Return.

•If the host name is different, enter the correct hostname.

The following message appears:
Found a unique IP address for <hostname> in /etc/hosts.
IP address of CNS-NOTE InfoMediator host machine [xxx.xxx.xxx.xxx]: 
d. Do one of the following

•If the indicated IP address is correct, press Return.

•If the Cisco CNS Notification Engine product is running on a host with another IP address, enter that IP address.

The following prompt appears:
Port Number CNS-NOTE InfoMediator will use [4000]: 
e. Do one of the following:

•To accept the default port number (4000) press Return.

•To use another port number, enter that port number.

Messages similar to the following appear:
Checking Port Availability Please Wait
If the specified port number is not available, you are prompted to enter another port number.

f. If the specified port number was not available, enter another port number.

After you have entered a valid port number, messages appears indicating the Info Mediator(s) that were installed.

The following messages appear:
Info Mediator C-NOTE Configured
Press <Return> when ready...
g. Press Return.

Step 14 If you selected option 8 (CNS-NOTE using TIBCO) complete these steps:

a. Observe the following prompt:
Enter the path for the Tib/rendezvous daemon [eg. /opt/bin/ssng or 
/opt/DAS/tools/tibrv or /usr/tibco/tibrv/bin/
b. Enter the path to the directory where the Tib/Rendezvous daemon is installed.

The following prompt appears:
Are you using CNS-Note 3.x or higher? (y/n) [y]
c. Do one of the following:

–If you are using Cisco CNS Notification Engine 3.0, press Return.

–If you are using an earlier version of Cisco CNS Notification Engine enter n.

If you enter n, the following message appears:
Enter the subject, CNS-NOTE notifier is configured for [eg. cisco.mgmt.ssng]:
d. If this prompt appears, enter the subject for which the Cisco CNS Notification Engine notifier or DAS notifier is configured.

If you pressed Return in response to the Cisco CNS Notification Engine version prompt, the following message appears:
CIC will support all the alarms with subject = cisco.mgmt.CNS-NOTE.*.*.*.*.*
The installation script generates a cisco.rules file that reflects the choices you make and messages similar to the following appear.
Info Mediator tibco configured
Press <Return> when ready.
e. Press Return.

If you selected option 11 (CNS-PE using TIBCO, the following message appears:
Enter the subject, CNE-PE notifier is configured for [eg. cisco.mgmt.das]:
a. Enter the subject for which Cisco CNS Performance Engine is configured.

The following messages appear:
Creating the ncoadmin group for CIC...
The ncoadmin group already exists in the /etc/group file.
Creating the cicpa user for CIC...
The cicpa user already exists.
Press <Return> when ready... 
If you selected option 12 (Cisco Element Manager (NEI), the following messages appear:
*** Configuring mttrapd Info Mediator ***
As part of the CEMF NEI support, a Clear Alarm Tool will be configured to allow you
to clear alarms inside CEMF. To configure this tool you will now need to enter
the name of the host where you are running CEMF. After this tool has completed, you will 
need to install the CIC/Process Agent Daemon (PAD) component only, on the remote CEMF NEI 
host.
You will be prompted below for the name of the remote PAD and the port of the remote PAD,
please ensure you use the same details when configuring PAD on the remote host!
Please enter the name of the remote CEMF NEI host: 
a. Enter the name of the remote host where the Cisco Element Manager System is installed.

The following messages appear:
Configuring CEMF NEI 
 
Enter Process Control name on the remote CEMF NEI host [CEMFNEI_PA}:
b. Do one of the following:

–If you will use the default Process Control agent name on the remote host running the Cisco Element Manager system (CEMFNEI_PA), press Return.

–If you plan to use another Process Control name on the remote host running the Cisco Element Manager system, enter the Process Control name you will use when you install the Process Control agent on the remote host.

The following prompt appears:
Enter the Process Control port number on the remote CEMF NEI host [4200]: 
c. Do one of the following:

–If you will specify the default Process Control port number (port 4200) when you install the Process Control agent on the remote Cisco Element Manager System host, press Return.

–If you plan to use another port number, enter the port number you will use when you install the Process Control agent on the remote Cisco Element Manager host.

The following messages appear:
CEMF NEI Support now configured!
To complete CEMF NEI installation, please install the Process Agent component only on 
the
remote CEMF host. After installation, please run the following utility to complete 
installation
/opt/Omnibus/utils/install/cemf_nei_pa_conf.sh
Note In a true single system installation, you would normally not install the Process Control component on a remote host. However, if you choose to install the Cisco Element Manager System Info Mediator in a single system installation, you must install the Process Control component on the remote host running the Cisco Element Manager system and then configure it.

For instructions on how to do this, go to the "Installing the Process Control Agent on the Remote Cisco Element Manager Host" section of "Installing and Configuring the Multi-System Architecture."

Step 15 Press Return.

The following messages appear:
You have chosen to configure the InfoServer on the local host.
If the InfoServer needs to communicate with the remote InfoMediators via
the Process Control Agent,  it is necessary for the Process Control Agents
to be aware of each other.  The next set of prompts will configure the
the InfoServer to be aware of the remote InfoMediators.
Press <Return> when ready... 
Step 16 Press Return.

A series of prompts appears asking whether there are remote Info Mediators. Respond to these prompts as indicated in the following section, the "Specifying Remote Info Mediator Information" section.

Specifying Remote Info Mediator Information

This steps presented in this section are required if you will use remote Info Mediators to forward information to the Cisco Info Server from the following remote data sources:

•Cisco WAN Manager

•the Cisco CNS Notification Engine product (either SNMP-based messages or CNS messages from the Tibco Info Mediator)

•Cisco Transport Manager

•Cisco Mobile Wireless Fault Manager (MWFM)

•CiscoWorks2000, including Device Fault Manager (DFM) and Voice Health Monitor (VHM)

•The Cisco CNS Performance Engine product.

If you are not using one of these data sources, then enter "n" when you are prompted as to whether the Cisco Info Server will receive events from remote Info Mediators for these data sources.

Step 1 As the configuration utility prompts you whether you will receive events from remote Info Mediators, respond to the prompts as follows:

•If the Cisco Info Server will receive events from the remote Info Mediator identified in the prompt, press Return. You will then be prompted for the Process Control agent name and port number for the remote Info Mediator.

•If the Cisco Info Server will not receive events from the remote Info Mediator identified in the prompt, enter n.

•When asked whether there are additional instances of this Info Mediator, press Return if there are additional instances; enter n if there are no more additional instances.

•If you respond to the prompt for the Cisco Transport Manager Info Mediator, you are prompted for additional information (see Step 2 below).

Table 4-2 shows the prompts that appear and the possible responses you can make.

Table 4-2 Prompts for Remote Info Mediators

Prompt

If you are using this Info Mediator

If you are not using this Info Mediator

If there are additional instances of this remote Info Mediator

Is there a remote CWM InfoMediator? (y/n)? [y]

Press Return.

When prompted:

1. Enter the hostname of the host running Cisco WAN Manager and the RTtrapd (nco_p_cwm) Info Mediator.

2. Enter the Process Control name for the remote Info Mediator.

3. Enter a unique port number for Process Control communication with the remote Info Mediator.

4. When the prompt Select the version for your remote CWM appears, specify the Cisco WAN Manager version running on the remote Cisco WAN Manager host.

Enter n.

Press Return when asked whether there is another remote Info Mediator. When prompted:

1. Enter hostname for additional host running Cisco WAN Manager, RTtrapd (nco_p_cwm) Info Mediator.

2. Enter Process Control name for remote Info Mediator.

3. Enter unique port number for Process Control communication with remote Info Mediator.

Is there a remote Cisco CNS Notification Engine InfoMediator? (y/n)? [y]

Press Return.

When prompted:

1. Enter the hostname of the host running the Cisco CNS Notification Engine and the RTtrapd (nco_p_ssng) Info Mediator.

2. Enter the Process Control name for the remote Info Mediator.

3. Enter a unique port number for the Process Control communication with the remote Info Mediator.

4. Specify additional information as described below.

Enter n.

Press Return when asked whether there is another remote Info Mediator. When prompted:

1. Enter hostname for additional host running Cisco CNS Notification Engine, RTtrapd (nco_p_ssng) Info Mediator.

2. Enter the Process Control name for the remote Info Mediator.

3. Enter a unique port number for the Process Control communication with the remote Info Mediator.

Is there a remote CEMF InfoMediator? (y/n)? [y]

Press Return.

When prompted:

1. Enter the hostname for the host running CEMF and the CEMF Info Mediator.

2. Enter the Process Control name for the remote CEMF Info Mediator.

3. Enter a unique port number for the Process Control communication with the remote Info Mediator

Enter n

Press Return when asked whether there is another remote Info Mediator. When prompted:

1. Enter hostname for additional host running CEMF, CEMF Info Mediator.

2. Enter the Process Control name for the remote Info Mediator.

3. Enter a unique port number for the Process Control communication with the remote Info Mediator.

Is there a remote CTM Info Mediator? (y/n)? [y]

Press Return.

1. Enter the hostname of the host running the Cisco Transport Manager, Cisco Transport Manager Info Mediator.

2. Enter the Process Control name for the remote Cisco Transport Manager Info Mediator.

3. Enter a unique port number for the Process Control communication with the remote Info Mediator.

4. Enter additional information as described in Step 2 below.

Enter n.

Press Return when asked whether there is another remote Info Mediator.When prompted:

1. Enter the hostname for additional hosts running the Cisco Transport Manager, Cisco Transport Manager Info Mediator.

2. Enter the Process Control name for the remote Info Mediator.

3. Enter a unique port number for the Process Control communication with the remote Info Mediator.

Is there a remote MWFM InfoMediator? (y/n)? [y]

Press Return.

When prompted:

1. Enter the hostname of the h