Table Of Contents
What's New in This Release
New Features in IPM 4.0
Navigational Approaches of IPM 2.6 and IPM 4.0
Managing IPM Devices
Managing IPM Operations
Understanding IP SLA Operations
Managing IPM Collectors
Managing IPM Collector Groups
Managing Archived Reports
Managing Report Jobs
Managing Audit Reports
Managing System Reports
Setting System Preferences
Managing Specific Settings for Standalone Client
Managing IPM Backup
Using IPM CLI Commands
What's New in This Release
This section explains the new features and enhancements in IPM 4.0. It also compares the navigational approach of IPM 4.0 and IPM 2.6.
It contains the following topics:
•
New Features in IPM 4.0
•Navigational Approaches of IPM 2.6 and IPM 4.0
New Features in IPM 4.0
The following are the new features and enhancements in Internetwork Performance Monitor (IPM) 4.0.
•Import New Devices from Device and Credential Repository (DCR)
•Leveraging Common Services Device Selector into IPM 4.0
•Adhoc Target Devices
•Integration with LMS Setup Center
•One-Step Multiple Collector Creation
•Rich Graphs and Improved Reports
•Overlay Graphs
•Lightweight Front End
•Support for Latest IP SLA Operations
•Infrastructure Support
•Customizable Polling Frequency
Import New Devices from Device and Credential Repository (DCR)
IPM 4.0 is completely integrated with CiscoWorks LMS 3.0. You can import devices from DCR either automatically or manually.
•To automatically import the devices, set the Automatically Manage Devices from the Credential Repository option on the Application Settings page.
For more information, see Adding Devices Using Device Management.
or
•To manually import the devices, go to the IPM Devices page and select the required DCR devices.
For more information, see Adding Devices Using Device Management.
Leveraging Common Services Device Selector into IPM 4.0
The enhanced Device Selector in IPM 4.0 allows you to select devices, add devices, and perform a simple search on devices.
For more information, see Using Device Selector.
Adhoc Target Devices
Supports adding adhoc target devices into IPM. The adhoc target devices added are available only in the IPM and not in the DCR.
For more information, see Adding Adhoc Target Devices to IPM.
Integration with LMS Setup Center
IPM 4.0 allows you to view and modify the purge settings for historical and audit reports on the LMS Setup Center page.
See Common Services Online help.
One-Step Multiple Collector Creation
Supports a single wizard-based approach. This procedure allows you to create multiple collectors. This wizard involves the following steps:
1. Create Collectors—Allows you to specify a source, targets, and operations to create collectors.
2. Select Collectors—Allows you to select the required collectors that were created in the first step.
3. Schedule Collectors—Allows you to schedule the selected collectors.
4. View the Summary of the Collectors—Allows you to view the summary of the collectors that you have created.
For more information, see Defining Collectors.
Rich Graphs and Improved Reports
The Reports module in IPM 4.0 supports rich fusion Chart graphs and enhanced Historical reports. This module allows you to manage Archived reports, Report jobs, Audit reports, and System reports.
You can customize Historical reports by specifying the report type, granularity, report period, and schedule details.
You can generate system reports, audit reports, minute reports and graphs, and historical reports and graphs.
•To generate real-time reports
For more information, see Monitoring a Collector.
•To customize Historical reports
For more information, see Generating Statistical Reports and Graphs.
•To generate Minute and Historical reports and graphs
For more information, see Working with Minute/Historical Reports and Graphs.
•To generate Audit reports
For more information, see Generating Audit Reports.
•To generate System reports
For more information, see Understanding System Reports.
Overlay Graphs
These graphs allow you to compare the latency of the collectors based on the granularity and time period. You can overlay graphs only for collectors in the Running, Completed, or Stopped status.
For more information, see Viewing Collector Graphs.
Lightweight Front End
Supports LMS UI standards to make IPM compatible with other LMS applications.
Support for Latest IP SLA Operations
Supports RTP, VoIP Gatekeeper Delay, VoIP Call Setup, and ICMP Jitter operations in addition to the existing operations in IPM 2.6.
UDP Jitter additionally supports MOS (Mean Opinion Scores) and ICPIF (Calculated Planning Impairment Factor) features. These features measure the voice quality in the network.
For more information, see Managing IPM Operations.
Infrastructure Support
IPM 4.0 is fully integrated with Common Services (CS) and will be shipped on CS 3.1 with LMS 3.0.
Customizable Polling Frequency
In addition to the existing 60 minutes polling frequency, IPM 4.0 also supports 1, 5, 15, and 30 minutes polling frequencies. It allows you to specify the polling details such as frequency, day, and time while creating collectors.
For more information, see the Managing Collectors in IPM chapter in the IPM 4.0 User Guide.
Navigational Approaches of IPM 2.6 and IPM 4.0
The following sections list the tasks in IPM and compare the differences between the navigational approaches of IPM 2.6 and IPM 4.0.
•Managing IPM Devices
•Managing IPM Operations
•Managing IPM Collectors
•Managing IPM Collector Groups
•Managing Archived Reports
•Managing Report Jobs
•Managing Audit Reports
•Managing System Reports
•Setting System Preferences
•Managing Specific Settings for Standalone Client
•Managing IPM Backup
•Using IPM CLI Commands
Managing IPM Devices
Table 2-1 lists the tasks in Device Management module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-1 Managing IPM Devices
Tasks
|
IPM 2.6
|
IPM 4.0
|
Viewing IPM devices
|
•Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Sources
Lists the source devices in IPM.
•Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Targets
Lists the target devices in IPM.
or
•Internetwork Performance Monitor > Reports > Configuration Reports > Sources
•Internetwork Performance Monitor > Reports > Configuration Reports > Targets
|
•Internetwork Performance Monitor > Collector Management > Devices
Lists all source and target devices in IPM.
•Internetwork Performance Monitor > Collector Management > Collectors > Create
Lists the source devices, target devices, and responder-enabled target groups individually.
|
Viewing source device properties
|
Internetwork Performance Monitor > Client > Web Client > View > Properties
|
•To view source device details such as SNMP Retry and Timeout, go to Internetwork Performance Monitor > Collector Management > Devices > Edit Device Attributes
•To view source device details such as IOS version, IP SLA information, maximum configured collectors, go to Internetwork Performance Monitor > Collector Management > Collectors > View
|
Viewing target device properties
|
Internetwork Performance Monitor > Client > Web Client > View > Properties
|
Internetwork Performance Monitor > Collector Management > Collectors.
To view the properties of a target device, you must associate it with a collector.
|
Adding devices manually from DCR
|
Internetwork Performance Monitor > Admin > Import From Device and Credential Repository > Sources
You can add sources, targets as SAA Responders, or target as IP devices.
|
Internetwork Performance Monitor > Collector Management > Devices > Add Devices
By default, all devices are added as targets. Based on the IP SLA capability on devices, they are categorized as source or target responder devices.
|
Importing devices from DCR automatically
|
Not supported.
|
Internetwork Performance Monitor > Admin > Application Settings > Automatically Manage Devices from Credential Repository
|
Adding adhoc target devices into IPM space
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Target > Add
Adhoc target devices are not included in the device license count.
|
Internetwork Performance Monitor > Collector Management > Devices > Add Adhoc Devices
Adhoc target devices are not included in the device license count.
|
Editing SNMP Retry and Timeout for a single or multiple devices
|
Update the ipm.env file to edit the SNMP Retry and Timeout details.
|
To edit the SNMP Retry and Timeout details, go to Internetwork Performance Monitor > Collector Management > Devices > Edit Device Attributes.
You cannot edit the adhoc target device attributes.
|
Deleting IPM devices
|
•Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Sources > Delete
•Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Targets > Delete
|
Internetwork Performance Monitor > Collector Management > Devices > Delete
The devices deleted from IPM are still available in DCR.
|
Managing IPM Operations
Table 2-2 lists the tasks in the Operation module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-2 Managing IPM Operations
Tasks
|
IPM 2.6
|
IPM 4.0
|
Viewing the list of existing system defined and user defined operations
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Operations
or
Internetwork Performance Monitor > Reports > Configuration Reports > Operations
|
Internetwork Performance Monitor > Collector Management > Operations
|
Creating user-defined operations
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Operations > Add
|
Internetwork Performance Monitor> Collector Management > Operations > Create
See Table 2-3 for more information on each operation.
|
Editing an user-defined operation
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Operations > Edit
|
Internetwork Performance Monitor> Collector Management > Operations > Edit
|
Deleting user-defined operations
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Operations > Delete
|
Internetwork Performance Monitor> Collector Management > Operations > Delete
|
Viewing the details of an operation
|
Internetwork Performance Monitor > Client > Web Client > Edit > Config
|
Internetwork Performance Monitor> Collector Management > Operations > View
|
Understanding IP SLA Operations
Table 2-3 lists all the operations and a comparison of their features.
Table 2-3 List of IP SLA Operations
Operation Name
|
IPM 2.6
|
IPM 4.0
|
Path Echo
•IP QOS Type is configured as:
–IP Precedence
–DSCP
•IP QoS Settings range between 0 and 7.
•Request Payload. The default value is 64 bytes.
•Maximum Paths. The default value is 5.
•Maximum Hops. The default value is 10.
|
Supported
|
Supported.
|
UDP Echo
•IP QOS Type is configured as:
–IP Precedence
–DSCP
•IP QoS Settings range between 0 and 7.
•Request Payload. The default value is 64 bytes.
•Enable and disable data verification for UDP Echo operations
•Maximum Hops. The default value is 10.
•Target Port. The default value is 7. Valid values range between 7,1025 and 65535.
|
Supported.
|
Supported.
|
TCP Connect
•IP QOS Type is configured as:
–IP Precedence
–DSCP
•IP QoS Settings range between 0 and 7.
•Default Operations are NNTP, POP3, SMTP, TELNET
•Target Port. The default value is 3000. Valid values range between 1 and 65535.
|
Supported.
|
Supported.
|
DNS
•DNS Name Server
•DNS Lookup Name
|
Supported.
|
Supported.
Since the workflow has changed, you must specify the DNS Lookup Name while creating the collectors as part of target.
|
HTTP
•IP QOS Type is configured as:
–IP Precedence
–DSCP
•IP QoS Settings range between 0 and 7.
•URL Lookup String
•Enable and disable Download URL from cache
•Enable and disable proxy server
•Enable and disable proxy server.
To configure, enable the proxy server.
|
Supported.
|
Supported.
Since the workflow has changed, you must specify the HTTP server while creating the collectors as part of target.
|
FTP
•IP QOS Type is configured as:
–IP Precedence
–DSCP
•IP QoS Settings range between 0 and 7.
•FTP URL Lookup String
•FTP session Mode (Active and Passive)
|
Supported.
|
Supported with the following workflow change:
•User name and Password are specified while creating the operation.
•FTP server is specified while creating collector as part of target.
|
Enhanced UDP Jitter
•IP QOS Type is configured as:
–IP Precedence
–DSCP
•IP QoS Settings range between 0 and 7.
•Request Payload. The default value is 64 bytes.
•Packet intervals. The default value is 10 milliseconds.
•No.of packets. The default value is 20.
•Target port. Valid values range between 0 and 65535.
The default value is 16400 for Voice and 2000 for other traffic.
|
Supported.
|
Supported, but referred as UDP Jitter.
|
DLSw
•Request Payload. The default value is 64 bytes.
•Response Payload. The default value is 64 bytes.
|
Supported.
|
Supported.
|
DHCP
Enable and disable DHCP server. You can configure the name and IP address only if the DHCP server is enabled.
|
Supported.
|
Supported.
Since the workflow has changed, you must specify the DHCP server while creating the collectors as part of target.
|
Managing IPM Collectors
Table 2-4 lists the tasks in Collector module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-4 Managing IPM Collectors
Tasks
|
IPM 2.6
|
IPM 4.0
|
Viewing the collector list
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Collectors
Or
Internetwork Performance Monitor > Reports > Configuration Reports > Collectors
|
Internetwork Performance Monitor > Collector Management > Collectors
|
Viewing the collector state summary
|
Internetwork Performance Monitor > Client > Web Client > View > Collector State Summary
|
Internetwork Performance Monitor > Collector Management > Collectors
|
Viewing collector properties
|
Internetwork Performance Monitor > View > Properties
|
Internetwork Performance Monitor > Collector Management > Collectors > View
|
Creating collectors using a source device, target devices, and IP SLA probes
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Collectors > Add
|
Internetwork Performance Monitor> Collector Management > Collectors > Create
|
Editing collector details such as collection information and scheduling details
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Collectors > Edit
|
Internetwork Performance Monitor> Collector Management > Collectors > Edit
|
Deleting collectors
|
Internetwork Performance Monitor > Client > Web Client > Edit > Configuration > Collectors > Delete
|
Internetwork Performance Monitor > Collector Management > Collectors > Delete
|
Exporting collector configuration information
|
The ipm mirror CLI command supports exporting collectors.
|
Internetwork Performance Monitor > Collector Management > Collectors > Export
|
Importing collector configuration information
|
Internetwork Performance Monitor > Client > Web Client > File > Open Seed File
Or
Using the CLI command, ipm loadcoll
|
Internetwork Performance Monitor > Collector Management > Collectors > Import
|
Generating real-time graph for a collector in Running status
|
Internetwork Performance Monitor > Client > Web Client > View > Real-time Statistics
|
Internetwork Performance Monitor > Collector Management > Collectors > Monitor
|
Starting the stopped collectors
|
Internetwork Performance Monitor > Client > Web Client > Edit > Start
|
Internetwork Performance Monitor > Collector Management > Collectors > Start
|
Stopping the collectors in Running status
|
Internetwork Performance Monitor > Client > Web Client > Edit > Stop
|
Internetwork Performance Monitor > Collector Management > Collectors > Stop
|
Comparing the latency of various collectors based on the granularity
|
You can view the statistics for more than one collector.
|
Internetwork Performance Monitor > Collector Management > Collectors > Overlay
|
Managing IPM Collector Groups
Table 2-5 lists the tasks in Collector Groups module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-5 Managing IPM Collector Groups
Tasks
|
IPM 2.6
|
IPM 4.0
|
Creating user-defined collector groups
|
Not supported.
|
Internetwork Performance Monitor > Collector Management > Group Administration > Create
|
Editing a user-defined collector group
|
Not supported.
|
Internetwork Performance Monitor > Collector Management > Group Administration > Edit
|
Viewing collector group details
|
Not supported.
|
Internetwork Performance Monitor > Collector Management > Group Administration > View
|
Refreshing group membership
|
Not supported.
|
Internetwork Performance Monitor > Collector Management > Group Administration > Refresh
|
Deleting user-defined collector groups
|
Not supported.
|
Internetwork Performance Monitor > Collector Management > Group Administration > Delete
|
Managing Archived Reports
Table 2-6 lists the tasks in Report Archives module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-6 Managing Archived Reports
Tasks
|
IPM 2.6
|
IPM 4.0
|
Creating report jobs
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Archives > Create
|
Generating Minute reports and graphs
|
Not supported
|
You can generate statistical data for a single or group of collectors on a Minute basis. To do this, go to:
Internetwork Performance Monitor > Reports > Report Archives > Create > Generate Report
|
Generating Historical reports and graphs
|
Internetwork Performance Monitor > Reports > Configuration Reports > Collectors > Hourly
|
You can generate statistical data for a single or a group of collectors on a Hourly, Daily, Monthly, and Weekly basis. To do this, go to:
Internetwork Performance Monitor > Reports > Report Archives > Create > Generate Report
|
Viewing Archived report details
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Archives > View
|
Deleting Archived reports
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Archives > Delete
|
Managing Report Jobs
Table 2-7 lists the tasks in Report Jobs module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-7 Managing Report Jobs
Tasks
|
IPM 2.6
|
IPM 4.0
|
Viewing the output of the completed report jobs
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Jobs > Show Output
|
Viewing the Report job details
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Jobs
|
Stopping the Report jobs that has Running or Scheduled status
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Jobs > Stop
|
Deleting the Report jobs
|
Not supported.
|
Internetwork Performance Monitor > Reports > Report Jobs > Delete
|
Managing Audit Reports
Table 2-8 lists the tasks in Audit Reports module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-8 Managing Audit Reports
Tasks
|
IPM 2.6
|
IPM 4.0
|
Generating Audit reports
|
Not supported.
|
Internetwork Performance Monitor > Reports > Audit Reports > Generate
|
Purging Audit reports
|
Not supported.
|
Internetwork Performance Monitor > Admin > Purge Settings
|
Managing System Reports
Table 2-9 lists the tasks in System Reports module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-9 System Reports
Tasks
|
IPM 2.6
|
IPM 4.0
|
Viewing Daily system reports
|
You can view the system report only for Latency, Jitter, and HTTP.
Internetwork Performance Monitor > Reports
|
You can generate system reports for Availability, Latency, UDP Jitter, HTTP, ICMP, PathEcho, and RTP report types.
Internetwork Performance Monitor> Reports > System Reports > Daily
|
Viewing Weekly system reports
|
Internetwork Performance Monitor> Reports > System Reports > Weekly
|
Viewing Monthly system reports
|
Internetwork Performance Monitor> Reports > System Reports > Monthly
|
Setting System Preferences
Table 2-10 lists the tasks in Administration module and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-10 Setting System Preferences
Tasks
|
IPM 2.6
|
IPM 4.0
|
Server Info
|
Viewing process status
|
Internetwork Performance Monitor > Admin > Server Info > Process Status
|
Common Services > Admin > Processes
|
Viewing version details
|
Internetwork Performance Monitor > Admin > Server Info > Version Info
|
Common Services > Software Center > Software Updates
|
Viewing server logfile
|
Internetwork Performance Monitor > Admin > Server Info > Server Log File
|
You can find the server log file at the following location:
•Windows: NMROOT\log
where NMSROOT is CiscoWorks Installation directory.
•Solaris: /var/adm/CSCOpx/log
|
Viewing console logfile
|
Internetwork Performance Monitor > Admin > Server Info > Console Log File
|
Not supported.
|
Viewing troubleshooting information
|
Internetwork Performance Monitor > Admin > Server Info > Troubleshooting Info
|
Common Services > Server > Admin > Collect Server Information
|
Download Client
|
Download ipm client for Windows from a Windows server
|
Internetwork Performance Monitor > Admin > Download Client > Windows Client > Download IPM Client for Windows
|
Not applicable.
|
Download ipm client for both Windows and Solaris from a Solaris server
|
Internetwork Performance Monitor > Admin > Download Client
|
System Preferences
|
Setting log level
|
Internetwork Performance Monitor > Client > Web Client > File > Message Log Client
|
Internetwork Performance Monitor> Admin > Log Level Settings
|
Auto update from DCR
|
Not supported.
|
Internetwork Performance Monitor > Admin > Application Settings
|
Copying IP SLA configuration to running-config
|
The ipm.env property file supports this feature.
|
Internetwork Performance Monitor > Admin > Application Settings
|
Managing source interface settings
|
The ipm.env property file supports this feature.
|
Internetwork Performance Monitor > Admin > Application Settings
|
Purging report data
|
Update the ipmDbPref.txt file to purge the report data.
|
Internetwork Performance Monitor > Admin > Purge Settings
|
Managing Specific Settings for Standalone Client
Table 2-11 lists the specific settings for Standalone Client and compares the navigational approaches of IPM 2.6 and IPM 4.0.
Table 2-11 Standalone Client Specific Settings
Tasks
|
IPM 2.6
|
IPM 4.0
|
Setting log level for each process
|
Internetwork Performance Monitor > Client > Web Client >File > Message Log Client
|
Internetwork Performance Monitor > Admin > Log Level Settings
Supports the following log levels:
•Debug
•Warning
•Info
•Error
•Fatal
|
Creating log view by specifying:
•Filter for log messages
•Fields to be displayed
•Automatic clearing of messages after `N' messages
|
Not applicable.
The messages are logged into log files like other LMS applications.
|
Clearing log view
|
Internetwork Performance Monitor > Client > Web Client > File > Message Log Client > Log Display > Clear View
|
Not applicable.
The messages are logged into log files like other LMS applications.
|
Pausing/Resuming log view
|
Internetwork Performance Monitor > Client > Web Client > File > Message Log Client > Log Display > Pause View
|
Not applicable.
The messages are logged into log files like other LMS applications.
|
Viewing all the process information:
•Process name
•Process ID
•Process status
•Last message
|
The ipm status CLI command displays process information.
|
You can view the process information on the CiscoWorks home page using pdshow.
Common Services > Admin > Processes
|
Viewing each process information
|
Not supported.
|
|
You can view each process details using pdreg-l.
|
Launching the CiscoWorks homepage
|
Internetwork Performance Monitor > Client > Web Client > View > CiscoWorks Home page
|
Not supported.
|
Managing IPM Backup
Table 2-12 compares the backup settings of IPM 2.6 and IPM 4.0.
Table 2-12 Managing IPM Backup
Task
|
IPM 2.6
|
IPM 4.0
|
Backup
|
Windows allow two versions to be backed up.
|
Common Services Framework is used for backup. This framework supports any number of backups.
|
Using IPM CLI Commands
Table 2-13 lists the CLI commands supported in IPM 2.6 and IPM 4.0.
See User Guide for Internetwork Performance Monitor 2.6 and User Guide for Internetwork Performance Monitor 4.0 for the syntax, description, and examples of CLI commands supported in IPM 2.6 and IPM 4.0.
Table 2-13 CLI Command Reference
Tasks
|
IPM 2.6
|
IPM 4.0
|
Process related commands
|
•ipm start
•ipm stop
•ipm restart
•ipm start/stop
•ipm restart
•ipm start client
•ipm stopclients
•ipm forcestop
•ipm status
•ipm pmstatus
•ipm pmstatus
•ipm password
•ipm
|
Supports the following CLI commands:
•ipm addadhoctarget
•ipm baseline
•ipm deletedevice
•ipm export
•ipm exportstats
•ipm importcollector
•ipm controlcollector
•ipm deletereports
•ipm generatereports
•ipm listcollectors
All process related commands will be governed by Daemon Manager CLI utilities provided by Common Services Framework.
|
Adding source, target, and collector
|
•ipm addsrc
•ipm addtarg
•ipm delsrc
•ipm deltarg
|
Importing or exporting source, target, and collector using a seed file
|
•ipm loadsrc
•ipm loadtarg
•ipm loadcoll
•ipm viewsrc
•ipm viewtarg
•ipm viewcoll
•ipm editsrc
•ipm edittarg
•ipm editcoll
|
Supports only import and export of collector configuration:
•Importing collector configuration
ipm importcollector
•Exporting collector configuration
ipm export
|
Database related
|
•ipm backupdir
•ipm dbbackup
•ipm dbclean
•ipm restore
|
•ipm backupdir is not supported.
•Supports ipm dbbackup, ipm dbclean, and ipm restore.
For the complete command syntax, see Common Services Framework.
|
Others
|
ipm regen
|
Supported as system jobs.
|
ipm export
|
ipm exportstats.
|
ipm.env file
|
Stores SNMP retry, timeout, timeout increment, source interface, and NVRAM enable in the database.
|
.dbPasswd
|
Not applicable.
|
ipmDbPref.txt
|
Purge settings and polling interval are stored in the database.
Polling interval is specified while creating collectors.
Internetwork Performance Monitor > Collector Management > Admin > Purge Settings
|
