Guest

CiscoWorks Internetwork Performance Monitor

Release Notes for Internetwork Performance Monitor 4.1 on Windows and Solaris (With LMS 3.1)

  • Viewing Options

  • PDF (221.7 KB)
  • Feedback
Release Notes for Internetwork Performance Monitor 4.1 on Windows and Solaris

Table Of Contents

Release Notes for Internetwork Performance Monitor 4.1 on Windows and Solaris

New Features

Product Documentation

Known Problems in IPM 4.1

Resolved Problems in IPM 4.1

Obtaining Documentation, Obtaining Support, and Security Guidelines

Open Source License Acknowledgements

OpenSSL/Open SSL Project

License Issues


Release Notes for Internetwork Performance Monitor 4.1 on Windows and Solaris


These Release Notes contain information about new features in Internetwork Performance Monitor (IPM) 4.1 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.1, running on a Windows platform and include:

New Features

Product Documentation

Known Problems in IPM 4.1

Resolved Problems in IPM 4.1

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.1:

10000 Collector Support

IPM now supports 10000 collectors. You can create maximum of 5000 historical collectors and the remaining as real-time collectors. This is based on the LMS license you have opted for.

Device Auto Allocation

The device allocation in IPM 4.1 has been enhanced to include two new methods for Auto allocation:

Manage All Devices — Allows you to automatically add devices into IPM after they are added to DCR.

Manage By Groups — Allows you to automatically add devices into IPM, based on device groups.

However, the number of devices added into IPM depends on the license limit.

Metro Ethernet

IPM now supports the following IP SLA operations:

ethernetPing

ethernetPingAutoIPSLA

ethernetJitter

ethernetJitterAutoIPSLA

For more information, see the following sections in the User Guide for Internetwork Performance Monitor 4.1:

Defining an Ethernet Ping Operation

Defining an Ethernet Ping Auto IP SLA Operation

Defining an Ethernet Jitter Operation

Defining an Ethernet Jitter Auto IP SLA Operation

CLI Support

You can use CLI commands in IPM to import collectors from specified source devices.

DNS Server Name

You can now enter the Hostname or the IP Address for the DNS server.

Microseconds Accuracy

You can collect the jitter statistics for a UDP Jitter Operation at a precision level of microseconds.

Reaction Types for each Operation

IP SLA can be configured to react to certain measured network parameters. IPM now allows you to create collectors so that they react to various Reaction parameters such as RTT, MOS, ICPIF, packet loss, etc.

Whenever the threshold levels are violated for any of the reaction variable configured, SNMP traps are sent to the configured management stations.

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

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.1

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.1

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.1

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.1 on Windows and Solaris (this document)

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 Help in the dialog box.


Known Problems in IPM 4.1

Table 2 explains the known problems in IPM 4.1:

Table 2 Known Problems in IPM 4.1

Bug ID
Summary
Explanation

CSCsh59293

IP SLA probes are not deleted when you restore data.

During the Data Restore operation in IPM 4.x, the IP SLA probes are not deleted from the source router.

Workaround 1:

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

GUI

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

The Collector Management page appears.

2. Select the collectors and delete them.

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 collectors that have 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 started the uninstallation, delete the collectors from the server, using GUI or CLI.

GUI

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

The Collector Management page appears.

2. Select the collectors and delete them.

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 collectors that have ipm| IPM Server name in the Owner field.

CSCsi58023

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

While upgrading from IPM 2.6 to IPM 4.x, the database password used in IPM 2.6 is automatically applied to IPM 4.x. This database password is applied to IPM 4.x 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.x 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.x.

When you migrate from IPM 2.6 to IPM 4.x, 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.x.

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 Backup-Restore of the same version, the server IP of the default DNS operation on the restored server is overwritten with the backed up server IP.

For example, a backup 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 a customized DNS operation to create new collectors.

CSCsi98010

Target device of the DHCP collector is not migrated while backing up and restoring IPM 2.6.

This problem occurs if you restore a back up of IPM 2.6 in IPM 4.x. 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.x, 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.x that was specified by the DHCP server in IPM 2.6.

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

CSCso55002

Collectors are reconfigured with wrong values in a specific scenario.

This occurs if before you create collectors, the application settings options, are set as follows:

Copy IPSLA Configuration to Running-config

Use Managed Source Interface Address to Enabled.

For instance if you:

3. Create 100 collectors on device, dev1.

The collectors created are not shown in the show run output of the device, dev1. The collectors do not have a source interface/address value configured.

4. Delete the collector on the device manually.

The device reboots.

5. In the IPM server, change the application settings options, Copy IPSLA Configuration to Running-config and Use Managed Source Interface Address to Enabled.

During the next poll the collectors missing or reboot of device is sensed and reconfiguration happens.

6. Run the show run CLI command.

All 100 collectors appear in the show run output of the device, dev1. These collectors are configured with a source interface value.

Workaround:

None.

CSCsq18835

Customized AdminThreshold MIB values are not reflected in MIB browser for Gatekeeper Registration Delay probes.

This occurs when you:

1. Create a Gatekeeper Registration Delay probe with 5000 as the threshold value.

2. View the configuration by using the show ip sla configuration command.

The threshold value is displayed as 5000.

3. Open the MIB browser and analyze the value of ttMonCtrlAdminThreshold MIB variable.

The ttMonCtrlAdminThreshold MIB variable value is set as "0".

When you try to import the VoIP probes from this device, the AdminThreshold value is set to "0". This occurs although the threshold value has been customized on the device.

Workaround:

None.

CSCsj70412

IPM Collectors do not sense Probe Configuration changes done through device CLI.

This problem occurs in the following scenarios:

Scenario 1:

1. Create a collector such as, ipmcoll using IPM. Assume that the admin index is 1234.

2. Stop the collector in IPM.

3. Delete the collector in the CLI.

4. Configure a probe in the device with the same admin index 1234, using CLI commands.

5. Start the collector ipmcoll from IPM.

6. Run the following command on the device:

sh ip sla conf adminindex

Where adminindex is 1234.

The collector created using CLI remains on the device.

Scenario 2:

1. Create a collector such as, ipmcoll using IPM. Assume that the admin index is 1234.

2. Edit the collector in IPM so that it moves to a scheduled state.

3. Configure a probe in the device(preferrably with a configuration other than ipmcoll) with the same admin index 1234, using the CLI commands.

When the schedule time for ipmcoll arrives, the collector gets created with the same admin index. In this case, it is 1234.

4. Run the following command on the device:

sh ip sla conf adminindex

Where adminindex is 1234.

The probe configured on the device gets deleted or replaced by the collector created by IPM.

Workaround:

None.

CSCsm87616

The probes do not get deleted from the source device and the uninstallion fails if the IPM process is down during uninstallation.

This occurs if you do the following while uninstalling LMS:

1. Ensure that the IPMprocess is down.

2. Proceed with uninstalling LMS.

During uninstallation, you are prompted to delete probes.

3. Click Yes or enter Y to delete probes.

The probes are not deleted from the source device and the uninstallation fails.

Workaround:

None.


Resolved Problems in IPM 4.1

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

Table 3 Resolved Problems in IPM 4.1

Bug ID
Summary
Explanation

CSCsi42099

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

This happened if the existing reports were not cleaned up after running dbrestoreorig.

This problem has been resolved.

CSCsi98010

Target device of the DHCP collector did not migrate while backing up and restoring IPM 2.6.

This problem occurred if you restored a backup of IPM 2.6 in IPM 4.0.

In this case, the target device of the DHCP collector was not migrated.

This problem has been resolved.

CSCsk13949

The source device displayed a Source Not Responding state even when the associated collectors were running.

This problem has been resolved.

CSCsk96639

Sometimes, two collectors were shown with same admin index in the server when bulk collectors were created on a source device.

This problem has been resolved.

CSCsl36804

Polling did not happen for any collector in a server loaded with 5,000 devices and 5,000 collectors after few days.

This occurred only in a Solaris server.

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:

Copyright © 1998-2007 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:

Copyright © 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].