|
|
This chapter provides information on the installation, configuration, and licensing of Cisco Info Center 2.0.
This chapter includes the following sections:
 |
Note Licenses are required on a per component basis. To effectively use the Cisco Info Center product, a license is necessary to complete the installation. The licenses can be obtained from the Micromuse Technical Support Center. See the "Licensing Cisco Info Center" section section for detailed information. |
The multi-system architecture is the recommended client-server architecture for Cisco Info Center. With this architecture, different components of Cisco Info Center are installed and configured on different Sun Solaris systems.
With the multi-system architecture, you have several options for distributing the Cisco Info Center components. This section covers three installation and configuration scenarios.
The following sections describe each of these scenarios.
In this scenario, the CIC components are installed as follows:
Figure 2-1 shows a multi-system architecture that includes the Cisco Info Center Policy Manager component.
You might use this architecture if you want CIC to monitor VPNs configured using Cisco MPLS VPN Solution. Alternatively, you can run the STG on the same host that is running the Cisco Info Server.
|
Note Do not install the Policy Manager component of Cisco Info Center on a host that is running Cisco MPLS VPN Solution. |
In this scenario, the CIC components are installed as follows:
You might want to use this architecture if you have one or more versions of Cisco WAN Manager running on your network and want to deploy Cisco Info Server on a separate host.
Figure 2-2 shows an example of the multi-system architecture with Cisco Info Center and CWM.
|
Note Cisco WAN Manager 9.2.08 and higher includes a built-in version of the Syslog Trap Generator. Do not install the Cisco Info Center version of the STG on a host that is running Cisco WAN Manager. |
In this scenario, the CIC components are installed as follows:
You might want to use this scenario if you want to monitor Cisco IOS devices and Cisco digital subscriber line (DSL) devices.
Figure 2-3 shows an installation of the Cisco Info Server and the standalone STG application.
This section presents component installation tables that show the components to be selected in the installation process. Details on the installation process for a multi-system architecture are provided in "Installing and Configuring the Multi-System Architecture."
The multi-system architecture installation process involves the installation and configuration of the Cisco Info Server, Info Mediators (consisting of the HP NNM Info Mediator and the RTtrapd Info Mediator), and the Cisco Info Admin Desktop. It may also involve installation of the STG and the Policy Manager component.
Table 2-1 shows the components to be selected in the multi-system architecture installation process.
You can pick the options in any order.
|
Note You can install the Licensing component on any host. Also, if you have purchased a license for the Info Gateway component, you can install the Info Gateway on the host that will run the Cisco Info Server component. |
| Host | Required Installation |
|---|---|
Cisco Info Server host | Install Process Control component Install Info Server component (optional) Info Gateway component (optional) Policy Manager component |
Mediators only host | Install Process Control component Install Info Mediators component |
STG host | Install the STG Install the Info Mediators component and configure the RTTrapd Info Mediator Install Process Control component |
Admin Desktop host | Install Info Admin Desktop component |
|
Note You must install the Licensing component on a host that is accessible to your CIC components. In addition, if you have purchased a license for the Info Gateway component, you may want to install the Info Gateway component on the host that is running the Info Server component. You may also choose to install the Admin Desktop component on the host that is running the Info Server component. |
For information on installing Info Mediators other than the NNM Info Mediator and the RTtrapd Info Mediator on the Syslog Info Mediator, see "Installing and Configuring the Single-System Architecture."
The following section provides details on minimum hardware requirements for the various components of the Cisco Info Center; the Cisco Info Server, the CWM host, and the Cisco Info Admin Desktop client (system requirements and front-end software requirements).
|
Note If there is not enough space available in /var/tmp, you can create a soft link from /var/tmp to an available partition: by issuing the following command: host% ln -s /var/tmp /tmp |
The system requirements for the Cisco Info Center and CWM Mediators (HP NNM and RTtrapd) host specified below, are in addition to the recommended requirements for CWM, Informix, and HP NNM:
|
Note If there is not enough space available in /var/tmp, you can create a soft link from /var/tmp to an available partition by issuing the following command: host% ln -s /var/tmp /tmp |
In order to use the Policy Manager Component of Cisco Info Center, you must have the Cisco MPLS Solution product installed on your network. For information on installing Cisco MPLS VPN solution, refer to the following documents:
The host that will run the Policy Manager component must meet the minimum system requirements for the Cisco Info Server.
|
Note Do not install the Policy Manager component on a host that is running Cisco MPLS VPN Solution. Install it only on a host that is running the Info Server component. |
If you are running the STG on a Cisco WAN Manager host, you do not need to install the STG. If you want to use the STG to monitor IOS facility messages but do not have CWM running on your network, you can install STG in two ways:
If you install the STG on the host that is running the Cisco Info Center, the system requirements are the same as for the standalone Cisco Info Center.
To install the STG on another host, the requirements are minimal.
The system requirements for the Cisco Info Center Admin Desktop specified below, are in addition to the recommended requirements for any products running on that specific Desktop:
|
Note If there is not enough space available in /var/tmp, you can create a soft link from /var/tmp to an available partition: host% ln -s /var/tmp /tmp |
Cisco Info Center supports the following user interface environments:
|
Note A single-system architecture with two or all three of the above configurations on one host can also be installed. |
In this architecture, Cisco Info Server, Cisco Info Admin Desktop, Syslog Mediator, and CWM Mediators (HP NNM and RTtrapd Info Mediators), are installed and configured on the CWM host workstation, as shown in Figure 2-4. While this is not the preferred architecture, it is supported for the following conditions:
|
Note If there is not enough space available in /var/tmp, you can create a soft link from /var/tmp to an available partition: host% ln -s /var/tmp /tmp |
Cisco Info Center supports the following user interface environments:
During installation using the OINSTALL installation program, select the following components to install the single-system architecture with Cisco WAN Manager.
1. Desktop SELECTED 2. Gateway 3. Licensing SELECTED 4. Process Control SELECTED 5. Mediators SELECTED 6. InfoServer SELECTED 7. Java Event List 8. Wave 9. Syslog Trap Generator 10. Policy Manager
|
Note If you have purchased a license for the Info Gateway component and want to install it on the Cisco WAN Manager host, you may also select the Gateway component for installation. |
During system configuration, select the following:
************************************ Info Mediators configuration menu ************************************ 1. NNM probe SELECTED 2. rttrapd probe SELECTED 3. syslog probe
Details on the single-system architecture installation process are provided in Chapter 4, "Installing and Configuring the Single-System Architecture".
In this architecture, the Info Server component, the Policy Manager component, and the STG component are installed on a single host and are configured to communicate with a host that is connected to the Cisco MPLS VPN Solution application.
Figure 2-5 shows the single-system architecture with Policy Manager.
|
Note If there is not enough space available in /var/tmp, you can create a soft link from /var/tmp to an available partition: host% ln -s /var/tmp /tmp |
During installation using the OINSTALL installation program, select the following components to install the single-system architecture with Cisco WAN Manager.
1. Desktop SELECTED 2. Gateway 3. Licensing SELECTED 4. Process Control SELECTED 5. Mediators SELECTED 6. InfoServer SELECTED 7. Java Event List 8. Wave 9. Syslog Trap Generator SELECTED 10. Policy Manager SELECTED
During system configuration, select the following:
************************************ Info Mediators configuration menu ************************************ 1. NNM probe 2. rttrapd probe SELECTED 3. syslog probe
Details on the single-system architecture installation process are provided in "Installing and Configuring the Single-System Architecture."
In this architecture, the Info Server component, the Syslog Trap Generator component, and the RTTrapd Info Mediator are installed on a single host. This allows the Info Server to communicate with devices running the Cisco IOS, including DSL devices.
Figure 2-6 shows the single system architecture with the standalone STG.
|
Note If there is not enough space available in /var/tmp, you can create a soft link from /var/tmp to an available partition: host% ln -s /var/tmp /tmp |
During installation using the OINSTALL installation program, select the following components to install the single-system architecture with the Syslog Trap Generator.
1. Desktop SELECTED 2. Gateway 3. Licensing SELECTED 4. Process Control SELECTED 5. Mediators SELECTED 6. InfoServer SELECTED 7. Java Event List 8. Wave 9. Syslog Trap Generator SELECTED 10. Policy ManagerD
During system configuration, select the following:
************************************ Info Mediators configuration menu ************************************ 1. NNM probe 2. rttrapd probe SELECTED 3. syslog probe
Details on the single-system architecture installation process are provided in Chapter 4, "Installing and Configuring the Single-System Architecture".
This section describes how to obtain the required license keys for the Cisco Info Center.
Step 2 Provide the number of license servers required. After several questions, a machine code is returned.
Step 3 Contact your Micromuse Technical Support Center. Provide the Micromuse Technical Support Center with the machine code for each license server, as well as, the configuration components (that is, Info Mediators, Info Gateways, Info Servers, etc.) License keys will be emailed to you. The license keys are used to complete all of the nco_license steps for a full installation.
Step 4 After you have obtained the required license key, run the nco_license utility again and enter the license keys when prompted for them.
Complete these steps to obtain license keys for the Policy Manager application.
The nci_license utility runs and generates a server license code. This code appears on the console display.
Step 2 Email Micromuse Technical Support and include the server license code and hostname in your email.
The email address is as follows:
Micromuse Technical Support will email you a feature key and a license key.
Step 3 Press Return.
The following prompt appears:
Enter the feature code (press <Enter> to exit):
Step 4 Enter the feature key that you received in the email.
The following prompt appears:
Enter the license key:
Step 5 Enter the license key:
You can now start Policy Manager.
Complete these steps to license the Java Event List application.
The email address is as follows:
Micromuse Technical support will email you a license that looks something like the following:
jeld.license.key:7&&6bsbsR.X6.-ycg.CuuWaxI jeld.license.address:250.71.228.47 jeld.license.count:2 jeld.license.expire:14/Jun/2000
Step 2 Use the text editor of your choice to create a file called jeld.lic.
Step 3 Copy the license key information into the file and save it in the following directory:
/opt/Omnibus/java/props
You will now be able to start the JEL application.
The email address is as follows:
Micromuse Technical support will email you a license that looks something like the following:
wave.license.key:eee8lZ6661Ynfo-Ag3PMTPgVrQ wave.license.address:250.71.228.47 wave.license.count:2 wave.license.expire:14/Jun/2000
Step 2 Use the text editor of your choice to create a file called wave.lic.
Step 3 Copy the license key information into the file and save it in the following directory:
/opt/Omnibus/wave/props
You will now be able to start the Wave application.
Licensing for the Info Center components is implemented as follows:
1. At least one host is set up as a license server by installing the Licensing component on that host and then starting the license server using the nco_start_license command.
2. Other hosts that are running licensed components are given access to the license server by setting the NCO_ELMHOST variable to point to the host that is acting as a license server.
Complete these steps to implement licensing.
Step 2 Install the Cisco Info Center Licensing component on at least one host.
For installation instructions, refer to the following chapters:
Step 3 At the host where you have installed the Licensing component, enter the following commands to start licensing:
setenv OMNIHOME /opt/Omnibuswhere license_server_hostname is the hostname of the license server.
Step 5 If you are running the ksh and sh shell, enter the following command:
NCO_ELMHOST=<license_server_hostname>; export NCO_ELMHOSTThis command ensures that components search for licenses on the host license_server_hostname only.
Step 6 To search for licenses on multiple sources, prefix the hostname with an @.
For example, the following command (csh) ensures that components search for licenses on license_server_hostname, then on boomerang, before doing a network broadcast:
setenv NCO_ELMHOST=@<license_server_hostname>:boomerang:BROADCASTFor ksh and sh shell users, the command is as follows:
NCO_ELMHOST=@license_server_hostname:boomerang:BROADCAST; export NCO_ELMHOST |
Note If you do not set the NCO_ELMHOST environment variable, components search for licenses by network broadcast only. |
This section describes how to stop and deinstall the Cisco Info Center.
|
Note Deinstall Cisco Info Center only if you want to delete it completely. |
To remove the CIC installation you must be root. Complete these steps to remove the installation.
Step 2 Issue the following command to stop all CIC Server and Mediator(s) processes:
The following message appears:
Login Password:
Step 3 Enter the password for root.
The following message appears:
Connected To PA Server [NCO_PA] Shutdown Options :-
1) Shutdown Server leaving managed processes running.
2) Shutdown Server and stop all managed processes.
3) Exit shutdown interface.
Select Option [1-3] 2
Select option 2.
Step 4 To identify all current CIC Syslog Trap Generator processes, issue the following command:
ps -ef | grep cicStep 5 Issue the following command to stop all CIC Syslog Trap Generator processes:
Step 6 If the Policy Manager component is installed and running, complete the following steps:
a. Issue the following command to determine whether Policy Manager processes are running:
b. Issue the following command:
Step 7 To identify all other CIC processes, issue the following command:
ps -ef | grep ncoStep 8 To identify all current CIC packages, issue the following command:
Step 9 Issue the following command to remove the CIC components:
Step 10 Issue the following commands:
rm -rf /.omnibus
Complete these steps to deinstall Cisco Info Center 2.0:
The following message appears:
Login Password:
Step 2 Enter the password for root.
The following message appears:
Connected To PA Server [NCO_PA] Shutdown Options :-
1) Shutdown Server leaving managed processes running.
2) Shutdown Server and stop all managed processes.
3) Exit shutdown interface.
Select Option [1-3] 2
Select option 2.
Step 3 Issue the following command to ensure that the Info Center processes are down:
/usr/bin/ps -ef | grep ncoStep 4 Issue the following command to remove the installed Cisco Info Center Release 1.2 packages:
pkgrm CICcom CICdsk CICgtw CICjel CIClic CICmed CICpad CICsrvSome of the packages listed above may not exist. You can use the pkginfo utility to find out which exist and then use the returned list with the pkgrm utility:
pkginfo |grep CICStep 5 Issue the following command:
rm -rf /opt/OmnibusStep 6 Issue the following rm commands:
rm -rf /etc/init.d/nco
Complete these steps to deinstall Cisco Info Center 1.1:
The following prompt appears:
Login Password :
Step 2 Enter the password for root.
The following messages appear:
Connected To PA Server [NCO_PA] Shutdown Options :-
1) Shutdown Server leaving managed processes running.
2) Shutdown Server and stop all managed processes.
3) Exit shutdown interface.
Select Option [1-3] 2
Step 3 Select option 2.
Step 4 Issue the following command to remove the installation directory ($OMNIHOME):
rm -rf /opt/OmnibusStep 5 Issue the following rm commands:
rm -rf /etc/init.d/nco
Posted: Tue Jun 13 16:31:05 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.