-
User Guide for Internetwork Performance Monitor 4.0
-
Preface
-
Chapter 1 Overview of IPM
-
Chapter 2 What's New in This Release
-
Chapter 3 Adding Devices Using Device Management
-
Chapter 4 Managing IPM Operations
-
Chapter 5 Managing Collectors in IPM
-
Chapter 6 Managing Collector Groups
-
Chapter 7 Managing Admin Settings in IPM
-
Chapter 8 IPM Reports and Graphs
-
Chapter 9 IP SLA Feature Mapping
-
Chapter 10 IPM CLI Command Reference
-
Appendix A IPM 4.0 FAQs and Troubleshooting Tips
-
Appendix B : IPM 4.0 Database Schema
-
Index
-
Table Of Contents
Managing Admin Settings in IPM
Copying IP SLA Configuration to Running-Config
Managed Source Interface Setting
Managing Admin Settings in IPM
You can set system-wide parameters for IPM such as log level settings, application settings, and purge audit and historical reports from the Admin module (Internetwork Performance Monitor > Admin).
This chapter contains the following topics:
Log Level Settings
You can use the Log Level Settings option to set the log levels for IPM modules. You can either set the log levels for all IPM modules or at a module level. By default, the log level is `INFO' for all the modules after installation.
The log files are stored at the following location:
•
Windows: NMSROOT\log, where NMSROOT is the CiscoWorks installation directory.
•
To set the log level:
Step 1
The Log Level Settings page appears as shown in Figure 7-1.
Figure 7-1 Log Level Settings
Step 2
Step 3
Step 4
A message appears that the log levels have been successfully updated.
To clear the settings, click Reset.
Step 5
Application Settings
The Application Settings page allows you to automatically update the Common Services' Device Credential Repository (DCR) devices in IPM, copy IP SLA (Internet Protocol Service Level Agreement) configuration to running-config, and set managed source interface.
•
•
Figure 7-2 Application Settings
Auto Update From DCR
You can import devices automatically from Common Services' Device Credential Repository (DCR) to IPM by setting the Automatically Manage Devices from Credential Repository option on the Application Settings page.
However, the devices that were in DCR before setting this option are not added into IPM. You can add those devices manually. For more information on how to import the devices manually, see Manually Importing DCR Devices.
To automatically update devices from DCR:
Step 1
The Application Settings page appears as shown in Figure 7-2.
Step 2
Step 3
A message appears that the application settings have been modified successfully.
Step 4
Copying IP SLA Configuration to Running-Config
You can see the IP SLA (Internet Protocol Service Level Agreement) probes for the collectors that you configure in IPM at the command line interface of the router in the running configuration by selecting the Copy IP SLA Configuration to running-config option on the Application Settings page.
This option is not selected by default. You cannot view the IP SLA probes in the running configuration of the source router if this option is not set.
Note
To view the configured collectors in the running configuration:
Step 1
The Application Settings page appears as shown in Figure 7-2.
Step 2
Step 3
A message appears that the application settings have been modified successfully.
Step 4
Managed Source Interface Setting
Managed Source Interface configures the source router with appropriate IP address for sending/receiving the IP SLA (Internet Protocol Service Level Agreement) operation packets.
You can set a source interface address for the source router by selecting the Use Managed Source Interface Address option on the Application Settings page. After this option is set, the source router uses the managed interface address while configuring the collectors on the source device.
However, you can also specify a source interface address while configuring a collector. In that case, the source router uses the specified interface.
If the Use Managed Source Interface option is not set, then by default, the source router selects the source interface for the collector from the Routing Table based on the IP address of the destination.
To set a source interface address:
Step 1
The Application Settings page appears as shown in Figure 7-2.
Step 2
Step 3
A message appears that the application settings have been modified successfully.
Step 4
Purging Settings
The Purge Settings page allows you to set the purge period for historical and audit reports. You can also set the purge period from the Setup Center.
Figure 7-3 Purge Settings
Purging Historical Data
IPM purges the historical data automatically everyday based on the purge period specified on the Purge Settings page. It purges the historical data that is older than the specified purge period. If the purge period is not specified, it purges the historical data based on the default values.
The minute-based reports are purged daily by default.
To purge historical reports:
Step 1
The Purge Settings page appears as shown in Figure 7-3.
Step 2
Step 3
A message appears that the purge settings are updated successfully.
Step 4
Table 7-2 Purging Reports
Hourly
Specify the number of days for which you want to keep the hourly historical data in the database.
The default value is 32 days.
Daily
Specify the number of days for which you want to keep the daily historical data in the database.
The default value is 180 days.
Weekly
Specify the number of weeks for which you want to keep the weekly historical data in the database.
The default value is 12 weeks.
Monthly
Specify the number of months for which you want to keep the monthly historical data in the database.
The default value is 12 months.
Audit Reports Purge Period
Allows you to purge the audit reports. The default purge period for audit reports is 180 days.
For more information, see Purging Audit Reports.
