Guest

CiscoWorks Internetwork Performance Monitor

Release Notes for Internetwork Performance Monitor 4.0 on Windows

  • Viewing Options

  • PDF (459.2 KB)
  • Feedback
Release Notes for Internetwork Performance Monitor 4.0 on Windows

Table Of Contents

Release Notes for Internetwork Performance Monitor 4.0 on Windows

New Features

Product Documentation

Related Documentation

Known Problems in IPM 4.0

Resolved Problems in IPM 4.0

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

OpenSSL/Open SSL Project

License Issues


Release Notes for Internetwork Performance Monitor 4.0 on Windows


These Release Notes contain information about new features in Internetwork Performance Monitor (IPM) 4.0 and provide pointers to information on product documentation. They also give details about the known and resolved problems in this release.

These release notes apply to IPM 4.0, running on a Windows platform and include:

New Features

Product Documentation

Related Documentation

Known Problems in IPM 4.0

Resolved Problems in IPM 4.0

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

New Features

This section describes the new features and enhancements in Internetwork Performance Monitor (IPM) 4.0:

New Devices Import from Device and Credential Repository (DCR)

Adhoc Target Devices Addition

Integration with Common Services

One-Step Multiple Collector Creation

Rich Graphs and Improved Reports

Customization of Historical Reports

Overlay Graphs

Lightweight Front End

Support for Latest IP SLA Operations

Customizable Polling Frequency

New Devices Import from Device and Credential Repository (DCR)

IPM 4.0 is completely integrated with CiscoWorks LMS 3.0. You can import devices from DCR either automatically or manually.

To automatically import the devices, set the Automatically Manage Devices from the Credential Repository option on the Application Settings page.

or

To manually import the devices, go to the IPM Devices page and select the required DCR devices.

Adhoc Target Devices Addition

Supports adding adhoc target devices into IPM. The adhoc target devices added are available only in IPM and not in the DCR. Examples: Workstations, PCs, Printers, etc.

Integration with Common Services

IPM 4.0 is fully integrated with Common Services (CS) and will be shipped on CS 3.1 with LMS 3.0. IPM 4.0 supports the following:

DCR—Allows you to import devices from DCR either automatically or manually.

Device Selector—The enhanced Device Selector in IPM 4.0 allows you to select devices, add devices, and perform a simple search on devices.

Daemon Manager—IPM processes are registered with Common Services Daemon Manager. Hence, the IPM processes can be started or stopped using the utilities provided by Common Services.

Setup Center—Allows you to view and modify the purge settings for historical (such as hourly, daily, weekly, and monthly) and audit reports on the Setup Center page.

One-Step Multiple Collector Creation

Supports a single wizard-based approach. This procedure allows you to create multiple collectors. This wizard involves the following steps:

1. Create Collectors—Allows you to specify a source, targets, and operations to create collectors.

2. Select Collectors—Allows you to select the required collectors that were created in the first step.

3. Schedule Collectors—Allows you to schedule the selected collectors.

4. View the Summary of the Collectors—Allows you to view the summary of the collectors that you have created.

Rich Graphs and Improved Reports

The Reports module in IPM 4.0 supports rich fusion Chart graphs and enhanced Historical reports. This module allows you to manage Archived reports, Report jobs, Audit reports, and System reports.

You can customize Historical reports by specifying the report type, granularity, report period, and schedule details.

You can generate system reports, audit reports, minute reports and graphs, and historical reports and graphs.

Customization of Historical Reports

Supports customizing historical reports. These customized reports are generated either Immediate or Scheduled.

Immediate Reports—Generated instantly and are not stored in the Report Archives.

Scheduled Reports—Scheduled to run at the time specified while creating the report jobs. These reports are stored in the archives for future reference.

Overlay Graphs

These graphs allow you to compare the latency of the collectors based on the granularity. You can overlay graphs only for collectors in the Running, Completed, or Stopped status.

Lightweight Front End

Supports LMS UI standards to make IPM compatible with other LMS applications.

Support for Latest IP SLA Operations

Supports RTP, VoIP Gatekeeper Delay, VoIP Call Setup, and ICMP Jitter operations in addition to the existing operations in IPM 2.6.

UDP Jitter additionally supports MOS (Mean Opinion Scores) and ICPIF (Calculated Planning Impairment Factor) features. These features measure the voice quality in the network.

Customizable Polling Frequency

In addition to the existing 60 minutes polling frequency, IPM 4.0 also supports 1, 5, 15, and 30 minutes polling frequencies. It allows you to specify the polling details such as frequency, day, and time while creating collectors. For more information, see the Managing Collectors in IPM chapter in the IPM 4.0 User Guide.

For more details about the New Features in IPM 4.0, see the User Guide for Internetwork Performance Monitor.

Product Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 1 describes the product documentation that is available.

Table 1 Product Documentation

Document Title
Available Formats

Installing and Getting Started with CiscoWorks LAN Management Solution 3.0

Printed document that is included with the product.

On Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

Data Migration Guide for LMS 3.0

PDF on the product DVD and on the documentation CD-ROM.

On Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps2425/prod_installation_guides_list.html

User Guide for Internetwork Performance Monitor 4.0

PDF on the product DVD and on the documentation CD-ROM.

On Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps1008/products_user_guide_list.html

Release Notes for CiscoWorks Internetwork Performance Monitor 4.0 on Windows

PDF on the product DVD and on the documentation CD-ROM.

On Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps1008/prod_release_notes_list.html

Release Notes for CiscoWorks Internetwork Performance Monitor 4.0 on Solaris

PDF on the product DVD and on the documentation CD-ROM.

On Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps1008/prod_release_notes_list.html

Context-sensitive Online help

Select an option from the navigation tree and click Help.

Click the Help button in the dialog box.


Related Documentation


Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates.


Table 2 describes the additional documentation that is available.

Table 2 Related Documentation

Document Title
Available Formats

User Guide for CiscoWorks Common Services 3.1

Describes CiscoWorks Common Service 3.1. It gives an overview of the applications that comprise Common Services 3.1 and provides conceptual information about network management.

This guide also describes common tasks you can accomplish with Common Services. This document is available in the following formats:

PDF on the product CD-ROM.

On Cisco.com at:

http://www.cisco.com/en/US/products/sw/cscowork/ps3996/products_user_guide_list.html


Known Problems in IPM 4.0

This section explains the known problems in IPM 4.0:

Table 3 Known Problems in IPM 4.0

Bug ID
Summary
Explanation

CSCsi42099

After running dbrestoreorig, the scheduled jobs move to the Failed status.

This happens if the existing reports are not cleaned up after running dbrestoreorig.

Owing to this, the reports and the scheduled jobs move to a Failed status on the Historical Reports and Report Job Browser pages.

Workaround

After running the dbRestoreOrig, delete all the files and subdirectories from the following archive folder:

$PX_DATA_DIR/ipm/archives

where $PX_DATA_DIR represents NMSROOT/files.

CSCsh59288

IP SLA probes are not deleted when IPM is uninstalled.

After uninstalling IPM, the IP SLA probes are deleted only from the IPM server but not from source router.

Workaround 1

If you have not the started the uninstallation, delete the collectors from the server using GUI or CLI to proceed.

GUI

1. Go to Internetwork Performance Monitor > Collectors > Collector Management page.

2. Select the collectors and delete.

CLI

Run ipm controlcollector -u userid -p password -delete -coll collectorname.

Workaround 2

If the uninstallation is complete, do the following to delete the IP SLA probes from the source router:

1. Run show ip sla configuration or show rtr configuration command to see the admin index of the collectors.

2. Run no ip sla Admin Index command to delete the collectors.

You can delete only the collectors with ipm| IPM Server name in the Owner field.

CSCsh59293

IP SLA probes are not deleted when a data restore is done.

During the data restore operation in IPM 4.0, the IP SLA probes are not deleted from the source router.

Workaround 1

If you have not the started the uninstallation, delete the collectors from the server using GUI or CLI to proceed.

GUI

1. Go to Internetwork Performance Monitor > Collectors > Collector Management page.

2. Select the collectors and delete.

CLI

Run ipm controlcollector -u userid -p password -delete -coll collectorname.

Workaround 2

If the uninstallation is complete, do the following to delete the IP SLA probes from the source router:

1. Run show ip sla configuration or show rtr configuration command to see the admin index of the collectors.

2. Run no ip sla Admin Index command to delete the collectors.

You can delete only the collectors with ipm| IPM Server name in the Owner field.

CSCsh59299

IP SLA probes are not deleted while running the DbRestoreOrig script on IPM.

To restore the database to the factory settings (default settings), the DbRestoreOrig script is run on IPM.

As a result, the IP SLA probes are deleted only from the IPM server. They are not deleted from the source router.

Workaround 1

If you have not the started the uninstallation, delete the collectors from the server using GUI or CLI to proceed.

GUI

1. Go to Internetwork Performance Monitor > Collectors > Collector Management page.

2. Select the collectors and delete.

CLI

Run ipm controlcollector -u userid -p password -delete -coll collectorname.

Workaround 2

If the uninstallation is complete, do the following to delete the IP SLA probes from the source router:

1. Run show ip sla configuration or show rtr configuration command to see the admin index of the collectors.

2. Run no ip sla Admin Index command to delete the collectors.

You can delete only the collectors with ipm| IPM Server name in the Owner field.

CSCsg62084

The values in the graphs are not plotted properly if more than one parameter has the same value.

If more than one parameter (such as Timeouts, Busies, Drops, VerifyErrors) in a graph has the same value, the values plotted appear as a single line on the graph.

This is because the value of one parameter overwrites the values of other parameters.

As a result, the value of the last parameter overwrites other values.

Workaround

None.

CSCsi58023

Cannot change the database password while upgrading from IPM 2.6 to IPM 4.0.

While upgrading from IPM 2.6 to IPM 4.0, the database password used in IPM 2.6 is automatically applied to IPM 4.0. This database password is applied to IPM 4.0 only if the existing password in IPM 2.6 has at least five characters.

If the database password in IPM 2.6 is less than five characters, an error message appears.

ERROR: Unable to Change password for DSN ipm

ERROR: IPM database password change failed

ERROR: After install you can change the database password

ERROR: by running /opt/CSCOpx/bin/dbpasswd.pl

In this case, the database password for IPM 4.0 is set to the default settings.

Workaround

Enter a minimum of five characters for the database password in IPM 2.6 before the upgrade.

CSCsi35998

Customized Falling Threshold is not set on the source router for a specific combination.

The value specified for Falling Threshold does not take effect, if the operation has the following settings:

Generate Action Event: Never

Action Event Type: None

In this case, the source router is set to the default value, 3000.

Workaround

Use a different combination for Generate Action Event and Action Event Type.

CSCsh98268

Statistical data of PathEcho collectors are not migrated while migrating from IPM 2.6 to IPM 4.0.

When you migrate from IPM 2.6 to IPM 4.0, the collectors and their statistics from IPM 2.6 also get migrated.

If you generate reports for the migrated collectors, the report displays only the statistics that were migrated and not the Availability statistics. This is because the Availability feature is supported only in IPM 4.0.

However, you can view the availability statistics for the migrated collectors from the next polling interval.

Workaround

None.

CSCsd72665

IPM server truncates the original collector name to 15 characters.

Collector names are truncated if they are more than 15 characters, when configured on the source router. This is because the source router does not accept more than 15 characters.


Note This bug is specific to IOS version less than 12.4.


The collector name is truncated if:

You run show ip sla configuration Admin Index command.

Only the first 15 characters of the collector name are displayed.

You configure SNMP trap on the source router.

The trap sent to the trap receiver has only the first 15 characters.

Workaround

None.

CSCsh60910

Backup-restore of same version overwrites the default DNS operation.

During the same version backup-restore, the server IP of the default DNS operation on the restored server is overwritten with the backed up server IP.

For example, a back up taken for server A is restored on server B. After restore, the DNS address of server B is overwritten with the DNS address of server A.

Owing to this, the collectors configured with the default DNS operation in server B are affected.

Workaround 1

After restore, use the DNS server IP available in the backup.

Workaround 2

