Release Notes for Cisco Info Center Release 3.5

These release notes provide information about the Cisco Info Center 3.5 release.

Introduction

Cisco Info Center is a Service-Level Management (SLM) system that provides a consolidated view of enterprise-wide events and status information. It collects event streams or messages from many different data sources and presents a single, consistent view of the current state of all Cisco Info Center managed systems. It distributes the event information to the operators and administrators responsible for monitoring service levels.

Cisco Info Center allows diverse management platforms, applications, and Internet protocols to be brought together to provide the administrator a single point of monitoring those platforms and applications. Cisco Info Center does not replace the management platforms. It instead complements them by providing an enterprise wide event/fault and status exchange. Cisco Info Center can also tie together domain limited network management platforms in remote locations.

Cisco Info Center tracks the state of events in a high performance distributed database and presents information of interest to specific users through individually configurable filters and views. Cisco Info Center automation functions can be used to perform intelligent processing on the current state of managed objects. Cisco Info Center can build upon existing management systems or applications and, therefore, uses existing management skills and minimizes deployment time.

Cisco Info Center 3.5 Components

•

Cisco Info Server—The core of the Cisco Info Center system—an active, main-memory database that stores and manages events. The Info Server consolidates, associates, and normalizes event data received from Info Mediators, Info Gateways, and monitors.

•

Info Mediators—Applications that act as data acquisition agents. Info Mediators acquire data from events sources such as Cisco WAN Manager, HP Network Node Manager, the Cisco Info Center Policy Manager application, the Cisco IOS syslog, Cisco Element Management System (CEMF)-based applications, Cisco Transport Manager, and a variety of SNMP-enabled devices.

•

Policy Manager—An extension to Cisco Info Center that receives Customer Edge router and Provider Edge router events from Cisco's MPLS VPN Solution product, an application that allows service providers to define and monitor virtual private networks (VPNs).

•

Info Gateways—Software modules that allow the Cisco Info Server to read events from and write events to third party applications and forward alerts between Cisco Info Servers.

•

Cisco Info Admin Desktops—An integrated graphical suite of tools used by operators. These tools are the starting points for designing filters and customizing views. Cisco Info Admin Desktop information can be viewed from a UNIX/Motif front-end or a Java-driven Web browser. Event information is delivered in a format that allows operators to quickly respond.

•

Webtop 1.1—Webtop provides the read-only event publication of Wave with the interactive features of JEL for manipulating alerts, combined in one web-based product. Webtop publishes Netcool alerts for viewing in a web browser, and enables certain users to manipulate them using an active event list launched from a web browser.

For instructions on installing the Webtop component, refer to Chapter 5 of the Cisco Info Center Installation and Configuration Guide, "Installing the Webtop Component." For detailed documentation on the Webtop product, go to the Micromuse support site at the following URL:

•

Virtual Operator. Virtual Operator is a product that allows the Info Server to execute resolution scripts that mimic the actions that a network operations center (NOC) operator would take to resolve an alert. Scripts or applications supported by Virtual Operator can be UNIX shell scripts, PERL scripts, or compiled programs written in C or C++.

For instructions on installing Virtual Operator, refer to Chapter 5 of the Cisco Info Center Installation and Configuration Guide, "Installing the Virtual Operator Component." For detailed documentation on the Virtual Operator product, go to the Micromuse support site at the following URL:

For detailed information on the Cisco Info Center components and how they interoperate, refer to Chapter 1, "Overview," in the Cisco Info Center Installation and Configuration manual.

Info Mediator Modules

When you purchase Cisco Info Center you purchase licenses for one or more Info Mediators. The following Info Mediators have been developed to monitor specific types of Cisco hardware and software:

•

RTTrapd Info Mediator—Interfaces with devices monitored by Cisco WAN Manager to monitor events from Cisco wide-area switches and syslog events from IOS devices through the Cisco CNS Notification Engine product. In the Cisco Info Center configuration interface, RTTrapd is referred to as the CWM Info Mediator when it is used to monitor CWM.

•

HP NNM Info Mediator—Interfaces with the Hewlett Packard Network Node Manager (NNM) system.

•

Syslog Info Mediator—Acquires event data from syslogd, the UNIX system message logger, by reading from a FIFO that syslogd has been configured to write messages to.

•

CEMF Info Mediator—An Info Mediator that interfaces with Cisco CEMF-based application, such as Cisco Connection Manager, Cisco DSL Manager (CDM), and Cisco Media Gateway Node Manager (CMNM). Refer to the "CEMF Support" section for a detailed list of supported applications.

•

CTM Info Mediator—Interfaces with the Cisco Transport Manager (CTM) application to allow monitoring of Cisco optical devices, including the Cisco ONS 15454, ONS 15327, ONS 15600, ONS 15800, ONS 15801, and ONS 15808 optical transport platforms.

•

MTTrapd Info Mediator—Multithreaded Info Mediator that interfaces with a variety of SNMP-enabled devices and event correlation engines such as CiscoWorks2000 (DFM and VHM) and MWFM. This also includes specific enhancements and fixes recommended by the CERT team. The set of rules also includes the best practices set of rules developed by Micromuse.

With Cisco Info Center 3.5, the MTTrapd Info Mediator also processes events transmitted by element managers that support the Northbound Event Interface (NEI) included with Cisco Element Manager System version 3.2 and higher, such as Cisco Media Gateway Manager (CMGM) 2.0 and Cisco Media Gateway Controller Node Manager 2.3.1 and 2.3.1. The NEI allows element managers to send events encapsulated in SNMP messages to network management systems such as Cisco Info Center.

To enable support for the Cisco Element Manager System, select Cisco Element Manager from the Device Configuration Menu during Info Mediator configuration with the nco_config configuration utility.

•

Tibco Info Mediator—Info Mediator that interfaces with the CNS-NOTE 2.0 and 3.0 product and the CNS Performance Engine 1.0 product.

Additional Info Mediators that work with a variety of hardware and software can be ordered in addition to Cisco Info Center.

For detailed information on the event sources and Info Mediators used with Cisco Info Center, refer to Chapter 3, "Info Center Mediators and Event Receivers," in the Cisco Info Center Mediator and Gateway Reference.

Cisco Info Center Add-On Products

Cisco Info Center can work with several related products that can be ordered from the Cisco Info Center pricelist. These products include the following:

•

Internet Service Monitors (ISM) 2.1—A set of components designed to monitor the status and performance of internet services. The information gathered and processed by the monitors is used to determine whether a particular service is performing adequately, to identify problem areas, and to report service performance. Performance is measured against agreed Service Level Agreement (SLA) criteria. A set of specific ISM utilities have been added to Cisco Info Center, which simplify the bulk configuration and loading of ISM data.

•

Firewall—A real-time security application that helps managers in secure operations centers to resolve network events that may disrupt business services or cause a security breach.

•

Fusion—A fault management application that provides access to mainframe computer management applications for non-mainframe network operators.

•

Impact —A value-added application that works with Cisco Info Center to assist network operators in monitoring Service Level agreements by providing additional event analysis beyond that available with Cisco Info Center. For example, Impact users can determine the consequences of an event, such as what or when services are affected and which users are affected by specific alarm conditions.

•

Netcool for Voice Networks—A supplement to Cisco Info Center that is designed specifically for providers of carrier-grade voice services. It includes a Central Configuration Tool that allows voice service providers to install the system at multiple sites from a central location and a set of Telecommunications Service Managers (TSMs) that work with TL1-based monitoring systems as well as Marconi, Alcatel, Ericsson, and Nortel devices.

•

Netcool/Tivoli—An application that integrates the Cisco Info Server product with the Tivoli network management application and allows Tivoli to manage a Cisco Info Server installation.

•

Precision—A network monitoring product that applies root cause analysis based on network slice technology.

•

Reporter—A real-time, Web-based client-server application that provides accurate, historical reporting on Cisco Info Center event data forwarded from the Info Server.

•

Visionary—A product that utilizes a network agent that receives events from an intelligent, high-volume SNMP polling engine called the Distributed Status Monitor (DSM) and performs a rules-based analysis of network events, based on Internet Engineering Task Force (IETF) standards and vendor-specific management information.

For additional information on these products, refer to the Release Notes for Cisco Info Center Add-On Products.

New Features and Enhancements for the Release 3.5

•

Option to Install the Webtop Product. The component selection menu for Cisco Info Center 3.5 now allows you to install the Webtop 1.1 product directly during Cisco Info Center installation.

Webtop provides is a web-based version of the Cisco Info Center interface. Webtop publishes alerts for viewing in a web browser, and enables certain users to manipulate them using an active event list launched from a web browser. Webtop also includes server administration pages, which can be used to set up users, table views, and other configurable elements. It also includes the Webtop Editor, which is a powerful tool used for creating and editing maps. Netcool Webtop meets the need for service providers to deal with user problems relating to network alerts by publishing Netcool alerts and active event list applets over the HTTP or HTTPS protocol to supported web browsers.

•

Option to Install the Virtual Operator Product. Virtual Operator is a product that allows the Info Server to execute resolution scripts that mimic the actions that a network operations center (NOC) operator would take to resolve an alert. Scripts or applications supported by Virtual Operator can be UNIX shell scripts, PERL scripts, or compiled programs written in C or C++.

•

Support for the Cisco Voice over Cable Solution. Cisco Info Center 3.5 includes support for Cisco's Voice over Cable solution. Cisco Info Center can now receive events from hardware and software platforms used with this solution by means of the Tibco Info Mediator, the MTTrapd Info Mediator, and the CEMF Info Mediator (through the Cisco Media Gateway Manager element manager).

•

Support for SNMP-Based Northbound Events from Cisco Element Management Framework (CEMF)-Based Applications. Cisco Info Center 3.5 can now receive and process "raised" and "cleared" events from the CEMF Northbound Event Interface (NEI).

•

Support for CNS-NOTE 3.0 Events. Cisco Info Center 3.5 can receive and interpret events from the Cisco Networking Service Notification Engine (CNS-NOTE) 3.0 product. The enhancements include a new version of the Info Desktop support file for CNS-NOTE and a new tool—the Encoder/Decoder tool.

The Encoder/Decoder tool is a Web-based application that describes information contained in syslog messages that are forwarded to Cisco Info Center by the CNS-NOTE product. In order to use the Decoder/Encoder tool, you must have a Web browser installed on the host that is running the Info Desktop.

•

Support for CWM 11.0.10 Events. Cisco Info Center 3.5 provides processing rules to provide support for CWM 11.0.10 events.

•

Enhanced Support for CTM Events. Cisco Info Center 3.5 provides processing rules to provide support for CTM 3.2 events.

System Requirements

Operating System Requirements

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

If you need to run the CiscoView application, view the CNS-NOTE help page, or view the Cisco Info Center online documentation on CCO, a supported browser is required. For current browser requirements for the CiscoView application, refer to the documentation for the CiscoWorks2000 component that your Cisco Info Center installation will monitor. The documentation for the Device Fault Manager and Voice Health Monitor components of CiscoWorks2000 is listed in the "Related Documentation" section.

If you will install the Virtual Operator component, the target host must be running Solaris 8.

Minimum Configuration

•

Info Server— Sun Ultra 10 or higher 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 that you will use with each Info Mediator to determine the installation requirements for the NMS.

•

Info Mediators—Sun Ultra II or higher 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 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.

•

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

Additional Requirements for Virtual Operator

If you will install the Virtual Operator component in a single-system architecture, note the following additional requirements.

•

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:

Recommended Configuration for Managing Large Networks

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

•

Info Server — Sun Ultra 60 or higher with a minimum of 1 GB of RAM and a 512-MB hard drive disk storage per Info Mediator

Note

•

Info Mediators—Sun Ultra II or higher 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

Cisco Info Center 3.5 Support Matrix

Table 1 indicates which components of Cisco Info Center can co-exist on the same host with which Network Management Systems (NMSs) or be installed standalone in combination with specified Solaris versions and software releases. A notation of "yes" indicates that a Cisco Info Center 3.5 component can co-exist on the same host or be installed standalone with an indicated operating system, software release, and/or NMS.

Note The MTTrapd, CEMF, and NNM mediators cannot co-exist in a single machine. Only one of these can be installed on one machine, since by default they all bind to port 162.

Table 1 Cisco Info Center 3.5 Compatibility Matrix
Cisco Info Center 3.5 Component	Required Solaris Version	NMS/ Manager	Solaris Version for NMS/ Manager	Can Be Installed Standalone	Can Co-exist with NMS/Manager	Can Co-exist¹ with NMS/ Manager and Info Server
RTTrapd Info Mediator	2.6 7, 8	CWM 9.2.x CWM 11.x.x CNS-NOTE 2.0, 3.0	2.6 7 7, 8	yes	yes yes yes	yes yes yes
NNM Info Mediator	2.6 7, 8	HP-OV 5.01 HP-OV 6.10	2.6 7, 8	yes	yes yes	yes yes
Syslog Info Mediator	2.6 7, 8	syslog	7	yes	yes	yes
CTM Info Mediator	2.6 7, 8 7, 8	CTM 2.2 CTM 3.0 CTM 3.2	7 8 8	yes yes	yes yes	yes yes
CEMF Info Mediator	2.6 7, 8	CEMF 3.0.4 CEMF 3.1 CEMF 3.2	7, 8 7, 8 7, 8		yes yes yes	yes yes yes
MTTrapd Info Mediator	2.6 7, 8	DFM 1.0/1.1 VHM 1.0 MWFM 2.0 Gateways Gatekeepers Any SNMP device/interface Cisco Element Manager System 3.2	7, 8 7, 8 7, 8 NA NA NA 7, 8	yes yes yes yes	yes yes yes yes	yes yes yes yes
Tibco Info Mediator	2.6 7, 8	CNS-NOTE 2.0, 3.0 CNS Performance Engine 2.0.1	7, 8 8	yes	yes	yes
Policy Manager	2.6 7, 8	VPNSC 1.1 VPNSC1.2 VPNSC1.2.1 VPNSC 2.0 VPNSC 2.1 VPNSC 2.1.1 VPNSC 2.2.1	7 7 7 7			yes yes yes yes
ISM 2.1	7, 8	Internet services: RADIUS HTTP HTTPS DNS ICMP²	7, 8	yes	yes	yes

¹Although the Info Server component and the NMS/Manager can co-exist on the same host machine, this is not recommended for reasons of efficiency and to ensure load balancing.

²Refer to the ISM documentation for a complete list of supported Internet services.

Supported Hardware and Software

Cisco Info Center 3.5 operates with the following hardware and software platforms.

CWM Support

Table 2 presents a platform compatibility matrix that indicates Cisco Info Center 3.5 support for Cisco WAN Manager and switches managed by CWM.

For the most up to date information on which software and firmware releases are supported, refer to the Release Notes for your version of CWM Release 11.0.10. The Release Notes are located at the following location on Cisco.com:

Table 2 Platform Compatibility Matrix
Cisco Info Center	CWM (SV+)	HPOV	IOS	Solaris
3.5	9.0	4.01		2.5.1
3.5	9.1	5.01		2.5.1
3.5	9.2.09 (Solaris 2.6 only)	5.01	12.0.5	2.6/2.7 (Cisco Info Center Mediators only)
3.5	10.4.10, 10.5.10 (Solaris 7 only)	6.10	12.0.5 or above	2.6/2.7 (Cisco Info Center Mediators only)
3.5	11.0.10 (Solaris 7 and 8)	N/A	12.0.5 or above	7, 8

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/svplus/11/rnotes/index.htm

IOS Support

IOS syslog messages are supported through CNS-NOTE product and through the Syslog Info Mediator.

CTM Support

CEMF Support

Through the CEMF Info Mediator, Cisco Info Center 3.5 supports the following element managers that run under CEMF:

–

Cisco Media Gateway Node Manager (CMNM). An element manager that manages media gateways running on Cisco MGX 8260 devices.

–

Cisco DSL Manager (CDM). An element manager for managing Cisco DSL Aggregation Modules (DSLAMs) such as the Cisco 6260 DSLAM

–

Cisco Service Connection Manager (SCM). An element manager for managing the Cisco aggregation-layer router, often used in xDSL environments, such as the 6400

–

Cisco Universal Gateway Manager (UGM). An element management system offering robust, scalable, carrier-class capabilities for the Cisco AS5xx0 series of universal gateways.

–

Cisco Cable Manager (CCM). An element management system that manages Cisco uBR7200 series broadband routers.

–

Cisco 7200/7400 Manager (C72/74M). An element manager that manages Cisco 7200 and Cisco 7400 routers.

–

Cisco 12000 Manager. An element manager that manages Cisco 12000 routers.

Cisco Element Manager System Support

With Cisco Info Center 3.5, the MTTrapd Info Mediator supports Cisco Element Manager System 3.2, including events sent in SNMP messages from element managers that support the Northbound Event Interface (NEI).

Generic SNMP Support

Cisco Info Center 3.5 supports monitoring a varied set of hardware devices and software applications through the MTTrapd Info Mediator: The supported MIBS are documented in the New Features and Enhancements. The best practices rules from Micromuse have also been included in Cisco Info Center for customer's convenience.However, they have not been tested by Cisco and will not be supported.

Note The MTTrapd Info Mediator also includes enhancement and fixes recommended by the CERT team.

NMS and Cisco Info-Center Component Specific Considerations

This section presents considerations that you should be aware of when installing specific Cisco Info Center components or NSM applications that work with Cisco Info Center.

CNS Notification Engine (CNS-NOTE)

Note the following information regarding the use of Cisco Info Center with the CNS-NOTE product.

SNMP Version

If you plan to use the CNS-NOTE product to monitor syslog events from IOS devices, then CNS-NOTE must be installed and running. When you start CNS-NOTE, specify SNMP v1 in the startup command.

Cisco Info Center CNS-NOTE Repeat Count Attribute

Note the following differences in how CNS-NOTE and Cisco Info Center process repeat count information.

The CNS-NOTE product classifies events based on their frequency of occurrence and the pattern of occurrence, within time intervals that are specified by a set of timers. It then compares events on this basis and sometimes creates one event for multiple events along with the frequency attribute.

For information on how these timers are set, refer to the "Configuring Timers" section in Chapter 1 of the Cisco CNS Notification Engine Comprehensive Guide, "Overview of the CNS Notification Engine."

When Cisco Info Center receives events from CNS-NOTE, along with the "CNS-NOTE Repeat" Count attribute, these appear in the "CNS-Note3.0" view in the Cisco Info Center event interface.

Cisco Info Center deduplicates instances of the same event received from CNS-NOTE during event processing, and each time an event is deduplicated the "count" attribute is incremented. However, when this occurs, only the latest value of the "CNS-NOTE Frequency" attribute is retained by Cisco Info Center; therefore any previous values for the event frequency attribute are lost.

Start CNS-NOTE Before Starting Cisco Info Center Components

If you are using Cisco Info Center with the CNS-NOTE product, make sure to start CNS-NOTE before starting the Cisco Info Center components.

Use of the CNS Info Mediator with CNS-NOTE

Note the points itemized in the following section— "CNS Info Mediator"—if you are using the CNS Info Mediator with CNS-NOTE.

CNS Info Mediator

•

The CNS or Tib/Rendezvous daemon (rvd or rvrd) must be installed and running.

•

The CNS Info Mediator must run on the same machine as the CNS-NOTE product or the CNS Performance Engine product, or must run on a host that has the TIB/Rendezvous daemon installed on it.

•

The Tibco Info Mediator (nco_p_tibco) must run on the same machine as the CNS-NOTE product or the CNS Performance Engine product, or must run on a host that has the TIB/Rendezvous daemon installed on it.

•

When prompted for the notifier name used with the CNS Info Mediator, enter the notifier name for which the CNS-NOTE application or the CNS Performance Engine application is configured, for example, cisco.mgmt.ssng or cisco.mgmt.das.

ISM

If you plan to monitor Internet service events, it is recommended to install ISM 2.1 on separate host to monitor the Internet services.

Note The ISM product is a separate product from Cisco Info Center, and is orderable from the Cisco Info Center pricelist. ISM is not provided on the Cisco Info Center distribution media.

Two special utilities have been developed to further integrate the Internet Service Monitors into Cisco Info Center. The two utilities are:

Both of these utilities can be launched from the $OMNIHOME/bin directory. There are two cases for the installation of the ISM utilities. You might have the ISMs running on the same host as the Cisco Info Center Info Server, or you might have the ISMs running on a standalone host that forwards events to the Cisco Info Center Info Server.

•

If you are running the ISMs on the same host as the InfoServer, then the ISM utilities will be automatically installed with the InfoServer, and you can just use them.

If you are running the ISMs on a stand-alone host, then it will be necessary to install the ISM utilities on the stand-alone host. A separate installation script is included on the Cisco Info Center CDROM for this purpose.

Follow the prompts displayed by the installation script to complete the installation.

Properties

•

If the rules and properties need to be customized, the variable name '$OMNIHOME' cannot be used in them. The actual and the complete path needs to be specified in them.

Generic SNMP

•

All of the Info Mediators used with Cisco Info Center bind to SNMP port 162. If you want to install them on the same host, you must configure them to use different SNMP ports.

HP-OV

•

For HP OpenView installation requirements and procedures, please refer to the HP OpenView Network Node Manager Products, Installation Guide

•

The rules for the NNM Info Mediators are tuned to receive the Cisco 1000 series traps, for the NNM to co-exist with CWM. Here is a CWM limitation: the NNM5 Info Mediator is supported only along with OV 5.01 & CWM 9.2.x, and only on the Solaris 2.6 platform and the NNM6 Info Mediator is supported only along with OV 6.10 & CWM 10.4.10 or 10.5.10 and only on the Solaris 7 platform.

Note 1000 series traps from the eventd in CWM are also supported through the MTTrapd Mediator.

DFM and VHM

•

To monitor devices managed by the Device Fault Manager (DFM) component of CiscoWorks2000 (CW2K), DFM must be installed and configured to send traps to the host that is running the MTTrapd Info Mediator.

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 and Windows NT manual.

•

To monitor devices and software managed by the Voice Health Monitor (VHM) component of CiscoWorks2000, VHM must be installed and configured to send traps to the host that is running the MTTrapd Info Mediator.

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 To monitor events coming in from the Device Fault Manager (DFM) application through Voice Health Monitor (VHM), you must configure both the DFM and the VHM trap notifier to send traps to Cisco Info Center.

MWFM

•

To monitor devices managed by MWFM, MWFM must be installed and configured to send traps to Cisco Info Center.

NEI Support

If you will use Cisco Info Center to monitor Northbound Event Interface (NEI) events from element managers running under the Cisco Element Manager System, then you must install the MTTrapd Info Mediator on one host and also install the Process Control component on the host that is running the Cisco Element Manager System. After you install the process control component on the remote host, you must run the cemf_nei_pa_conf.sh script on the remote host.

For information on running the cemf_nei_pa_conf script, refer to the "Selecting and Configuring Info Mediators" section in Chapter 3 of the Cisco Info Center Installation and Configuration Guide, "Installing and Configuring the Multi-System Architecture."

Syslog Info Mediator

To use the Syslog Info Mediator, the following Solaris 2.6 patches must be installed:

The Syslog Mediator receives Syslog messages from the UNIX syslogd process. There is a bug with this daemon on Sun Solaris 2.5.1 where a burst of events to the syslogd process will overload the buffer for the named pipe /var/adm/nco, which is created by the Syslog Mediator to receive messages from syslogd. It is recommended that Sun patch 103738-07 or higher be applied to any Sun host running the Syslog Mediator to help remedy this problem.

Problems with syslogd on Sun Solaris 2.6 can also occur. When started, the Syslog Mediator sends a HUP signal to the syslogd process to force it to reread its config file, /etc/syslog.conf, and begin forwarding messages to the Syslog Mediator on the named pipe, /var/adm/nco. The syslogd process on 2.6 will not reread the config file unless it has changed. A touch on the syslog.conf file, followed by start of the Syslog Mediator will remedy this. You should apply Sun Patch 106439-02 or higher on any Sun host running the Syslog Mediator to help remedy this problem.

CEMF

•

Eldora gateways that forward events through CMNM forward numerous events to Cisco Info Center that are not deduplicated. Because each of these events are unique, due to the fact that a gateway can have many DSP cards, and because an asynchronous port is created for each card, it is not possible to deduplicate these events.

•

The nco_license licensing utility does not prompt for a license key for the CEMF Info Mediator. To enter a license key for the CEMF Info Mediator, obtain a license key for the Info Mediator. Enter this license key in response to the prompt for a license key for a component that you are not using, such as the ISM component.

CWM

CWM version 9.2.x, 10.4.10, 10.5.10, or CWM 11.0.10 is needed for proper functioning with Cisco Info Center 3.5. To check the existence of the process, issue the command ps -ef | grep <process_name> where <process_name> can be svmain or RtmProxy.

Network names must be unique as they appear in the CWM hosts' svplus/config.sv file or the network.conf file (in case of CWM 10.4.10, 10.5.10, or 11.0.10) as managed by a single Info Server. You can edit these files and restart the CWM hosts to ensure the names are all different.

•

dbaccess must only exist in /usr/users/informix/bin and INFORMIXDIR must be set to /usr/users/informix for the root user.

CiscoView

CiscoView should be installed in the different directories depending on which release of CWM you are running. The following list indicates which directories CiscoView should be installed in for specific CWM releases:

