User Guide for Internetwork Performance Monitor Software Release 2.6 CiscoWorks Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS Preface ix Audience ix Conventions ix Product Documentation x Obtaining Documentation xi Cisco.
Contents Starting IPM as a Standalone Client 2-3 Starting IPM Standalone Client on Solaris 2-3 Enabling the IPM Password on Solaris 2-5 Starting IPM Standalone Client on Windows 2-6 Starting IPM Client from the Windows Command Prompt Enabling the IPM Password on Windows 2-7 Running Simultaneous IPM Sessions 2-6 2-8 Configuring the IPM Components 2-8 Defining a Source Device 2-8 Defining a Target 2-10 Defining a Collector 2-12 Viewing Network Performance Statistics 2-17 Viewing Network Performance Statis
Contents Measuring Network Performance for IP 3-18 Measuring End-to-End Performance for IP 3-19 Defining an IP Echo Operation 3-19 Viewing End-to-End Statistics for IP 3-21 Measuring Hop-by-Hop Performance for IP 3-22 Defining an IP Path Echo Operation 3-22 Viewing Hop-by-Hop Statistics for IP 3-24 Measuring Network Performance for SNA 3-29 Defining an SNA Echo Operation 3-30 Viewing Statistics for SNA 3-31 Measuring Network Performance for TCP Defining a TCP Operation 3-33 Viewing Statistics for TCP 3-35
Contents Working With Collectors 4-11 Viewing a List of Defined Collectors 4-12 Viewing a Collector State Summary 4-12 Viewing Collector Properties 4-13 Adding a New Collector 4-14 Stopping Collectors 4-15 Deleting Collectors 4-15 Adding Components Using Seed Files 4-16 Creating a Seed File 4-16 Seed File Syntax 4-17 Sample Source Seed File 4-18 Sample Target Seed File 4-19 Sample Collector Seed File 4-19 Loading Components From a Seed File 4-21 Viewing Seed File Output Files 4-21 Changing IP Addresses Set
Contents CHAPTER 5 Working With IPM From the CiscoWorks Homepage 5-1 Accessing IPM Data From the CiscoWorks Homepage 5-1 Viewing IPM Server Information 5-2 Viewing Status Information for IPM Servers 5-3 Viewing Version Information for the IPM Server and Components Viewing the IPM Server Log 5-4 Viewing the IPM Console Log 5-5 Viewing the Troubleshooting Log for IPM 5-6 Importing Devices From Device and Credential Repository 5-4 5-7 Downloading the IPM Client 5-10 Downloading the IPM Client for Sol
Contents APPENDIX B IPM Command Reference B-1 Output of ipm status Command Output of ipm help Command B-8 B-8 Output of ipm export help Command IPM Internal Commands APPENDIX C B-11 B-13 SA Agent Feature Mapping C-1 Verify Your SA Agent Version C-2 GLOSSARY INDEX User Guide for Internetwork Performance Monitor viii OL-11291-01
Preface This document describes how to use Internetwork Performance Monitor (IPM) 2.6, a software to monitor the performance of multi-protocol networks. This preface describes who should read this guide, and outlines the document conventions used in this guide. Audience This document is for the network administrator or operator who uses the Internetwork Performance Monitor software.
Preface Product Documentation Caution Warning Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. This symbol means danger. You are in a situation that could cause bodily injury. 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.
Preface Obtaining Documentation Obtaining Documentation Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems. Cisco.com You can access the most current Cisco documentation at this URL: http://www.cisco.com/techsupport You can access the Cisco website at this URL: http://www.cisco.
Preface Documentation Feedback Documentation Feedback You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com. You can send comments about Cisco documentation to bug-doc@cisco.com.
Preface Obtaining Technical Assistance Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x. Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL: http://www.cisco.
Preface Obtaining Additional Publications and Information Submitting a Service Request Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions.
Preface Obtaining Additional Publications and Information • Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL: http://www.ciscopress.com • Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments.
Preface Obtaining Additional Publications and Information User Guide for Internetwork Performance Monitor xvi OL-11291-01
C H A P T E R 1 Overview of IPM This chapter provides an overview of Internetwork Performance Monitor (IPM) application. It contains the following sections: • What is IPM? • Key Terms and Concepts • How Does IPM Work? • Client/Server Architecture What is IPM? IPM is a network management application that allows you to monitor the performance of multi-protocol networks. IPM measures the latency and availability of IP networks on a hop-by-hop (router-to-router) basis.
Chapter 1 Overview of IPM Key Terms and Concepts The IPM/SA Agent monitoring solution is composed of: 1. The IPM server 2. The IPM client application 3. The Service Assurance (SA) Agent feature of the Cisco IOS software The focus of this document is the IPM network management application, which includes the server and the client. In some cases, however, it is not possible to fully describe IPM without including information about the SA Agent feature.
Chapter 1 Overview of IPM How Does IPM Work? How Does IPM Work? IPM measures and displays network performance statistics (latency, availability, jitter, packet loss, and error information) between a source and a target device. The target can be an IP-addressable device, an IBM MVS mainframe, or an SA Agent-enabled Cisco router: • If the target is an IP-addressable device, it can be a network device, a server, or a workstation.
Chapter 1 Overview of IPM Client/Server Architecture Figure 1-1 IPM Client/Server Architecture Solaris or Windows 2000 System (IPM server, client, and database) IPM client on Windows 2000 workstation IPM client on Windows XP workstation IPM client on Solaris workstation 85632 Network For this release of IPM, the server software runs on Solaris 2.8, Solaris 2.
Chapter 1 Overview of IPM New Features in IPM 2.6 • Download/Launch the IPM client. • View Web-based troubleshooting information. • Determine the version of IPM that has been installed. • View seed files. All the above functions can be launched via the CiscoWorks homepage. New Features in IPM 2.6 These are the new features in IPM 2.6: • Support for importing device from Device and Credential Repository — IPM 2.
Chapter 1 Overview of IPM New Features in IPM 2.
C H A P T E R 2 Getting Started With IPM This chapter provides information about starting the IPM application and configuring a collector to gather latency data.
Chapter 2 Getting Started With IPM Starting IPM Client Starting IPM Server on Windows To start the IPM server on a Windows system, enter: cd c:\Program Files\Internetwork Performance Monitor\Server\bin ipm start To enter the ipm start command, you must be logged in as the administrator, or your login must have administrator privileges. Starting IPM Client You can access the IPM Client in two ways: As a web client from the CiscoWorks homepage, or as a standalone client.
Chapter 2 Getting Started With IPM Starting IPM Client Figure 2-1 IPM CiscoWorks Homepage If you do not have this URL, contact the system administrator who installed the IPM server software. Step 3 Select Client > Web Client. The Java applet loads and the IPM Main Window is displayed. The IPM Main Window is the starting point from where you can carry out the various IPM operations.
Chapter 2 Getting Started With IPM Starting IPM Client The default directory for installing IPM is /opt. If you installed IPM in a different directory, you must specify that directory instead of /opt. If you installed the IPM client and IPM server on different Solaris systems, you must enter the ipm start command from the /opt/CSCOipmClient/bin directory: # cd /opt/CSCOipmClient/bin # .
Chapter 2 Getting Started With IPM Starting IPM Client Enabling the IPM Password on Solaris To enable IPM passwords on Solaris: Step 1 Log in as the root user. Step 2 Enter: # cd /opt/CSCOipm/bin # ./ipm password Note The default directory for installing IPM is /opt. If you installed IPM in a different directory, you must specify that directory instead of /opt. IPM prompts you to enter a password. Step 3 Enter a password and press Enter.
Chapter 2 Getting Started With IPM Starting IPM Client Starting IPM Standalone Client on Windows When you install the IPM client on a Windows 2000 Professional and Server (with SP3 and SP4), Windows 2000 Advanced Server (with SP3, SP4), Windows XP Pro (SP1a) or Windows 2000 (WS2K3) system, the installation program adds two icons to your desktop: one icon for connecting to the IPM server you specified during installation, and one icon for connecting to any IPM server.
Chapter 2 Getting Started With IPM Starting IPM Client To start the IPM client and connect to an IPM server other than the default server, enter: cd c:\Program Files\Internetwork Performance Monitor\client\bin ipm start client server_name where server_name is the Solaris or Windows system on which the IPM server is running. Note To protect IPM device credentials, IPM does not allow you to disable the administrative password. IPM will prompt you to enter the password when you launch the client.
Chapter 2 Getting Started With IPM Running Simultaneous IPM Sessions Running Simultaneous IPM Sessions IPM allows you to run multiple sessions of the IPM client simultaneously. Central services and database functions are provided on an IPM server that communicates to multiple IPM clients. You can install the IPM client software on the same system as the IPM server, or on a different system on the same network as the IPM server.
Chapter 2 Getting Started With IPM Configuring the IPM Components Figure 2-3 Configuration Window—Source Configuration Step 3 In the Hostname or IP Address field, enter the host name or IP address of the device to use as the source for network performance measurements. This host name can be from 1 to 64 characters in length. Step 4 In the Read Community field, enter the SNMP community name for read access to the information maintained by the SNMP agent on the source device.
Chapter 2 Getting Started With IPM Configuring the IPM Components If you must add a large number of source routers to IPM, you can use the Source Configuration window to add them one by one, but it is more efficient to use a seed file. For information about using a seed file to add source routers to IPM, see the “Adding Components Using Seed Files” section on page 4-16. For information about viewing or deleting source routers, see the “Working With Source Devices” section on page 4-1.
Chapter 2 Getting Started With IPM Configuring the IPM Components Step 3 In the Target Type field, select the protocol type to be used with this target. The possible values are: • IP—Any IP-addressable device. Requires a destination IP address or host name. • Cisco SAA Responder—Component embedded in a target Cisco device running version 12.1 or later of the Cisco IOS software. Its function is to respond to SA Agent request packets from a source router running the SA Agent software.
Chapter 2 Getting Started With IPM Configuring the IPM Components Defining a Collector Defining a new collector involves selecting a source, a target, an operation, and a collector schedule. IPM configures collectors on the source device. There are two modes in which IPM configures a collector: • Mode 1: Collector is configured on the device without specifying which IP address to be filled in as source IP address.
Chapter 2 Getting Started With IPM Configuring the IPM Components Figure 2-5 Step 3 Collector Configuration Window In the Name field, type a name to assign to the collector. In the Description field, you can enter a brief description of the collector. Though the Name field in the Collector Settings dialog box allows you to enter more than 15 characters, the trap PDUs displays only the first 15 characters. The IPM database, however, will contain the complete collector name you have entered.
Chapter 2 Getting Started With IPM Configuring the IPM Components Set Date Range Window 39286 Figure 2-6 Step 6 Specify a start date for the collector. The options are: • Now—Starts the collector immediately after it is configured. This is the default setting. • On Date—Starts the collector at the specified date and time.
Chapter 2 Getting Started With IPM Configuring the IPM Components Step 10 In the Source Interface field, enter a valid IP address of the source device interface. This is the IP address of the source device interface to which the packets are returned from the destination The Source Interface field is an optional field. If you do not specify an IP address, IPM configures collector based on the properties specified in the ipm.env file.
Chapter 2 Getting Started With IPM Configuring the IPM Components Table 2-1 Predefined Operations (continued) Operation Description DefaultSMTP Measures the time to perform a TCP connect operation directed at the selected target on the standard Simple Mail Transfer Protocol (SMTP) port 25. Packet Priority is set to 0 (no priority) and Target Port is set to 25. DefaultSnaLu0Echo Measures end-to-end latency in an SNA network using LU0.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Step 13 Click Add. IPM adds the newly defined collector to the IPM database.If you selected a DNS operation, the Extra DNS Settings window appears (Figure 2-7). Step 14 Enter a DNS Lookup Name (the name of the host to look up for the DNS request) and click OK. Figure 2-7 Step 15 Extra DNS Settings Window Click Close to close the Configuration window and return to the IPM Main Window.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Viewing Network Performance Statistics in Real Time The Real Time Statistics window allows you to view statistics for an active collector as the data is being collected. This data appears only in real time, it is not stored in the IPM database. The Real Time Statistics window displays up to 1000 points of data; the most recent 1000 points are always displayed.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Jitter Real Time Statistics Window 39288 Figure 2-9 Statistics appear as soon as the frequency interval elapses. Data points are added to the graph for each interval that the statistics are measured for the selected collector. Table 2-2 describes the actions you can perform in the Real Time Statistics window.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Viewing Historical Network Performance Statistics To view statistics gathered over an historical monitoring period: Step 1 From the IPM Main Window (Figure 2-2), select one or more collectors (up to 10) to be viewed. Step 2 Select View > Statistics. The Statistics Data Filter window (Figure 2-10) appears.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Step 6 In the Statistical Format field, specify the initial increment for the granularity for displaying the statistical graphs. Choose one of the available options: Hourly, Daily, Weekly, or Monthly. For Weekly statistical graph, the start time is always the beginning of the Week i.e. Sunday. For Monthly statistical graph, the start time is always the beginning of the Month. Consider a Collector started on 15 January 2004.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Figure 2-12 Historical Statistics Window—Path Echo Collector User Guide for Internetwork Performance Monitor 2-22 OL-11291-01
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Figure 2-13 Historical Statistics Window—Enhanced UDP Collector If you selected more than one collector, their statistics appear in a single graph in the Historical Statistics—Multi-Collector Graph window (Figure 2-14). Multi-collector graphing is not available for Enhanced UDP, HTTP, or Path Echo collectors.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Historical Statistics Window—Multi-Collector Graph 39290 Figure 2-14 Table 2-3 describes the tasks you can perform in the Historical Statistics window. Table 2-3 Historical Statistics Window Options To Action Zoom in on a specific point Press Shift and click a point on the graph. on the graph. Zoom in on a specific area of the graph. Press Shift and drag and click on an area of the graph.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Table 2-3 Historical Statistics Window Options (continued) To Action Request an immediate poll of statistics (single-collector graphs only). Select View > Demand Poll. IPM typically polls a collector once per hour. If you are between polls and do not want to wait until the next polling period, you can use the Demand Poll function to request an immediate poll of the collector. The graphs are updated with the new statistics.
Chapter 2 Getting Started With IPM Viewing Network Performance Statistics Understanding Next Range Keep the following points in mind when you select View > Next Range: • The new start time is the current end time. The new end time is the current end time, plus the current duration. For example, if the current start time is midnight April 11 and the current end time is midnight April 12, the duration is 24 hours. So the new start time is midnight April 12, and the new end time is midnight April 13.
Chapter 2 Getting Started With IPM Printing IPM Statistics Printing IPM Statistics IPM provides the following printing options for the Real Time Statistics and Historical Statistics windows: • Specifying options for printing. • Printing the currently displayed statistical graphs. To access the printing options: Step 1 Display the window containing the data you want to print, either the Real Time Statistics window or the Historical Statistics window for a specific collector.
Chapter 2 Getting Started With IPM Exiting the IPM Client Exiting the IPM Client When you are finished monitoring network performance statistics, you can exit the IPM client by completing the following steps: Step 1 From the IPM Main Window (Figure 2-2), select File > Exit. The Exit IPM confirmation window appears. If you are running IPM as an applet and you exit the Web browser or close the active window, IPM exits but the confirmation window does not appear.
C H A P T E R 3 Using IPM to Measure Network Performance This chapter provides details on using IPM to measure latency, jitter, availability, packet loss, and errors.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DHCP Measuring Network Performance for DHCP The DHCP operation measures the round-trip latency time taken to discover a DHCP server and obtain a lease from it. After obtaining an IP address, SA Agent releases the IP address that was leased by the server. By default, the DHCP operation sends discovery packets on every available IP interface on the source router.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DHCP Figure 3-1 DHCP Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose. Step 5 Select Enable DHCP Server to enable a specific server name or address for DHCP operations. Then, enter the DHCP server name or address.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DHCP Viewing Statistics for DHCP The DHCP Historical Statistics window displays statistical and graphical information gathered over the monitoring period for the selected DHCP collector. To view end-to-end statistics for DHCP: Step 1 From the IPM Main Window, select one or more DHCP collectors (up to 10). Step 2 Select View > Statistics. The DHCP Historical Statistics window (Figure 3-2) appears.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DLSw Measuring Network Performance for DLSw DLSw+ is the enhanced Cisco version of DSCP RFC 1795. DLSw+ tunnels SNA traffic over IP backbones via TCP. The routers performing the tunneling of SNA traffic onto TCP/IP are referred to as DLSw peers. The DLSw operation measures the DLSw+ protocol stack and round-trip latency between DLSw peers. Normally DLSw peers communicate through TCP port 2065.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DLSw Step 3 Click DLSw. The DLSw Operation Configuration window (Figure 3-3) appears. Figure 3-3 DLSw Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DLSw Viewing Statistics for DLSw The DLSw Historical Statistics window displays statistical and graphical information gathered over the monitoring period for the selected DLSw collector. To view end-to-end statistics for DLSw: Step 1 From the IPM Main Window, select one or more DLSw collectors (up to 10). Step 2 Select View > Statistics. The DLSw Historical Statistics window (Figure 3-4) appears.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DNS Measuring Network Performance for DNS DNS operation latency is computed by measuring the time between sending a DNS request and receiving a reply. The operation queries for an IP address if you specify a host name, or queries for a host name if you specify an IP address. The DNS operation also measures availability and errors for DNS services.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DNS Figure 3-5 DNS Operation Configuration Window Step 6 In the DNS Lookup Name field, enter the DNS host name to look up on the specified DNS name server. Step 7 Click Add. IPM adds the newly defined operation to the IPM database. Step 8 Click Close to close the Configuration window.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for DNS Figure 3-6 DNS Historical Statistics Window If you selected more than one collector, their statistics appear in a single graph in the Historical Statistics—Multi-Collector Graph window (see Figure 2-14 for an example). For more detailed information about the statistics displayed in the DNS Historical Statistics window, see the “DNS Historical Statistics Window” section in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for HTTP Measuring Network Performance for HTTP The HTTP operation measures the round-trip latency time required to connect to and access data from an HTTP server. Three HTTP server response time measurements are made: • DNS Lookup—Round-trip latency in looking up the domain name. • TCP Connect—Round-trip latency in performing a TCP connect to the HTTP server.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for HTTP Figure 3-7 HTTP Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose. Step 5 Select the IP QoS Type as IP Precedence or DSCP. The IP QoS Settings values change based on your IP QoS Type selection.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for HTTP Step 7 To configure IPM so that it can use a proxy server, select Use HTTP Proxy Server, and enter the name or address of the proxy server. IPM will use the proxy server you specify for collectors you have configured for the HTTP operation. The default port for the HTTP proxy server would be 80, and the type of proxy server would be HTTP. You can set proxy server settings for IOS versions 12.1(9a) and above.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for HTTP Figure 3-8 HTTP Historical Statistics Window For more detailed information about the statistics displayed in the HTTP Historical Statistics window, see the “HTTP Historical Statistics Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for FTP Measuring Network Performance for FTP The FTP operation measures the round-trip latency time required to connect to and access data from an FTP server. The FTP transaction time server response shows the round-trip latency in sending a request to, and downloading the file from the FTP server. The FTP operation also measures availability and errors for FTP services.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for FTP The FTP Operation Configuration window (Figure 3-9) appears. Figure 3-9 FTP Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose. Step 5 Select the IP QoS Type as IP Precedence or DCSP. The IP QoS Settings values change based on your IP QoS Type selection.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for FTP Step 7 • The server name contains only alphanumerical characters, '.' and '-'. • The username contains only alphanumerical characters, safe characters ('$','-','_','.','+'), and extra characters ('!','*',',',0x27,0x28,0x29). • The password contains only alphanumerical characters, safe characters, extra characters, and ‘%’.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Figure 3-10 FTP Historical Statistics Window For more detailed information about the statistics displayed in the FTP Historical Statistics window, see the “FTP Historical Statistics Window” topic in the online help. Measuring Network Performance for IP In an IP network there are two types of measurements that you can take: • IP Echo—Measures the total round-trip latency from the source to the target device.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Measuring End-to-End Performance for IP IPM’s Echo operations measure end-to-end performance between a source and any IP-enabled device. Latency is computed by measuring the time taken between sending an ICMP echo request message to the destination and receiving an ICMP echo reply. The IP Echo operation also measures availability and errors for IP services.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Figure 3-11 IP Echo Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP To measure performance for a specific path, enable the Loose Source Routing option and add the hops for the operation to use. Note Step 7 Step 6 is valid only if you have selected the protocol as IP in step 5. In case you have selected any other protocol, this step is not applicable. Click Add. IPM adds the newly defined operation to the IPM database. Step 8 Click Close to close the Configuration window.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP If you selected more than one collector, their statistics are displayed in a single graph in the Historical Statistics—Multi-Collector Graph window (see Figure 2-14 for an example). For more detailed information about the statistics displayed in the Echo Historical Statistics window, see the “Echo Historical Statistics Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Step 3 Click Path Echo. The Path Echo Operation Configuration window (Figure 3-13) appears. Figure 3-13 IP Path Echo Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose. Step 5 Select the IP QoS Type as IP Precedence or DCSP.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Step 7 Click Add. IPM adds the newly defined operation to the IPM database. Step 8 Note Click Close to close the Configuration window. The sample interval must be greater than the timeout value multiplied by the number of hops. For more detailed information about the options available from the Path Echo Operation Configuration window, see the “Path Echo Operation Configuration Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Figure 3-14 IP Path Echo Historical Statistics Window—All Paths By default, IPM displays graphs for all paths in the path list. To view the list of hops for a single path, and their graphs, click on the path folder. The Path Echo Historical Statistics window for all hops in a single path (Figure 3-15) appears.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Figure 3-15 IP Path Echo Historical Statistics Window—All Hops in a Path To view the graphs for a specific hop, click on the hop. The Path Echo Historical Statistics window for a single hop (Figure 3-16) appears.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP Figure 3-16 Step 3 IP Path Echo Historical Statistics Window—One Hop By default, IPM displays a single graph for each path in the path list, or for each hop in a given path. However, you can choose to display combined statistics for more than one path or hop in a single graph also. To do so, select the path list, or a specific path, in the Path Echo Historical Statistics window, then select View > Show Combined.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for IP IP Path Echo Combined Path List Window 39292 Figure 3-17 Figure 3-18 shows a sample Combined Hop List window.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for SNA IP Path Echo Combined Hop List Window 39293 Figure 3-18 It is easier to compare different paths and hops when viewing combined statistics. To return to separate graphs for each path or hop, select View > Show Separate. For more detailed information about the statistics displayed in the Path Echo Historical Statistics window, see the “Path Echo Historical Statistics Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for SNA You can customize both the request and response payload sizes to model traffic flow for various applications. The SNA operations also measure availability and errors for SNA services. To measure end-to-end performance for SNA: Step 1 Define a device as the source device from which to measure performance. For details on defining a source device, see the Defining a Source Device.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for SNA Step 7 Step 8 In the Response Payload field, enter the number of bytes to use for the size of the payload of the response packet. The default setting is 64 bytes. • To check for connection loss, click Enable Connection Lost Action. • To increment the Verify Data counter whenever a response contains unexpected data, click Enable Data Verification. Click Add.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for SNA SNA Echo Historical Statistics Window 39294 Figure 3-19 If you selected more than one collector, their statistics appear in a single graph in the Historical Statistics—Multi-Collector Graph window (see Figure 2-14 for an example). For more detailed information about the statistics displayed in the Echo Historical Statistics window, see the “Echo Historical Statistics Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for TCP Measuring Network Performance for TCP IPM’s TCP Connect operation measures round-trip latency between a source and any IP-enabled device running TCP services. Latency is computed by measuring the time taken by the source to perform a TCP connect operation to the target device. This operation is useful for simulating Telnet or HTTP connection times.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for TCP Figure 3-20 TCP Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose. Step 5 Select the IP QoS Type as IP Precedence or DCSP. The IP QoS Settings values change based on your IP QoS Type selection.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for TCP For more detailed information about the options available from the TCP Operation Configuration window, see the “TCP Operation Configuration Window” topic in the online help. Viewing Statistics for TCP The TCP Historical Statistics window displays statistical and graphical information gathered over the monitoring period for the selected TCP collector.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for UDP For more detailed information about the statistics displayed in the TCP Historical Statistics window, see the “TCP Historical Statistics Window” topic in the online help. Measuring Network Performance for UDP IPM’s UDP operation measures round-trip latency between a source and any IP-enabled device running UDP services.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for UDP Figure 3-22 UDP Operation Configuration Window Step 4 In the Name field, enter a descriptive name to assign to the operation. In the Description field, you can enter a brief description of the operation, including its purpose. Step 5 Select the IP QoS Type as IP Precedence or DCSP. The IP QoS Settings values change based on your IP QoS Type selection.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for UDP Step 9 Click Add. IPM adds the newly defined operation to the IPM database. Step 10 Click Close to close the Configuration window. For more detailed information about the options available from the UDP Operation Configuration window, see the “UDP Operation Configuration Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for Enhanced UDP If you selected more than one collector, their statistics appear in a single graph in the Historical Statistics—Multi-Collector Graph window (see Figure 2-14 for an example). For more detailed information about the statistics displayed in the UDP Historical Statistics window, see the “UDP Historical Statistics Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for Enhanced UDP Defining an Enhanced UDP Operation IPM provides several default Enhanced UDP operations for measuring performance between a source and target. In addition, IPM provides the option to create, modify, or delete your own Enhanced UDP operations from the Enhanced UDP Operation Configuration window. To define an Enhanced UDP operation: Step 1 From the IPM Main Window, select Edit > Configuration.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for Enhanced UDP Step 6 In the Request Payload field, enter the number of bytes to use for the size of the payload of the UDP request packet.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for Enhanced UDP Figure 3-25 Enhanced UDP Historical Statistics Window—Part 1 User Guide for Internetwork Performance Monitor 3-42 OL-11291-01
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for Enhanced UDP Figure 3-26 Enhanced UDP Historical Statistics Window—Part 2 For more detailed information about the statistics displayed in the Enhanced UDP Historical Statistics window, see the “Enhanced UDP Historical Statistics Window” topic in the online help.
Chapter 3 Using IPM to Measure Network Performance Measuring Network Performance for Enhanced UDP User Guide for Internetwork Performance Monitor 3-44 OL-11291-01
C H A P T E R 4 Modifying IPM Components This chapter provides information about modifying IPM components. IPM components include collectors, source devices, target devices, and operations. Information is provided on viewing, updating, and deleting these components.
Chapter 4 Modifying IPM Components Working With Source Devices Viewing a List of Configured Source Devices To view a list of configured sources, select Edit > Configuration from the IPM Main window. The Configuration window (Figure 2-3) appears. By default, Sources is selected in the navigation pane and the Source Configuration window appears within the Configuration window. The Source Configuration window displays source devices you have already configured.
Chapter 4 Modifying IPM Components Working With Target Devices Adding a New Source Device Before you can use a source for a collector, you must add the source to IPM. You can optionally, verify that the SNMP read community and write community strings are configured properly on the source. Also, if you want to receive traps at your network management system (NMS), verify that the router is configured to send SA Agent-generated traps to your NMS. IPM itself does not receive traps.
Chapter 4 Modifying IPM Components Working With Target Devices Viewing a List of Defined Targets After you have defined a device as an IPM target, it appears in the list of defined targets in the Target Configuration window. To view a list of defined targets: Step 1 In the IPM Main Window, select Edit > Configuration. The Configuration window (Figure 2-3) appears. Step 2 Click Targets. The Target Configuration window (Figure 2-4) appears.
Chapter 4 Modifying IPM Components Working With Target Devices Figure 4-2 Target Properties Window For information about these fields, see the “Target Properties Window” topic in the online help. Adding a New Target IPM targets are destination devices for which you want to gather data. A target can be any IP-addressable device, an SA Agent Responder, or an SNA host. To add a new target, see the Defining a Target Deleting Targets You can delete targets you no longer need.
Chapter 4 Modifying IPM Components Working With Operations If you try to delete a target and IPM issues an error message such as Could not delete the target, appears. The reason could be: • The target is being used as a final target by one or more collectors. • The target is being used as an intermediate hop by one or more Path Echo collectors. To resolve this problem: Step 1 Make sure the target is not being used as a final target by any collector.
Chapter 4 Modifying IPM Components Working With Operations Step 3 Click an operation type. The Operation Configuration window (Figure 4-3) shows the default configuration for the selected operation type and the list of operations expands to show all defined operations of that type. The Operation Configuration window displays a list of all defined operations. From this window, you can define a new operation, modify an existing operation, or delete an existing operation.
Chapter 4 Modifying IPM Components Working With Operations Viewing Operation Properties The Operation Properties window allows you to view the properties of a defined operation. To view Operation Properties: Step 1 From the IPM Main Window, select a collector that uses the operation. Step 2 Select View > Properties. The Properties Viewer window (Figure 4-6) appears. By default, the Collector Properties window appears within the Properties Viewer window. Step 3 Click Operation.
Chapter 4 Modifying IPM Components Working With Operations Adding a New Operation An IPM operation is an alias for a set of parameters used for measuring performance between source router and a target device. IPM allows you to define packet priorities when you define an operation. You can select the packet priority as either IP Precedence or DSCP, with IP Precedence being the default selection. Based on the selection you make, IPM sets the values for the IP QoS Type.
Chapter 4 Modifying IPM Components Working With Operations • X of Y—When the latency exceeds the rising threshold or drops below the falling threshold X out of the last Y times, perform the action defined by Action Event Type. Optionally, specify the number of violations that must occur within a specified number. Valid values for both the x-value (X) and y-value (Y) are 1 through 16. The default is 5 for both values.
Chapter 4 Modifying IPM Components Working With Collectors Step 8 In the Sample Interval field, enter the frequency (in seconds) in which data has to be collected by the source router. The valid values are 10 to 3600 (1 hour). The default is 60 seconds. Step 9 Click OK to complete the operation definition. IPM adds the new or updated operation to the IPM database. Deleting Operations You can delete user-defined operations you no longer need.You can delete more than one operation at a time.
Chapter 4 Modifying IPM Components Working With Collectors Viewing a List of Defined Collectors All of the defined collectors are listed in the IPM Main Window (Figure 2-2). Any collectors with start dates and times earlier than the current date and time, and end dates and times later than the current date and time, are considered active collectors.
Chapter 4 Modifying IPM Components Working With Collectors Figure 4-5 Collector State Summary Window Viewing Collector Properties To view detailed information about a defined collectors: Step 1 From the IPM Main Window, select a collector. Step 2 Select View > Properties. The Properties Viewer window (Figure 4-6) appears. By default, the Collector Properties window appears within the Properties Viewer window.
Chapter 4 Modifying IPM Components Working With Collectors Figure 4-6 Collector Properties Window If the Collector Properties window is not displayed by default, click Collector. For information about these fields, see the “Collector Properties Window” topic in the online help. Adding a New Collector For information about adding a new collector, see Defining a Collector.
Chapter 4 Modifying IPM Components Working With Collectors Stopping Collectors You can stop collectors that you no longer need. When you stop a collector, the collector and the SA Agent entry are removed from the source router. You can stop more than one collector at a time. To stop an IPM collector: Step 1 From the IPM Main Window, select the collector or collectors to stop. Select Edit > Stop. The confirmation box appears Step 2 Click Yes. The selected collectors are stopped from the IPM Main Window.
Chapter 4 Modifying IPM Components Adding Components Using Seed Files Adding Components Using Seed Files In addition to defining source routers, targets, and collectors from their respective Configuration windows, you can define them using seed files. A seed file is a text file containing the information required to define one or more components. This is especially useful if you must add a large number of sources, targets, or collectors quickly.
Chapter 4 Modifying IPM Components Adding Components Using Seed Files Seed File Syntax The top of the seed file contains a comments section for any information you want to note about the file, followed by each component’s definition on a separate line. • In a source router seed file, for each source router you must provide a command, host name, read community string, and write community string.
Chapter 4 Modifying IPM Components Adding Components Using Seed Files Table 4-1 Parts of a Component’s Definition (continued) Part Description Target Type (Target only) The protocol type to be used with this target. Specify one of the following values: 1—IP. Requires an IP address or host name. 2—Cisco SAA Responder. Requires an IP address or host name and read community string. This is an optional field. 3—SNA LU0, SNA LU2, or SNA SSCP-LU. Requires a host name.
Chapter 4 Modifying IPM Components Adding Components Using Seed Files Sample Target Seed File A sample target seed file is shown below: #################################################################### # # This file has example definitions for target devices # # Comments starts with the "#" character # # The format of the file is as follows: # # # # characters are " ;,\t" "space,semicolon,comma,tab" # #
Chapter 4 Modifying IPM Components Adding Components Using Seed Files ## = 0 -> Forever # # = zero and = zero -> ON_DEMAND collector # # For DHCP, HTTP, FTP, and DNS Operation types, the target field must be Unused or unused. # MyHTTP should be replaced with the name of an HTTP operation you created. # # DefaultJitter should be replaced by Default60ByteVoice, Default160ByteVoice, # DefaultVideo, or DefaultVPN.
Chapter 4 Modifying IPM Components Adding Components Using Seed Files Loading Components From a Seed File To load components from a seed file into IPM: Step 1 From the IPM Main Window, select File > Open Seed File. The Seed File window appears. Seed File Window 39295 Figure 4-7 Step 2 In the Seed File Type field, select Source, Target, or Collector as the type of seed file to load. Step 3 In the Seed File Name field, enter the name of the source routers, targets, or collectors seed file.
Chapter 4 Modifying IPM Components Changing IP Addresses Then, if the addition of the resources is successful, the output file labsrcfile.txt.out would contain the following information: a cwb-ipm-1600a public private - OK a cwb-ipm-1600b public private - OK a cwb-ipm-1700a public private - OK If the resources cannot be added for some reason, OK is replaced with an appropriate error message.
Chapter 4 Modifying IPM Components Setting the Baseline To change the IP address: Step 1 Select Edit > IP Address from the IPM Main Window. The Change IP Address window (Figure 4-8) appears. Figure 4-8 Change IP Address Window Step 2 In the Old IP Address field, enter the old address you want to change. This must be an IP address; it cannot be a host name. Step 3 In the New IP Address field, enter the new IP address. Do not enter an IP address that already exists in the IPM database.
Chapter 4 Modifying IPM Components Setting IPM Database Preferences To edit the baseline: Step 1 Select Edit > Baseline from the IPM Main Window. The Edit Baseline window (Figure 4-9) appears. Figure 4-9 Step 2 Edit Baseline Window In the Enter New Baseline field, enter a percentage by which to increase the latency threshold. The valid range is 1 to 999 (percent). The default is 20 (percent).
Chapter 4 Modifying IPM Components Setting IPM Database Preferences The IPM database preferences file allows you to control these parameters and also define the business hours and days. Defined business hours are used in determining the daily, weekly, and monthly averages, whereas business days are used in determining the weekly and monthly averages. The database preferences file also allows you to set the length of time that daily data is retained in the database.
Chapter 4 Modifying IPM Components Setting IPM Database Preferences The day is divided into increments of one hour, starting at 0:00 a.m. (ipm_business_hour_0) and ending at 11:59 p.m. (ipm_business_hour_23=0). For the hours you want to include in averages, set the hour interval value to 1. For example, to store collected statistics over a business day that runs from 8:00 a.m. to 5:00 p.m.
Chapter 4 Modifying IPM Components Setting IPM Database Preferences For example, to set the business days to Monday through Friday, you would use the following setting (the default setting): ipm_business_day_0=0 ipm_business_day_1=1 ipm_business_day_2=1 ipm_business_day_3=1 ipm_business_day_4=1 ipm_business_day_5=1 ipm_business_day_6=0 By default, the business week is defined as 7 days, Sunday morning to Saturday evening. Step 4 Save your changes to the IPM database preferences file.
Chapter 4 Modifying IPM Components Setting IPM Database Preferences # of days.# ipm_daily_stats_life=180# # The ipm_business_hour_x settings describe which hours of the day IPM # will use when generating daily, weekly and monthly reports. Each hour # of the day, starting with 0 (midnight) and going through 23 (11 PM) # may be included in the reports. However, you will probably want to # restrict the hours included in the reports to normal business hours.
Chapter 4 Modifying IPM Components Setting SNMP Timeout and Retry Environment Variables Setting SNMP Timeout and Retry Environment Variables An IPM server and source router need not be physically near each other. In fact, they can be thousands of miles apart. However, as the distance increases, so does the time it takes the source router to respond to SNMP requests.
Chapter 4 Modifying IPM Components Setting SNMP Timeout and Retry Environment Variables The following environment variables control SNMP timeouts and retries: Variable Description IPM_SNMP_TIMEOUT Time in seconds for the IPM server to wait for a response. The valid range is 1 to 60 seconds. The default is 5 seconds. IPM_SNMP_RETRIES Number of times the IPM server tries again to send a request that has timed out while waiting for a response. The valid range is 1 to 5 retries.
Chapter 4 Modifying IPM Components Setting SNMP Timeout and Retry Environment Variables By default, the variable definitions are commented out in the file: Step 3 # Max value is 60 (seconds), default is 5 (seconds), min is 1 (second) #IPM_SNMP_TIMEOUT=5 #export IPM_SNMP_TIMEOUT # Max value is 5, default is 3, min is 1 #IPM_SNMP_RETRIES=3 #export IPM_SNMP_RETRIES # Max value is 60, default is 5, min is 1 #IPM_SNMP_TIMEOUT_INCREMENT=5 #export IPM_SNMP_TIMEOUT_INCREMENT To change a variable definition, rem
Chapter 4 Modifying IPM Components Setting New IPM Server Process Timeout Values By default, the variable definitions are commented out in the file: Step 3 # Max value is 60 (seconds), default is 5 (seconds), min is 1 (seconds) #set IPM_SNMP_TIMEOUT=5 # Max value is 5, default is 3, min is 1 #set IPM_SNMP_RETRIES=3 # Max value is 60, default is 5, min is 1 #set IPM_SNMP_TIMEOUT_INCREMENT=5 To change a variable definition, remove the comment markers (#) from the definition and change the settings.
Chapter 4 Modifying IPM Components Setting New IPM Server Process Timeout Values Setting Server Timeout Values in Solaris To set server timeout values in Solaris: Step 1 On your IPM server, use a text editor to open the ipm.conf file. In Solaris, the default directory for the ipm.conf file is /opt/CSCOipm/etc. Note The default directory for installing IPM is /opt. If you installed IPM in a different directory, specify that directory instead of /opt.
Chapter 4 Modifying IPM Components Setting the DISPLAY Variable in Solaris The data collection server’s timeout value is defined in the following line in the file: DataCollectionServer R MessageLogServer,SNMPServer C:\PROGRA~1\INTERN~1\Server\bin\CWB_ipmData_colld -ORBagentPort,44342,-OAconnectionMaxIdle,8640000,-PMCserverName,IPMProcessMgr,-PMCname,Dat aCollectionServer,-MLCserverName,IPMMsgLogServer,-MLCname,DataCollectionServer,-N,IPMDataC ollectionServer,-R,C:\PROGRA~1\INTERN~1\Server,-MLCfilterFileN
Chapter 4 Modifying IPM Components Backing Up or Restoring the IPM Database Backing Up or Restoring the IPM Database The IPM database is backed up automatically every day at 1:00 a.m. If your database file is corrupted, you can restore the data in the IPM database from the previous day’s backed-up data. To restore the IPM database from a previous back up: • In Solaris, enter: # cd /opt/CSCOipm/bin # .
Chapter 4 Modifying IPM Components Managed Source Interface Settings On Solaris systems: Step 1 Edit the file ipm.env in the /opt/CSCOipm/etc directory The default directory for installing IPM is /opt. If you installed IPM in a different directory, you must specify that directory instead of /opt. Step 2 Change the value of IPM_NVRAM_ENABLE to 1(default set to 0) set IPM_NVRAM_ENABLE=1 Step 3 Restart the IPM server by entering ipm restart at the command line.
Chapter 4 Modifying IPM Components Changing Administrative Password Step 3 Restart the IPM server by entering ipm restart at the command line. If you have set IPM_USE_MANAGED_SRC_INTF_ADDR to 0, the router will select the source interface from the routing table based on the IP address of the destination. This is the default mode. If you have set IPM_USE_MANAGED_SRC_INTF_ADDR to 1, the source interface address will be the same as the Managed Interface address in all the configurations.
Chapter 4 Modifying IPM Components Working With Message Log Window Working With Message Log Window The Message Log window provides a log of status messages generated by IPM. To access the Message Log window, enter the following command at the command line: ipm debug [hostname] The Message Log Window (Figure 4-10) appears.
Chapter 4 Modifying IPM Components Working With Message Log Window Field Description Process Name Name of the process. Message Category Types of messages which can be generated for troubleshooting process problems. The message categories available for IPM include: Debug—Helps to debug a problem in conjunction with Cisco’s Technical Assistance Center (TAC). Error—Generates messages when an error condition occurs. Info—Generates messages to notify you of status information. Trace—Generates trace calls.
Chapter 4 Modifying IPM Components Working With Message Log Window Buttons The buttons in the Log Display tab of the Message Log window provide the following functions: Button Description All Displays all messages generated by the message categories enabled in the Log Control tab of the Message Log window. ViewN (up to 6) Displays the messages that match the criteria you defined in the New View window.
C H A P T E R 5 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing IPM Server Information Figure 5-1 Step 2 CiscoWorks Homepage Click Client, Reports, or Admin to launch the IPM Client, IPM Reports and IPM Admin pages, respectively. 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing IPM Server 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing IPM Server Information 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing IPM Server Information 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing IPM Server Information 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Importing Devices From Device and Credential Repository 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Importing Devices From Device and Credential Repository 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 On the CiscoWorks Homepage, select Internetwork Performance Monitor > Admin > Import From Device and Credential Repository. Step 2 Click Import Devices.
Chapter 5 Working With IPM From the CiscoWorks Homepage Importing Devices From Device and Credential Repository Table 5-1 describes the response codes: Table 5-1 Description of Response Code during import Response Code Description 0 Success. The device has been imported successfully. 24 Invalid device. Check whether the device exists and has SAA. 25 Invalid device. Check whether the device exists and has SAA. 62 Invalid host name. Provide a valid host name for the device.
Chapter 5 Working With IPM From the CiscoWorks Homepage Downloading the IPM Client 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Downloading the IPM Client Step 5 From the Solaris command line, change to the directory where you downloaded the installation software and uncompress the files using: # uncompress CSCOipmClient.tar.Z Step 6 In the directory where you uncompressed the files, extract the IPM client installation files to the CDImage directory using: # /usr/bin/tar -xvf CSCOipmClient.
Chapter 5 Working With IPM From the CiscoWorks Homepage Downloading the IPM Client Step 5 Go to the download directory and run the ipmclnt.exe command to install the software. The installation files automatically uncompress into a temporary directory, and the installation setup program starts. Step 6 Follow the prompts displayed on your screen to complete the installation.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Configuration Information Viewing Configuration Information You can view configuration for IPM’s sources, targets, operations and collectors from the CiscoWorks homepage.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Configuration Information 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Configuration Information 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Configuration Information 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 Select Internetwork Performance Monitor > Reports > Configuration Reports > Collectors. The Collector Information Report page (Figure 5-13) appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Latency Data 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Latency Data 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 Select Internetwork Performance Monitor > Reports > Latency Reports > Daily on the CiscoWorks homepage. The Daily Latency Reports page (Figure 5-15) appears, with reports sorted by average latency.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Latency Data Figure 5-16 Daily IP-Echo Latency Summary Report Page Figure 5-17 Daily Services Latency Summary Report Page User Guide for Internetwork Performance Monitor OL-11291-01 5-19
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Latency Data Figure 5-18 Daily IP-Path Latency Summary Report Page Figure 5-19 Daily Latency Alert Report Page User Guide for Internetwork Performance Monitor 5-20 OL-11291-01
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Latency Data 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 Select Internetwork Performance Monitor > Reports > Latency Reports > Weekly on the CiscoWorks homepage. The Weekly Latency Reports page (Figure 5-20) appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Latency Data 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Jitter Data • Alert—To view monthly alert statistics. Alerts are collectors with errors. The Monthly Latency Alert Report page appears. 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.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Jitter Data Figure 5-22 Step 2 Daily Jitter Reports Page From the Daily Jitter Reports page, select one of the following options: • Jitter—To view daily jitter latency statistics for a specific date. The Daily Jitter Summary Report page (Figure 5-23) appears. • Alert—To view daily alert statistics for a specific date. The Daily Jitter Alert Report page appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Jitter Data 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 Select Internetwork Performance Monitor > Reports > Jitter Reports > Weekly. The Weekly Jitter Reports page (Figure 5-24) appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing Jitter Data 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 Select Internetwork Performance Monitor > Reports > Jitter Reports > Monthly. The Monthly Jitter Reports page (Figure 5-25) appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing HTTP Data 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 • Viewing Weekly HTTP Data • Viewing Monthly HTTP Data Viewing Daily HTTP Data You can view a daily summary of HTTP data for each HTTP collector on the IPM server.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing HTTP Data 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 Select Internetwork Performance Monitor > Reports > HTTP Reports > Weekly. The Weekly HTTP Reports page (Figure 5-28) appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Viewing HTTP Data 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 Select Internetwork Performance Monitor > Reports > HTTP Reports > Monthly. The Monthly HTTP Reports page (Figure 5-29) appears.
Chapter 5 Working With IPM From the CiscoWorks Homepage Accessing Software Updates and Additional Information 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.
A P P E N D I X A IPM FAQs and Troubleshooting Tips This appendix provides answers to the commonly asked IPM questions and also gives tips on troubleshooting specific IPM issues.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs • How much of the router’s memory do collectors in SA Agent consume? • How frequently can network performance measurements be taken? • When IPM collects the data from the SA Agent using SNMP, is this data averaged or summarized in any way? • What data collectors are available in IPM 2.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs Q. What workstation and network devices do I need to run IPM? A. IPM comprises several distinct pieces of functionality. • The IPM server application runs on Solaris 2.8, Solaris 2.9, and Windows 2000 Server and Windows 2000 Professional. • The IPM client application, including the user interface, runs on Solaris 2.8, Solaris 2.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs CLASSPATH is set to null, and you can run the IPM client as an applet. Also make sure that you set the environment variables NPX_PLUGIN_PATH and NPX_JRE_PATH to the correct values. For example in ksh, enter: NPX_PLUGIN_PATH=/opt/NSCPcom/j2re1_3_1/plugin/sparc NPX_JRE_PATH=/opt/NSCPcom/j2re1_3_1 For more detailed and current information on the environment variables to be set, refer the installation instructions of Netscape. export export Q.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs 4. IP Path Echo collectors are not supported on routers running Cisco IOS software release12.0(x)T. To create IP Path Echo collectors, you must upgrade the routers defined as source routers to Cisco IOS software release 12.1(1) or later. 5. Maximum number of collector depends on the available memory on the router.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs Q. Does a target device need to be a router that supports SA Agent? A. No. IPM supports targets as long as they are reachable through IP. These targets can be Web servers, PCs, printers, routers, switches, other network devices, or any other device with an IP address. IPM also supports SNA targets running the NSPECHO application provided with IPM.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs Q. How frequently can network performance measurements be taken? A. SA Agent generates several measurements per hour, then IPM polls the router once per hour and collects summarized statistics for that period. You can set the sampling interval for SA Agent for as often as every 10 seconds, but for optimal performance, we recommend a sample interval of at least 60 seconds (1 minute). This is the default value.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs Q. For UDP operations, what port numbers does IPM support? A. For UDP connections, valid port numbers are 7, and 1025 to 65535. If the target device is a Cisco router running version 12.1 or later of the Cisco IOS software, you can specify any port that is not well known (that is, you can specify any port number greater than 1024) to communicate with the SA Agent Responder, as long as someone is listening on that port on the target.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs Q. Can I use a firewall between IPM server and client? A. Yes, firewall can be used between the IPM Server and client. Following ports need to be opened for IPM to work across a firewall. TCP 1741 TCP 9088 TCP 1783 TCP 1784 TCP 443 (https) In addition, to use the IPM Standalone client across a firewall, the UseGKStandalone property in {IPM client install dir}\classes\IPM_ConfigMain.properties file must be set to Yes. Q.
Appendix A IPM FAQs and Troubleshooting Tips IPM FAQs The steps in the Active mode are: 1. The client opens a control channel (port 21) to the server and tells the server the port number to respond on. This port number is a randomly determined port greater than 1023. 2. The server receives this information and sends the client an acknowledgement “OK” (ack). The client and server exchange commands on this control connection. 3.
Appendix A IPM FAQs and Troubleshooting Tips Troubleshooting IPM Q. What does the “Responder On” field mean in Target Configuration? A. Rtr responder enables you to capture the jitter statistics, if you have enabled this feature on a device. You can enable this feature from the router by using this command: rtr responder Rtr responder was introduced from SAA Version 2.1.1. In SAA 2.1.1, there was no MIB variable to provide the status, so IPM captured the status as “Unknown”. From SAA version 2.2.
Appendix A IPM FAQs and Troubleshooting Tips Troubleshooting IPM Q. IPM is not working after I upgraded my IPM servers to Release 2.6. Why? A. When you upgrade IPM servers and clients, you must upgrade your IPM servers and clients to the same version and release level, such as Release 2.6. Q. When I make changes to IPM components, how can I force IPM to detect the changes now, without waiting for the next automatic poll? A. IPM typically polls source routers once every hour.
Appendix A IPM FAQs and Troubleshooting Tips Troubleshooting IPM You can continue using IPM as usual. If the attempt to reconnect to the server fails, IPM displays the following message: Reconnection to the server Failed. Please shutdown this client or restart the server. To recover, you must either shutdown the client and closer your browser window. Incase this condition persist even after restarting the client, you may have to IPM servers. Q.
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.
Appendix A IPM FAQs and Troubleshooting Tips Troubleshooting IPM • (Solaris only) If you change the host name of an IPM system, IPM no longer starts up or works correctly. To correct this problem, issue the ipm hostname command, then reboot the system. • (Windows only) To change the IPM Server hostname, you need to update the IPM_ConfigMain.properties, under IPMROOT\Server\htdocs\webclient directory. Q.
Appendix A IPM FAQs and Troubleshooting Tips Troubleshooting IPM Q. How do I access the database directly? A. Follow these steps on your machine: On Windows machine: cd install dir/Server/bin setIPMEnv isql –UDBA –P dbpassword On Solaris machine: csh cd install dir/CSCOipm/bin Source setIPMEnv isql –UDBA –P dbpassword Where install dir is the IPM installed directory. Q. I am not getting any response from SA Agent Responder, how do I resolve this problem? A.
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.
Appendix A IPM FAQs and Troubleshooting Tips Troubleshooting IPM User Guide for Internetwork Performance Monitor A-18 OL-11291-01
A P P E N D I X B IPM Command Reference This appendix provides a list of the IPM commands. Table B-1 shows the format of the commands and a description of the actions they perform. If you Telnet into a remote workstation and you do not set the DISPLAY variable to local display, you cannot use this command. See Setting the DISPLAY Variable in Solaris for details. Some IPM commands can be run only by the root user while the others can be run by the root user and also by members of the casusers group.
Appendix B Table B-1 IPM Command Reference IPM Commands (continued) Command Description ipm browserpath (Solaris only) Sets a user-defined IPM Web browser path, and verifies that the browser specified by the user exists. (Windows only) Resets the IPM Web browser path to the Internet Explorer path. If Internet Explorer is not found, resets to the Netscape Navigator path. If neither is found, clears the IPM Web browser path. You can use this command only if you have administrative privileges.
Appendix B IPM Command Reference Table B-1 IPM Commands (continued) Command Description ipm cw2ksetup install Identical to ipm cw2ksetup. Checks to see which files are installed, and installs additional files as necessary. Use this command to integrate IPM and CiscoWorks in the following instances: • You installed CiscoWorks after you installed IPM. • IPM and CiscoWorks are no longer integrated for some reason. You can use this command only if you have administrative privileges.
Appendix B Table B-1 IPM Command Reference IPM Commands (continued) Command Description ipm deltarg Removes a target device from the IPM database using command line prompts. If you try to delete a target and IPM issues an error message such as Could not delete the target, the cause might be one of the following: • The target is being used as a final target by one or more collectors. • The target is being used as an intermediate hop by one or more Path Echo collectors.
Appendix B IPM Command Reference Table B-1 IPM Commands (continued) Command ipm loadcoll Description filename Loads the specified collector seed file into the IPM database. You can use this command if you are a member of the casusers group. ipm loadsrc filename Loads the specified source seed file into the IPM database. You can use this command if you are a member of the casusers group. ipm loadtarg filename Loads the specified target seed file into the IPM database.
Appendix B Table B-1 IPM Command Reference IPM Commands (continued) Command Description ipm restart name Restarts the IPM Naming Server on the local host. You can use this command only if you have administrative privileges. You can use this command only on a Solaris machine. ipm restart pm Restarts all IPM server processes on the local host except the IPM database, and Naming Server. You can use this command only if you have administrative privileges.
Appendix B IPM Command Reference Table B-1 IPM Commands (continued) Command Description ipm start db Starts the IPM Database Server on the local host. You can use this command only if you have administrative privileges. ipm start name Starts the IPM Naming Server on the local host. You can use this command only if you have administrative privileges. Starts the IPM Process Manager on the local host. ipm start pm You can use this command only if you have administrative privileges.
Appendix B IPM Command Reference Output of ipm status Command Output of ipm status Command The following example shows the status information displayed when you use the ipm status command: ============================================================ IPM Server Version: 2.6.0.0 IPM Server Hostname: raest-w201 IPM Server Build Date: Fri Mar 29 15:34:08 IST 2004 ============================================================ IPM Database Server Already Running. IPM Naming Server Already Running.
Appendix B IPM Command Reference Output of ipm help Command ipm ipm ipm ipm ipm ipm ipm ipm ipm iosinfo -Display the IPM-IOS-Info file. services.conf -Display the services.conf file. console -Display the ipmConsoleLog.log file. viewlog -Display the ipmLoggerLog.x file with PAGER logger -Display the ipmLoggerLog.x file with tail -f. browserpath -Reset the path to the system Web Browser. servername -Reset the default server to connect to. export -Call the ipm export utility. ipm export help for more info.
Appendix B IPM Command Reference Output of ipm help Command ipm start name -Starts IPM Naming Server on the local host. ipm stop name -Stops IPM Naming Server on the local host. ipm start aging -Starts IPM Aging Server on the local host. ipm stop aging -Stops IPM Aging Server on the local host. ipm start pm -Starts IPM Process Manager on the local host. ipm stop pm -Stops IPM Process Manager on the local host. ipm debug [] -Starts a Message Log Display Client.
Appendix B IPM Command Reference Output of ipm export help Command ipm upgrade -remote upgrade IPM. ipm cleanreport - Clean HTML Reports older than n days. Output of ipm export help Command The following example shows the command syntax and help that is displayed when you use the ipm export help command: Note You must be logged in as the root user (Solaris) or administrator (Windows) to use export IPM data using the ipm export command.
Appendix B IPM Command Reference Output of ipm export help Command information about the specified collector. Information displayed same as displayed by the -c option with more readability. -t Display target configuration. If is omitted, display a list of all targets. If is specified, display information about the specified target. -o Display operation configuration. If is omitted, display a list of all operations.
Appendix B IPM Command Reference IPM Internal Commands IPM Internal Commands A list of internal commands is given below. It is recommended that you do not use these commands.
Appendix B IPM Command Reference IPM Internal Commands User Guide for Internetwork Performance Monitor B-14 OL-11291-01
A P P E N D I X C SA Agent Feature Mapping This appendix lists the IPM operations supported in different versions of SA Agent versions. This section also provides the procedure to verify whether SA Agent is running on your Cisco IOS software. Table C-1 lists the IPM operations supported in different versions of Cisco IOS releases: Table C-1 IPM Operations Mapped to SA Agent Version Operations1 SAA Version DLSw 2.1.0 DHCP 2 2.1.0 DNS 2.1.0 HTTP 2.1.0 IP PathEcho 2.1.0 ICMP Echo 1.0.
Appendix C SA Agent Feature Mapping Verify Your SA Agent Version On your device run the command: show rtr application The expected output on your device is: Version: 2.2.0 Round Trip Time MIB Max Packet Data Size (ARR and Data): 16384 Time of Last Change in Whole RTR: *17:23:28.
GLOSSARY A agent Process that resides in all managed devices and reports the values of specified variables to management stations. B browser GUI-based hypertext client application, such as Internet Explorer and Netscape Navigator, used to access hypertext documents and other services located on innumerable remote servers throughout the World Wide Web (WWW) and Internet. C Cisco IOS software Cisco Internetwork Operating System software.
Glossary dedicated line Communications line that is indefinitely reserved for transmissions, rather than switched as transmission is required. See also leased line. device See node. DHCP Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses dynamically so that addresses can be reused when hosts no longer need them. DLSw data-link switching.
Glossary H hop Term describing the passage of a data packet between two network nodes (for example, between two routers). See also hop count. hop count Routing metric used to measure the distance between a source and a destination. RIP uses hop count as its sole metric. See also hop. host Computer system on a network. Similar to the term node, except host usually implies a computer system, whereas node generally applies to any network system, including access servers and routers. See also node.
Glossary I ICMP Internet Control Message Protocol. Network layer Internet protocol that reports errors and provides other information relevant to IP packet processing. Documented in RFC 792. Internet Control Message Protocol See ICMP. Internet Protocol See IP. Internetwork Performance Monitor See IPM. interval See duration. IP Internet Protocol. Network layer protocol in the TCP/IP stack offering a connectionless internetwork service.
Glossary logical unit See LU. Loose Source Routing IP source routing in which the IP address of the next router can be one or more routers away (multiple hops). The alternative is strict source routing, in which the next router must be adjacent (single-hop). LU logical unit. Primary component of SNA, an LU is an NAU (network addressable unit) that enables end users to communicate with each other and gain access to SNA network resources. M Management Information Base See MIB.
Glossary NMVT Network Management Vector Transport. SNA message consisting of a series of vectors conveying network management specific information. NSPECHO VTAM application running in the mainframe to support the IPM and SA Agent solution. NSPECHO is used by IPM for measuring latency to the mainframe. O Set of parameters used in measuring network performance statistics.
Glossary RTR See SA Agent. RTT round-trip time. Time required for a network packet to travel from the source to the destination and back. RTT includes the time required for the destination to process the message from the source and generate a reply. The latency measurements taken by IPM and SA Agent are round-trip time latency measurements. RTTMON MIB round-trip time monitor management information base. Proprietary MIB created by Cisco to obtain and store round-trip time statistics.
Glossary SRB source-route bridging. Method of bridging originated by IBM and popular in Token Ring networks. In an SRB network, the entire route to a destination is predetermined, in real time, prior to transmission of the data to its destination. SSCP System Services Control Point. Focal point within an SNA network for managing network configuration, coordinating network operator and problem determination requests, and providing directory services and other session services for network end users.
Glossary Transmission Control Protocol/Internet Protocol See TCP/IP. trap Message sent by an SNMP agent to an NMS, console, or terminal indicating the occurrence of a significant event, such as a specifically defined condition or a threshold that has been reached. U UDP User Datagram Protocol. Connectionless transport layer protocol in the TCP/IP protocol stack.
Glossary V Virtual Telecommunications Access Method See VTAM. VTAM Virtual Telecommunications Access Method. Set of programs that control communication between LUs. VTAM controls data transmission between channel-attached devices and performs routing functions. See also LU. W World Wide Web See WWW. WWW World Wide Web. Large network of Internet servers providing hypertext and other services to terminals running client applications such as browsers. See also browser.
INDEX client, glossary definition A G-1 client/server architecture, overview adding clientaddr command, description a new collector 4-13 a new operation 4-9 disabling the IPM password on Windows systems 4-3 a new target device 4-5 on Solaris systems B-1 addtarg command, description 2-5 on Windows systems B-1 administrative password, changing agent, glossary definition 4-36 about 1-2 adding 4-9 4-13 configuration information, viewing ix defining 2-12 deleting 4-14 glossary defin
Index dbrestore start client B-3 debug B-3 start db delsrc B-3 start name deltarg B-4 start pm editcoll B-4 status editsrc edittarg B-13 ipaddrchg ipmcw2ksetup B-2 ipmcw2ksetup install ipmdbbackup B-3 B-3 B-4 B-4 B-5 mirror B-5 B-7 viewcoll B-7 viewlog B-7 viewsrc B-7 viewtarg B-7 name, glossary definition G-1 string, glossary definition G-1 collector, defining B-5 logger B-7 collectors adding 4-13 B-5 defined, viewing list of password B-5 deleting pmstatu
Index IPM database preferences changing file format for adding 4-24 4-26 4-23 IPM server process timeout values, setting new in Solaris Managed Interface settings message log window log control 4-37 log display 4-38 4-35 4-37 4-34 deleting 4-5 4-38 4-9 console command, description B-2 control command, description B-2 D 4-36 preferences defined, viewing list of 4-6 changing 4-11 4-8 file format setting thresholds and generating alerts working with 4-9 4-6 creating a seed fil
Index Device Center Integration, support in this release editcoll command, description 1-5 devices editsrc command, description glossary definition importing from Device and Credential Repository 5-7 operations, defining statistics, viewing G-2 network performance, measuring statistics, viewing 3-2 3-2 3-19 3-19 3-21 enhanced UDP (VoIP) network performance, measuring 3-39 statistics, viewing 3-4 3-41 UDP operation, defining 3-40 Differentiated Service Code Point (DSCP), support in this
Index host IPM client address, glossary definition glossary definition downloading G-3 G-3 node, glossary definition G-3 number, glossary definition 2-28 starting 2-2 as a standalone client G-3 hostname command, description exiting 5-10 2-3 from the CiscoWorks homepage B-4 HTTP ipm command, description data, viewing storing, about 5-27 monthly data weekly data B-1 IPM data 5-27 daily data configuration information, viewing 5-28 network performance, measuring operations, defi
Index troubleshooting log 5-6 version information 5-4 IP echo operations DSCP ipmdbbackup command, description 3-20 IP Precedence B-3 IPM password 3-20 3-20 IP path echo operations disabling on Windows systems DSCP 2-7 enabling 3-23 IP Precedence on Solaris systems TCP operations 2-5 on Windows systems DSCP 2-7 3-23 3-34 3-34 IPM server troubleshooting 5-2 IP Precedence 3-34 IPM console log, viewing 5-5 UDP operations 3-37 status, viewing DSCP 5-3 troubleshooting log f
Index loadcoll command, description loadsrc command, description about B-5 B-5 logical unit, glossary definition 1-2 viewing 2-17 DLSw 3-7 G-5 Loose Source Routing, glossary definition LU, glossary definition historical G-5 HTTP G-5 2-20 3-13 in real time IP M Managed Interface settings message log window 4-35 4-37 2-18 3-21 SNA 3-31 TCP 3-35 UDP 3-38 log control 4-37 UDP, enhanced log display 4-38 VoIP warning regarding Debug and Trace options MIB, glossary definition m
Index VoIP (enhanced UDP) deleting DefaultEcho 3-40 2-15 DefaultIpPathEcho 4-11 glossary definition G-6 list of defined, viewing 4-6 properties of, viewing thresholds, setting working with 4-9 client/server architecture 2-15 2-16 DefaultSnaLu0Echo 2-16 DefaultSnaLu2Echo 2-16 DefaultTelnet 1-3 key terms and concepts DefaultVideo 1-2 new features in this release DefaultVPN 1-5 Device and Credential Repository support Device Center Integration 1-5 1-5 Differentiated Service Code P
Index source interface on collector, support in this release S source-route bridging, glossary definition SA Agent G-7 source routers feature mapping C-1 glossary definition working with G-7 adding SA Agent Responder about 1-2 G-7 seed command, description B-6 4-15 4-20 sample target seed file 4-18 start aging command, description B-6 start client command, description B-6 B-6 start db command, description B-7 starting 4-16 IPM viewing seed file output files 4-20 servername co
Index historical troubleshooting information, viewing 2-20 in real time FAQs and troubleshooting tips 2-18 status command, description B-7 stop aging command, description B-7 stop clients command, description stop command, description B-7 stop name command, description stopping a collector 5-5 IPM server log 5-4 A-1 status information for IPM servers B-7 B-7 stop db command, description IPM consol log 5-2 troubleshooting log 5-6 version information 5-4 tshoot command, description
Index target information 5-14 configured source routers database preferences HTTP data 4-24 5-27 daily data 5-27 monthly data weekly data jitter data 4-2 5-29 5-28 5-23 daily data 5-23 monthly data weekly data 5-26 5-24 latency data 5-17 daily data 5-18 monthly data weekly data 5-22 5-21 operations, defined 4-6 properties of operations seed file output files 4-8 4-20 source router properties 4-2 source routers, configured target properties targets, defined 4-2 4-4 4-4 viewlog
Index User Guide for Internetwork Performance Monitor IN-12 OL-11291-01
