[an error occurred while processing this directive]

Support

Getting Started With IPM

Hierarchical Navigation

Downloads

 Feedback

Table Of Contents

Getting Started with IPM

Starting IPM

Starting IPM on Solaris

Starting IPM on Windows

Starting the IPM Server on Windows

Starting the IPM Client on Windows

Starting the IPM Client in a Web Browser

Implementing Client Security

Enabling the IPM Password on Solaris

Disabling the IPM Password on Solaris

Enabling the IPM Password on Windows

Disabling the IPM Password on Windows

Running Simultaneous IPM Sessions

Configuring the IPM Components

Defining a Source Router

Defining a Target

Defining a Collector

Viewing Network Performance Statistics

Viewing Network Performance Statistics in Real Time

Viewing Historical Network Performance Statistics

Understanding Next Range

Understanding Previous Range

Printing IPM Statistics

Exiting the IPM Client


Getting Started with IPM

This chapter provides information about starting the IPM application and configuring a collector to gather latency data. It includes the following major sections:

•Starting IPM

•Implementing Client Security

•Configuring the IPM Components

•Viewing Network Performance Statistics

•Printing IPM Statistics

•Exiting the IPM Client

Starting IPM

Since the IPM application is comprised of a server component and a client component, you must start both components to run the application. If the IPM server and client are installed on the same system, you can start the IPM server and client using a single command, or you can start them separately.

The following sections provide details for starting the IPM server and client:

•Starting IPM on Solaris

•Starting IPM on Windows

•Starting the IPM Client in a Web Browser

Starting IPM on Solaris

To start the IPM server and client on a Solaris system, enter: 

# cd /opt/CSCOipm/bin

# ./ipm

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.

To start only the IPM server on a Solaris system, enter: 

# cd /opt/CSCOipm/bin

# ./ipm start

Note To enter the ipm start command, you must be logged in as the root user, or your login must have administrator privileges.

To start only the IPM client on a Solaris system, enter: 

# cd /opt/CSCOipm/bin

# ./ipm start client

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

# ./ipm start client

To start the IPM client and connect to an IPM server other than the default server, enter: 

# cd /opt/CSCOipmClient/bin

# ./ipm start client server_name

where server_name is the Solaris or Windows NT system on which the IPM server is running.

When the IPM client starts, it displays the IPM Main window (Figure 2-1). The name of the system on which the IPM server is running appears in the title bar of the IPM main window.

Figure 2-1 IPM Main Window

When you start IPM for the first time, the IPM Main window contains no collectors. As you configure collectors, they appear in the window. Each collector is a combination of a configured source, a target, and an operation. For each collector, you specify parameters for gathering statistics and scheduling.

Starting IPM on Windows

This section describes how to start the IPM server on Windows, and how to start the IPM client on Windows 98, Windows NT, Windows 2000 Professional or Windows 2000 Server. It includes the following sections:

•Starting the IPM Server on Windows

•Starting the IPM Client on Windows

•Starting the IPM Client in a Web Browser

Starting the IPM Server on Windows

To start the IPM server and client on a Windows system, enter: 

cd c:\Program Files\Internetwork Performance Monitor\Server\bin

ipm

Note The default directory for installing IPM is C:\Program Files\Internetwork Performance Monitor\. If you installed IPM in a different directory, you must specify that directory instead of C:\Program Files\Internetwork Performance Monitor\.

To start only the IPM server on a Windows system, enter: 

cd c:\Program Files\Internetwork Performance Monitor\Server\bin

ipm start

Note To enter the ipm start command, you must be logged in as the administrator, or your login must have administrator privileges.

To start only the IPM client on a Windows system, enter: 

cd c:\Program Files\Internetwork Performance Monitor\Server\bin

ipm start client

If you installed the IPM client and IPM server on different Windows systems, you must enter the ipm start command from the c:\Program Files\Internetwork Performance Monitor\client\bin directory: 

cd c:\Program Files\Internetwork Performance Monitor\client\bin

ipm start 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.

When the IPM client starts, it displays the IPM Main window (Figure 2-1). The name of the system on which the IPM server is running appears 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 the window. Each collector is a combination of a configured source, a target, and an operation. For each collector, you specify parameters for gathering statistics and scheduling.

Starting the IPM Client on Windows

When you install the IPM client on a Windows 98, Windows NT, Windows 2000 Server or Windows 2000 Professional 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.

To start the IPM client on a Windows system and connect to the default IPM server:

Step 1 Make sure the IPM server to which you are connecting is currently running.

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 system and connect to any IPM server:

Step 1 Make sure the IPM server to which you are connecting is currently running.

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).

Starting the IPM Client in a Web Browser

You can run the IPM client as an applet from an Internet Explorer or Netscape Navigator Web browser if:

•You are running Solaris, Windows NT 4.0, Windows 98, Windows 2000 Professional or Windows 2000 Server.

•You have installed the Java plug-in 1.3 or higher. (For information about installing the Java plug-in, see the "Installing IPM on Windows" chapter of the Cisco Internetwork Performance Monitor Installation Guide.)

To start the IPM client as an applet in a Web browser:

Step 1 Make sure the IPM server to which you are connecting is currently running.

Step 2 From your browser, go to the URL for the IPM Web Server (for example, http://youripmserver:1744). The Web Server Home Page for the IPM Client Software appears (Figure 2-2).

Figure 2-2 IPM Server Home Page

Note If you do not have this URL, contact the system administrator who installed the IPM server software.

Step 3 Click Launch Secure Web Client or Launch Web Client. The Java applet loads and the Web client launches.

Implementing Client Security

To help protect the integrity of your IPM database, IPM provides client security, which enables you to define an IPM password. Thereafter, the username and password are required to access secure Web client functions, including:

•Using the ipm tshoot troubleshooting command

•Opening seed files

•Downloading the IPM client software from the IPM Server Home Page

•Launching the secure Web client from the IPM Server Home Page

Note The secure Web client enables the Edit menu option, providing full access to IPM functions, including adding, deleting, and editing source routers, targets, operations, and collectors, and starting and stopping collectors.

The non-secure Web client allows you to view statistical graphs, but you cannot modify, start, or stop IPM resources.

During a given Web browser session, IPM prompts you only once for the username and password. Thereafter, you can launch the Web client, download the client, view seed files from the Web, or use the ipm tshoot command without re-entering the username and password.

However, if you close and re-open the Web browser, you are prompted for the username and password the next time you launch the Web client, download the client, view seed files from the Web, or use the ipm tshoot command.

IPM on Solaris also provides a second password, independent of the first, which is required to start any IPM client from the command line on a Solaris system. If you enter the ipm start client command, IPM prompts you for the password before starting the client. (This password is not required when launching the secure Web client from the IPM Server Home Page.)

If at any time you change an IPM password, you must clear the Web browser's cache and start the Web browser again. It is the user's responsibility to control the IPM passwords.

The following sections provide details for setting up IPM client security:

•Enabling the IPM Password on Solaris

•Disabling the IPM Password on Solaris

•Enabling the IPM Password on Windows

•Disabling the IPM Password on Windows

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.

Step 3 IPM displays:

Password protection on Secure Client and Seed Files is Disabled. Enable? [y]

Type y and press Enter.

Step 4 IPM prompts you to enter a password. Enter a password and press Enter.

Step 5 IPM prompts you to confirm the password. Enter the password again and press Enter.

IPM displays:

Password protection on Secure Client and Seed Files is Enabled.

Use username 'ipm' and the chosen password to access IPM Secure Client and Seed Files.

Clear Browser cache and restart browser after changing IPM password.

The username (ipm) and password for the secure client, seed files, and ipm tshoot command are enabled.

IPM then displays:

Password protection on Client Launching is Disabled. Enable? [y]

Type y and press Enter.

Step 6 IPM prompts you to enter a password. Enter a password and press Enter.

Step 7 IPM prompts you to confirm the password. Enter the password again and press Enter.

IPM displays:

Password protection on Client Launching is Enabled.

Enter the password when launching Solaris client.

The IPM password for starting IPM clients on the Solaris system is enabled.

Disabling the IPM Password on Solaris

To disable 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 displays:

Password protection on Secure Client and Seed Files is Enabled. Disable? [y]

Step 3 Type Y and press Enter. The username and password for the secure client, seed files, and ipm tshoot command are disabled. All IPM users can access the secure Web client functions.

IPM then displays:

Password protection on Client Launching is Enabled. Disable? [y]

Step 4 Type Y and press Enter. The IPM password for starting IPM clients on the Solaris system is disabled. All IPM users can start clients.

Enabling the IPM Password on Windows

To enable an IPM password on Windows:

Step 1 Log in as the administrator.

Step 2 Enter: 

cd c:\Program Files\Internetwork Performance Monitor\Server\bin

ipm password

Note The default directory for installing IPM is c:\Program Files\Internetwork Performance Monitor. If you installed IPM in a different directory, specify that directory instead of c:\Program Files\Internetwork Performance Monitor.

IPM displays:

Password protection on Secure Client, Trouble Shooting, and viewing Seed Files via Web is Disabled. Enable? [y]

Step 3 Type Y and press Enter.

Step 4 IPM prompts you to enter a password. Enter a password and press Enter.

Step 5 IPM prompts you to confirm the password. Enter the password again and press Enter.

IPM displays:

Password protection on Secure Client, Trouble Shooting, and viewing Seed Files via Web is Enabled.

Use username `ipm' and chosen password to access IPM Secure Client, Trouble Shooting, and viewing Seed Files via Web.

Clear Browser cache and restart browser after changing IPM password.

The username (ipm) and password for the secure client, ipm tshoot command, and viewing seed files via the Web, are enabled.

Disabling the IPM Password on Windows

To disable the IPM password on Windows:

Step 1 Log in as the administrator.

Step 2 Enter: 

cd c:\Program Files\Internetwork Performance Monitor\Server\bin

ipm password

Note The default directory for installing IPM is c:\Program Files\Internetwork Performance Monitor. If you installed IPM in a different directory, specify that directory instead of c:\Program Files\Internetwork Performance Monitor.

IPM displays:

Password protection on Secure Client, Trouble Shooting, and viewing Seed Files via Web is Enabled. Disable? [y]

Step 3 Type Y and press Enter. The username and password are disabled. All IPM users can access the secure Web client functions.

Running Simultaneous IPM Sessions

IPM uses a client/server architecture that 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.

Note Running more than one IPM client on the same workstation can degrade the workstation's performance.

Configuring the IPM Components

To collect network performance metrics using IPM, you must define a collector in a source router. A collector is a definition of a source router, a target device, an operation, and a collector schedule.

To define a collector, complete the following tasks:

•Defining a Source Router

•Defining a Target

•Defining a Collector

Defining a Source Router

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 SA Agent feature.

The types of operations 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 about 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 1 Verify that the SNMP read community and write community strings are configured properly on the router.

Step 2 (Optional) 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.

For information about configuring SNMP on the source router, see the "Configuring Your Routers to Send SA Agent-Related Traps" section in the "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-3) is displayed. By default, Sources is selected in the navigation pane and the Source Configuration window appears within the Configuration window.

Figure 2-3 Configuration Window—Source Configuration

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. Do not include special characters such as ` @ $ ^ * ' '' & |. 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. Do not include special characters such as ` @ $ ^ * ' '' & |. 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 (for example, to use as an alias).

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 host name, 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 host name.

Step 10 Click OK to close the Configuration window and return to the IPM Main window.

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. For information about viewing or deleting source routers, see the "Working with Source Routers" section.

Note IPM uses SNMP for all configuration tasks. SNMP in turn generates RTR configuration statements, which you can see if you enter the show rtr configuration command. This is normal, expected behavior, and nothing to be concerned about.

Those RTR configuration statements typically appear only in the running configuration; they are not saved to the nonvolatile RAM (NVRAM) configuration. They affect only RTR-based functions, and have no other effect on router configuration.

Defining a 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 define a device as a target:

Step 1 Select Edit > Configuration from the IPM Main window (Figure 2-1). The Configuration window (Figure 2-3) appears.

Step 2 Click Targets. The Target Configuration window(Figure 2-4) appears within the Configuration window.

Figure 2-4 Target Configuration Window

Step 3 In the Target Type field, select the protocol type to be used with this target. The possible values are:

•IP—IP/ICMP Echo. Any IP-addressable device. Requires a destination IP address or host name.

•Cisco SAA Responder—Component embedded in a target Cisco router that is 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. This target type is required for Enhanced UDP operations measuring jitter, or if the target uses the SA Agent (to avoid potential connection problems).

You must enable the SA Agent Responder at the router using the rtr responder configuration command.

•SNA—SNA LU Type 0 or Type 2 connection to Cisco's NSPECHO mainframe host application, or SNA SCCP-LU Native Echo. Requires the PU name defined for the SNA PU connection to VTAM.

NSPECHO must be installed on the VTAM mainframe to be used as the target. The NSPECHO application is provided on the IPM product CD. For information about installing NSPECHO, see the "Installing NSPECHO to Measure SNA Response Times" chapter in the Cisco Internetwork Performance Monitor Installation Guide.

Step 4 Based on the protocol type you selected, take one of the following actions:

•If you selected IP, enter the host name or IP address of the target device in the Hostname or IP Address field.

•If you selected Cisco SAA Responder, enter the host name or IP address of the target device in the Hostname 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.

•If you selected SNA, enter the SNA host name of the target device in the PU Name field.

Step 5 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 (for example, to use as an alias).

Step 6 (Optional) In the Description field, enter a brief description of the target.

Step 7 Click Add. IPM adds the newly defined target to the IPM database.

Note If you specify an IP address instead of a host name, 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 host name.

Step 8 Click OK to close the Configuration window and return to the IPM main window.

If you must add a large number of targets to IPM, you can use the Target 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 targets to IPM, see the "Adding Components Using Seed Files" section. For information about viewing or deleting targets, see the "Working with Target Devices" section.

Defining a Collector

Defining a collector involves selecting a source router, a target, an operation, and a collector schedule.

To define a new collector:

Step 1 From the IPM Main window (Figure 2-1), select Edit > Configuration. The Configuration window (Figure 2-3) appears.

Step 2 Click Collectors. The Collector Configuration window (Figure 2-5) appears within the Configuration window.

Figure 2-5 Collector Configuration Window

Step 3 In the Name field, enter a name to assign to the collector. A common format for collector names is NewYorkToSanJoseIp.

Step 4 (Optional) In the Description field, enter a brief description of the collector.

Step 5 In the Collector Type field:

•Select Statistical to gather data and store it in the IPM database for future analysis. This is the default setting.

•Select Monitored to monitor for threshold violations and view data in real-time, but network performance data is not stored in the IPM database.

Step 6 Do one of the following tasks to define the schedule for the collector:

•To configure and start the collector at a later time, enable the On Demand option and go to Step 11.

•To specify when the collector starts, click Set Date. The Set Date Range window is displayed (Figure 2-6). By default, the collector schedule is set to start now and run forever.

Figure 2-6 Set Date Range Window

Step 7 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. If you select this option, you must specify the time based on a 24-hour clock, specify the year in the format YYYY, select the month from the month list, and select the date from the calendar. The default setting for On Date is the current date and time when the collector is being defined.

Note If the date selected 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 options are:

•Forever—Allows the collector to run continuously until you stop it by selecting Edit > Stop from the IPM Main menu.

•Duration—Stops the collector after the specified length of time has expired. You can specify the duration in any combination of days, hours, and minutes.

•On Date—Stops the collector at the specified date and time. If you select this option, you must specify the time based on a 24-hour clock, specify the year in the format YYYY, select the month from the month list, and select the date from the calendar. The default end date is exactly one day from the current date and time.

Step 9 Click OK. The specified start time and end time 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, DHCP, or HTTP 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 is provided. The predefined operations are described in Table 2-1.

Table 2-1 Predefined Operations 

Operation
Description

DefaultDHCP

Measures end-to-end latency for acquiring a new DHCP lease.

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 Payload is set to 64.

DefaultDNS

Measures end-to-end latency for DNS lookups. DNS Name Server is set to the IP address of the DNS server configured on the system on which the IPM server is running. The DNS Lookup Name is set to the name of the host to look up for the DNS request.

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.

DefaultHTTPConn
(was called DefaultHTTP prior to IPM Release 2.2)

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.

Note that DefaultHTTPConn is not a true HTTP operation, it is a TCP Connect operation. IPM does not provide a true default HTTP operation; you must create your own. See the "Measuring Network Performance for HTTP" section for information about creating a new HTTP operation.

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 Payload is set to 64 bytes.

DefaultIpPathEcho

Measures hop-by-hop latency in an IP network. Packet Priority is set to 0 (no priority), Request Payload is set to 64 bytes, Maximum Paths is set to 5, Maximum Hops is set to 15, and sample interval is set to 180 seconds.

DefaultNNTP

Measures the time to perform a TCP connect operation directed at the selected target on the standard Network News Transport Protocol (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 Post Office Protocol v.3 (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 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. Protocol is set to SNA LU0, Mode Name is set to INTERACT, and Response Payload 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 Payload 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 Payload is set to 64 bytes, and Target Port is set to 7.

DefaultVideo

Measures latency and jitter for Video traffic. Packet Priority is set to 0 (no priority), Request Payload is set to 1024 bytes, Packet Interval is set to 20 milliseconds, Number of Packets is set to 20, Jitter Threshold is set to 250, and Target Port is set to 50505.

DefaultVPN

Measures latency and jitter for VPN traffic. Packet Priority is set to 0 (no priority), Request Payload is set to 1024 bytes, Packet Interval is set to 20 milliseconds, Number of Packets is set to 20, Jitter Threshold is set to 250, and Target Port is set to 2000.

Default160ByteVoice

Measures latency and jitter for Voice over IP traffic. Packet Priority is set to 5, Request Payload is set to 160 bytes, Packet Interval is set to 20 milliseconds, Number of Packets is set to 10, Jitter Threshold is set to 250, and Target Port is set to 16400.

Default60ByteVoice

Measures latency and jitter for Voice over IP traffic. Packet Priority is set to 5, Request Payload is set to 60 bytes, Packet Interval is set to 20 milliseconds, Number of Packets is set to 10, Jitter Threshold is set to 250, and Target Port is set to 16400.


Note that you can define one or more new operations to fit your needs. For information about defining, modifying, or deleting operations, see the "Working with Operations" section.

Note Although you cannot modify the default operations, you can use them as templates for creating your own operations.

Note IPM does not provide a predefined HTTP operation. Therefore, before you create an HTTP collector, you must first create an HTTP operation. See the "Adding a New Operation" section for more information.

Step 13 Click Add. IPM adds the newly defined collector to the IPM database.

Step 14 If you selected a DNS operation, the Extra DNS Settings window appears (Figure 2-7).

Step 15 Enter a DNS Lookup Name (the name of the host to look up for the DNS request) and click OK.

Figure 2-7 Extra DNS Settings Window

Step 16 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.

If you must add a large number of collectors to IPM, you can use the Collector 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 collectors to IPM, see the "Adding Components Using Seed Files" section. For information about viewing or deleting collectors, see the "Working with Collectors" section.

Viewing Network Performance Statistics

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:

•Viewing Network Performance Statistics in Real Time

•Viewing Historical 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. That is, when a real time graph reaches 1000 points of data, as the most recent points are added to the right side of the graph the earliest points disappear from the left side. If you watch the last data point at the far right of the graph, you can see it change at the end of a sampling interval.

For example, if your sampling interval is once every 60 seconds, in less than a day the real time graph will have reached 1000 points of data. After that time, you can see the last data point on the right of the graph change every 60 seconds.

To view statistics in real time:

Step 1 From the IPM Main window (Figure 2-1), select the collector to be viewed.

Step 2 Select View > Real Time. The Real Time Statistics window (either Figure 2-8 or Figure 2-9) appears.

Figure 2-8 Real Time Statistics Window

Figure 2-9 Jitter Real Time Statistics Window

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.

Table 2-2 Real Time Statistics Window Options

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 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, then drag left or right to go backward or forward, or drag up or down to shift the x-axis of the graph.


Viewing Historical Network Performance Statistics

To view statistics gathered over an historical monitoring period:

Step 1 From the IPM Main window (Figure 2-1), 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.

Figure 2-10 Statistics Data Filter Window

In this window, 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. The window displays the currently defined start date and end date.

Step 3 To change the date range, click the Calendar icon. The Set Date Range window appears (Figure 2-6). Specify a new start date, a new end date, or both, and click OK. The start time and end time you specified for the collector for viewing statistics is displayed.

For more information about changing the date range, see the "Defining a Collector" section.

Step 4 To make graphs easier to read, IPM provides optional popup labels for historical graphs. (Popup labels are always on for real-time graphs.)

When you turn on popup labels for a graph, you can roll the cursor over a collection point on the graph and see a popup label containing key information for that point, such as the exact latency value.

To turn on popup labels for a graph, select the Show Popup Labels checkbox. To turn off popup labels, clear the checkbox.

Step 5 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.

By default, IPM automatically selects the option that best matches the amount of data currently in the IPM database for the selected collector. For additional information about how IPM gathers and calculates hourly, daily, weekly, and monthly data, see the "Setting IPM Database Preferences" section.

Step 6 Click OK. The Historical Statistics window (Figure 2-11, Figure 2-12, or Figure 2-13) appears.

Figure 2-11 Historical Statistics Window—IP Echo Collector

Figure 2-12 Historical Statistics Window—IP Path Echo Collector

Figure 2-13 Historical Statistics Window—Enhanced UDP Collector

Note 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.

Figure 2-14 Historical Statistics Window—Multi-Collector Graph

Table 2-3 describes the actions you can perform in the Historical Statistics window.

Table 2-3 Historical Statistics Window Options 

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 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, then drag left or right to go backward or forward, or drag up or down to shift the x-axis of the graph.

Print or save the graph.

Select File > Print to print or save the graph.

For more information, see the "Printing IPM Statistics" section.

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.

If for some reason the poll fails and new statistics are not collected, the following error message appears. 

Demand Poll Failed, make sure router is 
available.

Change settings in the Statistics Data Filter window.

Select View > Filter Data to change the time period and granularity of the graphs.

Display statistics for the next time period.

Select View > Next Range. The graphs are updated to reflect the new range.

For more information, see the "Understanding Next Range" section.

Display statistics for the previous time period.

Select View > Prev Range. The graphs are updated to reflect the new range.

For more information, see the "Understanding Previous Range" section.

Hide the legend bar at the bottom of each graph.

Select View > Hide Legend.

Show the legend bar at the bottom of each graph.

Select View > Show Legend.

Show combined statistics in one graph for all paths in the path list, or all hops in a selected path (Path Echo collectors only).

Select Path List, or select a specific path, then select View > Show Combined. A single graph is displayed showing combined statistics for all the paths in the path list (up to 128 paths), or all the hops in the hop list (up to 25 hops) for the selected path. The combined graph shows only average statistics.

If a path has no data available, IPM displays (No Data) for that path in the right side of the window.

If a path never reaches its target, it is an invalid path, and IPM displays (No Target) for that path in the right side of the window.

Show separate statistics in one or more graphs for all paths in the path list, or all hops in a selected path (Path Echo collectors only).

Select Path List, or select a specific path, then select View > Show Separate. Multiple graphs are displayed, one for each path in the path list, or hop in the hop list for the selected path. Each graph shows minimum, maximum, and average statistics.

If a path has no data available, IPM displays No Data Available for that path instead of a graph.


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.

•The new end time might be later than the actual current time, even though you are displaying historical statistics.

•If View > Next Range is grayed out, it means the new range falls after the collector was stopped.

•If you select View > Next Range and IPM displays the following error message: 

Could not get operation stats from the server for the given time 
range, chart will be empty.

This means there was no statistical data available for the next time period. The IPM server or source router might have been down during that time period, and no statistical data was collected. When you click OK, IPM displays blank graphs for the next time period.

•If you select View > Next Range for a Path Echo collector and IPM displays the following error message: 

No Path List could be found. Forcing a demand poll. Wait a few minutes 
and try again.

This means there was no statistical data available for the next time period. The IPM server or source router might have been down during that time period, and no statistical data was collected. When you click OK, IPM still displays graphs for the current time period.

Understanding Previous Range

Keep the following points in mind when you select View > Prev Range:

•The new start time is the current start time, minus the current duration. The new end time is the current start time.

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 10 and the new end time is midnight April 11.

•If View > Prev Range is grayed out, it means the new range falls before the collector was started.

•If you select View > Prev Range and IPM displays the following error message: 

Could not get operation stats from the server for the given time 
range, chart will be empty.

This means there was no statistical data available for the previous time period. The IPM server or source router might have been down during that time period, and no statistical data was collected. When you click OK, IPM displays blank graphs for the previous time period.

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.

•Saving the currently displayed statistical graphs to a file.

Note For security reasons, you cannot print or save statistical graphs if you are running IPM as an applet in a Web browser. The Print button and File > Print menu option are not available.

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.

Step 2 Click the Print button (from a Real Time Statistics window) or select File > Print (from a Historical Statistics window). The Print Dialog window (Figure 2-15) is displayed.

Note The printing options require you to define a printer on your system. If you click the Print button or select the File > Print menu option and the Print Dialog window does not appear, make sure you have defined a printer on your system.

Figure 2-15 Print Dialog Window

Step 3 Enter data in the following fields:

•Copies—Specify the number of copies you want to print. The default setting is 1 copy.

•Print to—Specify whether you want the data printed to a printer, or saved to a file. If printing to a printer, specify the name of the printer. If saving to a file, specify the directory and filename.

•Paper Size—Specify whether you want the data printed on Letter, Legal, Executive, or A4 paper. The default setting is Letter.

•Orientation—Specify whether you want the data printed in a Landscape or Portrait orientation on the page. The default setting is Portrait.

Step 4 Click Print. IPM sends the output to the printer or file you specified.

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-1), 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.

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. Collectors defined to run forever, 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.

Collectors remain in the IPM database until you do one of the following:

•Delete them from the IPM server

•Delete them from the source routers using the ipm rmcoll command

[an error occurred while processing this directive]