Consult the CiscoView documentation for a detailed description of CiscoView installation.

Informix Database

Service and Network Agents

CWM Version	Installation Directory
9.2.x	/opt/CSCOcv/bin/nmcview
10.4.x	/usr/users/svplus/wancv/bin/cvw
10.5.10, 11.0.10	Web CiscoView needs to be in place along with CWM.

•

The CWM Service and Network Agent should be installed and running. Refer to the Cisco WAN Manager Installation Guide for installation instructions.

•

The CWM SNMP Agent must use default port 8161 for SNMP Trap Registration. The Info Server uses port 8161 to communicate with the Service and Network Agent.

Policy Manager

The Policy Manager component can only be installed on the same host as the Cisco Info Server component. Note the following:

•

In order to run the Policy Manager, you must obtain a license for the Cisco MPLS Solutions Center Application Programming Interface (API) product.

•

The Info Server and Policy Manager must be installed on a Solaris 2.7 or 2.8 platform.

•

Do not install the Policy Manager component on a host that is running Cisco WAN Manager.

–

As the orbixadm user, change directory to the /bin directory under the orbixadm directory (for example, /opt/orbixadm/orbix/Orbix3/bin) and issue this command:

–

as the vpnadm user, change directory to the orbixadm/orbix/Orbix3/bin directory and run this command:

–

If DNS is not active, add the hostnames of Provider Edge (PE) devices that Policy Manager to the /etc/hosts file

Virtual Operator

If you do not select the Info Server component when the Virtual Operator component is selected, the installation utility automatically selects it and installs it.

•

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:

Note For detailed information on Virtual Operator licensing and installation, refer to Chapter 6 of the Cisco Info Center Installation and Configuration Guide, "Installing the Virtual Operator Component."

Webtop

•

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

•

During Webtop installation, you must select the Webtop component and at least one additional Info Server component such as the Info Server component, Info Mediators components, or Desktop component.

•

Webtop uses the Flexlm license server to enable licensing. In order to enable licensing, you must complete these steps:

–

Navigate to the /opt/Omnibus/license/flexlm-7.2/bin directory and run the lmhostid script.

–

Contact Micromuse Technical Support to request a license. You can contact Micromuse in several ways:

Link to the Micromuse support site and complete the license request form at the following URL:

If you do not have a login to the Micromuse support site, please contact the Cisco Technical Assistance Center at 800 553-2447 or at the following email address:

Send an email to licensing@micromuse.com to request a license. Include the host ID output by the lmhostid script in the email.

–

Micromuse will provide you with a license.dat file that looks similar to the following:

–

Edit this file and replace hostname with the host ID that Micromuse provides you.

–

Copy the license.dat file to the /opt/Omnibus/license/license.dat director.

–

When you are prompted for the location of the license file, enter the path the directory where you copied the license file.

Note You can also run Webtop and use a Flexlm license server that is running on another host. For information on how to do this, refer to the "Configuring Webtop to Use an Existing License Server" section in Chapter 5 of the Cisco Info Center Installation and Configuration Guide, "Installing the Webtop Component."

–

For more detailed instructions on installing Webtop, refer to Chapter 5 of the Cisco Info Center Installation and Configuration Guide, "Installing the Webtop Component."

Automations

•

In order to use the administrator interface to implement automations, an infoadmin user must exist. Do not delete this user ID and do not change the password for this user ID.

•

The Num Lock key must be off for the right mouse button to start the Automation Pop-up menu.

•

12-hour-Cleared and 24-hour-Deleted automation is disabled by default. Users must enable it. Consult the Cisco Info Center documents for a detailed description.

•

No automation to handle a change of IP address. Currently, if a node has an IP address already configured, changing the IP address on the node will not trigger an update to Info Server. This means that all incoming events from that node still carry an old NEAddress. Users can create tools to execute nco_sql to run an update on a node if that node's IP address is changed.

•

Object Deletion automation clears any events of the same ObjectType and updates the ObjectStatus and Severity as "Cleared". This is as designed. These "Cleared" traps will then be physically deleted by 12-hour-Cleared automation (if this automation is enabled).

Note The "Resolve NEName or Address" automation updates the NEName, using NEAddress or updates the NEAddress using the NEName, when only one of the two fields—NEName or NEAddress— is available. This automation is turned off by default, since it will cause a significant performance penalty. Users who concerned about performance are advised not to turn on this automation.

Do Not Modify the Default Automations

Do not modify the default set of Cisco Info Center automations provided with the initial installation. If you want to customize an automation, first rename the automation (make sure not to use a name that is already in use), then implement your changes. Alternatively, you can turn off the default automations, copy them to a new name, edit them, and then save them under a new name.

Filters

•

Unique Class numbers have been assigned to each event category. The filters are based on that category

Tools

Note For the Ping, Telnet, and Traceroute tools, NEAddress is used by default. These automations will not work if NEAddress is not populated with a value.

•

Launching CiscoView tool from CW2K or CWM 10.4.10, 10.5.10, or 11.0.10 requires specific versions of browsers. Please refer to the respective CW2K or CWM documentation on the browser requirements.

•

Cisco Info Center tools that initiate remote scripts rely on the nco_pa process. If this process dies or cannot get a connection, none of the tools will work. The status of the nco_pa process is logged in the /opt/Omnibus/log/NCO_PA.log file.

•

Voice and data connections. Only AdminGUI, CiscoView, and get_config are associated with voice and data endpoint traps in the 1.x release. Tools such as RTC and add/delete loop back are not available.

•

dsx3RcvEXZCounter in the RTC tool gives a "does not exist" error message. The MGX dsx3 counter does not work on the SRM card but works on the BNM card.

•

There must be connectivity to the CWM host for all CWM tools to work. All nodes should be reachable from the CWM machine through IP-relay. The CWM gateway node should be LAN connected.

Note If you are deleting a tool prior to re-inserting it, then when you delete the tool, you must delete the menu on which the tool occurs, the menu item, and the tool before re-inserting the tool.

Modifying Info Server Parameters When Large Numbers of Events Are Handled

When an large number of events is handled by a single Info Server, the startup parameters for the Info Server may need to be changed. Messages in the log files for the process control agent running the Info Server or the log file for the Info Server might indicate that a serious performance problem exists.

If you see messages in the <NCO.PA>.log file for the process agent running the Info Server or in the <OMNIHOME>/log/<INFOSERVER_NAME>.log file for the Info Server that indicate that the queue for the Info Server is full, you can try restarting the Info Server with an increased queue size (using the -queue command line object for the nco_objserv command).

