Navigating Cisco Prime Internetwork Performance Monitor Tasks in LMS 4.2
Cisco Prime Internetwork Performance Monitor (IPM) is a network troubleshooting application that gauges network response time and availability. It allows network administrators to proactively discover and address end-to-end network performance issues. Real-time and historical reports are used for network troubleshooting, helping administrators locate and diagnose congestion and latency problems.
This chapter provides mapping of IPM tasks in LMS 4.2.
You can define one or more new operations to fit your needs. Although, you cannot modify the default operations, you can use them as templates for creating your own operations.
The List of Operations page allows you to view the list of system-defined and user-defined operations and filter the list of operations.
You can view, edit, create and delete user defined operation
You can list all the operation-based (system-defined) and user-defined collector groups in IPM.
You can list collectors, filter collectors, view collector details and view the collector statistics or compare the latency of collectors based on the granularity.
You can also edit collector details, delete, monitor, start, stop, create collectors, export and import collectors, and reconfigure collectors.
You can use the Log Level Settings option to set the log levels for LMS modules. You can either set the log levels for all LMS modules or at a module level.
The Application Settings page allows you to copy IP SLA (Internet Protocol Service Level Agreement) configuration to running-config, and set managed source interface.
Before adding devices to LMS you can use the Auto Allocation Settings option to enable automatic allocation of devices from Device Credentials Repository (DCR).
Admin > Network: Purge Settings > IPSLA Data Purge 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.
IPM purges the historical data automatically everyday, based on the purge period specified on the Purge Settings page. If the Purge period is not specified, it purges the historical data based on the default values.