user manual
Table Of Contents
- User Guide for Internetwork Performance Monitor
- Contents
- Preface
- Overview of IPM
- Getting Started With IPM
- Using IPM to Measure Network Performance
- Measuring Network Performance for DHCP
- Measuring Network Performance for DLSw
- Measuring Network Performance for DNS
- Measuring Network Performance for HTTP
- Measuring Network Performance for FTP
- Measuring Network Performance for IP
- Measuring Network Performance for SNA
- Measuring Network Performance for TCP
- Measuring Network Performance for UDP
- Measuring Network Performance for Enhanced UDP
- Modifying IPM Components
- Working With Source Devices
- Working With Target Devices
- Working With Operations
- Working With Collectors
- Adding Components Using Seed Files
- Changing IP Addresses
- Setting the Baseline
- 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
- Managed Source Interface Settings
- Changing Administrative Password
- Changing IPM Database Password
- Working With Message Log Window
- Working With IPM From the CiscoWorks Homepage
- Accessing IPM Data From the CiscoWorks Homepage
- Viewing IPM Server Information
- Importing Devices From Device and Credential Repository
- Downloading the IPM Client
- Viewing Configuration Information
- Viewing Latency Data
- Viewing Jitter Data
- Viewing HTTP Data
- Accessing Software Updates and Additional Information
- IPM FAQs and Troubleshooting Tips
- IPM Command Reference
- SA Agent Feature Mapping
- Glossary
- Index

4-17
User Guide for Internetwork Performance Monitor
OL-11291-01
Chapter 4 Modifying IPM Components
Adding Components Using Seed Files
Seed File Syntax
The top of the seed file contains a comments section for any information you want to note about the file,
followed by each component’s definition on a separate line.
• In a source router seed file, for each source router you must provide a command, host name, read
community string, and write community string.
• 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.