- Introduction to Administering Cisco Prime Infrastructure
- Prime Infrastructure Server Settings
- Maintaining Prime Infrastructure Server Health
- Backing Up and Restoring Prime Infrastructure
- Maintaining Network Health
- Managing Data Collection and Retention
- Configuring Access Point and Controller Settings
- Configuring High Availability and Redundancy
- Controlling User Access
- Advanced Monitoring
- Managing Licenses
- Managing Traffic Metrics
- Planning Network Capacity Changes
Cisco Prime Infrastructure 2.0 Administrator Guide
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- February 12, 2018
Chapter: Managing Data Collection and Retention
Managing Data Collection and Retention
One of the roles of an administrator is to manage Prime Infrastructure’s network data collection and retention so that it:
- Scales to fit the real needs of the system’s users.
- Minimizes the burden on monitored devices, applications, and network bandwidth.
- Survives hardware failures.
The following topics explain how to achieve these goals and perform other data management tasks.
- Specifying Data Retention Periods
- Enabling Data Deduplication
- Specifying Where and for How Long to Save Reports
- Controlling Report Storage and Cleanup
- Specifying Inventory Collection After Receiving Events
- Device Configuration Settings
- Controlling Background Data Collection Tasks
- Migrating Data from Cisco Prime LMS to Cisco Prime Infrastructure
Specifying Data Retention Periods
You can configure retention periods for trend data, device health data, and system health data on an hourly, daily, and weekly basis. You can configure retention periods for performance data on a short, medium, and long term basis.
To set retention periods for aggregated data used in timed calculations and network audit calculations:
Step 1
Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Data Retention. The Data Retention page appears.
Step 3 Modify the values as required. See Table 6-1 for the default values.
Note For the best interactive graph data views, change the settings to default value.
Prime Infrastructure Historical Data
There are two types of historical data in Prime Infrastructure, including the following:
- Aggregated historical data—Numeric data that can be gathered as a whole and aggregated to minimum, maximum, or average. Client count is one example of aggregated historical data.
Use the Administration > System Settings > Data Retention page to define the aggregated data retention period. Aggregation types include hourly, daily, and weekly.
The retention period for these aggregation types are defined as Default, Minimum, and Maximum (see Table 6-1 ).
| Trend Data1 Retain Periods |
|||
| Device Health Data2 Retain Periods |
|||
| Performance Data3 Retain Periods |
|||
- Non-aggregated historical data—Numeric data that cannot be gathered as a whole (or aggregated). Client association history is one example of non-aggregated historical data.
You can define a non-aggregated retention period in each data collection task and other settings.
For example, you define the retention period for client association history in Administration > System Settings > Client. By default, the retention period is 31 days or 1 million records. This retention period can be increased to 365 days.
Performance Data Aggregation
Enabling Data Deduplication
Data Deduplication allows you to identify authoritative sources for each of the following classes of application data:
Whenever Prime Infrastructure receives duplicate data about the same network elements and protocols from two or more data sources, it resolves all such conflicts in the authoritative source’s favor.
The Data Deduplication page allows you to specify a data source at a specific site. For example, if you have a Network Analysis Module (NAM) at a branch office as well as NetFlow data that is sent from the same branch, you can specify which data source Prime Infrastructure uses.
Step 1 Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Data Deduplication. The Data Deduplication page appears.
Step 3 Select the Enable Data Deduplication check box to remove the duplicated information from Prime Infrastructure, then click Apply.
Specifying Where and for How Long to Save Reports
To indicate where the scheduled reports reside and for how many days:
Step 1 Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Report. The Report page appears.
Step 3 Enter the path for saving report data files on a local PC. You can edit the existing default path.
Step 4 Specify the number of days to retain reports.
Controlling Report Storage and Cleanup
All scheduled reports are stored in the Scheduled Reports Repository. You will want to ensure that scheduled reports are retained in the report repository for reasonable lengths of time only, and deleted on a regular basis. The default retention scheme is to retain generated reports for a maximum of 31 days.
To customize the retention period:
Step 1 Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Report. The Report page appears.
Step 3 In Repository Path, specify the report repository path on the Prime Infrastructure server.
Step 4 In File Retain Period, specify the maximum number of days reports should be retained.
Specifying Inventory Collection After Receiving Events
The Inventory page allows you to specify if Prime Infrastructure must collect inventory when a syslog event is received for a device.
To configure the inventory settings:
Step 1 Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Inventory. The Inventory page appears.
Step 3 Select the Enable event based inventory collection check box to allow Prime Infrastructure to collect inventory when it receives a syslog event for a device.
Step 4 Select the Enable Syslog and Traps on device check box to allow Prime Infrastructure to enable syslog and trap notifications on newly added devices.
Device Configuration Settings
Backing up and Rolling Back Configurations
You can back up and roll back the running configuration from the Administration > System Settings > Configuration page.
Step 1 Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Configuration.
Step 3 Enter the required information.
Specifying When to Archive Configurations
Configuration archive/rollback is only supported for running-config on devices with WLC software. It is not supported for startup-config.
The configuration changes (such as turning on/off options) that you perform in the Administration > System Settings > Configuration page have no relevance to configuration archive operations. The configurations that you perform in this page are related to template deployment. For example, Backup running Configuration is to archive configuration before any template is deployed.
By default, Prime Infrastructure archives up to five device configuration versions for each device for seven days after:
- Every inventory collection
- Prime Infrastructure receives notification of a configuration change event
To change when Prime Infrastructure archives configurations:
Step 1 Choose Administration > System Settings > Configuration Archive.
Step 2 Change the necessary settings.
Step 3 To have Prime Infrastructure ignore commands for a particular device type, click the Advanced tab, choose the device type, and enter the commands to be ignored.
If the device you specify has a change in its configuration and Prime Infrastructure detects that the change is in one of the commands in the exclude list, Prime Infrastructure does not create an archived version of the configuration with this change.
Controlling Background Data Collection Tasks
Prime Infrastructure performs scheduled data collection tasks on the background on a regular basis. You can enable or disable these collection tasks, change the interval at which each task is performed, or change the retention period for the data (raw or aggregated) collected during each task.
Disabling or limiting these background data collection tasks can have a direct impact on how you use Prime Infrastructure, especially for reporting. To help you consider these impacts, take note of the reports this data is used in. These reports are listed in the Collection Set Details for each task.
To create a background data collection task:
Step 1 Choose Administration > Background Tasks.
Step 2 Under Data Collection Tasks, in the Task column of the table, click the name of the task that you want to create.
Step 3 Enter the required information and click Save.
To enable or disable background data collection tasks in bulk:
Step 1 Choose Administration > Background Tasks.
Step 2 Under Data Collection Tasks, select the check box next to each task you want to enable or disable.
Step 3 Choose Go, then choose to either enable or disable tasks.
Understanding What Data Is Collected and When
The following table describes the various data collection tasks in Prime Infrastructure.
Controlling Prime Infrastructure Background Tasks
The following table describes the background tasks Prime Infrastructure performs. You can manage how and when they are performed by selecting Administration > System Settings > Background Tasks, then selecting the hypertext link for that task in the Other Background Tasks area of the page.
Migrating Data from Cisco Prime LMS to Cisco Prime Infrastructure
Prime Infrastructure supports data migration from Cisco Prime LAN Management Solution (LMS) version 4.2.4 on the Windows NT, Solaris and Linux platforms. The following LMS data can be imported into Prime Infrastructure using CAR CLI:
- Device Credential and Repository (DCR) Devices
- Static Groups
- Dynamic Groups
- Software Image Management Repository Images
- User Defined Templates (Netconfig)
- LMS Local Users
- MIBs
Only the Dynamic Groups containing the rule with the following attributes can be imported from LMS.
- PI attribute Name—LMS attribute name
- Contact—System.Contact
- Description—System.Description
- Location— System.Location
- Management_Address—Device.ManagementIpAddress
- Name—System.Name
- Product_Family—Device.Category
- Product_Series—Device.Series
- Product_Type—Device.Model
- Software_Type—System.OStype
- Software_Version—Image.Version
To migrate LMS data to Prime Infrastructure:
Step 1 Identify the FTP server where LMS backup data is stored, then log in to the Prime Infrastructure server as an admin user.
Step 2 Configure the backup location in the Admin Console by entering the following commands:
admin(config)# repository carsapps
(for example, ftp://10.77.213.137/opt/lms or sftp://10.77.213.137/opt/lms or fdisk:foldername)
admin(config-Repository)# user root password plain xxxxxxx
Step 3 Import the LMS backup into Prime Infrastructure using the following command:
admin# lms migrate repository carsapps
Step 4 Log back in to the Prime Infrastructure user interface.
The following table lists the locations of the imported LMS data:
|
|
|
|---|---|
Feedback