If you see similar messages regarding the stack size used by the Info Server, you may also need to change the startup parameters or properties.

Note Cisco strongly recommends that you contact technical support for advice on changing the queue size, stack size, or other Info Server startup parameters.

The Cisco Info Center Administration Guide (Chapter 1, "Changing the Queue Size") describes how to change the queue size.

In some instances, if the Info Server is processing a very large number of events (25,000 events or more), display errors may occur. To remedy this problem, shut down the Info Server components and then rerun the Info Center configuration program (nco_config). When prompted to use the existing configuration, enter n. This will cause the database to be cleaned of existing events.

Notes Regarding Processing Rules

The rules for the NNM mediators are tuned to receive the Cisco 1000 series traps, for the NNM to co-exist with CWM. Here is a CWM limitation: the NNM5 Info Mediator is supported only with OpenView 5.01 and CWM 9.2.x, and only on the Solaris 2.6 platform and the nnm6 Info Mediator is supported only along with OV 6.10 & CWM 10.4.10 or 10.5.10 and only on the Solaris 7 platform. These traps are also supported through the MTTrapd mediator, for CWM installations without HP-OV.

Installation Notes

This section contains information that you should be aware of when installing Cisco Info Center 3.5. For complete installation instructions, refer to the Cisco Info Center Installation and Configuration manual.

Cisco Info Center 3.5 Installation Packages

Table 3 lists the software packages created by the Cisco Info Center 3.5 installation process.

Table 3 Cisco Info Center 3.5 Installation Packages
Release 3.5 Package Name	Description
CICcom	Info Center 3.5 Foundation Component
CICdsk	Info Center 3.5 Desktop Component
CICgtw	Info Center 3.5 Gateway Component
CIClic	Info Center 3.5 License Component
CICmed	Info Center 3.5 Mediator Component
CICpad	Info Center 3.5 PAD Configuration Component
CICpmr	Info Center 3.5 Policy Manager Component
CICsrv	Info Center 3.5 Server Component
CICutl	Info Center 3.5 Utilities Foundations Component
CICvo	Info Center 3.5 Virtual Operator Component
CICweb	Info Center 3.5 Webtop Component

Prerequisites for CTM Info Mediator Installation

If you have purchased a license for the CTM Info Mediator, then before you can use the CTM Info Mediator to monitor Cisco Transport Manager (CTM) events, you must complete these steps to create an OSS client profile for Cisco Info Center:

For information on installing CTM, refer to the Cisco Transport Manager 3.2 Installation Guide.

On the CTM Server tree, click the GW icon for the GateWay/TL1 Service property sheet.

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

•

OSS Profile Name—Enter user name (This must be used in nco_config also).

•

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

Step 3

From the machine that is running the Info Server, enter the following command to test connectivity to the CTM machine:

Step 4

Install Cisco Info Center 3.5 and install the CTM Info Mediator either on the CTM host or a remote host.

For information on running the Cisco Info Center installation program, see the "Running the Cisco Info Center 3.5 Installation Program" section. For information on installing and configuring the CTM Info Mediator, refer to the Cisco Info Center Installation and Configuration manual.

Note The optical devices must already be in communication with CTM through TL1.

Running the Cisco Info Center 3.5 Installation Program

Step 6

Follow the instructions in the prompts displayed by the installation program.

Refer to the Cisco Info Center Installation and Configuration manual for complete instructions.

•

If you are installing Cisco Info Center in the multi-system architecture, refer to Chapter 3, "Installing and Configuring the Multi-System Architecture."

•

If you are installing Cisco Info Center in a single system architecture, refer to Chapter 4, "Installing and Configuring the Single-System Architecture."

•

If you are installing the Webtop component, refer to Chapter 5, "Installing the Webtop Component."

•

If you are installing the Virtual Operator component, refer to Chapter 6, "Installing the Virtual Operator Component."

•

If you are installing the Policy Manager component, refer to Chapter 8, "Installing Policy Manager."

•

If you are installing Info Center and want to use the Info Mediator failover feature or the Info Server failover feature, select the desired failover feature(s) when prompted during installation. For information on configuring failover, refer to Chapter 7, "Configuring Failover."

Note The default Cisco Info Center desktop administration user id is "root" and the password is"" (no password). The user ID and password are also set this way if you upgrade to Cisco Info Center 3.5 from a previous release.

Note If started from the CD volume Manager, the install shell does not exit after the installation is complete. The user is required to close the shell or the window.

Obtaining Licenses

Change directory to the /opt/Omnibus/polmgr/install directory and run the nci_license script.

–

Link to the Micromuse support site and complete the license request form at the following URL:

If you do not have a login to the Micromuse support site, please contact the Cisco Technical Assistance Center at 800 553-2447 or at the following email address:

–

Call the support number for technical support and licensing issues (1-800-NET-COOL).

If you exit the licensing utility before obtaining the license keys, rerun nci_license to install the licenses after you have received them.

When nci_license prompts you for licensing information, enter the following feature codes and the associated license keys (sent to you by Micromuse):

Step 2

If you are installing the Webtop product, refer to the "Webtop" section for instructions on licensing.

Change directory to the /opt/Omnibus/install directory and run the nco_license script.

–

Link to the Micromuse support site and complete the license request form at the following URL:

If you do not have a login to the Micromuse support site, please contact the Cisco Technical Assistance Center at 800 553-2447 or at the following email address:

–

Call the support number for technical support and licensing issues (1-800-NET-COOL).

If you exit the licensing utility before obtaining the license keys, rerun nco_license to install the licenses after you have received them.

When nco_license prompts you for the license keys, enter the license keys provided by Micromuse.

This prompt is for the resolution license. The resolution license allows you to run 20 resolution scripts simultaneously

–

Enter the license key for the Info Server in response to the prompt for the Object Server license key.

–

Enter the license key for Admin Desktop(s) in response to the prompt for Desktop keys.

–

Enter the license keys for the RTTtrapd, MTTrapd, CEMF, and Tibco Info Mediators in response to the Key for Probe Band C prompt.

–

Enter the license key for the Syslog Info Mediator in response to the prompt for Probe Band E.

–

Enter the license key for the CTM Info Mediator in response to the prompt for the TSM Band key.

–

Enter the license keys for any additional components you may have purchased in response to the appropriate prompts.

For additional information on license bands, go to the Micromuse License Request page at the following URL and select the link labelled "Please see here for Probe/Band Info":

http://194.131.185.78/licrequest/licrequest.cgi?ri=128.107.253.41&ru=90005005&rf=support&rh=EAAC2E64BF6ABA723A2B82191CB46869

If you do not have a login for the Micromuse Support site, contact the Cisco TAC.

Starting the License Server

Step 1

Issue the following commands to start the license serve (in the C-shell environment):

Step 2

Issue the following command to make sure the license server is running

Note When you start Cisco Info Center components on the license server host using the /etc/init.d/nco start command, the license server is started, along with any other components that are installed on the host. Also, if you specified automatic startup during the Cisco Info Center configuration process, the license server is started automatically if installed on the current host. The Policy Manager license several is started on either the local host or a remote host.

Setting Licensing Information on Info Center Component Hosts

If you have installed additional Info Desktop components on one or more separate hosts, then you need to "point" the remote Info Desktop components to the license server component on the host where licensing is installed.

To enable the licenses on Cisco Info Center component hosts where the Licensing component is not installed, enter one of the following commands on each host:

Note To ensure that this variable is set when hosts that require licensing are started, add these commands to the /.profile or /.cshrc file on each host.

Note If you stop the Info Center components and reboot the host, the NCO_ELMHOST variable will be reset. Before attempting to restart the components, make sure that you reset the NCO_ELMHOST variable to point to a host that is running a license server (setenv NCO_ELMHOST @license_host).

Starting Cisco Info Center Processes

Note If you configured automatic startup during the Cisco Info Center configuration process, then the Cisco Info Center processes start automatically when the host is started.

To start the processes for all of the Cisco Info Center components configured on a host:

Step 3

Issue the command /usr/bin/ps -ef | grep nco to make sure the processes shown in Table 4 are running, if installed.

Table 4 Cisco Info Center Processes
Release 3.5 Service	Process Name
Object Server	/opt/Omnibus/bin/solaris2/nco_objserv
Process Control	/opt/Omnibus/bin/solaris2/nco_pad
CWM/CNS-NOTE Mediator	/opt/Omnibus/probes/solaris2/nco_p_cwm /opt/Omnibus/probes/solaris2/nco_p_ssng
HPOV Info Mediator	/opt/Omnibus/probes/solaris2/nco_p_nnmx (where x indicates the version of the HPOV Info Mediator)
Syslog Info Mediator	/opt/Omnibus/probes/solaris2/nco_p_syslog
CTM Info Mediator	/opt/Omnibus/probes/solaris2/nco_t_ctm
CEMF Info Mediator	/opt/Omnibus/probes/nco_p_cemf
Tibco Info Mediator	/opt/Omnibus/probes/nco_p_tibco
DFM/MWFM/Generic SNMP /CEMF /NEI	/opt/Omnibus/probes/solaris2/nco_p_mttrapd

Step 4

If you have installed the Policy Manager component on this host, issue the following command to make sure that the Policy Manager processes shown in Table 5 are running:

Starting Cisco Info Center in Installations with CNS-NOTE or CWM

If you are using CNS-NOTE or CWM as an event source for Cisco Info Center, then the Cisco Info Center processes should be started after the CNS-NOTE or CWM processes are started, to avoid connection monitoring alarms.

Table 5 Policy Manager Processes
Release 3.5 Service	Process Name
Server process for Policy Manager	nci_server
License Server Process for Policy Manager	nci_licserv

When you run the CNS-NOTE release 3.0 setup utility to configure CNS-NOTE for use with Cisco Info Center, make the following selections:

•

When prompted to publish events using the CNS Notification Release 2.0 MIB for Syslog messages, enter n.

Stopping the Cisco Info Center Processes

Step 2

Stop the Cisco Info Center Desktop by selecting Exit from the Conductor.

Step 3

Issue the following commands to stop the processes for all Cisco Info Center components configured on the host:

Step 4

To identify all current Cisco Info Center processes, issue the following commands:

Step 5

Otherwise, complete these steps to stop any nco, cic, or pol processes that are still running:

Issue a kill <pid> command to stop any nco, cic, or pol processes that are running.

Repeat step 3 above to verify that no nco, cic, or nci processes are running.

If any of these processes are running, issue a kill -3 <pid> command to stop them.

Check again to see whether any nco, cic, or pol processes are running.

If any of these processes are running, issue a to use kill -9 <pid> to stop any remaining nco, cic, or pol processes.

Step 6

If the Webtop component is installed on the host, make sure that the following processes are not running:

Step 7

If the Virtual operator component is installed on the host, make sure that the following process is not running:

Upgrade Notes

Note the following points before upgrading to Cisco Info Center 3.5 from a previous release.

–

If you have customized any of the default Cisco Info Center automations, rename the automations before upgrading.

•

For detailed upgrade instructions, refer to Chapter 9 of the Cisco Info Center Installation and Configuration Guide, "Upgrading to Cisco Info Center 3.5."

•

The upgrade utility will prompt you to add any new release 3.5 components that you might want to install.

Severity Level Assignments

Cisco Info Center maps MGX alarms to a severity level according to the value of the MGX SNMP varbind: moduleTrapAlarmSeverity. Table 6 indicates the mapping details that are used.

Severity Mappings for Cisco to NetCool Severity Levels

Table 6 MGX Severity Level Mapping
MGX:	Cisco Info Center Severity Level
minor (1)	Minor (3—Yellow)
major (2)	Major (4—Mustard)
dontCare (3)	Warning (2—SkyBlue)
N/A	Indeterminate (—Purple)

Table 7 indicates the severity level mapping between Cisco severity levels and NetCool severity levels. 0 indicates a clear event.

Table 7 Cisco Error Message Severity Levels Mapped to Info Center Severity
Cisco Defined Level	Cisco Description	Info Center Severity
0—emergency	System unusable	5—Critical
1—alert	Immediate action needed	5—Critical
2—critical	Critical condition	4—Major
3—error	Error condition	3—Minor
4—warning	Warning condition	2—Warning
5— notification	Normal, but significant, condition	2—Warning
6—informational	Informational message only	1—Indeterminate
7—debugging	Appears during debugging only	1—Indeterminate

Severity Mappings for IOS Syslog Messages to Cisco Info Center Event Severity Levels

Cisco IOS Syslog messages have eight severity levels. In contrast, Cisco Info Center events have five possible severity levels. Table 8 indicates the mapping of IOS severity levels to Cisco Info Center severity levels.