Use customized DNS operation to create new collectors.

CSCsi85402

PathEcho graph hop list preserved across duration.

PathEcho collectors take different paths to traverse from source to destination.

For example, on January 2007, the collector would have taken two paths, but the same collector on February 2007, would have had three paths to reach the destination.

When you try to generate reports for this collector for the time period January 2007, the report generated shows two paths.

Again, from the same session, if you try to generate reports for the time period February 2007, the report generated still shows two paths instead of three paths.

This is because of launching the report from the same session.

Workaround

Log out and log in.

CSCsi92859

IPM 2.5 back up folder is not migrated to temporary location.

During migration from IPM 2.5 to IPM 4.0, the ipm.env file settings are not migrated. This file in IPM 2.5 contains settings such as SNMP Timeout, SNMP Retry, and NVRAM Enable.

Workaround 1

If migration has not yet started, do the following and then proceed with the migration:

1. From the IPM 4.0 installed machine, open $NMSROOT/MDC/tomcat/webapps/ipm/WEB-INF/classes/com/Cisco/nm/ipmng/classes/properties/common/IPM.properties.

2. Change the values of SNMP_TIMEOUT and SNMP_RETRY to the current values in ipm.env.

3. Change the admin settings of Copy IPSLA configuration to running config to the value set in ipm.env.

Workaround 2

If migration is already complete, do the following:

1. Launch Internetwork Performance Monitor 4.0 > Collector Management > Devices.

2. Select a set of source devices that were present in IPM2.5.

3. Click Edit Device Attributes.

A dialog box appears.

4. Enter the SNMP Timeout and Retry as present in the ipm.env of IPM 2.5.

5. Click Apply All to apply the settings to all the selected source devices.

6. Change the admin settings of Copy IPSLA configuration to running config to the value set in ipm.env.

CSCsi98010

Target device of the DHCP collector is not migrated during backup-restore of IPM 2.6.

This problem occurs if you restore a back up of IPM 2.6 in IPM 4.0. In this case, the target device of the DHCP collector is not migrated.

For example, if you:

1. Customize a DHCP operation in IPM 2.6 with DHCP server, Server1.

2. Use this customized operation to create a collector, CustomDHCPCollector.

3. Take a back up of IPM 2.6 using Single Migration script.

When you restore the IPM 2.6 backup in IPM 4.0, the target device of the CustomDHCPCollector is not migrated.


Note This also applies to the default DHCP operation.


Workaround

1. Add a target device in IPM 4.0 that was specified by the DHCP server in IPM 2.6.

2. Create a new collector with the customized DHCP operation.

CSCsj17761

JOS: Cannot specify the End Date while creating new collectors.

In a JOS (Japanese Operating System), you cannot specify the End Date while creating new collectors. This occurs if you launch the application using IE. However, you can specify the End Date if you launch the application using Firefox.

Workaround

Specify the End Date duration in days instead of specifying the date.


Resolved Problems in IPM 4.0

Table 4 describes the problems resolved since the last release of IPM.

Table 4 Resolved Problems in IPM 4.0

Bug ID
Summary
Explanation

CSCsa93425

If you launched the Device Update page, after installing IPM on LMS 2.5, it displayed a 500 server error.

This problem has been resolved.

CSCsa69919

Device Selector was not supported while importing devices from DCR into IPM.

This problem has been resolved.

CSCsa22981

You were able to back up only two copies using the ipmDbBackup. argument.

This problem has been resolved.

CSCsa10955

IPM 2.6 was not managed by Common Services Daemon Manager.

This problem has been resolved.

CSCdw65638

The database password was not encrypted.

This problem has been resolved.


Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Open Source License Acknowledgements

The following acknowledgements pertain to this software license.

OpenSSL/Open SSL Project

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

This product includes software written by Tim Hudson (tjh@cryptsoft.com).

License Issues

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.

OpenSSL License:

© 1998-1999 The OpenSSL Project. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org.

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.

6. Redistributions of any form whatsoever must retain the following acknowledgment:

"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License:

© 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.

This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).

The implementation was written so as to conform with Netscapes SSL.

This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).

Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgement:

"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".

The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)".

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].