|
|
These release notes describe caveats for installing and using Cisco Internetwork Performance Monitor (IPM) Software Release 2.3.
These release notes are for use with the CiscoWorks2000 family of products running on Solaris and Windows platforms. Supported Solaris versions are 2.6 and 2.7. Supported Windows versions are Windows 98, Windows NT 4.0, Windows 2000 Professional, and Windows 2000 Server.
These release notes provide:
IPM 2. 3 contains these new features:
The following documents are provided in PDF on your product CD:
 |
Note Adobe Acrobat Reader 4.0 is required. |
This section provides information about the following known caveats for using IPM 2.3:
As soon as you have finished using the CD-ROM, to install the IPM client in Windows 98, remove the CD-ROM from the workstation's drive. If you leave the CD-ROM in the drive and reboot, or if you remove and then reinsert the CD-ROM, InstallShield setup runs and prompts you to uninstall the IPM client.
If there is a failure in the upgrade process or if you terminate the upgrade process, you cannot restore the old database.
Before you do an upgrade, take a backup of IPMDB.db, IPMDB.log, and ipm.env.
When you upgrade your IPM servers and clients:
If you do not follow these rules when you upgrade, IPM cannot function properly. In most cases, the IPM client cannot even access the IPM server.
If you have upgraded to IPM 2.3, and then want to upgrade your operating system, make sure that before running IPM 2.3, you install all the required:
for the current operating system.
 |
Caution Make sure that you also upgrade the third party device drivers for the current operating system. |
When you have both IPM and CiscoWorks2000 on your system, always run ipm cw2ksetup uninstall before uninstalling CiscoWorks2000.
If Enhanced UDP jitter collectors get no response from the SA Agent Responder on a target router, the Responder might have become disabled, or it might show control message errors.
To determine whether the Responder is disabled, enter the following command on the target router:
sh rtr respIf you see this message, the Responder is disabled:
RTR Responder is: Disabled.
If you see these messages, the Responder is enabled, but control message errors have occurred:
Number of Errors:
Recent Error Sources:
To correct either of these problems, reboot the target router.
[CSCdr41422]
When you use DHCP operations with certain DHCP servers, all DHCP IP address leases on the servers can be exhausted. To reduce the likelihood of this problem occurring:
[CSCdr57382]
In general, you should not allow an IP Path Echo collector to use another collector's source or target as an intermediate hop. However, if you do allow this configuration, the Change IP Address utility fails as a result of this sequence of events:
1. An IP Path Echo collector uses another collector's source or target as an intermediate hop.
2. The IP address of the source or target changes.
3. The IP Path Echo operation automatically discovers the change and adds the new address to its data structures in the IPM database.
4. You run the Change IP Address utility.
5. IPM detects that the new address already exists in the IP Path Echo data structures. Since you cannot change an IP address to an address that already exists in the database, IPM does not allow you to make the change, and the Change IP Address utility fails.
If this situation occurs in your configuration, you must remove the old target or source from the database, as well as any IP Path Echo collectors that use the old target or source as an intermediate hop, then add the collectors back to your configuration.
[CSCdr84534]
You do not specify IP addresses for DHCP, DNS, and HTTP collectors. Therefore, you cannot change IP addresses for those collectors. Instead, use these guidelines to change parameters for DHCP, DNS, and HTTP collectors:
[CSCdr89787]
Bad data from SA Agent can skew daily, weekly, and monthly statistical reports. To prevent this situation, IPM filters very large values (greater than 999999) and negative values from the data it receives from the SA Agent. [CSCdr41703]
The IPM database uses two important files:
If the database process halts while it is writing information to either of these files, one or both might be corrupted.
When the IPM Database Server starts, it tries to connect to the IPM database. If either IPMDB.db or IPMDB.log is corrupted, the Database Server cannot connect to the database. If it cannot connect, it writes as much information as it can to the server_root/logs/ipmServices.log file and exits gracefully.
You can use any of these methods to determine whether the Database Server started:
6/8/2000 14:27:01 | Cisco IPM DB Server | INFO | Starting Database
Services
6/8/2000 14:27:02 | Cisco IPM DB Server | INFO | Database will
time out in 5 minutes
6/8/2000 14:32:17 | Cisco IPM DB Server | ERROR: [ 0 ]| Unable to
connect to database after 5 minutes
6/8/2000 14:32:17 | Cisco IPM DB Server | ERROR: [ 183 ]| There
was a problem starting the database, please consult your
documentation.
6/8/2000 14:32:17 | Cisco IPM DB Server | INFO | Stopping Open
Server Gateway
6/8/2000 14:32:17 | Cisco IPM DB Server | INFO | Stopping IPM
Database Server
6/8/2000 14:32:17 | Cisco IPM DB Server | INFO | Database services
stopped.
If the Database Server cannot connect to the database, it is likely that either IPMDB.db or IPMDB.log is corrupt. To correct this problem:
Step 1 Select Start > Programs > Internetwork Performance Monitor > IPM MSDOS Prompt.
Step 2 Change to the install_root\server\sybase directory, enter the dir command and look for IPMDB.log.
Step 3 Enter the dbsrv6 -a IPMDB.log IPMDB command. This command attempts to integrate IPMDB.log with IPMDB.db. A Sybase window opens and tracks the progress of the command.
Step 4 Delete (or rename) IPMDB.log.
Step 5 Enter the dbsrv6 -f IPMDB command. This command attempts to force the database back to its last checkpoint. Forcing the database back to its last checkpoint should lose only a few hours of data, unless the database file itself is corrupt.
Step 6 Enter the ipm dbrestore command. This command restores the IPM database to the last backed up version. If you backed up your IPM database nightly, you should lose no more than 24 hours of data.
This command can take several hours to complete.
 |
Warning Do not interrupt this command. Doing so can corrupt your IPM database. |
Step 7 Restart the IPM servers using the ipm restart command.
[CSCdr17233]
On some Windows 2000 systems, the initial download of large Java applets (or subsequent downloads of the same applets that are not cached locally) might take longer than expected. In some instances, it may take up to six minutes. After the applet has been loaded and cached locally, the problem no longer occurs.
The delay is caused by client side filtering mechanisms, such as virus scanning. Some virus scanners are configured to automatically scan content downloaded by browsers. Scanning consumes a lot of memory and results in disk paging on most systems. Downloading is significantly slower than expected, due to this reason. The effect is less on systems with large amounts of RAM and virtual memory.
To work around this problem, disable your virus scanner. Doing so will improve Java applet download times considerably. You can also disable the automatic scanning of all downloaded files, and instead enable the scanning of program files only (specified by file extension).
|
Note Exact instructions vary depending on the virus scanner installed on your system. |
If you are using Norton AntiVirus 2000, disable the Auto-Protect feature.
If you are using McAfee VirusScan:
Step 1 Close and exit any programs that are actively downloading.
Step 2 Launch the VirusScan console.
Step 3 Click Configure.
Step 4 Select the Detection tab.
Step 5 Verify that Enable Internet download scanning is not selected.
Step 6 Select Program files only.
Step 7 Click Apply.
Step 8 Click OK.
For more information, see the following article: http://support.microsoft.com/support/kb/articles/q240/3/09.asp
If you access IPM web client with http://localhost:(IPM Web Port) URL, the Java plug-in does not load the applet and there is a Java Security Exception. This is due to a Java plug-in open bug (Bug Id 4203626).
Workaround: Always use real host name in the URL.
While adding a Source or Target using IP address, you may get a SNMP API Error. This problem may occur when the DNS server can resolve an IP address to a host name but cannot resolve a host name to an IP address. That implies that the DNS server is not reverse address resolvable.
IPM supports devices that cannot be resolved by the DNS server or devices that are reverse address resolvable.
Workaround: You can either remove the IP address from the DNS or make the device reverse address resolvable.
While importing a device database from Resource Manager Essentials to IPM, your browser may sometimes report a web server timeout. This occurs if the database has a large number of devices. The script ipmimportbackend.pl takes more time to execute and a web server timeout may occur.
Workaround: You can use OS specific methods to prevent a timeout from occurring. Refer to the following sections for more information.
You can prevent timeout by either increasing the Directive Timeout value in httpd.conf or importing the Source and Target devices using internal commands.
To increase the Directive Timeout value:
Step 1 Go to Server\Apache\conf sub directory in the IPM 2.3 root directory.
Step 2 Change the default value from 300 to 1800.
Step 3 Stop the web server by entering ipm stop web.
Step 4 Start the web server by entering ipm start web.
To import source files:
Step 1 Go to the directory where you have installed IPM 2.3.
Step 2 cd Server\cgi-bin
Step 3 At the command prompt, enter perl ipmsourceexport.pl followed by the location of the IPM installation directory\Server.
If the command is successful, there is no output.
You can check the results in IPMsourceexport.dat and IPMsourceexport.dat.out file in IPM Installation directory\Server \ etc\source.
To import target files:
Step 1 Go to the directory where you have installed IPM 2.3.
Step 2 cd Server\cgi-bin
Step 3 At the command prompt, enter perl ipmtargetexport.pl followed by the location of the IPM installation directory\Server.
If the command is successful, there is no output.
You can check the results in IPMtargetexport.dat and IPMtargetexport.dat.out files in IPM Installation directory\Server \etc\target
You can prevent timeout by either increasing the Directive Timeout value in httpd.conf or importing the Source and Target devices using internal commands.
To increase the Directive Timeout value:
Step 1 Go to CSCO\Apache\etc sub directory in the IPM 2.3 root directory.
Step 2 Change the default value from 300 to 1800.
Step 3 Stop the web server by entering ipm stop web.
Step 4 Start the web server by entering ipm start web.
To import the source files:
Step 1 Go to CSCOipm/cgi-bin in the IPM 2.3 root directory.
Step 2 At the command prompt, enter the location of the CiscoWorks2000 installation directory followed by /CSCOpx/bin/perl ipmsourceexport.pl
pkgparam CSCOipm -s BASEDIR
If the command is successful, there is no output.
You can check the results in the /CSCOipm/etc/source/IPMsourceexport.dat and IPMsourceexport.dat.out files in the IPM root directory.
To import the target files:
Step 1 Go to CSCOipm/cgi-bin in the IPM 2.3 root directory.
Step 2 At the command prompt, enter the location of the CiscoWorks2000 installation directory followed by /CSCOpx/bin/perl ipmtargetexport.pl
pkgparam CSCOipm-s BASEDIR
If the command is successful, there is no output.
You can check the results in the /CSCOipm/etc/source/IPMtargetexport.dat and IPMtargetexport.dat.out files in the IPM root directory.
Known problems are unexpected behaviors or defects in Internetwork Performance Monitor software releases. They are graded according to severity level.
You can search for known problems on the Cisco bug tracking system tool, called Bug Navigator II.
To access Bug Navigator II, enter http://www.cisco.com/support/bugtools in your web browser or log into Cisco.com and select Service & Support>
Technical Assistance Center> Tools>Software Bug Toolkit >
Bug Navigator II.
The known bugs for this release of IPM are:
| Bug ID | Summary | Explanation |
|---|---|---|
CSCdt36439 | If the IPM install directory does not have write or execute permissions, IPM installation proceeds without displaying any warnings or errors. | When the IPM server/Client session is started, the following error message appears "Error in Func ExecIPMMainScript: Error = IMP Server and Client not installed" This message also appears if the permissions of IPM installation directory are changed to Read Only after installation. Workaround: This error occurs because of the Unix operating system (root overrides the permission settings) Make sure that the IPM install directory has read, write, and execute permissions for the group. |
CSCds33719 | Update of CD one fails due to locked perl.dll.
| If IPM is installed on a machine that has the RWAN bundle, re-installation of CD One may fail due to a shared library being locked. This problem also occurs when CiscoWorks2000 and IPM installations exist on the same machine and you install or upgrade other CiscoWorks2000 components. Workaround: 1. Run ipm stop 2. Run ipm cw2ksetup uninstall 3. Re-install CD one 4. Run ipm cw2ksetup install 5. Run ipm start The first two steps remove IPM's dependency on the shared library and the last two steps integrate IPM with CiscoWorks2000. |
CSCds65863 | While the Java applet loads, web server warnings appear. | While the IPM server is running, the web server error log shows a few periodic warnings. Workaround: Ignore these warnings. The web server log file is cleared automatically when it reaches 200K. |
CSCdr78845 | Intermediate hops are added to the target list. | Whenever a path-hop (path-echo) analysis is done, IPM adds each hop IP address to the target list. Each hop IP address then becomes a new target. Workaround: None. |
CSCdt37627 | Changes in the operation template are not reflected in the collectors. | If latency, threshold, and miscellaneous settings of a user defined operation template are changed, IPM displays a message that states that the changes will be reflected in all the collectors of that operation. However, these changes are not reflected in the configured collectors of that operation. Only IP echo operation with collectors in the "running" state reflect the change. Workaround: Select Edit Collector > General Operation to change the settings of every instance of the configured collectors, for that operation. |
CSCdt04199 | Operation pending at source, but client shows running. | Sometimes, collectors display "running" state in the IPM client window but real-time statistics of the same collector may show that the operation is "pending at source". This occurs because once the parameters are specified to a newly configured collector, the state of the collector appears as "running" in the GUI. However, synchronization occurs only when the hourly data collection from the routers start. From then on, the actual status (namely pending at source) appears on the GUI. As real-time statistics start checking the status at the routers, the correct state of the collector appears. Workaround: Run real time display to check the current state of the collector on the router. |
CSCdp64700 | Seed File Error Messages | If you start a seed file configuration process by selecting File > Open Seed File from the IPM Main window, and one or more of the seeds fails, IPM displays the resulting error and warning messages one at a time, instead of in a group at the end of the process. The flow of error and warning messages can accumulate on-screen, and can be annoying to clear. Workaround: Use the ipm seed command to start the seed file configuration process. |
CSCdr73988 | Incorrect Error Statistics for TCP Connect | If a TCP Connect statistical graph has 100% errors, the total number of errors should remain constant. However, in some cases the number of errors begins increasing hourly. Workaround: None |
CSCdr84612 | Business days calculations do not include timezone of source and target. | The business day setting is applied only to the IPM server's location. This setting does not take into account, the business day at source and target. Workaround: None. |
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site 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. (0102R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Wed Oct 2 01:51:46 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.