Table Of Contents
Working With IPM From the CiscoWorks Homepage
Accessing IPM Data From the CiscoWorks Homepage
Viewing IPM Server Information
Viewing Status Information for IPM Servers
Viewing Version Information for the IPM Server and Components
Viewing the Troubleshooting Log for IPM
Importing Devices From Device and Credential Repository
Downloading the IPM Client for Solaris
Downloading the IPM Client for Windows
Viewing Configuration Information
Viewing Source Configuration Information
Viewing Target Configuration Information
Viewing Operation Configuration Information
Viewing Collector Configuration Information
Viewing Path Echo Collector Path Usage Data
Accessing Software Updates and Additional Information
Viewing Information About IPM on Cisco.com
Working With IPM From the CiscoWorks Homepage
This chapter provides information about accessing IPM status and statistical data from a Web browser. Using a Web browser, you can access IPM data via the CiscoWorks homepage.
This chapter includes the following sections:
•
Accessing IPM Data From the CiscoWorks Homepage
•
•
•
•
Accessing IPM Data From the CiscoWorks Homepage
From the CiscoWorks homepage, you can access IPM statistics, such as server status or configuration, latency, jitter, and HTTP reports. You can download the IPM client to a Solaris or Windows workstation. Also, you can launch the IPM Web client or access cisco.com.
To access IPM data from the CiscoWorks homepage:
Step 1
For information on starting IPM client from the CiscoWorks homepage see "Starting IPM Client From the CiscoWorks Homepage" section
Figure 5-1 CiscoWorks Homepage
Step 2
Detailed information about the IPM data you can view from the CiscoWorks homepage is provided in the relevant sections of this chapter.
Viewing IPM Server Information
When troubleshooting problems with IPM, you can view useful information from the CiscoWorks homepage. The following sections provide details on pertinent information:
•
•
•
Viewing Status Information for IPM Servers
You can display status information for all IPM servers.
To view status information for the IPM servers select Internetwork Performance Monitor > Admin > Server Info > Process Status in the CiscoWorks homepage.
The Process Status page (Figure 5-2) appears.
Figure 5-2 Server Status Page
Viewing Version Information for the IPM Server and Components
You can display version information for all IPM servers. To view version information for the IPM server and components select Internetwork Performance Monitor > Admin > Server Info > Version Info in the CiscoWorks homepage. The IPM Version Info page (Figure 5-3) appears.
Figure 5-3 IPM Versions Page
Viewing the IPM Server Log
You can display the contents of the IPM server log file on the server to which you are connected, and which is currently running the IPM server. This log contains useful information for diagnosing and correcting IPM operational problems.
To view the IPM server log select Internetwork Performance Monitor > Admin > Server Info> Server Log File in the CiscoWorks homepage.
The Server Log File page (Figure 5-4) appears.
Figure 5-4 Server Log File Page
Viewing the IPM Console Log
You can display the contents of the IPM console log file on the server to which you are connected and which is currently running the IPM server. This log contains unexpected error and warning messages from the IPM server.
To view the IPM console log, select Internetwork Performance Monitor > Admin > Server Info> Console Log File in the CiscoWorks homepage.
The Console Log page (Figure 5-5) appears.
Figure 5-5 Console Log File Page
Viewing the Troubleshooting Log for IPM
You can display the troubleshooting information for IPM. This log contains information that might be requested by Cisco customer support personnel.
To view troubleshooting information for IPM select Internetwork Performance Monitor > Admin > Server Info > Troubleshooting Info in the CiscoWorks homepage.
The IPM Server Troubleshooting Info page (Figure 5-6) appears.
Figure 5-6 IPM Server Troubleshooting Info Page
Importing Devices From Device and Credential Repository
You can import the devices from the Device Credential Repository. Device Credential Repository is a common repository of devices in Common Services and stores the attributes and credentials required to manage devices in a management intranet. IPM interacts with this repository to get the device list, device attributes and device credentials.
You can import devices as
•
•
•
When you import devices as Sources, IPM contacts the device and adds them only if they are running SAA and if the Read and Write community strings are provided.
When devices are imported as Target SAA Responders, if the device has a read community string, IPM verifies if the SAA responder is enabled on the target or not. If there is not Read Community String, the SAA responder status is not verified.
When you import devices as Target IP Devices, IPM adds the device without either contacting the device or making any verifications.
When you import devices from the Device and Credential Repository, if the devices already exist in IPM, they will be updated. IPM creates a separate log file for the Device and Credential Repository Import status. You can view the log file in: IPMROOT/etc/source or IPMROOT/etc/target.
You can view the results of importing devices from the CiscoWorks homepage by clicking View Import Source Log or View Import Target log.
To import devices from the Device and Credential Repository:
Step 1
Step 2
The Import from Device and Credential Repository screen appears.
Figure 5-7 Import From Device and Credential Repository page
Step 3
•
•
•
Step 4
The devices are imported based on the option you have selected, and a message indicating the location of the log file is displayed.
You can also view the log file by selecting Source Import Log or Target Import Log on the Import From Device and Credential Repository page.
Before you import devices from Device and Credential Repository, ensure that there are devices in the repository. For information about adding devices to Device and Credential Repository, see the User Guide for CiscoWorks Common Services 3.0 on Cisco.com. Also, IPM does not support importing devices from Resource Manager Essentials (RME).
When you import devices from Device and Credential Repository into IPM, IPM returns a response code for each operation indicating its success or failure. It also gives you the reason why the operation failed.
Table 5-1 describes the response codes:
Downloading the IPM Client
You can access the IPM client installation software from the CiscoWorks homepage. This access is useful if you do not have the CD-ROM, or if you prefer to download the software using your Web browser.
After you have downloaded the IPM client installation software to your workstation, you must install the software on your local system.
You cannot download the Solaris client from Windows IPM servers. You can download it only from Solaris IPM Servers.
The following sections provide details on downloading the IPM client:
•
•
Downloading the IPM Client for Solaris
To download the IPM client for Solaris:
Step 1
Step 2
The IPM Client for Solaris page (Figure 5-8) appears.
Figure 5-8 IPM Client for Solaris Page
Step 3
Step 4
Step 5
#uncompress CSCOipmClient.tar.ZStep 6
#/usr/bin/tar -xvf CSCOipmClient.tarStep 7
#./setupCli.shStep 8
#rm -rf temp_directoryWhere temp_directory is the directory containing the downloaded files.
For more information about installing the IPM client software on a Solaris workstation, see the "Installing IPM on Solaris" chapter of the Installation Guide for Internetwork Performance Monitor.
Downloading the IPM Client for Windows
To download the IPM client for Windows:
Step 1
Step 2
The IPM Client for Windows page (Figure 5-9) appears.
Figure 5-9 IPM Client for Windows Page
Step 3
Step 4
Step 5
The installation files automatically uncompress into a temporary directory, and the installation setup program starts.
Step 6
For more information about installing the IPM client software on a Windows workstation, see the "Installing IPM on Windows" chapter of the Installation Guide for Internetwork Performance Monitor.
Viewing Configuration Information
You can view configuration for IPM's sources, targets, operations and collectors from the CiscoWorks homepage. The following sections provide details on viewing configuration information for IPM:
•
•
•
•
•
While viewing IPM configuration information from your Web browser, you can sort the information displayed by clicking on the column title of a field. For example, to sort the information displayed in the Target Configuration Information page by target type, click the heading of the Type column.
Viewing Source Configuration Information
You can display information about all source routers defined to IPM. The configuration information displayed includes alias name, host name, IP address, Cisco IOS software release, SA Agent version, maximum payload size, last time configuration was set, maximum number of collectors that can be defined on the source router, and system up time.
To view configuration information for the source routers defined to IPM select Internetwork Performance Monitor > Reports > Configuration Reports > Sources on the CiscoWorks homepage.
The Source Configuration Report page (Figure 5-10) appears.
Figure 5-10 Source Configuration Report Page
Viewing Target Configuration Information
You can display information about all devices defined as targets to IPM. The configuration information displayed includes alias name, host name or PU name, IP address, and target type.
To view configuration information for the targets defined to IPM select Internetwork Performance Monitor > Reports > Configuration Reports > Targets on the CiscoWorks homepage.
The Targets Configuration Report page (Figure 5-11) appears.
Figure 5-11 Targets Configuration Report Page
Viewing Operation Configuration Information
You can display information about all operations defined to IPM. The configuration information displayed includes operation name, frequency, timeout, rising threshold, falling threshold, threshold count1 and count2, operation type, threshold type, action event type, and timeout enable status.
To view configuration information for the operations defined to IPM select Internetwork Performance Monitor > Reports > Configuration Reports > Operations on the CiscoWorks homepage. The Operation Information page (Figure 5-12) appears.
Figure 5-12 Operations Configuration Report Page
Viewing Collector Configuration Information
You can display information about all collectors defined to IPM. The configuration information displayed includes the collector name, source, target, operation, current status, collector type, and links to latency, jitter, and HTTP reports for various time periods.
To view configuration information for the collectors defined to IPM, select Internetwork Performance Monitor > Reports > Configuration Reports > Collectors on the CiscoWorks homepage. The Collector Information page (Figure 5-13) appears.
Figure 5-13 Collectors Configuration Report Page
Viewing Path Echo Collector Path Usage Data
You can view the usage percentage for each path in a Path Echo collector's path list from the CiscoWorks homepage.
To view path usage data collected by IPM:
Step 1
The Collector Information Report page (Figure 5-13) appears.
Step 2
The Path Usage page (Figure 5-14) appears, where:
•
•
•
For example, if a Path Echo collector passes through three different paths (p1, p2, and p3) between its source router and target, and the Counts for those paths are 15, 10, and 5 respectively, then the Percentage for p1 is 15/(15+10+5)=50%.
Figure 5-14 Path Usage Page
For more information about Path Echo operations, see Measuring Hop-by-Hop Performance for IP.
Viewing Latency Data
You can view latency data gathered by IPM from its collectors from the CiscoWorks homepage. The following sections provide details on the latency data you can view.
Viewing Daily Latency Data
You can view a daily summary of latency data for each collector on the IPM server.
To view daily latency data collected by IPM:
Step 1
The Daily Latency Reports page (Figure 5-15) appears, with reports sorted by average latency.
Figure 5-15 Daily Latency Reports Page
Step 2
•
•
•
If a path never reaches its target, IPM calculates the Web report based on the last hop in each path.
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
Figure 5-16 Daily IP-Echo Latency Summary Report Page
Figure 5-17 Daily Services Latency Summary Report Page
Figure 5-18 Daily IP-Path Latency Summary Report Page
Figure 5-19 Daily Latency Alert Report Page
Viewing Weekly Latency Data
You can view a weekly summary of latency data for each collector on the IPM server.
To view weekly latency data collected by IPM:
Step 1
The Weekly Latency Reports page (Figure 5-20) appears.
Figure 5-20 Weekly Latency Reports
Step 2
•
•
•
If a path never reaches its target, IPM calculates the Web report based on the last hop in each path.
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
For Weekly Reports, the start time is always the beginning of the Week i.e. Sunday.
Consider a Collector started on 16 January 2002, which is Wednesday. The Weekly Data for that Collector would have a time stamp of 13 January 2002, which is Sunday (the start date of that week).
Viewing Monthly Latency Data
From the CiscoWorks homepage, you can view a monthly summary of latency data for each collector on the IPM server.
To view monthly latency data collected by IPM:
Step 1
The Monthly Latency Reports page (Figure 5-21) appears.
Figure 5-21 Monthly Latency Reports Page
Step 2
•
•
•
If a path never reaches its target, IPM calculates the Web report based on the last hop in each path.
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
For Monthly Reports, the start time is always the beginning of the Month.
Consider a Collector started on 15 January 2002, which is Tuesday. The Monthly data for that Collector would have a time stamp of 1 January 2002 (the start date of that month).
Viewing Jitter Data
You can view jitter data gathered by IPM from its collectors from the CiscoWorks homepage. The following sections provide details on the jitter data you can view.
Viewing Daily Jitter Data
You can view a daily summary of jitter data for each collector on the IPM server.
To view daily jitter data collected by IPM:
Step 1
The Daily Jitter Reports page (Figure 5-22) appears.
Figure 5-22 Daily Jitter Reports Page
Step 2
•
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
Figure 5-23 Daily Jitter Summary Report Page
Viewing Weekly Jitter Data
You can view a weekly summary of jitter data for each collector on the IPM server.
To view weekly jitter data collected by IPM:
Step 1
The Weekly Jitter Reports page (Figure 5-24) appears.
Figure 5-24 Weekly Jitter Reports Page
Step 2
•
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
For Weekly Reports, the start time is always the beginning of the Week i.e. Sunday.
Consider a Collector started on 16 January 2002, which is Wednesday. The Weekly Data for that Collector would have a time stamp of 13 January 2002, which is Sunday (the start date of that week).
Viewing Monthly Jitter Data
You can view a monthly summary of jitter data for each collector on the IPM server.
To view monthly jitter data collected by IPM:
Step 1
The Monthly Jitter Reports page (Figure 5-25) appears.
Figure 5-25 Monthly Jitter Reports Page
Step 2
•
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
For Monthly Reports, the start time is always the beginning of the Month.
Consider a Collector started on 15 January 2002, which is Tuesday. The Monthly data for that Collector would have a time stamp of 1 January 2002 (the start date of that month).
Viewing HTTP Data
You can view HTTP data gathered by IPM from its HTTP collectors from the CiscoWorks homepage. The following sections provide details on the HTTP data you can view.
Viewing Daily HTTP Data
You can view a daily summary of HTTP data for each HTTP collector on the IPM server.
To view daily HTTP data collected by IPM:
Step 1
The Daily HTTP Reports page (Figure 5-26) appears.
Figure 5-26 Daily HTTP Reports Page
Step 2
•
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
Figure 5-27 Daily HTTP Summary Report Page
Viewing Weekly HTTP Data
You can view a weekly summary of HTTP data for each HTTP collector on the IPM server.
To view weekly HTTP data collected by IPM:
Step 1
The Weekly HTTP Reports page (Figure 5-28) appears.
Step 2
•
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
For Weekly Reports, the start time is always the beginning of the Week i.e. Sunday.
Consider a Collector started on 16 January 2002, which is Wednesday. The Weekly Data for that Collector would have a time stamp of 13 January 2002, which is Sunday (the start date of that week).
Figure 5-28 Weekly HTTP Reports Page
Viewing Monthly HTTP Data
You can view a monthly summary of HTTP data for each HTTP collector on the IPM server.
To view monthly HTTP data collected by IPM:
Step 1
The Monthly HTTP Reports page (Figure 5-29) appears.
Step 2
•
•
In all IPM Web reports, if the Error % field shows 100%, then the Avg (average) and Avg Max (average maximum) fields show N/A (not available), because no data is available.
For Monthly Reports, the start time is always the beginning of the Month.
Consider a Collector started on 15 January 2002, which is Tuesday. The Monthly data for that Collector would have a time stamp of 1 January 2002 (the start date of that month).Figure 5-29 Monthly HTTP Reports Page
Bad data from SA Agent can affect daily, weekly, and monthly statistical reports. To prevent this, IPM filters very large values (greater than 999999) and negative values from the data that it receives from the SA Agent.
Accessing Software Updates and Additional Information
You can access additional information about IPM via the CiscoWorks homepage. See section Viewing Information About IPM on Cisco.com
Viewing Information About IPM on Cisco.com
To view information about IPM available on Cisco's Website, select Common Services > Software Center Software Update from the CiscoWorks homepage.
