user manual
Table Of Contents
- User Guide for Internetwork Performance Monitor
- Contents
- Preface
- Overview of IPM
- Getting Started With IPM
- Using IPM to Measure Network Performance
- Measuring Network Performance for DHCP
- Measuring Network Performance for DLSw
- Measuring Network Performance for DNS
- Measuring Network Performance for HTTP
- Measuring Network Performance for FTP
- Measuring Network Performance for IP
- Measuring Network Performance for SNA
- Measuring Network Performance for TCP
- Measuring Network Performance for UDP
- Measuring Network Performance for Enhanced UDP
- Modifying IPM Components
- Working With Source Devices
- Working With Target Devices
- Working With Operations
- Working With Collectors
- Adding Components Using Seed Files
- Changing IP Addresses
- Setting the Baseline
- Setting IPM Database Preferences
- Setting SNMP Timeout and Retry Environment Variables
- Setting New IPM Server Process Timeout Values
- Setting the DISPLAY Variable in Solaris
- Backing Up or Restoring the IPM Database
- NVRAM Settings
- Managed Source Interface Settings
- Changing Administrative Password
- Changing IPM Database Password
- Working With Message Log Window
- Working With IPM From the CiscoWorks Homepage
- Accessing IPM Data From the CiscoWorks Homepage
- Viewing IPM Server Information
- Importing Devices From Device and Credential Repository
- Downloading the IPM Client
- Viewing Configuration Information
- Viewing Latency Data
- Viewing Jitter Data
- Viewing HTTP Data
- Accessing Software Updates and Additional Information
- IPM FAQs and Troubleshooting Tips
- IPM Command Reference
- SA Agent Feature Mapping
- Glossary
- Index

A-14
User Guide for Internetwork Performance Monitor
OL-11291-01
Appendix A IPM FAQs and Troubleshooting Tips
Troubleshooting IPM
Q.
Did you create any collectors when no LUs were available?
A.
Each collector creates a logical unit (LU) connection to the mainframe. Therefore, if you create
collectors when all LUs were used, those collectors accrue no data for Real Time or Historical
graphs. For example, if 20 LUs were activated by the host (mainframe) and 20 LUs were used for
20 collectors, the 21st created collector would accrue no statistics. The Real Time graph displays
“No Connection” for the Last Data Point.
To avoid this problem, make sure the number of collectors you create is equal to or less than the
number of LUs defined on the mainframe. To display the number of LUs defined on the mainframe
that are still available, use the show sna IOS command.
Q.
Did you create any HTTP collectors that require authentication?
A.
If you create an HTTP collector using a URL Lookup String that requires authentication (that is, a
user name and password), no statistics are collected. The HTTP General Error or HTTP Timeout
Error window appears.
Similarly, if you create an HTTP collector and specify a URL Lookup String that is separated from
the source router by a firewall, no statistics are collected. The Real Time graph displays the “TCP
Timeout” error message. You might see a DNS error message as well, if there is no entry in the DNS
table for the URL Lookup String. Also current version of IPM does not support proxy environment.
Q.
Did you specify any incorrect target PU names?
A.
When you run an SNA collector, use the PU you defined for the source router as the target PU name.
When you use service point PUs, use the service point PU name configured in the router as the target
PU name.
In the following example, the source router is cwb-ipm-2500a, and the target PU name must be
IPM2500A:
sna host IPM2500A xid-snd 05ddd025 rmac 4001.7200.d022 rsap 4 lsap 4 focalpoint
cwb-ipm-2500a#
Q.
Did you specify any incorrect IP addresses?
A.
If you receive a No Connection error from the Real Time graph when you create DLSW collectors,
make sure the DLSW source IP address and target IP address are both correct. Use the
View > Properties menu option to display these addresses. If either address is missing or incorrect,
add the correct address and recreate the collector with the correct addresses.
Q.
Did you specify large mainframe RU sizes?
A.
When you modify Request Payload and Response Payload sizes (for RU-response/request units), do
not exceed the defined mainframe RU sizes. Doing so causes Real Time graph errors, such as the
“Data Verification Error.” If you must modify the Request Payload and Response Payload
parameters to make them smaller, you can access them from the Edit > Configuration >
Operations > Echo > Packet Settings for SNA LU0 and SNA LU2 menu.
Q.
How do I change the IP address or host name of an IPM server?
A.
If you must change the IP address or host name of the server on which IPM is running, keep the
following considerations in mind:
• If you change the IP address of the IPM server, but the host name of the server remains
unchanged, IPM is not impacted. If the /etc/hosts, host name, DNS, Network Information
Services (NIS), netmask, and so on are all configured correctly with the new IP address, the IPM
server and client work correctly after you reboot the system.