|
|
These release notes provide information about the Cisco Info Center (CIC) version 2.0 release.
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.
This information can then be:
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 compliments 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.
The following documents are available on the Cisco Documentation CD-ROM and are companion documents to this document:
The following list of documents contains additional information which may help you more fully understand the material described in this manual:
Table 1 shows the different ways you can distribute the CIC components to monitor networks that include different types of hardware devices. Each row in the table indicates the type of network management software and managed devices, how the Info Center and Info Mediator components are distributed, and the total number of hosts required.
| Management Software and Managed Devices | Info Server | Info Mediator | Total # of Hosts |
|---|---|---|---|
CWM 9.2x running on Solaris 2.6 host BPX, MGX, IGX, IPX RPM, 3810 MPLS VPN Solution (multi-system architecture) | Info Server component and Policy Manager component running on a Solaris 2.7 or 2.6 host | RTtrapd Info Mediator component running on CWM host (Solaris 2.6) Additional host (Solaris 2.7 or Solaris 2.6) running the RTTrapd Info Mediator and the STG component to monitor IOS devices | 4 hosts CIC - 1 server, plus1 Info Mediator client CWM - 1 host MPLS VPN Solution 1.1, Solaris 2.6 - 1 host |
CWM 9.2x running on Solaris 2.6 host BPX, MGX, IGX, IPX (multi-system architecture) | Info Server component running on Solaris 2.7 or 2.6 | RTtrapd Info Mediator running on the CWM host (Solaris 2.6) | 2 hosts CIC - 1 host CWM - 1 host |
CWM 9.2x running on Solaris 2.6 host BPX, MGX, IGX, IPX RPM and Cisco 3810 devices (multi- system architecture) | Info Server component running on Solaris 2.7 or 2.6 | RTtrapd Info Mediator running on the CWM host (Solaris 2.6) | 2 hosts CIC -1 server CWM - 1 server |
CWM 9.2x running on Solaris 2.6 host BPX, MGX, IGX, IPX RPM and Cisco 3810 devices (multi-system architecture with separate STG host) | Info Server running on Solaris 2.6 or 2.7 | RTTrapd Info Mediator on CWM host in the Sol 2.6 CWM host (+0) STG component and RTtrapd Info Mediator running on an additional host (Solaris 2.6 or 2.7) to monitor IOS devices | 3 hosts CIC - 1 server, 1 mediator client CWM - 1 server |
Standalone IOS Devices (single- system architecture) | Info Server component running on Solaris 2.7 or 2.6 | STG component and RTTrapd Info Mediator running on same host as Info Server component (Solaris 2.7 or 2.6) | 1 host CIC - 1 host |
Standalone IOS Devices (multi-system architecture)
| Info Server component running on Solaris 2.7 or 2.6 | STG component and RTTrapd Info Mediator running on an additional Solaris 2.7 or 2.6 | 2 hosts CIC - 1 host STG - 1 host |
Standalone IOS Devices
MPLS VPN Solution (single-system architecture)
| Info Server component and Policy Manager component running on one Solaris 2.7 or 2.6 host | STG component and RTtrapd Info Mediator running on same host as Info Server and Policy Manager components | 2 hosts CIC - 1 server MPLS VPN 1.1 Solution Sol 2.6 - 1 server
|
Standalone IOS Devices
MPLS VPN Solution (multi-system architecture) | Info Server component and Policy Manager component running on one Solaris 2.7 or 2.6 host | STG component and RTtrapd Info Mediator running on an additional host)
| 3 hosts CIC - 1 server, 1 Mediator client MPLS VPN 1.1 Solution Sol 2.6- 1 host |
Release 2.0 includes the following new features and enhancements:
Table 2 lists the software packages created by the CIC 2.0 installation process.
The Cisco Info Center 2.0 release operates with SV+ 9.0, 9.1, CWM 9.2.03-9.2.08, IPX 9.1, BPX/IGX release 9.0, 9.1, and 9.2, as well as MGX 8220 release 4.0, 4.1, and 5.0, MGX 8850 1.1.23, and IOS 12.05 for all supported features. CiscoView 4.2 and HP Network Node Manager 5.01 are required for OpenView and Element support.
 |
