- Print
- PDF
You can manage the creation and transfer of history files, which are logs that contain statistics related to the services (for example, flowmeter) for which the history feature has been enabled.
You can also configure the Cisco Provider Connectivity Assurance Sensor Control to transfer its history files to a server.
Note: The exported history CSV files may not all contain the identical range of period numbers, depending on when the given history metrics were collected. Enabling multiple categories of history metrics with many instances requires more time for processing than the length of the reporting period. Since the history files are processed sequentially, some exported files may consequently present different period numbers compared to others.
Creating History Files
▶ To enable the creation of history files
Access the page System ▶ Agent ▶ History.
In the Local Configuration section of the screen, select the Enable History box for each feature whose history you want to retain.
Note: Disabling the history disables the filling; enabling the filing enables the history.
In the Local Configuration section of the screen, select the Enable Filing box for each feature for which you want to create history files, then enter the Period after which you want the data files to be collected for storage.
Click Apply.
For more information on specific parameters, refer to the following table.
History Files, Local Configuration (System ▶ Agent ▶ History)
Local Configuration
Parameter | Description |
---|---|
Enable history | Select this box to allow the creation of history files, which are stored in RAM. You can access these files via the SNMP get command. |
Enable filing | Select this box to allow the history files to be stored locally in nonvolatile memory (NVM). Storing these files protects against losing history statistics in the event of a power failure or system restart. If this box is not selected, the local history files for this feature are removed. Use the Scheduling and File Transfer Configuration frame on this page to have the history files pushed to a server. History files can be stored locally for the following features:
|
Period (mins) | Indicate the frequency at which the history statistics will be collected, expressed in minutes. Acceptable values range from 1 to 60. |
Transferring History Files
▶ To enable the transfer of history files
Access the page System ▶ Agent ▶ History.
Customize when the history files will be scheduled by completing the fields in the Scheduling part of the Scheduling and File Transfer Configuration section of the screen.
Provide the URL where the file transfer server is located and the SCP password in the File Transfer part of the Scheduling and File Transfer Configuration section of the screen.
Choose a Period Mode and any optional fields in the File Options section, then click Apply in the Scheduling and File Transfer Configuration section of the screen.
For more information on specific parameters, refer to the following tables.
History Files, Scheduling and Files Transfers (System ▶ Agent ▶ History)
Scheduling and File Transfer Configuration
Parameter | Description |
---|---|
Enable scheduler | Check this box to enable automatic transfer of history buckets report files from the Sensor Control to a server. The details of the scheduler and server are configured in this page. Note: Report files will only be generated for the services whose Enable Filing box in the Local Configuration frame is enabled. |
Scheduled hours | Indicate when to transfer the history buckets by making a selection from the list. Press the CTRL key to select more than one time. Note: Finer granularity is possible using the Hourly Minutes or Periodic Minutes field, in combination with the Schedule Offset field. |
Scheduling mode | Select a value from the drop-down list to set the type of interval that will be used for history bucket file transfers:
|
Hourly minutes | Use this feature to set the scheduling to trigger every 15 minutes, either right on the hour or at the 00:15, 00:30 and 00:45 marks. Any value combination is valid, provided at least one box is selected and Hourly is selected in the drop-down list above the boxes. |
Periodic minutes | Select a value from the drop-down list to set the scheduling trigger interval. Example:
Any value is valid, provided that Periodic is selected in the drop-down list above the boxes. |
Schedule offset | Enter a value in this to set the number of minutes by which to offset file transfers.
This field allows you to generate reports as often as four times per hour, at any minute thereof. When a large number of units are set to generate report files, the offset feature can be used to spread the load on the network and servers. Examples:
|
Random offset | Enter a value in this field add a random number of seconds to the number of minutes entered in the Schedule Offset field. Adding a random offset allows multiple units to send reports to the same server at slightly different times. This relieves the load that would be created by several concurrent transfers. The combined value of the schedule offset and random offset cannot exceed 15 minutes (900 seconds) in Hourly mode or the value of Periodic Minutes in Periodic mode. If the sum of the schedule offset and the random offset exceeds the specified limit, the random offset value is automatically adjusted to the highest possible value. |
File Transfer
Parameter | Description |
---|---|
Server URL | Enter the full URL of the server to which the history bucket files will be sent once retrieved. Note: The following special characters are not allowed in the URL input: "<", ">", "\n", "\r", "\t". Examples: http://example.com ftp://username:password@example.com ftps://username:password@example.com sftp://username@192.0.2.0/24 tftp://192.0.2.0/24 scp://username@192.0.2.0/24:/target_directory scp://username@[2001:DB8::/32]:/target_directory |
SCP password | Enter the password required for SCP and SFTP transfers. |
File Options
Parameter | Description |
---|---|
Period mode | Indicate which periods to include in the reports by selecting one of the available options:
Note: Enabling "All Available Periods" mode when more than 1000 policies or 1000 bandwidth regulators have been activated can lead to prolonged, significant CPU usage. The same behavior may be observed when the remote server is unreachable for an extended period of time. |
Options | You can exercise greater control over how the reports are generated:
|
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks