User Guide for Internetwork Performance Monitor 2.6 (With LMS 2.5.1) - Modifying IPM Components [CiscoWorks Internetwork Performance Monitor]

Table Of Contents

Modifying IPM Components

Working With Source Devices

Viewing a List of Configured Source Devices

Viewing Source Properties

Adding a New Source Device

Deleting Source Devices

Working With Target Devices

Viewing a List of Defined Targets

Viewing Target Properties

Adding a New Target

Deleting Targets

Working With Operations

Viewing a List of Defined Operations

Viewing Operation Properties

Adding a New Operation

Setting Thresholds and Generating Alerts

Deleting Operations

Working With Collectors

Viewing a List of Defined Collectors

Viewing a Collector State Summary

Viewing Collector Properties

Adding a New Collector

Stopping Collectors

Deleting Collectors

Adding Components Using Seed Files

Creating a Seed File

Seed File Syntax

Sample Source Seed File

Sample Target Seed File

Sample Collector Seed File

Loading Components From a Seed File

Viewing Seed File Output Files

Changing IP Addresses

Setting the Baseline

Setting IPM Database Preferences

Displaying the Current Database Preferences

Changing the Database Preferences

Database Preferences File Format

Setting SNMP Timeout and Retry Environment Variables

Setting SNMP Environment Variables in Solaris

Setting SNMP Environment Variables in Windows

Setting New IPM Server Process Timeout Values

Setting Server Timeout Values in Solaris

Setting Server Timeout Values in Windows

Setting the DISPLAY Variable in Solaris

Backing Up or Restoring the IPM Database

NVRAM Settings

Managed Source Interface Settings

Changing Administrative Password

Changing IPM Database Password

Working With Message Log Window

Log Control

Log Display

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.

This chapter contains the following major sections:

•Working With Source Devices

•Working With Target Devices

•Working With Operations

•Working With Collectors

•Adding Components Using Seed Files

•Changing IP Addresses

•Setting IPM Database Preferences

•Setting SNMP Timeout and Retry Environment Variables

•Setting New IPM Server Process Timeout Values

•Setting the DISPLAY Variable in Solaris

•Backing Up or Restoring the IPM Database

•NVRAM Settings

•Changing Administrative Password

•Changing IPM Database Password

•Working With Message Log Window

Working With Source Devices

IPM source is a device from which you initiate operations for measuring network performance statistics. Each source must contain the SA Agent feature and an SNMP agent.

Information about working with source is provided in the following subsections:

•Viewing a List of Configured Source Devices

•Viewing Source Properties

•Adding a New Source Device

•Deleting 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. From this window, you can add a new source router, change the configuration of an existing source, or delete an existing source.

Viewing Source Properties

The Source Properties window allows you to view the properties of a defined source.

To view source properties:

Step 1 From the IPM Main Window, select a collector that uses the source.

Step 2 Select View > Properties.

The Properties Viewer window appears. By default, the Collector Properties window appears within the Properties Viewer window.

Step 3 Click Source.

The Source Properties window (Figure 4-1) appears.

Figure 4-1 Source Properties Window

For information about these fields, see the "Source Properties Window" topic in the Online help.

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.

For information about configuring SNMP on the source, see the "Configuring Your Routers to Send SA Agent-Related Traps" section in the "Preparing to Install" chapter of the Installation Guide for Internetwork Performance Monitor.

For information about adding a new source device, see Defining a Source Device

Deleting Source Devices

You can delete source devices you no longer need. You can delete more than one source device at a time.

Note If a source device has been configured as part of one or more collectors, you must delete the collectors before you can delete the source device.

To delete a source device:

Step 1 From the Source Configuration window (Figure 2-3), select the source device or sources you want to delete.

Step 2 Click Delete.

The confirmation box appears,

Step 3 Click Yes.

The selected source routers are deleted from the IPM database.

Working With Target Devices

IPM targets are destination devices for which you want to gather network performance statistics. A target can be any IP-addressable device, a Cisco device running the SA Agent Responder, or an SNA host.

Note The SA Agent Responder is supported only in Cisco IOS 12.1(2)T or later. We strongly recommend that you use software release 12.1 or later.

Information about working with target devices is provided in the following subsections:

•Viewing a List of Defined Targets

•Viewing Target Properties

•Adding a New Target

•Deleting Targets

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.

The Target Configuration window displays a list of all devices defined as IPM targets. From this window, you can define a new target, modify an existing target, or delete a target.

Viewing Target Properties

The Target Properties window allows you to view the properties of a defined target.

To view target properties:

Step 1 From the IPM Main Window, select a collector that uses the target device.

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

The Target Properties window (Figure 4-2) appears.

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. You can delete more than one target at a time.

After you have associated a target with a collector, you cannot delete the target without first deleting the collector with which it is associated.

To delete a target:

Step 1 From the Target Configuration window (Figure 2-4), select the target or targets you want to delete.

Step 2 Click Delete.

The confirmation box appears,

Step 3 Click Yes.

The selected targets are deleted from the IPM database.

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. On the IPM Main Window, look for the target's name in the Target column. If you find the target's name, you must delete that collector before you can delete the target.

If you cannot find the target's name, remember that the Path Echo Historical Statistics window shows only the 10 most used paths.

To see the rest of the intermediate paths, you must use the IPM Path Usage report. To do so:

a. On the CiscoWorks homepage, select Reports > Configuration Reports > Collectors.

The Collector Information page appears.

b. Select the first Path Echo collector in the list and click Path Usage in the Details column.

The Path Usage page appears.

c. Click a path to expand it, showing all of its intermediate hops, and look for the target's name. If you find the target's name, you must delete that Path Echo collector before you can delete the target.

d. Repeat this procedure for every path under every Path Echo collector.

Working With Operations

An IPM operation is an alias for a set of parameters used in measuring performance. information about working with operations is provided in the following subsections:

•Viewing a List of Defined Operations

•Viewing Operation Properties

•Adding a New Operation

•Setting Thresholds and Generating Alerts

•Deleting Operations

Viewing a List of Defined Operations

To view a list of defined operations:

Step 1 From the IPM Main Window, select Edit > Configuration.

The Configuration window (Figure 2-3) appears.

Step 2 Click Operations.

The list of operations expands to show the types of operations that were defined.

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.

When you install IPM, a group of predefined operations is provided. The predefined operations cannot be modified. However, you can use them as templates for creating your own operations. For a listing and brief description of these operations, see the Defining a Collector.

Figure 4-3 Operation Configuration Window

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.

The Operation Properties window (Figure 4-4) appears.

Figure 4-4 Operation Properties Window

For information about these fields, see the "Operation Properties Window" topic in the online help.

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.

To define an operation:

Step 1 From the IPM Main Window, select Edit > Configuration.

The Configuration window (Figure 2-3) appears.

Step 2 Click Operations.

The list of operations expands to show the types of operations that were defined.

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.

Step 4 Set the options for the operation you want to define. Detailed information about defining operations to measure performance for DHCP, DLSw, DNS, HTTP, IP, SNA, TCP, FTP, UDP, and Enhanced UDP is provided in the "Using IPM to Measure Network Performance" chapter.

Step 5 Click Close to complete the definition of a monitoring operation.

IPM redisplays the Operation window and the new operation is added to the list of defined operations.

Setting Thresholds and Generating Alerts

From the Operation Configuration window, you can configure thresholds and event notifications on the source.

To set thresholds and generate alerts using an operation:

Step 1 Select an existing operation or define a new operation by following the steps in Adding a New Operation.

Step 2 In the Generate Action Event field, select one of the algorithms to be used by IPM to calculate threshold violations. The following values are possible:

•Never—Do not calculate threshold violations. This is the default.

•Immediate—When the latency exceeds the rising threshold or drops below the falling threshold, immediately perform the action defined by Action Event Type.

•Consecutive—When the latency exceeds the rising threshold or drops below the falling threshold X times consecutively, perform the action defined by Action Event Type. Optionally, specify the number of consecutive occurrences. The default is 5.

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

•Average—When the average of the last X completion latency values exceeds the rising threshold or drops below the falling threshold, perform the action defined by Action Event Type.

Optionally, specify the number of operations to average. The default is the average of the last 5 latency operations.

For example, if the collector's rising threshold is 5000 milliseconds and the results of the collector's last 3 attempts are 6000, 6000, and 5000 milliseconds, the average would be 6000 + 6000 + 5000 = 17000/3 > 5000. The average of these values exceeds the 5000-milliseconds threshold, and the action is triggered.

Step 3 In the Rising field, enter a rising threshold, in milliseconds. Valid values are between 1 and 99999 milliseconds. The default is 5000 milliseconds.

When the latency exceeds the rising threshold, the collector uses the algorithm specified in Generate Action Event to determine if a threshold violation has occurred. If a violation occurs, the action defined in Action Event Type is taken.

Step 4 In the Falling field, enter a falling threshold, in milliseconds. Valid values are between 0 and 99999 milliseconds. The default value is 3000 milliseconds.

When the latency falls below the falling threshold, the threshold is reset. Only one event is generated for the time the latency is above the rising threshold.

Step 5 If you specified a Generate Action Event of Consecutive, X of Y, or Average, enter a value in the X field to be used in calculating the threshold. Valid values are 1 to 16. The default is 5.

If you specified a Generate Action Event of X of Y, enter a value in the Y field for the Y value to be used in calculating the threshold. Valid values are 1 to 16. The default is 5.

Step 6 In the Timeout Value field, enter the amount of time, in milliseconds, for the collector to wait for a response to its echo operation.

When a timeout occurs, the Timeout counter is incremented. The timeout value must be less than the specified sample interval. Valid values are between 0 and 604800.

The default value is:

•60000 milliseconds (for TCP Connect operations)

•9000 milliseconds (for DNS operations)

•5000 milliseconds (for all other operations)

To ensure interoperability with Cisco IOS, the Timeout Values for TCP Connect and DNS operations are fixed at 60000 and 9000 milliseconds, respectively. If you enter some other value, IPM changes the value you enter to the default value.

Step 7 Enable the Timeout Value option to check for latency reporting operation timeouts based on the timeout value configured for the collector.

If you enable the Timeout Action option, the action (specified in Action Event Type) is taken when a timeout occurs, or is cleared on this collector.

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.

Collectors that use the deleted operation continue to function correctly.

Note You cannot delete the default operations provided with IPM.

To delete an user-defined operation:

Step 1 From the Configuration window (Figure 2-3), select the operation or operations you want to delete.

Step 2 Click Delete.

The confirmation box appears,

Step 3 Click Yes.

The selected operations are deleted from the IPM database.

Working With Collectors

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

Information about working with collectors is provided in the following subsections:

•Viewing a List of Defined Collectors

•Viewing a Collector State Summary

•Viewing Collector Properties

•Adding a New Collector

•Stopping Collectors

•Deleting 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.

The following status information appears about each collector in the IPM Main Window:

•Collector name

•Source

•Target

•Operation

•Start Time

•Duration

•Type

•Status

You can sort the collector information displayed in the IPM Main Window by clicking on the column titles. By default, the information is sorted based on collector name. Optionally, you can sort the information based on start time, target, or operation type.

Viewing a Collector State Summary

To view a summary of the number of collectors on the server, broken down by current state (Running, Expired, and so on), select View > Collector State Summary from the IPM Main Window. The Collector State Summary window (Figure 4-5) appears.

For information about these fields, see the "Collector State Summary Window" topic in the online help.

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.

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.

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. The collector remains in the Cancelled status until that collector is started using either Edit > Start or Edit > Edit Collector.

For more detailed information about the options available in the Edit > Start and Edit > Edit Collector, see the context sensitive help.

Deleting Collectors

You can delete collectors you no longer need. When you delete a collector, all data related to that collector is removed from the database, and the collector and the SA Agent entry are removed from the source router. If the selected collector is active, IPM first stops the collector, then deletes it.

The collector remains in Delete Pending state until the data is completely deleted from the IPM database. It can take several minutes or more to delete a collector that has a large amount of data stored in the IPM database. You can delete more than one collector at a time.

To delete an IPM collector:

Step 1 From the IPM Main Window (Figure 2-2), select the collector or collectors to delete.

Step 2 Select Edit > Delete.

The confirmation box appears

Step 3 Click Yes.

The selected collectors are deleted from the IPM Main Window.

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.

You must create a separate seed file for each type of component. For example, you cannot mix source router definitions and collector definitions in the same seed file.

The following sections provide detailed information about seed files:

•Creating a Seed File

•Loading Components From a Seed File

•Viewing Seed File Output Files

Creating a Seed File

To create a source router, target, or collector seed file:

Step 1 Using any text editor, create a component-specific seed file following the format described in Seed File Syntax.

Sample seed files for each type of component are shown in Sample Source Seed File, Sample Target Seed File, and Sample Collector Seed File.

Step 2 Save the source router seed file as a text file.

The following table lists the default IPM seed file names and directories.

Platform

Default Seed File Name

Default Seed File Directory

Solaris

srcfile

/opt/CSCOipm/etc/source

trgtfile

/opt/CSCOipm/etc/target

collfile

/opt/CSCOipm/etc/collector

Windows

srcfile

C:\Program Files\Internetwork Performance Monitor\Server\etc\source

trgtfile

C:\Program Files\Internetwork Performance Monitor\Server\etc\target

collfile

C:\Program Files\Internetwork Performance Monitor\Server\etc\collector

If you installed IPM in a directory other than the default directory, you must specify that directory instead of /opt (for Solaris) or C:\Program Files\Internetwork Performance Monitor\ (for Windows).

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.

•In a target seed file, for each target you must provide a command, target type, host name, and for IP or SA Agent Responder targets a read community string. This is an optional field.

•In a collector seed file, for each collector you must provide a command, collector name, source router, target device, operation name, start time, duration, and collector type. The Source Interface IP address is an optional field in IPM.

You must separate each part of a component's definition with a delimiter. Valid delimiters are spaces, commas (,), semicolons (;), and tabs (\t). Use the same delimiter throughout a given seed file.

Do not begin a component with a comma, semicolon, or tab.

The following example is a valid source router definition, using spaces as delimiters:
# a router1 public private
If any part of a component's definition contains a space, you must use either a comma or a semicolon as the delimiter between all the parts of that definition. If the host name in the preceding example included a space (for example, router 1), you must use commas or semicolons as delimiters, instead of spaces:
# a,router 1,public,private
Table 4-1 describes the parts of a component's definition.

Table 4-1 Parts of a Component's Definition

Part

Description

Command

Defines whether the source router, target, or collector is added to the IPM database, removed from the IPM database, or whether an existing component entry in the IPM database is updated from the seed file. The following values are possible:

A or a—Adds the component to the IPM database.

D or d—Removes the component from the IPM database.

U or u—Updates an existing component entry in the IPM database from the information provided in the seed file.

Host Name

(Source router and target only) IP address or host name of the router on which the source resides, or of the target device. The host name can be from 1 to 64 characters in length. You can include an alias for the router by adding a vertical bar (|) and the alias after the host name.

Read Community

(Source router and target only) 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 255 characters in length.

Write Community

(Source router only) 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 255 characters in length.

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.

Collector Name

Name of the collector.

Source

(Collector only) Name of the defined source router to use for this collector. The source router must be already defined in IPM or in a source router seed file.

Target

(Collector only) Name of the defined target device to use for this collector. The target device must be already defined in IPM or in a target seed file.

Operation

(Collector only) Name of the defined operation to use for this collector. The operation must be already defined in IPM.

Sample Source Seed File

A sample source seed file is shown below:
####################################################################
#
# This file has example definitions for source routers. 
#
# Comments starts with the "#" character 
#
# The format of the file is as follows:
#
# <command><delim><hostname[|aliasname]><delim><read community><delim><write community>
#
# <delim> characters are " ;,\t" "space,semicolon,comma,tab"
#
# <hostname[|aliasname]> : Host name followed by optional aliasName
#                        separated with a `|' ("vertical bar")
#
# The valid commands are 'a|A' for add; 'd|D' for delete; 'u|U' for update;
#
# WARNING: Please assure the permissions on these files
#          do not allow read access to all users due to
#          the inclusions of SNMP community names.
#
####################################################################
#a router1 public private
#a router2 santa claus
#a router3.foobar.com open secret
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:
#
# <command><delim><target type><delim><hostname [<aliasname]><delim><read community>
#
# <delim> characters are " ;,\t" "space,semicolon,comma,tab"
#
# <hostname[|aliasname]> : Host name followed by optional aliasName
#                        separated with a `|' ("vertical bar")
#
# The valid commands are 'a|A' for add; 'd|D' for delete; 'u|U' for update;
#
# The <target type> is 1 for IP; 2 for CISCO_SAA_RESPONDER; 3 for SNA
#
# For CISCO_SAA_RESPONDER target type, read community string is optional.
# and the IOS RTR (SA Agent) Responder must be enabled
#
# WARNING: Please assure the permissions on these files
#          do not allow read access to all users due to
#          the inclusions of SNMP community names.
#
####################################################################
#a 1 www.foobar.com
#a 2 ios_router.foobar.com public
#a 3 sna_target.foobar.com
#a 1 server1
#a 2 router1 public
Sample Collector Seed File

A sample collector seed file is shown below:
####################################################################
# 
# This file has example definitions for collectors
#
# Comments starts with the "#" character 
#
# The format of the file is as follows:
#
# <command><delim><collName><delim><source><delim><target><delim>
# <operation><delim><startTime><delim><duration><delim><collType><SourceInterfaceIP>
#
# <delim> characters are " ;,\t" "space,semicolon,comma,tab"
#
# The valid commands are 'a|A' for add, 'd|D' for delete, 'u|U' for update;
#
# <collType> is M for Monitored, S for Statistical
#
# <startTime> is in the format MM:DD:YYYY:hh:mm:ss
#
# <startTime> = 1 -> start time will be now
#
# <duration> is in number of hours
## <duration> = 0 -> Forever 
#
# <startTime> = zero and <duration> = 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.
#
#  For DNS, DLSW and SNA Operation types, the SourceInterfaceIP field must blank
#
#  For any Operation types if you do not want to specify the SourceInterfaceIP
# leave the field blank
####################################################################
#a coll1 router1.cisco.com target1 DefaultIpEcho       1 12 M
#a coll2 router1.cisco.com target2 DefaultUDPEcho      1 0 S
#a coll3 router1.cisco.com target3 DefaultJitter       1 24 M
#a coll4 router1.cisco.com target4 DefaultDLSw         0 36 S
#a coll5 router2.cisco.com target1 DefaultSnaLu0Echo   1 6 M
#a coll6 router2.cisco.com target2 DefaultSnaLu2Echo   1 12 M
#a coll7 router2.cisco.com target3 DefaultSnaRuEcho    1 24 S
#a coll8 router2.cisco.com target2 DefaultIpPathEcho 10:20:1999:01:00:00 36 M
#a coll9 router.cisco.com Unused   DefaultHTTPConn     1 0 S
#a coll10 router.cisco.com Unused  MyHTTP              1 0 S
#a coll11 router.cisco.com Unused  DefaultDNS          1 0 S
#a coll12 router.cisco.com Unused  DefaultDHCP         1 0 S
####################################################################
####################################################################
#a coll1 router1.cisco.com target1 DefaultIpEcho                1   12 M SourceInterfaceIP     
#a coll2 router1.cisco.com target2 DefaultUDPEcho            1   	  0 S SourceInterfaceIP
#a coll3 router1.cisco.com target3 DefaultJitter       1 24 M
#a coll4 router1.cisco.com target4 DefaultDLSw         0 36 S
#a coll5 router2.cisco.com target1 DefaultSnaLu0Echo   1 6 M
#a coll6 router2.cisco.com target2 DefaultSnaLu2Echo   1 12 M
#a coll7 router2.cisco.com target3 DefaultSnaRuEcho    1 24 S
#a coll8 router2.cisco.com target2 DefaultIpPathEcho 10:20:1999:01:00:00 36 M
#a coll9 router.cisco.com Unused   DefaultHTTPConn     1 0 S
#a coll10 router.cisco.com Unused  MyHTTP              1 0 S
#a coll11 router.cisco.com Unused  DefaultDNS          1 0 S
#a coll12 router.cisco.com Unused  DefaultDHCP         1 0 S
####################################################################
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.

Figure 4-7 Seed File Window

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.

Step 4 Click OK.

The sources, targets, or collectors you defined in the seed file are added to the IPM database. When you access the Source Configuration, target Configuration, or Collector Configuration window, the changes you made to the components in the seed file are displayed.

If you do not remember the name of the seed file you want to load, you can view a list of available seed files from the Seed File window. Select Source, Target, or Collector as the Seed File Type and click View.

For information about listing, viewing, editing, or loading seed files from the command line, see the IPM Command Reference.

Viewing Seed File Output Files

When you add a source, target, or collector using a seed file, you create an output file that indicates whether the addition of the resource was successful. The output file has the same path and name as the seed file, with the addition of the .out suffix.

For example, a seed file named labsrcfile.txt generates an output file named labsrcfile.txt.out. An output file contains the same information as its seed file, with the addition of messages that indicate whether the addition of the resource was successful. For example, if labsrcfile.txt contains the following information:
a cwb-ipm-1600a public private
a cwb-ipm-1600b public private
a cwb-ipm-1700a public private
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. Possible error messages include:
ERROR: BAD VALUE PASSED
ERROR: COLLECTOR LIMIT EXCEEDED
ERROR: COLLECTOR NOT FOUND
ERROR: DATABASE ERROR
ERROR: DUPLICATE ENTRY
ERROR: DUPLICATE NAME
ERROR: INTERNAL ERROR
ERROR: INVALID COMMAND
ERROR: INVALID ENTRY
ERROR: INVALID IOS VERSION FOR TARGET
ERROR: INVALID PROTOCOL TYPE
ERROR: INVALID RTT TYPE
ERROR: INVALID TARGET FOR THE SELECTED OPERATION
ERROR: LOST CONNECTION TO SNMP SERVER
ERROR: OPERATION NOT FOUND
ERROR: SOURCE NOT FOUND
ERROR: TARGET NOT FOUND
Changing IP Addresses

When you physically move routers, servers, or other devices, you might need to change their IP addresses. You might also need to change IP addresses as your network grows. If you have a DNS server, IPM enables you to change an old IP address to a new IP address throughout the IPM database.

Caution Changing an IP address changes every occurrence of that address in the IPM database, including historical statistics and source and target IP addresses, even if the target is an intermediate hop. Therefore, make sure you want to change every occurrence of the IP address in the IPM database before using this procedure.

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. If you do, IPM issues an error message and does not change the old IP address.

Step 4 Click OK.

The IP address is changed throughout the IPM database.

The IPM client can seem unresponsive while the IP address is being changed. This is due to the high volume of messages being received by the client during this time.

If you change an IP address, you must wait until the change is complete in the IPM database before making another IP address change.

When you change the IP address of a device, IPM performs two checks. IPM first checks whether the same IP address is used by another device in the IPM database.

For more detailed information about the Change IP Address window, see the "Change IP Address Window" topic in the online help.

Setting the Baseline

You can increase, by a specified percentage (the baseline), the latency threshold for all statistical collectors in Running state that have collected at least one hour of data. Editing the baseline does not affect monitored collectors.

If you edit the baseline, then try to edit it again before the first edit is complete on all collectors, IPM blocks the second attempt and issues an error message. Wait for the baseline to be updated on all running collectors before editing the baseline again.

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 Edit Baseline Window

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

For example, if the current average latency is 100 milliseconds and you specify a baseline of 50, the new rising threshold is 150 milliseconds (50% above the current average latency), and the falling threshold is 50 ms (50% below the current average latency).

Step 3 Click OK.

The latency threshold is increased by the specified baseline percentage. The change is propagated to all Running statistical collectors.

On IPM servers with a large number of collectors, the IPM client can seem unresponsive while the baseline is being updated. This is due to the high volume of messages being received by the client during this time.

Note IPM does not automatically refresh open statistics windows to reflect the new baseline. To display the new baseline, close the statistics window and open it again.

For more detailed information about the Edit Baseline window, see the "Edit Baseline Window" topic in the online help.

Setting IPM Database Preferences

For collectors that are using a statistical operation, IPM gathers network performance and error statistics from the source router once every hour and stores the data in the IPM database. The collected hourly data is used to calculate daily, weekly, and monthly data.

By default, IPM stores the collected data for the following periods:

•Hourly data for up to 32 days

•Daily data for up to 180 days

•Weekly data forever

•Monthly data forever

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.

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

Information about viewing and changing the database preferences is provided in the following sections:

•Displaying the Current Database Preferences

•Changing the Database Preferences

•Database Preferences File Format

Displaying the Current Database Preferences

To display the preferences in the currently running IPM database in Solaris, enter:
# cd /opt/CSCOipm/bin
# ./ipm dbprefs view 
In Windows, enter:
cd c:\Program Files\Internetwork Performance Monitor\Server\bin 
ipm dbprefs view 
To display the preferences in the configuration file (which might differ from the preferences in the currently running IPM database), in Solaris, enter:
# cd /opt/CSCOipm/bin
# ./ipm dbprefs viewfile
In Windows, enter:
cd c:\Program Files\Internetwork Performance Monitor\Server\bin 
ipm dbprefs viewfile 
The output from the view and viewfile versions of this command is formatted differently because ipm dbprefs view displays the contents of a database, but ipm dbprefs viewfile displays the contents of a file.

Changing the Database Preferences

To change the IPM database preferences:

Step 1 Edit the IPM database preferences file (/opt/CSCOipm/etc/ipmDbPref.conf in Solaris; c:\Program Files\Internetwork Performance Monitor\server\etc\ipmDbPref.conf in Windows) using a text editor.

Step 2 Change the number of days that daily network performance statistics are stored, modify the following line:
ipm_daily_stats_life=180
Step 3 Set the business hours to be used in calculating averages, you must turn on or off the appropriate hourly interval.

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., you would use the following setting:
ipm_business_hour_0=0
ipm_business_hour_1=0
ipm_business_hour_2=0
ipm_business_hour_3=0
ipm_business_hour_4=0
ipm_business_hour_5=0
ipm_business_hour_6=0
ipm_business_hour_7=0
ipm_business_hour_8=1
ipm_business_hour_9=1
ipm_business_hour_10=1
ipm_business_hour_11=1
ipm_business_hour_12=1
ipm_business_hour_13=1
ipm_business_hour_14=1
ipm_business_hour_15=1
ipm_business_hour_16=1
ipm_business_hour_17=0
ipm_business_hour_18=0
ipm_business_hour_19=0
ipm_business_hour_20=0
ipm_business_hour_21=0
ipm_business_hour_22=0
ipm_business_hour_23=0
By default, the business day is defined as 24 hours, 0:00 a.m. to 11:59 p.m.

To set the business days used for calculating weekly and monthly averages, you must turn on or off the appropriate day. Each day of the week is represented by a number as follows:

•Sunday is ipm_business_day_0

•Monday is ipm_business_day_1

•Tuesday is ipm_business_day_2

•Wednesday is ipm_business_day_3

•Thursday is ipm_business_day_4

•Friday is ipm_business_day_5

•Saturday is ipm_business_day_6

For the days you want to set as business days, set the day to a value of 1. Days with a value of 0 are not counted as business days.

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.

Step 5 Run the database utility program to load your preferences.

In Solaris, enter:
# cd /opt/CSCOipm/bin 
# ./ipm dbprefs reload 
In Windows, enter:
cd c:\Program Files\Internetwork Performance Monitor\Server\bin 
ipm dbprefs reload 
Note You might want to make a backup copy of the database preferences file (ipmDbPref.conf) before modifying it.

Database Preferences File Format

The contents of the default IPM database preferences file (ipmDbPref.conf) are shown in the following example. This file is stored in the /opt/CSCOipm/etc directory in Solaris and in the c:\Program Files\Internetwork Performance Monitor\server\etc directory in Windows.
##
# (C) Copyright 1998 Cisco Systems, Inc.
# All Rights Reserved#
# IPM Web Report Preferences#
# The default maximum number of rows returned to the browser
# in any web report can be controlled with ipm_max_web_rpt_rows.#
ipm_max_web_rpt_rows=500#
#
# IPM Database Preferences#
# This file contains the IPM Database Preferences used for
# data aging, data reduction, and web reporting.#
# To change these values, update the values below and run the command:
# ipmDbPref.sh -s#
# To display the values currently set in the database, run the command:
# ipmDbPref.sh#
# NOTE: Changing these parameters has no effect on daily, weekly and
# monthly data that has already been calculated. Only new daily, weekly
# and monthly data will use these new settings.#
# The weekly and monthly data are always kept forever.
# The ipm_hourly_stats_life setting determines the number of days that IPM
# stores hourly statistics information. You can change this to any number
# of days.#
ipm_hourly_stats_life=32#
# The ipm_daily_stats_life setting determines the number of days that IPM
# stores daily statistics information. You can change this to any number
# 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.#
# The hours are defined as starting at 0 minutes past the hour, and going
# through 59 minutes and 59 seconds past the hour.#
# Set the value of each ipm_business_hour_x parameter to either 0 or 1.
# A value of 1 indicates that IPM will use this hour of the day when
# generating daily, weekly and monthly reports. A value of 0 indicates
# that IPM will ignore this hour of the day when generating daily, weekly
# and monthly reports.#
# For example, setting 'ipm_business_hour_9=1' will cause all data collected
# between 9:00AM and 9:59AM on business days to be included in reports.#
ipm_business_hour_0=1
ipm_business_hour_1=1
ipm_business_hour_2=1
ipm_business_hour_3=1
ipm_business_hour_4=1
ipm_business_hour_5=1
ipm_business_hour_6=1
ipm_business_hour_7=1
ipm_business_hour_8=1
ipm_business_hour_9=1
ipm_business_hour_10=1
ipm_business_hour_11=1
ipm_business_hour_12=1
ipm_business_hour_13=1
ipm_business_hour_14=1
ipm_business_hour_15=1
ipm_business_hour_16=1
ipm_business_hour_17=1
ipm_business_hour_18=1
ipm_business_hour_19=1
ipm_business_hour_20=1
ipm_business_hour_21=1
ipm_business_hour_22=1
ipm_business_hour_23=1#
# The ipm_business_day settings describe which days of the week IPM will
# use when generating weekly and monthly reports. Each day of the week
# is represented by a number:#
# Sunday is 0
# Monday is 1
# Tuesday is 2
# Wednesday is 3
# Thursday is 4
# Friday is 5
# Saturday is 6#
# Set the value of each ipm_business_day_x parameter to either 0 or 1.
# A value of 1 indicates that IPM will use this day of the week when
# generating weekly and monthly reports. A value of 0 indicates that IPM
# will ignore this day of the week when generating weekly and monthly reports.#
# For example, setting 'ipm_business_day_2=1' will cause all
# data collected on Tuesday during business hours to be included in reports.#
ipm_business_day_0=1
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=1
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. If the response time exceeds a predefined timeout value, IPM interprets the delay as an SNMP timeout, which could impact the operation of your collectors.

For example, if you have an IPM server in New York and a source router in Tokyo, SNMP timeouts might prevent you from configuring collectors on the source router. Or you might be able to configure the collectors, but timeouts might result in periods when no statistical data can be collected from the source router.

If you experience this problem, the best solution is to define an additional IPM server that is physically nearer the source router. However, if that is not an option, you can set new values for the SNMP timeout and retry environment variables.

Note SNMP environment variables are engineered for all but the most extreme operating conditions. Modifying these variables can adversely affect IPM's performance, resulting in unacceptably long delays in responding to user requests. Unless you are certain that you must, you should not modify these 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. The default is 3 retries.

IPM_SNMP_TIMEOUT_INCREMENT

Time in seconds to add to the current time-out value for subsequent retries. The valid range is 1 to 60 seconds. The default is 5 seconds.

Using the default values, IPM waits 50 seconds before determining that an SNMP request cannot be completed—5 seconds for the initial timeout, followed by 3 retries of 10, 15, and 20 seconds each.

If excessive SNMP timeouts are a problem in your network, try slightly increasing the timeout and timeout increment values until the problem is eliminated.

To set new values for these variables, use one of the following procedures:

•Setting SNMP Environment Variables in Solaris

•Setting SNMP Environment Variables in Windows

Setting SNMP Environment Variables in Solaris

To set SNMP environment variables in Solaris, use the following procedure:

Step 1 Make sure the IPM server is not running. You must set these environment variables while the IPM server is not running. To stop the IPM server, enter:
# cd /opt/CSCOipm/bin 
# ./ipm stop 
Step 2 On your IPM server, use a text editor to open the ipm.env file. In Solaris, the default directory for the ipm.env 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.