Note The CIC Info Server components must run on the Solaris 2.7 platform, while the CIC Mediator components can run on both Solaris 2.51 (SV+ 9.1) or 2.6 (CWM 9.2) platforms. |
Table 3 presents a platform compatibility matrix for CIC 2.0.
| CIC | CWM (SV+) | HPOV | SWSW | MGX 8220 | MGX 8850 | IOS | Solaris |
|---|---|---|---|---|---|---|---|
2.0 | 9.0 | 4.01 | 9.0 | 4.0 | na |
| 2.5.1 |
2.0 | 9.1 | 5.01 | 9.0, 9.1 | 4.0, 4.1 | na |
| 2.5.1 |
2.0 | 9.2.03-9.2.08 (Sol 2.6 only) | 5.01 (Stand- | 9.0,9.1, 9.2 | 4.0, 4.1, 5.0 | 1.1.23 | 12.0.5 | 2.6/2.7 (CIC Mediators only) 2.6/2.7 (CIC Server/Policy Manager) |
Table 4 summarizes the requirements for the single-system architecture.
| Application Type | Machine Type | Size of RAM | Hard Disk Drive | /var/tmp | OS |
|---|---|---|---|---|---|
Info Server + Info Mediator+ STG+ | Ultra60 or higher | 512MB | 350MB | +60MB | Solaris 2.7, 2.6 |
*Additional CWM requirement. Please read the CWM 9.2 Release Notes or Installation Guide.
** Additional requirements for any products running on that desktop.
Table 5 shows the software and firmware versions for the products that are monitored by Cisco Info Center 2.0.
| Platform | Version |
IPX | 9.0, 9.1 |
BPX 8600/IGX8400 | 9.0, 9.1,9.2 |
MGX 8220 | 4.0, 4.1, 5.0 |
MGX 8850 | 1.1.23 |
3810, RPM | 12.0.5 or above |
Advanced DSL Access Multiplexer (ADSLAM) | 6130 (NI-2) 12.05 (DA1) |
DSL Access Multiplexer (DSLAM) | 6260 (NI-2) 12.08DA |
Universal Access Concentrator (UAC) | 6400: NSP 12.05(DB), NRP 12.03(DC) |
In addition, the Sun system must have UNIX/Motif 1.2 or the Common Desktop Environment (CDE) installed.
To obtain licenses for CIC 2.0, complete these steps:
a. Change directory to the /opt/Omnibus/polmgr/install directory and run the nci_license script.
b. The script displays a license code and a function code.
c. Email the Micromuse help desk (support@micromuse.com) and include the license code, function code, and hostname in the email.
d. Micromuse will email you a license key.
Step 2 For all other components, complete the following steps:
a. Issue the following command:
b. Change directory to the /opt/Omnibus/install directory and run the nco_license script.
c. The script displays the server name and a license code.
d. Send an email to support@micromuse.com and include the server name and license code.
e. Micromuse will email you the required license keys.
|
Note If you are unable to contact Micromuse, contact Cisco. |
To obtain NetCool 3.4 baseline patches for CIC 2.0, complete these steps:
http://support.micromuse.com/downloads/34.html
Step 2 Register yourself on the bug fix mail alias to get bug fix updates.
Step 3 Download only NetCool 3.4 and Solaris2 patches. Follow the instructions in the CIC 2.0 README files to apply patches to CIC 2.0.
To obtain information on any required patches for Solaris 2.7, go to the following URL:
http://sunsolve.Sun.COM/pub-cgi/show.pl?target=patches/patch-acces
The Policy Manager component can be installed on the same host as the Cisco Info Server component. Note the following:
If you install the Policy Manager component in a multi-system architecture, note the following:
1. When you install the system using the OINSTALL installation script that is provided on the CD-ROM, select components 6 and 10 (in that order) to install the Info Server and Policy Manager components. Do not select component 10 first. Also select component 3 (Licensing) and component 4 (Process Control). The following screen capture shows what you should select. If you want to install an Admin Desktop, you can select component 1 (Desktop).
1. Desktop SELECTED 2. Gateway 3. Licensing SELECTED 4. Process Control SELECTED 5. Mediators 6. InfoServer SELECTED 7. Java Event List 8. Wave 9. Syslog Trap Generator 10. Policy Manager SELECTED
|
Note Make sure you select component 6 and then option 10. Do not select option 10 first. |
2. For the multi-system architecture, select the following components for installation on a separate host machine:
1. Desktop SELECTED2. Gateway 3. Licensing 4. Process Control S SELECTED 5. Mediators SELECTED 6. InfoServer 7. Java Event List 8. Wave 9. Syslog Trap Generator SELECTED 10. Policy Manager
If you are using the single-system architecture, install all of the following components on a single host:
If you want to install an Admin Desktop, you can also select component 1 (Desktop).
The following screen capture shows what you should select.
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
Make sure you perform these additional installation and configuration steps to install the Info Server and Policy Manager.
|
Note This step can be executed in a single-system host or in a multi-system host |
Note the following points if you will install the standalone STG and the RTtrapd Info Mediator:
1. Desktop SELECTED 2. Gateway 3. Licensing SELECTED 4. Process Control SELECTED 5. Mediators SELECTED 6. InfoServer 7. Java Event List 8. Wave 9. Syslog Trap Generator SELECTED 10. Policy Manager
1. On each host where you will install Info Center components (the Info Server and Policy Manager Host, the Mediator and CWM host, and the STG and RTtrapd host) run OINSTALL from the CD-ROM to start the installation process and create the /opt/Omnibus directory.
2. On the Info Server host, start the nco_pad process. If Policy Manager is installed, start the nci_pad process.
3. On each Info Mediator host, start the nco_pad -name SVHOST[123...]_PA process.
4. Cisco recommends you install CIC 2.0 on top of a fresh installation of HPOV 5.01, CWM 9.2.07-9.2.08 with Solaris 2.7 or 2.6. Note that CIC 2.0 can also be installed with HPOV 5.01, SV+ 9.1 with Solaris 2.5.1 but this does not provide support for any CWM 9.2.07-9.2.08 features.
5. To install Info Center, you must be logged in as root, install the software in the /opt/Omnibus directory, and have the environment variable OMNIHOME set to /opt/Omnibus. If no space is available in /opt, you must install CIC in another directory. The installation program will create a link to /opt/Omnibus.
files before other name services as follows:hosts: files dns nis
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:
/opt/Omnibus/bin/nco_pa_shutdown
Step 3 To identify all current CIC Syslog Trap Generator processes, issue the following command:
ps -ef | grep cic
Issue the command /usr/bin/ps -ef | grep nco to make sure none of the following processes are running:
/opt/Omnibus/bin/solaris2/nco_objserv
/opt/Omnibus/probes/solaris2/nco_p_rttrapd
/opt/Omnibus/probes/solaris2/nco_p_nnm5
/opt/Omnibus/bin/solaris2/nco_pad
/opt/Omnibus/probes/solaris2/nco_p_syslog
Step 4 Otherwise, use kill -9 <pid> to stop any nco processes that are still running.
Step 5 To stop all CIC Syslog Trap Generator processes, enter the following commands:
kill <pid of cic_stg_5.7> or <pid of cic_stg_5.6> and
kill <pid of cic_watch_stgd> and
kill <pid of cic_SNMPAgent> and
kill <pid of cic_watch_snmpd> and
kill <pid of cic_RtmProxy> and
kill <pid of cic_watch_rtmd>
Complete these steps to permanently remove all CIC files.
Step 2 To identify all current CIC packages, issue the following command:
pkginfo | grep Info-CenterStep 3 Issue the following command to remove the CIC components:
pkgrm <all current CIC package names>where the names can be all or part of the following: CICcom, CICdsk, CICgtw, CICjel, CIClic, CICmed, CICpad, CICpmr, CICsrv, CICstg, CICutl, or CICwav.
Step 4 Issue the following commands:
rm -rf /.omnibusComplete these steps to start the license server.
Step 2 Issue the following command to make sure the license server is running
/usr/bin/ps -ef | grep elmdTo start the CIC process, complete these steps.
Step 2 Issue the following command to start the default Info Server.
./nco_padStep 3 Issue the following command to start the Info Mediator
./nco_pad -name SVHOST[12345 . . .]_PAIssue the command /usr/bin/ps -ef | grep nco; /usr/bin/ps -ef | grep cic to make sure the processes shown in Table 6 are running, if installed.
| CIC 2.0 Services | Process Name |
|---|---|
Object Server | /opt/Omnibus/bin/solaris2/nco_objserv |
Process Control | /opt/Omnibus/bin/solaris2/nco_pad |
CWM 9.2.04-9.2.08 Mediator | /opt/Omnibus/probes/solaris2/nco_p_rttrapd |
HPOV Mediator | /opt/Omnibus/probes/solaris2/nco_p_nnm5 |
Syslog Mediator | /opt/Omnibus/probes/solaris2/nco_p_syslog |
Syslog Trap Generator (STG) | /opt/Omnibus/stg/bin/cic_SNMPAgent /opt/Omnibus/stg/bin/cic_watch_snmpd |
STG | /opt/Omnibus/stg/bin/cic_RtmProxy -v -L2 /opt/Omnibus/stg/bin/cic_rmtd |
STG | /opt/Omnibus/stg/bin/cic_stg_5.7 -s or /opt/Omnibus/stg/bin/cic_stg_5.6 -s /opt/Omnibus/stg/bin/cic_watch-stgd |
Third Party Mediators (other than the nco_p_rttrapd, nco_p_syslog, or nco_p_nnm5 Info Mediators) writing to the CIC Server must not leave any of the NEFWVersion, NEAddress, NEModelID, or NetworkName fields empty or set the NEType field to 999 when the Manager field is "NNM" or "SV+". This will cause the CIC Automation process to enter an infinite loop to query the CWM database for the missing values. In this case, the third party's Mediator rules must be modified to populate these fields with something---at least "N/A" or "unknown"--- or better yet, to set the @Manager field for these rules to say something like "IOSTrap@<HostName>" so that the SV+ or NNM is not found.
The following Solaris 2.6 patches must be installed:
|
Note No patch is needed for Solaris 2.7 installation. |
CiscoView should be installed in /opt/CSCOcv and integrated with CWM 9.2.03-9.2.08. Consult the CiscoView documentation for a detailed description.
The CWM Informix Database name should be "stratacom."
The network configuration should include:
<host>@SV+, <host>@NNM5 or <host>@syslog or <host> @ STG
Discrepancies are reported between the severity level assignments of the HPOV 4.1, 5.01 and CIC 1.x.
CIC maps MGX alarms to a severity level according to the value of the MGX SNMP varbind: moduleTrapAlarmSeverity. Table 7 indicates the mapping details that are used.
| MGX: | CIC Severity Level |
|---|---|
minor (1) | Minor (3 - Yellow) |
major (2) | Major (4 - Mustard) |
dontCare (3) | Warning (2 - SkyBlue) |
N/A | Indeterminate - (1 - Purple) |
HPOV maps the MGX alarms to a severity level according to a static file:
/etc/opt/OV/share/conf/C/StrataCom_trapd.conf
Cisco Info Center Release 2.0 works with HP Openview Release 5.01 and 6.01 for Solaris 2.7.
For HP OpenView installation requirements and procedures, please refer to the HP OpenView Network Node Manager Products, Installation Guide
Xnmgraph occasionally displays "no such name" or "wrapped (0->0). Waiting for next" even though the data is available for get as tested by xnmbrowser.
Xnmgraph shows an incremental statistics value that is not consistent with the Text counter display.
Cisco IOS messages are in a specific format:
"FACILITY-SEVERITY-MNEMONIC: Message Text"
For example, "LINEPROTO-5-UPDOWN: Link on Interface eth0 changed state to down".
The SEVERITY field is a number from 0 to 7, with 0 being the most critical. Severity mappings from Cisco Severity to NetCool severities (0-5) are shown in Table 8 below.
By default, the rules file discards any messages set to level "Indeterminate" (which matches Cisco levels 6 and 7). This default can be changed very simply in the rules file.
Each facility has multiple messages associated with it. Many facilities have additional configuration (such as Type 1 and Type 2 settings for generic clears) associated with them, while the majority have no additional configuration past the default. These facilities are still, however, left in the rules file to assist future customer configuration.
Some facilities (especially the CMCC/CIP messages) are preceded with "CARD-SEVERITY-MSG:SLOT" (for example, "CIP-5-MSG:SLOT7"). This information is stored in Info Server fields (the card is stored in Object Type, and the slot in Slot).
The event format is documented in detail in the Cisco IOS message URL shown below.
Table 8 indicates the severity level mapping between Cisco severity levels and NetCool severity levels.
| 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 - | 3 - Minor |
4 - warning | Warning condition | 2 - Warning |
5 - notification | Normal, but significant, condition | 2 - Warning |
6 - informational | Informational message only | 1 - Indeterminate (discarded) |
7 - debugging | Appears during debugging only | 1 - Indeterminate (discarded) |
Cisco IOS Syslog messages have eight severity levels. In contrast, Cisco Info Center events have five possible severity levels. Table 9 indicates the mapping of IOS severity levels to Cisco Info Center severity levels.
| IOS Severity | Cisco Info Center Severity | Description |
|---|---|---|
0 - Emergency | 5 - Critical | System unusable |
1 - Alert | 5 - Critical | Immediate action needed |
2 - Critical | 4 - Major | Critical condition |
3 - Error | 3 - Minor | Error condition |
4 - Warning | 2 - Warning | Warning condition |
5 - Notification | 2 - Warning | Normal but significant condition |
6 - Informational | 1 - Indeterminate | Informational only |
7 - Debugging | 1 - Indeterminate | Appears during debugging only |
The properties file should have the Manager variable set to Syslog@<host> where <host> is the name of the host running the syslog probe. This can also be set in the command line. The install script should be set up to configure this when installing the syslog probe.
Routers should be configured to send logging messages to the host where syslog is running. This can be configured with the logging <IPAddress> command where <IPAddress> is the IP address of the host running the syslog probe.
The /etc/syslog.conf file should be set to forward events to the syslog probe, as documented in the installation manual.
During development of the Cisco version 2.0 release, a new rules file was developed to parse Syslog messages from Cisco IOS devices (mainly routers, but any platform that runs IOS). This rules file is an enhancement of previous rules files that did only limited parsing of Cisco IOS messages.
This rules file was developed using messages from IOS version 12.0. The messages in this version should be a superset of previous software versions, so they should be backward compatible with previous versions of IOS. Please note that IOS devices include ATM line cards on the Catalyst devices. Also, note that IOS messages are mainly platform independent---there are only a small number of facilities that are specific to certain platforms. There is also no way to determine from the messages themselves what hardware platform they came from (unless they are a hardware specific message). Hardware specific message facilities are marked in the table that follows.
The rules file was developed with the following information found on CCO:
The "Table of Contents" of IOS Error messages is at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12supdoc/12sems/index.htm
The structure and format of IOS error messages is at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12supdoc/12sems/emover.htm
For de-duplication (and any other correlation) to work correctly, Syslog messages from a router should all come from the same source IP address. Ideally, this IP address should be resolvable (either through DNS or /etc/hosts) from the machine running the Syslog Mediator. Cisco recommends that routers have a "loopback" interface, and that you assign an address to the loopback interface.
If Syslog messages are set to come from the loopback interface (using the
logging-source interface loopback0 command), the hostname of the router will resolve to the same name. This is necessary, because if not set, the source address of the message will be the router interface of message egress. This may change in a dynamic environment.
If loopback addresses are not used, the command logging-source interface <interface> should still be used, with an interface chosen that is least likely to go down.
Because there is no way to determine from event messages what type of router or switch is sending messages, the following Class and NEType have been assigned to Cisco routers and Catalyst switches in the Rules file:
Class 255, NEType 13---Cisco IOS devices
The Syslog rules file does the following:
1. Determines whether the event is a Cisco IOS message by looking for an event preceded by a "%" and followed by some text, followed by a dash and then a number between 0 and 7.
2. Sets @Agent to "CiscoIOS" and the @Summary to $Details past the "%," and jumps in a switch statement to the "CiscoIOS' section.
3. Extracts the Facility, Severity, Mnemonic, and Message Text. If the message is prepended with slot and card information, this is extracted as well, and the slot is placed in @Slot, while the card type is placed in @ObjectType.
4. By default, the Identifier is set to "Node-> Summary," and the AlertGroup to the Facility.
5. The severity is set from the Cisco Severity, based on Table 8.
6. There is then a long switch statement that performs a switch on the Facility. Most entries are blank, as the default behavior is sufficient, but they are left in the statement for future enhancements.
7. In some of the cases (see Table 9 for information on which have been modified) certain events are discarded (for example, those with BRI for interfaces) and others have generic automations (Type 1 and 2) set.
8. After the switch statement, events that still have severity = 1, "Indeterminate" are discarded, except for those that have Type 2 set.
Table 10 summarizes the variables that are set by the rules file.
| Variable/Setting | Comment |
|---|---|
@Manager = syslog@host | Not set by rules file, should be set in syslog.props. |
@Node = $Token4 | This is the name of the router sending the message. |
@NEAddress = $Token4 | This is only set if $Token4 is an IP address. |
@Agent = "CiscoIOS" | This is the normal setting. |
@AlertGroup = $Facility | This is the facility of the message. |
@Severity = | Set from the Cisco Severity, extracted from message. |
@Summary= | Whole Message, FAC-SEV-MNE: Message Text. |
@Identifier = | @Node à @Summary. This is changed in a few places. |
@AlertKey = | By default, not set. If set, is normally set to interface value. |
@Slot = | Only set if prepended message available. Set to slot number. |
@ObjectType = | Set to the card type (CIP, FEIP, etc). |
The problems fixed since Release 1.1 and 1.2 are presented numerically in the following categories:
CSCdk75702 - Info Server upgrade data file does not match db schema.
CSCdk82108 - Upgrade script sometimes asks for INFOSERVER login/password.
CSCdk82938 - Steps to add additional SV+ hosts to existing system.
CSCdk82942 - Install error generate_lookups.auto-mod not found.
CSCdm50976 - Info Server does not start after the upgrade.
CSCdm50987 - rttrapd process can not be started after the upgrade.
CSCdr10737 - Changing the install directory to a new directory causes installation to abort.
CSCdr10741 - While installing a remote rttrapd, configuration hangs at port number.
CSCdr11333 - Unable to run mplsdev lookup because of improper Perl environment.
CSCdk75388 - Automation not working on node BPX---Deactivating a line.
CSCdk75707 - Registration problem with SV+ 9.1 when InfoServer is restarted.
CSCdk82911 - Generate-lookups.auto script is empty after installation.
CSCdk90055 - Generate auto lookup fails to update NEAddress field.
CSCdk62719 - NEFWVersion field is incorrectly mapped.
CSCdk66546 - Trap #1004 is mapped to various events.
CSCdk66896 - Need to remove NELANAddress field from the CIC View Builder.
CSCdk67871 - Values in SVVersion field should not be hard-coded.
CSCdm38773 - Wrong varbind reference when upping line.
CSCdm39659 - Node status change alarm is not de-duplicated.
CSCdm45908 - Wrong varbind for APS traps.
CSCdp53641 - Incomplete information in summary field for trap 26111.
CSCdk56542 - GetConfig should be disabled for card removal events.
CSCdk75356 - unable to launch GetConfig tool.
CSCdk75461 - Decode Bitmap tool is not available for AXIS traps.
CSCdk77640 - AdminGUI tool not available for deactivating port traps for UFM-U.
CSCdk78310 - All AXIS 50000 series traps are sent twice.
CSCdk82547 - A 3-segment connection endpoints trap disables the Tools menu.
CSCdk82924 - No tools available for 25010 ATM-ATM connection.
CSCdk88613 - Trap #50101 and 50121 Tools are grayed out.
CSCdk89131 - Unable to launch Cisco View for trap# 25010 and 25000.
CSCdm39666 - Real time counter doesn't recognize variables in the MIB.
CSCdm39690 - Tools-GetConfig on added virtual trunk trap missing some information.
CSCdm40595 - Trunk alarm reported with unrecognized trap reason.
CSCdm41680 - Tools menu is grayed out on upping a trunk.
CSCdm45159 - Health monitor trap NEType value not being converted.
CSCdk84544 - BPX 25000 series traps have no menu.
CSCdk57045 - Connection:fr-fr is sent twice.
CSCdk57061 - ATM-FR Connection traps (25010, 25011) missing from Event List.
CSCdk57602 - Test connection on ATM-ATM should be removed.
CSCdk58395 - No 20004 trap during image download.
CSCdk77246 - Data connection trap #25010 is reported twice.
CSCdk77275 - Trap reason 50021 summary still contains MGX name.
CSCdk77498 - Unable to launch StrataView Desktop from Tools menu.
CSCdk77502 - 25000 series trap in association with Axis shelf show as axis instead of bpx.
CSCdk80523 - Voice and data connections are not distinguished.
CSCdk80789 - Network name field does not reflect the change made in config.sv.
CSCdk82084 - Two-segment data connection shows as voice type instead.
CSCdk87102 - NEAddress field not populated for FTC card events.
CSCdm41173 - NEType for MGX8850 is set to MGX8220 instead.
CSCdm41917 - Trap for modifying VSI logical interface missing information from lookup.
CSCdk34634 - Event list, StrataView Plus Desktop, unable to start Reports.
CSCdk58066 - IGX 1000 series ATM events parsed as FR.
CIC 2.0 has been tested with CWM 9.2.07-9.2.08, IPX 9.1, BPX/IGX 9.2 and MGX 8850 1.1.23, MGX 8220 5.0, DSL 6160, 6260 12.05 on a Solaris 2.6/2.7 setup installed with HPOV 5.01. The following are the known issues in this release:
CSCdk92588 - Test Connection/Delay not launching
Trap #: 25010 After a FR-ATM connection is established, a trap is sent indicating ObjectType = connection and Trap #: 25010. Under the Tools menu, the Test Conn and Test Delay features perform no action when they are launched. As compared to SV+ Connection Manager, both tools launch and work just fine on the same connection.
Workaround: Use telnet or CWM's test connection/Delay
CSCdm69450 - SNMP get "Error: snmpget: Agent reported error ...".
This problem does not occur in a similar ATM-ATM connection (25016) using ASI E3 (ifcbpx03, slot 10) card as one the connection end points.
The RTC launches and displays the values just fine.
Workaround: No workaround. When this happens, the underlying agent does not support the RTC MIB. The Tools menu should be greyed out if this happens consistently.
CSCdm40637 - No cleared event for AXIS shelf alarms
Created major AXIS/Feeder alarms by disconnecting access trunks and LAN connectivity axis04 and 05. Received proper failure alerts from their respective routing nodes. Reconnected trunks and LAN access and verified restored through CWM and routing node CLI. Received no "cleared" status for either node. Problem recreated several times. IPX and Popeye feeder alarms are cleared as expected. Need to ensure that the "cleared" event is correctly propagated and displayed.
Workaround: Use routing node's fault alarms to manager shelf disconnection. Pending bug fix from AXIS shelf traps.
CSCdr07301 - No power supply alarm is generated in CIC
A power supply alarm on SVPLUS (version 9.1.07) was received for the nodes (BPX 9.1.07, MGX 4.1.05). But the event is not showing in CIC.
Workaround: No workaround. Pending bug fix from CWM to generator trap 20004.
CSCdr25036 - Event deselected when tool is launched
When a user selects an event and launches a tool, the event is deselected. This is an annoying problem as the user must search through the event list to find the relevant event.
Workaround: When needed, reselect the event element after launching a tool.
CSCdr57741 - STG traps incorrectly parsed into Event List
STG related traps for the physical interface show the interface number incorrectly parsed into the LSAP field in the Event List. This is wrong as there is no logical interface associated with the physical interface.
Workaround: When in doubt, the summary field has a description of the event. Ignore the LSAP field in case it does not make sense.
CSCdr11308 - Invalid Process Agent Name being accepted
When the default process agent name is not accepted by the user, the new name input by the user needs to be validated. For example, if nco_pa is given when such an agent already exists, an error must be returned.
Workaround: User must input a valid PA name in order to start up nco_pa successfully.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0005R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved
Posted: Mon Jun 19 16:06:30 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.