|
|
This chapter provides information on starting the IPM application and configuring a collector to gather latency data. It includes the following major sections:
The following sections provide details for starting the IPM server and client:
To start the IPM server and client on a Solaris workstation, enter the following commands:
# cd /opt/CSCOipm/bin # ./ipm
 |
Note The default directory for installing IPM is /opt. If you installed IPM in a different directory, then you must specify that directory instead of /opt. |
To start just the IPM server on a Solaris workstation, enter the following commands:
# cd /opt/CSCOipm/bin # ./ipm start server
|
Note To issue the ipm start server command, you must be logged in as the root user. |
To start just the IPM client on a Solaris workstation, enter the following commands:
# cd /opt/CSCOipm/bin # ./ipm start client
If you installed the IPM client on a different Solaris workstation from the default IPM server, you must issue the ipm start command from the /opt/CSCOipmClient/bin directory. To start the IPM client on a different Solaris workstation from the default IPM server, enter the following commands:
# cd /opt/CSCOipmClient/bin # ./ipm start client
To start the IPM client and connect to a different IPM server than the default server, enter the following commands:
# cd /opt/CSCOipmClient/bin # ./ipm start client server_name
Where server_name is the Solaris workstation where the IPM server is running.
When the IPM client starts, it displays the IPM Main window (Figure 2-1). The name of the workstation where the IPM server is running is displayed in the title bar of the IPM Main window.
When you start IPM for the first time, the IPM Main window contains no collectors. As you configure collectors, they are displayed in this window. Each collector is a combination of a configured source, a target, and an operation. For each collector, you specify parameters for gathering statistics, generating event notifications, and scheduling.
When you install the IPM client on a Windows 95, Windows 98, or Windows NT workstation, the installation program adds two icons to your desktop: one icon for connecting to the IPM server that you specified during installation and one icon for connecting to any IPM server.
To start the IPM client on a Windows workstation and connect to the default IPM server:
Step 2 Double click on the IPM client icon on your desktop. The IPM client starts and displays the IPM Main window (Figure 2-1).
To start the IPM client on a Windows workstation and connect to any IPM server:
Step 2 Double-click on the IPM Any Server icon on your desktop. A prompt is displayed asking you for the name of the IPM server to which you want to connect.
Step 3 Type the IPM server name and click OK. The IPM client starts and displays the IPM Main window (Figure 2-1).
|
Note Running multiple IPM clients on the same network and connecting to the same IPM server might impact the server's performance. For a large network, use multiple IPM clients connected to multiple IPM servers. |
To define a collector, complete the following tasks:
IPM source routers are the routers from which packets are sent to measure and store statistical data, including network latency, jitter, availability, packet loss, and errors. Each source router must contain the Cisco IOS software SAA feature.
The types of operations that you can use are determined by the version of the Cisco IOS software running on the source router. IPM automatically checks the Cisco IOS software version on the router and limits the creation of operations to those supported by the source router. For information on the recommended versions of Cisco IOS software to use with IPM, see the "Cisco IOS Software Requirements" section of the Cisco Internetwork Performance Monitor Installation Guide.
To define a new source router:
Step 2 (Optional) If you want to receive traps at your network management system (NMS), verify that the router is configured to send SAA-generated traps to your NMS.
For information on configuring SNMP on the source router, see the "Configuring Your Routers to Send SAA-Related Traps" section in "Preparing to Install" chapter of the Cisco Internetwork Performance Monitor Installation Guide.
Step 3 From the IPM Main window (Figure 2-1), select Edit > Configuration. The Configuration window (Figure 2-2) is displayed. By default Sources is selected in the navigation pane and the Source Configuration window is displayed within the Configuration window.
Step 4 In the Hostname or IP Address field, enter the host name or IP address of the router to use as the source for network performance measurements. This host name can be from 1 to 64 characters in length.
Step 5 In the Read Community field, enter the SNMP community name for read access to the information maintained by the SNMP agent on the source router. This value can be from 1 to 32 characters in length. The default value is public.
Step 6 In the Write Community field, enter the SNMP community name for write access to the information maintained by the SNMP agent on the source router. This value can be from 1 to 32 characters in length.
Step 7 In the Name field, enter a name to assign to the source router. By default, this field matches the Hostname or IP Address field, but you can modify the name.
Step 8 (Optional) In the Description field, enter a brief description of the source router.
Step 9 Click Add. IPM attempts to locate the router and determine whether or not it is SNMP enabled with the correct community string. If the router is successfully located, IPM adds it to the IPM database. If IPM cannot reach the router, IPM displays an error message.
|
Note If you specify an IP address instead of a hostname and that IP address cannot be resolved by standard address resolution techniques, then IPM assumes that the IP address is valid and does not resolve to a hostname. |
Step 10 Click OK to close the Configuration window and return to the IPM Main window.
For information on using a seed file to add source routers to IPM, see the "Adding Source Routers Using a Seed File" section. For information on modifying or deleting source routers, see the "Working with Source Routers" section.
IPM targets are destination devices for which you want to gather data. A target can be any IP-addressable device, a Cisco SAA responder, or an SNA host.
To define a device as a target:
Step 2 Click Targets. The Target Configuration window (Figure 2-3) is displayed within the Configuration window.
Step 3 In the Target Type field, select the protocol type to be used with this target. The possible values are:
Step 4 If the target type is IP, enter the host name or IP address of the target device in the Host Name or IP Address field.
Step 5 If the target type is Cisco SAA Responder, enter the host name or IP address of the target device in the Host Name or IP Address field. In the Read Community field, enter the SNMP community name for read access to the information maintained by the SNMP agent on the target device. The default value is public.
Step 6 If the target type is SNA, enter the SNA host name of the target device in the PU Name field.
Step 7 In the Name field, enter a name to assign to the target. By default, this field matches the Hostname, IP Address, or PU Name field, but you can modify the name.
Step 8 (Optional) In the Description field, enter a brief description of the target.
Step 9 Click Add. IPM adds the newly defined target to the IPM database.
|
Note If you specify an IP address instead of a hostname and that IP address cannot be resolved by standard address resolution techniques, then IPM assumes that the IP address is valid and does not resolve to a hostname. |
Step 10 Click OK to close the Configuration window and return to the IPM Main window.
For information on using a seed file to add targets to IPM, see the "Adding Targets Using a Seed File" section. For information on modifying or deleting targets, see the "Working with Target Devices" section.
Defining a collector involves selecting a source router, a target, an operation, and a collector schedule.
|
Note After you configure a collector, you cannot change its attributes. |
To define a new collector:
Step 2 Click Collectors. The Collector Configuration window (Figure 2-4) is displayed within the Configuration window.
Step 3 In the Name field, enter a name to assign to the collector.
Step 4 (Optional) In the Description field, enter a brief description of the collector.
Step 5 In the Collector Type field, select the Statistical option to gather data and store it in the IPM database for future analysis. If the Monitored option is selected, you can monitor for threshold violations and view data in real-time, but network performance data is not stored in the IPM database. By default the Collector type is set to collect statistics.
Step 6 Do one of the following tasks to define the schedule for the collector:
Step 7 Specify a start date for the collector. The following options are available:
|
Note If the date selected9 is in the future, then the collector's status in the IPM Main window is SCHEDULE_PENDING. At the scheduled start time, IPM configures the collector in the router and the status is reflected in the IPM Main window. |
Step 8 Specify an end date for the collector. The following options are available:
Step 9 Click OK. The start time and end time that you specified are defined for the collector.
Step 10 From the Sources list, select the router to designate as the source router for initiating test packets. If you already know the name of the router, start typing the name in the Search field and the cursor moves to the matching router in the Sources list.
Step 11 From the Targets list, select the device to designate as the target. If you already know the name of the target, start typing the name in the Search field and the cursor moves to the matching target in the Targets list.
|
Note If you select a DNS or DHCP operation, the Targets list is disabled because these operations do not use targets. |
Step 12 From the Operations list, select the operation to use for this collector. If you already know the name of the operation, start typing the name in the Search field and the cursor moves to the matching operation in the Operations list.
When you install IPM, a group of predefined operations are provided. The predefined operations are described in Table 2-1.
| Operation | Description |
|---|---|
DefaultDHCP | Measures end-to-end latency using a DHCP packet. |
DefaultDLSw | Measures end-to-end latency in a network which uses DLSw to route SNA traffic over an IP network. Request size is set to 64 and response size is set to 64. |
DefaultDNS | Measures end-to-end latency for DNS traffic. DNS server name is set to the IP address of the DNS server configured on the system where the IPM server is running and the DNS lookup name is set to the hostname of the system where the IPM server is running. |
DefaultFTP | Measures the time to perform a TCP connect operation directed at the selected target on the standard FTP port 21. Packet priority is set to 0 (no priority) and target port is set to 21. |
DefaultHTTP | Measures the time to perform a TCP connect operation directed at the selected target on the standard HTTP port 80. Packet priority is set to 0 (no priority) and target port is set to 80. |
DefaultIpEcho | Measures end-to-end latency in an IP network. Protocol is set to IP, packet priority is set to 0 (no priority), and request size is set to 64 bytes. |
DefaultIpPathEcho | Measures hop-by-hop latency in an IP network. Packet priority is set to 0 (no priority), request size is set to 64 bytes, maximum number of paths is set to 5, maximum number of hops is set to 28, and sample interval is set to 120 seconds. |
DefaultNNTP | Measures the time to perform a TCP connect operation directed at the selected target on the standard NNTP port 119. Packet priority is set to 0 (no priority) and target port is set to 119. |
DefaultPOP3 | Measures the time to perform a TCP connect operation directed at the selected target on the standard POP3 port 110. Packet priority is set to 0 (no priority) and target port is set to 110. |
DefaultSMTP | Measures the time to perform a TCP connect operation directed at the selected target on the standard 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. Protocol is set to SNA LU0, mode name is set to INTERACT, and response size is set to 64 bytes. |
DefaultSnaLu2Echo | Measures end-to-end latency in an SNA network using LU2. Protocol is set to SNA LU2, mode name is set to D4A32782, and response size is set to 64 bytes. |
DefaultSnaSSCPEcho | Measures end-to-end latency in an SNA network using SSCP protocol. Protocol is set to SNA SSCP. |
DefaultTelnet | Measures the time to perform a TCP connect operation directed at the selected target on the standard Telnet port 23. Packet priority is set to 0 (no priority) and target port is set to 23. |
DefaultUDPEcho | Measures end-to-end latency for a UDP datagram. Packet priority is set to 0 (no priority), request size is set to 64 bytes, and target port is set to 7. |
DefaultVPN | Measures latency and jitter for VPN traffic. Packet priority is set to 0 (no priority), request size is set to 1024 bytes, packet interval is set to 20 milliseconds, number of packets is set to 20, and target port is set to 2000. |
Default160ByteVoice | Measures latency and jitter for Voice over IP traffic. Packet priority is set to 5, request size is set to 160 bytes, packet interval is set to 20 milliseconds, number of packets is set to 10, and target port is set to 16400. |
Default60ByteVoice | Measures latency and jitter for Voice over IP traffic. Packet priority is set to 5, request size is set to 60 bytes, packet interval is set to 20 milliseconds, number of packets is set to 10, and target port is set to 16400. |
You can also define one or more new operations to fit your needs. Although the default operations cannot be modified, you can use them as templates for creating your own operations. For information on defining, modifying, or deleting operations, see the "Working with Operations" section.
Step 13 Click Add. IPM adds the newly defined collector to the IPM database.
Step 14 Click Close to close the Configuration window and return to the IPM Main window. The newly defined collector has been added to the list of collectors in the IPM Main window.
For information on using a seed file to add collectors to IPM, see the "Adding Collectors Using a Seed File" section. For information on viewing or deleting collectors, see the "Working with Collectors" section.
As your collectors begin to gather network performance statistics and store the information in the IPM database, you can view the resulting data.
IPM provides two methods for reviewing network performance statistics:
The Real Time Statistics window allows you to view statistics for an active collector as the data is being collected. This data is only displayed in real time, it is not stored in the IPM database.
To view statistics in real time:
Step 2 Select View > Real Time. The Real Time Statistics window (Figure 2-6 and Figure 2-7) is displayed.
Statistics are displayed as soon as the frequency interval elapses. Data points will be added to the graph for each interval that the statistics are measured for the selected collector.
To view statistics gathered over an historical monitoring period:
Step 2 Select View > Statistics. The Statistics Data Filter window (Figure 2-8) is displayed.
In this window, you specify the time period for which you want to view statistics. You can view statistics for all or part of the time that the data was collected. When this window is displayed, by default the start date is set to the starting date for the collector and the end date is set for one day from the start date.
Step 3 To change the date range, click the Calendar icon. The Set Date Range window is displayed (Figure 2-5).
Step 4 Specify a start date for the statistics that you want to view. The following options are available:
Step 5 Specify an end date for the statistics that you want to view. The following options are available:
Step 6 Click OK. The start time and end time that you specified are defined for the collector.
Step 7 In the Statistics 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.
By default, IPM automatically selects the option that best matches the amount of data currently in the IPM database for the selected collector.
Step 8 Click OK. The Historical Statistics window (Figure 2-9 and Figure 2-10) is displayed.
Table 2-2 describes the actions that you can perform from the Historical Statistics window.
| Action | Key Combination |
|---|---|
Zoom in on a specific point on the graph. | Press Shift and click a point on the graph. |
Zoom in on a specific area of the graph. | Press Shift and drag and click on an area of the graph. Release the mouse button and the graph zooms in on the area that you selected. |
Zoom out to the graph's original view. | Click anywhere on the graph. |
Shift the x-axis or y-axis of the graph through the data. | Press Ctrl and click a point on the graph and drag left or right to go backward or forward or drag up or down to shift the x-axis of the graph. |
You can display statistics in graphical and tabular format in the Real Time Statistics window and in the Historical Statistics window.
To print the data:
Step 2 Select File > Print. The Print Dialog window (Figure 2-11) is displayed.
Step 3 Enter data in the following fields:
Step 4 Click Print. IPM sends the output to the printer or file that you specified.
When you are finished monitoring network performance statistics, you can exit the IPM client by completing the following steps:
Step 2 Click Yes to close the IPM client application.
Collectors that were still running when you closed the IPM client will continue to run and gather statistics until they reach the end date specified in the collector configuration. For collectors defined to run forever, they will continue to run and gather statistics until you stop them.
To shut down the IPM servers completely, use the ipm stop command. To stop gathering statistics, stop the collectors before exiting the IPM client. When you stop a collector, the gathered data for that collector is still available for viewing.
|
Note Collectors remain in the database until you uninstall the IPM software from the workstation or directly delete the collectors from the IPM server. |
Posted: Sun Apr 16 12:58:09 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.