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-16
User Guide for Internetwork Performance Monitor
OL-11291-01
Chapter 4 Modifying IPM Components
Adding Components Using Seed Files
Adding Components Using Seed Files
In addition to defining source routers, targets, and collectors from their respective Configuration
windows, you can define them using seed files. A seed file is a text file containing the information
required to define one or more components. This is especially useful if you must add a large number of
sources, targets, or collectors quickly.
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.
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).
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