In ACS 5.5, you can schedule reports for a future date in such a way that ACS automatically generates the report. This can be done using the scheduled reports feature available in the Monitoring and Reports web interface. This feature is available only for the for RADIUS authentication, RADIUS accounting, TACACS+ authentication, TACACS+ authorization, and TACACS+ accounting reports. ACS generates the scheduled reports based on the given time range, exports them to a .csv file, and stores them in the specified remote repository.
Previous releases of ACS allowed you to export reports and copy the .csv file to the local file system. You need to copy the exported file using the copy command to a remote location. But in ACS 5.5, you have the option to configure the remote repository to which the generated reports are exported and stored.
An email notification is sent whenever a scheduled report is generated successfully. The email notification contains the following information:
Scheduled Report Name—Name of the scheduled report.
Cause—The reason for which you have received this email or alarm notification. In this case, the notification is a scheduled report alarm.
Details—The details of the email notification.
Repository Name—Name of the remote repository where the generated reports are stored.
Repository URL—URL of the remote repository.
File Name—Name of the generated report. The format of the filename is <Name of the Scheduled Report>-<Report Type>. For instance, if the name of the scheduled report is “report1” and the report type is RADIUS_Accounting, then the filename is displayed as: report1-RADIUS_Accounting.csv
Generated on—The date and time at which the report is generated.
ACS does not generate any alarms or email notifications if a scheduled report generation fails. To know the status of the scheduled reports, go to the Monitoring Configuration > System Operations > Scheduler page and check for the status.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :