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-17
User Guide for Internetwork Performance Monitor
OL-11291-01
Appendix A IPM FAQs and Troubleshooting Tips
Troubleshooting IPM
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.
Q.
I am unable to launch the web client, and I get a Java console error message: “Reason = hostname
is not DNS resolvable.” What should I do?
A.
This is because the DNS name in the IPM_ConfigMain.properties cannot be resolved on the client
side. To correct this, change:
hostName=hostname
to
hostName=IP Address
Q.
In the logs, I see the message “Unable to get version.” What does this mean?
A.
This could be because of one of the following reasons:
• Router down/unreachable at that time.
• Community strings were changed, and the IPM database was not updated.
• IP address was changed, and the IPM database not updated.
• This error message can be either for the source or from the target.
Q.
When I launch the IPM web client on Internet Explorer, I get the following message, and the web
client does not launch: “Your current settings prohibit running ActiveX controls on this page. As a
result, the page may not be displayed correctly.”What should I do?
A.
Add the IPM Server as a trusted site on Internet Explorer. Once you have added IPM Server as a
trusted site, the problem goes away. For more information, access the Microsoft site:
http://support.microsoft.com.?id=816702.
Q.
I have changed the date and time of my machine where I have installed the IPM Server. Do I need
to restart IPM?
A.
Yes. When you change the date and time of the IPM Server, you need to restart IPM. Else, IPM uses
the old time and date in reports.