Guest

CiscoWorks Internetwork Performance Monitor

Release Notes for Internetwork Performance Monitor 4.2 (With LMS 3.2)

  • Viewing Options

  • PDF (239.1 KB)
  • Feedback
Release Notes for Internetwork Performance Monitor 4.2 (With LMS 3.2)

Table Of Contents

Release Notes for Internetwork Performance Monitor 4.2 (With LMS 3.2)

New Features

Product Documentation

Known Problems in IPM 4.2

Resolved Problems in IPM 4.2

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Internetwork Performance Monitor 4.2 (With LMS 3.2)


Published: May 29, 2009
Revised: June 04, 2009, OL-19638-01

These Release Notes contain information about new features in Internetwork Performance Monitor (IPM) 4.2 and provide pointers to information on product documentation.

They also give details about the known and resolved problems.

These Release Notes apply to IPM 4.2, running on a Windows and Solaris platform and include:

New Features

Product Documentation

Known Problems in IPM 4.2

Resolved Problems in IPM 4.2

Obtaining Documentation, Obtaining Support, and Security Guidelines

New Features


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


The following are the new features and enhancements in Internetwork Performance Monitor 4.2:

Virtual Routing and Forwarding (VRF) Support

Planned Network Outage Support

Enabling and Disabling IPSLA Syslog Support

IPM Summarized Reports

Flexible Schedulable Option for IPM Reports

Open Database Schema Support

Virtual Routing and Forwarding (VRF) Support

Internetwork Performance Monitor 4.2 supports Virtual Routing and Forwarding (VRF). It does this by configuring collectors with the VRF name that you specify.

For more information, see the Configuring Collectors section in the User Guide for IPM 4.2.

Planned Network Outage Support

Collector Manager is enhanced to support planned network outage intervals for existing collectors. IPM allows you to specify the start and end times for selected collectors

For more information, see the Managing Outage Details section in the User Guide for IPM 4.2.

Enabling and Disabling IPSLA Syslog Support

You can select devices and enable or disable IPSLA syslog support for these devices.

For more information, see the IPSLA Syslog Configuration section in the User Guide for IPM 4.2.

IPM Summarized Reports

This release allows you to create summarized reports in IPM. The IPM summarized reports that are supported are:

IPM Highest Jitter

IPM Lowest Availability

IPM Highest Latency

IPM Violation Summary

For more information, see the Creating Summarized Reports section in the User Guide for IPM 4.2.

Flexible Schedulable Option for IPM Reports

IPM reports now have flexible scheduling options that allow you to generate reports. You can:

Generate daily, weekly, or monthly reports.

Enable the reports to e-mail notifications to other users.

Export reports with images to pdf formats.

For more information, see the Generating Statistical Reports and Graphics section in the User Guide for IPM 4.2.

Open Database Schema Support

LMS 3.2 supports exposing few database views and definitions.

You can access the created views using database access methods such as JDBC and ODBC, from a local or remote server.

To enable the access to applications database, you must run the dbaccess.pl utility from the command line.

See the Open Database Schema Support for LAN Management Solutions 3.2 document for more information on exposed database views and definitions.

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

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

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

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

Table 2 explains the known problems in IPM 4.2:

Table 2 Known Problems in IPM 4.2  

Bug ID
Summary
Explanation

CSCso97007

The Action Event is not set as Immediate for timeout

This problem occurs when you create custom operations in IPM 2.6, IPM 4.0, and IPM 4.0.1. If you:

1. Select the operation as Echo

2. Select Generate Action Event as X of Y

3. Select Action Event Type as SNMP Trap and enable Timeout Action In

If you upgrade to IPM4.1 after this, the operation Echo is created with the rtt and timeout reaction configuration.

However Action Event X of Y is set for Timeout reaction instead of Immediate.

Workaround:

None

CSCso61456

MIBs are set to default values.

While importing a collector, a new operation is created and MIBs are set to the default values.

Workaround:

None

CSCso55002

Collectors are re-configured with wrong values in some cases.

This problem occurs when you create collectors with the following application settings option. If you:

1. Copy IPSLA Configuration to Running-config

2. Use Managed Source Interface Address to Enabled.

For instance if you:

1. 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 or an address value configured.

2. Delete the collector on the device manually.

The device reboots.

3. 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 polling cycle, the collectors are missing or the device reboots and a reconsideration occurs.

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

CSCsq33221

In the Real-time graph some data points are plotted twice with same Timestamp.

This problem occurs if the SNMP response is greater than or equal to the polling frequency.

In this case, the Real time graph includes the previous data and the points are plotted twice in the same Timestamp.

Workaround:

None.

CSCsk96283

The Polling intervals in reports do not match after the deamons are restarted.

This problem occurs when you create a collector which starts at 1:30.

The polling of collector for hourly data occurs at 2:30, 3:30, 4:30, 5:30 and so on.

The first bucket gets created at 1:30 and fills up till 2:30. This bucket represents the operations occurred between 1:30 to 2:30.

At 2:30 the second bucket gets created at the device.

The first bucket completes filling up and the first bucket gets deleted or flushed and the second bucket completes filling up.

Now the daemons are stopped at 2.45

Polling will happen at 3:45 and it will poll the third bucket and in report represent the period of operation (packets being sent between src and target) as 2:30 to 3:45.

However, on this device the operation period is actually between 2:30 to 3:30.

Workaround:

None

CSCsv89332

The Tool tip does not appear when you click the Select VRF List button.

The Tool tip that should appear when you click Select VRF appears only in FireFox.

This feature is not supported in IE6, as the Tool tip is hidden behind the selected component.

Workaround:

None.

CSCsy31756

Problems while importing Real Time collectors from files

This problem occurs in the following scenarios:

Scenario 1

If you:

1. Export the historical collector (Days of Week: Sunday)

2. Change the collector name and collector type in the exported file as 2

3. Import the collector from the updated file

The collectors are imported successfully. However, the scheduling details do not apply to the Real Time collectors.

If you create the Real Time collector, it should run daily.

However in this case, the imported Real Time collector accepts the schedule details and after running on one day, it goes into a Dormant state.

Scenario 2

If you export the collector using for example, Start Date as 11 Mar 2009

In the exported file, the date appears as 10 Mar 2009.

Scenario 3

In the Exported collector file, the following information is appears:

Columns 1, 3,5,6, 8-14 are required

However, Column 8 is Source Interface Address and is an optional field, not a mandatory one.

Workaround:

None

CSCsy50193

Problem in the Syslog Configuration page if you select many devices

This problem occurs if you:

1. Go to the IPM Syslog Configuration page.

2. Select some devices from the All Devices group, where some devices are managed by RME and others are not.

3. After selecting the devices, click Enable or Disable

It displays the number of devices that are not managed by RME.

However, when this processes is repeated many times, it displays the wrong number of devices that are not managed by RME.

Workaround:

None.

CSCsy74148

Error while importing collectors with DHCP and AutoIPSLA

This error occurs only in ACS.

Workaround:

None

CSCsy82023

Incorrect link appears in an error message.

If you enter an invalid rule in the IPM Group Administration page an incorrect link appears.

This link points to the Common Services help page that gives information on Rules.

Workaround:

None.

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.

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.

CSCso55002

Collectors are re-configured 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 or an 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 re-configuration 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 problem occurs when you:

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

2. View the configuration 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 made using the CLI device.

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 (preferably 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 uninstallation fails if the IPM process is down during uninstallation.

This problem occurs if you do the following while uninstalling LMS:

1. Ensure that the IPM process 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.

CSCsz55721

The size of the archive charts folder increases during the endurance set up.

When the scheduled jobs are successful, then the job reports are stored in the archive folder along with the .jpg files.

If you schedule daily jobs, all jobs are run daily and the size of the folder gradually increases.

Workaround:

None.

CSCsz54494

Delay in the polling interval of collectors.

There is a delay in the polling interval of collectors because the device takes a long time to respond.

Workaround

None.

CSCsz55627

System Reports are not deleted by default

System Reports are generated (daily,weekly,monthly) by default when the jobs run

In 10k setup the system reports are generated for 10k collectors . As a result the size of the system reports folder increases.

In the Solaris endurance setup which runs for a month with 10k collectors system, the folder size increases to 4GB .

Hence the System Reports folder should be deleted by default because the folder size keeps increasing.

Workaround:

None.

CSCsz54494

Irregular polling in solaris endurance setup

If there is a delay in the SNMP response time from a single source device, the entire polling cycle is affected.

Workaround:

None


Resolved Problems in IPM 4.2

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

Table 3 Resolved Problems in IPM 4.2

Bug ID
Summary
Explanation

CSCsv91723

The order of setting of IPSLA MIBs had problems if the value of the frequency and timeout was less than the IPSLA's default value.

This problem has been resolved.

CSCsy78660

In IPM 4.0 the Collectors went o the Source Not Responding state because of the default community settings.

This problem has been resolved.

CSCsx73091

The IPM importcollector imported IP SLA entries only when the adminIndex on the device was between 1 and 999999.

If the entry number was 1000000 or higher, was the collector was not imported

This problem has been resolved.

CSCsw40391

A StackOverflowError appeared in the daemons.log file if the 5k one minute collectors ran for more than 15 days

This problem has been resolved

CSCsi61859

Could not open the ipmprocess log file.

This problem has been resolved.

The name of the log file has been changed from ipmprocess.log file to ipmserver.log.

CSCsh40270

Wrong bucket was polled when a collector was stopped and restarted

The problem has been resolved.

CSCsi53964

The exported reports in csv and pdf formats had links for graphs. This made the report unreadable.

The 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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.