Table 8 Cisco IOS to Cisco Info Center Severity Level Mappings
IOS Severity	Cisco Info Center Severity	Description
0—Emergency	5—Critical	System unusable
1—Alert	5—Critical	Immediate action needed
2—Critical	5—Critical	Immediate action needed
3—Error	4—Major	Critical condition
4—Warning	3—Minor	Error condition
5—Notification	2—Warning	Warning condition
6—Informational	2—Warning	Warning condition
7—Debugging	1—Indeterminate	Appears during debugging only
8—Undefined	1—Indeterminate	Undefined

Severity Mappings for TL1 to Cisco Info Center Event Severity Levels

Table 9 shows the mapping of TL1 alarm codes received through Cisco Transport Manager to Cisco Info Center severity levels. The default severity is 1. The severity of the generic TL1 messages is indicated by the AlarmCode, which is mapped to the standard Cisco Info Center severity levels ranging from 0—5.

Table 9 TL1 AlarmCode—Severity Mapping
$AlarmCode	Description	Cisco Info Center Severity
M	Response message (Heartbeat/Resync)	1—Indeterminate
A	Non-alarm event	2—Warning
*	Minor alarm	3—Minor
**	Major alarm	4—Major
C	Critical alarm	5—Critical

Note The above severity will be overridden by the specific severity of that particular alarm, which indicated by the notification codes in the alarm.

Table 10 indicates the mapping of TL1 Notification Codes to Cisco Info Center Severity Levels.

Caveats

Table 10 NotificationCode—Severity Mapping
NOTIF_CODE Values	Description	Cisco Info Center Severity
CL	The condition causing the alarm has Cleared.	0—Clear
CR	A Critical alarm.	5—Critical
MJ	A Major alarm.	4—Major
MN	A Minor alarm.	3—Minor
NA	The condition is Not Alarmed.	1—Indeterminate
NR	The alarm is not reported.	1—Indeterminate

•

CSCea78067. Alert details are turned on by default for all CNS-NOTE events (from either SNMP or the CNS Info Mediator). This can result in performance degradation.

To turn alert details for CNS-NOTE off to alleviate this problem, complete these steps:

–

Enter a pound sign (#) to comment out the line that reads details ($*), which is the first line in the rules entries.

This default setting in the ssng30.r file will be changed in a forthcoming patch release.

•

CSCea71493. On Solaris 8, if the system administrator has set the LANG variable in the startup script for the host, then during Virtual Operator installation or when the user attempts to start an Info Desktop, a Sybase error occurs and the installation fails. The workaround is to unset the LANG variable (unsetenv LANG) to a null value and then retry the installation or restart the Info Server components.

•

CSCea78711. After initial installation of the Cisco Info Sever, the user name for the Info Desktop component defaults to "root" and the password is blank. This creates a possible security problem. The workaround is to reset the password using the Info Desktop User Configuration tool.

•

CSCdy55972. When the Info Server components are stopped and the host is brought down, the NCO_ELMHOST environment variable is reset and the license server is no longer found. The solution to this problem is to reset the NCO_ELMHOST environment variable to point to the correct license server host before restarting the Info Server components (setenv NCO_ELMHOST @license_host, where license_host is the hostname of the host running the license server.)

•

CSCea60280. When release 3.0.1 is upgraded to release 3.5 the Info Server does not start when the /etc/inti.d nco start command is issued or the automatic startup script runs. The workaround is to start the Info Server using the /opt/Omnibus/bin/nco_pad command. This will be fixed in a future release.

•

CSCea57916. If the default port for the MTTrapd Info Mediator (port 162) is in use by another application such as CEMF or HP OpenView, then MTTrapd comes up, but no events are received. This problem will be fixed in a future release.

•

CSCea66582. The Extended Traceroute and Extended Ping tools in the Webtop application do not behave the same as in the UNIX Info Desktop. The "To Address" and "From Address" fields must have information entered for the Webtop version, but in the Info Desktop version, only the "Remote Router" address is required. This will be fixed in a future release.

•

CSCea70892. If you install the Webtop component and do not select at least one other core component (i.e., the Info Server component, the Desktop component, or the Info Mediators component) configuration with the nco_config configuration utility fails. The workaround is to install at least one other component (the Info Server component, the Desktop component, or the Info Mediators component) and also the Process Control component.

•

CSCdv29719.CWM recommends that the RetryConnectionCount be set to 0, so that the Rttrapd Info Mediator continuously retries to re-register with the RTM proxy. With this value set and retry count for the mediator also set to 0 by default, Rttrapd will indefinitely try to re-register with the RTM proxy, if the RTM proxy is not running, when the Info-Mediator starts.

•

CSCdw92164. If you want to add Policy Manager to an existing installation of Cisco Info Center with an Info Server installed, you must perform a fresh installation (re-install all of the components from a 3.5 release distribution).

•

CSCdw39708. When Cisco Info Center loses connectivity with any Info Mediator, the Cisco Info Center event list will fill up with a huge number of instances of the same event. This problem can be alleviated by deleting the duplicate events after they arrive, but if the situation is not monitored, so many events will be generated that the Cisco Info Center application will eventually go down.

•

CSCdw64887. Ignore extract errors and warnings in log files from the CNS Info Mediator (nco_p_tibco) stating "Warning: New value for field Summary truncated to 255 characters. They do not represent a problem condition. The size of the log file can be limited by setting the MaxLogFileSize property in the /opt/Omnibus/probes/solaris2/tibco.props file.

•

CSCdy63224. If the failover feature is configured, then if the Licensing component is installed on the same host as the Info Server and you attempt to stop the Info Server using the /etc/init.d/nco stop command, the Event List displayed by Info Desktops connected to the Info server goes down. To prevent this from occurring, use the $OMNIHOME/bin/nco_stop command to stop the Info Server.

•

CSCdy73360. If the failover feature is configured, then if the primary Info Server's host is rebooted, the Info Desktop is not available on the backup Info Server (if installed). This occurs only when the Info Desktops are configured to point to the Logical Info Server instead of either the primary or backup Info Server. However, when the primary Info Server comes up again, the Info Desktop comes up again on the backup Info server. To prevent this from occurring, restart the Info Desktop on the backup Info Server host and point it to the backup Info Server (INFOSERV_B). The desktop will then function correctly.

•

CSCdy50987. When a primary Info Server and a backup Info Server are receiving events from the MT Trapd Info Mediator and the primary Info Server is stopped, error events on the backup Info Server are not cleared if the timestamp on both Info Servers is not the same. The workaround for this problem is to make sure that the system time is synchronized on the primary and backup Info Servers.

Table Of Contents