By default, the variable definitions are commented out in the file:
# 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
Step 3 To change a variable definition, remove the comment markers (#) from the definition and change the settings. For example, to change the timeout value to 10 seconds, change the following lines in the file:
# Max value is 60, default is 5, min is 1
IPM_SNMP_TIMEOUT=10
export IPM_SNMP_TIMEOUT
Step 4 Save your changes and close the file.

Step 5 Log in as the root user.

Step 6 Restart the IPM servers by entering:
# cd /opt/CSCOipm/bin 
# ./ipm restart 
When the IPM servers start up, they discover the variables and use the new timeout and retry values.

Setting SNMP Environment Variables in Windows

To set SNMP environment variables in Windows:

Step 1 Make sure the IPM server is not running. You must set these environment variables while the IPM server is not running. To stop the IPM server, enter:
cd c:\Program Files\Internetwork Performance Monitor\Server\bin 
ipm stop 
Step 2 On your IPM server, use a text editor to open the ipm.env file. In Windows, the default directory for the ipm.env file is c:\Program Files\Internetwork Performance Monitor\server\etc.

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.

By default, the variable definitions are commented out in the file:
# 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
Step 3 To change a variable definition, remove the comment markers (#) from the definition and change the settings. For example, to change the timeout value to 10 seconds, change the following lines in the file:
# Max value is 60, default is 5, min is 1
set IPM_SNMP_TIMEOUT=10
Step 4 Save your changes and close the file.

Step 5 Log in as the administrator.

Step 6 Restart the IPM servers by entering:
cd c:\Program Files\Internetwork Performance Monitor\server\bin 
ipm restart 
When the IPM servers start up, they discover the variables and use the new timeout and retry values.

Setting New IPM Server Process Timeout Values

The default timeout value for data collection servers and configuration servers is 120 seconds. This value accommodates the longer startup times encountered when you have a large number of collectors. However, if you have configured more than 2000 collectors on a single IPM server, you might need to increase this timeout value. These timeout values control internal IPM timing; they do not affect communication with source routers.

For each group of 500 collectors above 2000, add 30 seconds to the default timeout value of 120 seconds for both the data collection server and configuration server. For example, for 1500 collectors change the timeout value to 150 seconds for both servers. If you do not make this change, the Process Manager might timeout while waiting for the data collection server to start up, thus preventing initialization of the configuration server.

To increase the timeout value, allowing sufficient time for the data collection server process to start, use one of the following procedures:

•Setting Server Timeout Values in Solaris

•Setting Server Timeout Values in Windows

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.

The data collection server's timeout value is defined in the following line in the file:
DataCollectionServer R MessageLogServer,SNMPServer /opt/CSCOipm/bin/CWB_ipmData_colld 
-ORBagentPort,44342,-PMCserverName,IPMProcessMgr,-PMCname,DataCollectionServer,-MLCserverN
ame,IPMMsgLogServer,-MLCname,DataCollectionServer,-N,IPMDataCollectionServer,-R,/opt/CSCOi
pm 120
The configuration server's timeout value is defined in the following line in the file:
ConfigServer R MessageLogServer,SNMPServer,DataCollectionServer 
/opt/CSCOipm/bin/CWB_ipmConfigServerd 
-ORBagentPort,44342,-PMCserverName,IPMProcessMgr,-PMCname,ConfigServer,-MLCserverName,IPMM
sgLogServer,-MLCname,ConfigServer 120
Step 2 To change the timeout definition for one or both servers, change the number 120 at the end of the appropriate line. For example, to change the timeout value for configuration servers to 240 seconds:
ConfigServer R MessageLogServer,SNMPServer,DataCollectionServer 
/opt/CSCOipm/bin/CWB_ipmConfigServerd 
-ORBagentPort,44342,-PMCserverName,IPMProcessMgr,-PMCname,ConfigServer,-MLCserverName,IPMM
sgLogServer,-MLCname,ConfigServer 240
Step 3 Save your changes and close the file.

Step 4 Log in as the root user.

Step 5 Restart the IPM servers by entering:
# cd /opt/CSCOipm/bin
# ./ipm restart
When the IPM servers start up, they use the new timeout values.

Setting Server Timeout Values in Windows

To set server timeout values in Windows:

Step 1 On your IPM server, use a text editor to open the ipm.conf file. In Windows, the default directory for the ipm.conf file is c:\Program Files\Internetwork Performance Monitor\server\pmconf.

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.

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,-MLCfilterFileName,C:\PROGRA~1\INTERN~1\Ser
ver\logs\DataCollectionServer.flt 120
The configuration server's timeout value is defined in the following line in the file:
ConfigServer R MessageLogServer,SNMPServer,DataCollectionServer 
C:\PROGRA~1\INTERN~1\Server\bin\CWB_ipmConfigServerd 
-ORBagentPort,44342,-OAconnectionMaxIdle,8640000,-PMCserverName,IPMProcessMgr,-PMCname,Con
figServer,-MLCserverName,IPMMsgLogServer,-MLCname,ConfigServer,-MLCfilterFileName,C:\PROGR
A~1\INTERN~1\Server\logs\ConfigServer.flt 120
Step 2 To change the timeout definition for one or both servers, change the number 120 at the end of the appropriate line. For example, to change the timeout value for configuration servers to 240 seconds:
ConfigServer R MessageLogServer,SNMPServer,DataCollectionServer 
C:\PROGRA~1\INTERN~1\Server\bin\CWB_ipmConfigServerd 
-ORBagentPort,44342,-OAconnectionMaxIdle,8640000,-PMCserverName,IPMProcessMgr,-PMCname,Con
figServer,-MLCserverName,IPMMsgLogServer,-MLCname,ConfigServer,-MLCfilterFileName,C:\PROGR
A~1\INTERN~1\Server\logs\ConfigServer.flt 240
Step 3 Save your changes and close the file.

Step 4 Log in as the administrator.

Step 5 Restart the IPM servers by entering:
cd c:\Program Files\Internetwork Performance Monitor\server\bin 
ipm restart 
When the IPM servers start up, they use the new timeout value.

Setting the DISPLAY Variable in Solaris

The DISPLAY variable is set as part of your login environment on Solaris. However, if you Telnet into a remote workstation, you must set the DISPLAY variable to local display. To do so, enter:

setenv DISPLAY local_ws:0.0

where local_ws is your local workstation.

If your shell does not support the setenv command, use:

export DISPLAY=local_ws:0.0

If you Telnet into a remote workstation and you do not set the DISPLAY variable to local display, you cannot use:

•ipm

•ipm control -rt

•ipm debug

•ipm pmstatus

•ipm start client

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
# ./ipm dbrestore
•In Windows, enter:
cd c:\Program Files\Internetwork Performance Monitor\server\bin 
ipm dbrestore 
When you are installing IPM on Windows, you have to select the option to automatically backup the database. On Solaris, the database backup is automatic.

Note This command can take several minutes to complete.

Warning Do not interrupt this command. Doing so can corrupt your IPM database.

NVRAM Settings

If you have configured collectors through IPM, you do not see the SAA instances that get created at the selected sources corresponding to these collectors in the running configuration. However, you can see the SAA instances that you configure at the command line interface of the router in the running configuration.

To see the IPM Collector SAAs in the running configuration follow these steps:

On Windows systems:

Step 1 Edit the file ipm.env in the C:\Program Files\Internetwork Performance Monitor\Server\etc folder

Step 2 Change the value of IPM_NVRAM_ENABLE to 1(default set to 0).
IPM_NVRAM_ENABLE=1
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\.

Step 3 Restart the IPM server by entering ipm restart at the command line.

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.

If you have set the IPM_NVRAM_ENABLE to 1 and also if you have saved the IPM Collector SAAs in the startup configuration, the SAA instances corresponding to IPM collectors gets reconfigured automatically at the time of router reboot.

Managed Source Interface Settings

A Managed Interface is the address of the source.

When you add a source, the IP address of the specific router is called the Managed Interface address.

To set the source interface address as the managed interface address, you must do the following:

On Windows systems:

Step 1 Edit the file ipm.env in the C:\Program Files\Internetwork Performance Monitor\Server\etc folder

Step 2 Change the value of IPM_USE_MANA GED_SRC_INTF_ADDR to 1
(default set to 0).
IPM_USE_MANA	GED_SRC_INTF_ADDR=1
The default directory to install 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\.

Step 3 Restart the IPM server by entering ipm restart at the command line.

On Solaris systems:

Step 1 Edit the file ipm.env in the /opt/CSCOipm/etc directory

The default directory to install 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_USE_MANA GED_SRC_INTF_ADDR to 1 (default set to 0)
IPM_USE_MANA	GED_SRC_INTF_ADDR=1
Step 3 Restart the IPM server by entering ipm restart at the command line.

If you have set IPM_USE_MANA GED_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. In other words, the router will select whatever source IP address you have specified while adding the source.

In addition, you can also specify a source interface while configuring a collector. In this case, the router uses the specified interface, and overrides the values you have set in IPM_USE_MANAGED_SRC_INTF_ADDR.

Changing Administrative Password

You can change the IPM Administrative password using this command at IPM command prompt:
ipm password 
IPM prompts you to change the Administrative password and to enter the new password. You need to enter the new password and confirm it by entering it again.

The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.

Changing IPM Database Password

You can change the IPM database password using this command at IPM command prompt:
ipm dbpassword 
The password is case sensitive and should begin with an alphabet. You can enter only a maximum of 15 characters and you can enter only alphanumeric characters.

For fresh IPM installations, it is mandatory that you enter a database password.

After you have restored the IPM database, the new database password would be the one that was last set on the server.

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.

Figure 4-10 Message Log Window

The Message Log window is composed of the following sections:

•Log Control

•Log Display

Log Control

When you access the Message Log window, the Log Control tab is displayed.

Fields

The Log Control tab of the Message Log window contains the following fields:

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.

The Error and Info message categories are enabled by default. To enable a message category, click Enabled.

Warning Enabling Debug and Trace options in the Message Log Window will affect the IPM performance. You need to use this option at minimum to avail the maximum performance of IPM.

Buttons

The buttons in the Log Control tab of the Message Log window provide the following functions:

Button

Description

Reset

Resets the message to its previous saved state. (Enabled or Disabled).

Apply

Executes the changes you made to the message categories (Enabled or Disabled).

Exit

Closes the Message Log window.

Help

Displays information about the window.

Log Display

The Log Display tab of the Message Log window displays messages generated by enabled message categories defined in the Log Control tab. When you access the Message Log window, the Log Control tab is displayed by default. To access the Log Display tab, click Log Display in the tab bar.

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.

New View

Displays the New View window which allows you to specify criteria for messages to be displayed in the Log Display tab of the Message Log window.

Clear View

Removes all currently displayed messages from view.

Pause View

Stops scrolling messages as they are received. New messages are still received but the list does not scroll in the view. New messages received while the view is paused are not saved.

If you pause while messages are still filling the view (that is, before the view begins scrolling), new messages are added to the view until it is full, then the pause takes effect.

To resume scrolling messages, click Pause View again. The view resumes scrolling, and new messages are saved once again.

Exit

Closes the Message Log window.

Help

Displays information about the window.