Table Of Contents
Managing System Operations and Configuration in the Monitoring & Report Viewer
Configuring Data Purging and Incremental Backup
Restoring Data from a Backup
Viewing Log Collections
Log Collection Details Page
Viewing Scheduled Jobs
Viewing Process Status
Viewing Data Upgrade Status
Viewing Failure Reasons
Editing Failure Reasons
Specifying E-Mail Settings
Configuring SNMP Preferences
Understanding Collection Filters
Creating and Editing Collection Filters
Deleting Collection Filters
Configuring System Alarm Settings
Configuring Alarm Syslog Targets
Configuring Remote Database Settings
Managing System Operations and Configuration in the Monitoring & Report Viewer
This chapter describes the tasks that you must perform to configure and administer the Monitoring & Report Viewer. The Monitoring Configuration drawer allows you to:
•
Manage data—The Monitoring & Report Viewer handles large volumes of data from ACS servers. Over a period of time, the performance and efficiency of the Monitoring & Report Viewer depends on how well you manage the data.
To do so efficiently, you must back up the data and transfer it to a remote repository on a periodic basis. You can automate this task by scheduling jobs to run periodically. See Configuring Data Purging and Incremental Backup for more information on data backup.
•View log collections—The Monitoring & Report Viewer collects log and configuration data from ACS servers in your deployment, stores the data in the Monitoring & Report Viewer server, and processes it to generate reports and alarms. You can view the details of the logs collected from any of the servers in your deployment. See Viewing Log Collections for more information.
•View scheduled jobs—The Monitoring & Report Viewer allows you schedule tasks that you must perform periodically.
For example, you can schedule an incremental or full backup to be run at regular intervals. You can use the Scheduler to view the details of these tasks. See Viewing Scheduled Jobs for more information on the Scheduler.
•View process status—You can view the status of the various processes that run in the Monitoring & Report Viewer. See Viewing Process Status for more information on the various processes that run in the Monitoring & Report Viewer.
•View data upgrade status—After you upgrade from ACS 5.1 to ACS 5.2 through the CLI, you must ensure that the Monitoring & Report Viewer data upgrade is complete. You can view the Monitoring & Report Viewer data upgrade status through the web interface and switch the Monitoring & Report Viewer database if upgrade is complete. See Viewing Data Upgrade Status for more information.
•Configure and edit failure reasons—The Monitoring & Report Viewer allows you to configure the description of the failure reason code and provide instructions to resolve the problem. See Viewing Failure Reasons for more information on how to edit the failure reason description and instructions for resolution.
•Configure e-mail settings—You can configure the e-mail server and administrator e-mail address. See Specifying E-Mail Settings for more information.
•Configure collection filters—The Monitoring & Report Viewer provides you the option to filter data that is not used for monitoring or troubleshooting purposes. The data that is filtered is not stored in the database and hence saves much needed disk space. See Understanding Collection Filters for more information on how to configure collection filters.
•Configure system alarms—System alarms notify you of critical conditions encountered during the execution of the ACS Monitoring and Reporting viewer. You can configure if and how you would like to receive notification of system alarms. See Configuring System Alarm Settings for more information.
•Configure Syslog targets—If you have configured the Monitoring & Report Viewer to send system alarm notifications as Syslog messages, then you must configure a Syslog target to receive the notification. See Configuring Alarm Syslog Targets for more information.
•Export Monitoring & Report Viewer data—You can configure a remote database, which could either be an Oracle SID or Microsoft AD to which you can export the Monitoring & Report Viewer data.
You can create and run custom reporting applications using the data in your remote database. See Configuring Remote Database Settings for more information on how to configure a remote database with the Monitoring & Report Viewer.
ACS provides you the option to schedule jobs in the Monitoring & Report Viewer. By scheduling jobs, you can automate the monitoring tasks to be run at specified intervals. You can view the status of the scheduled jobs, control events, and intervene whenever necessary. You can schedule the following jobs:
•Data Purge
•Backup
•Event notification (system and threshold alarms)
•Export of Monitoring & Report Viewer data to a remote database
This chapter contains the following sections:
•Configuring Data Purging and Incremental Backup
•Restoring Data from a Backup
•Viewing Log Collections
•Viewing Scheduled Jobs
•Viewing Process Status
•Viewing Data Upgrade Status
•Viewing Failure Reasons
•Editing Failure Reasons
•Specifying E-Mail Settings
•Configuring SNMP Preferences
•Understanding Collection Filters
•Configuring System Alarm Settings
•Configuring Alarm Syslog Targets
•Configuring Remote Database Settings
Configuring Data Purging and Incremental Backup
The Monitoring & Report Viewer database handles large volumes of data. When the database size becomes too large, it slows down all the processes. You do not need all the data all the time. Therefore, to efficiently manage data and to make good use of the disk space, you must back up your data regularly and purge unwanted data that uses up necessary disk space. Purging data deletes it from the database.
Since the Monitoring & Report Viewer database size is large, the backup process takes quite a bit of time to complete. ACS 5.2 introduces the incremental backup option, which enables you to take a complete backup of your Monitoring & Report Viewer database once and then to back up data incrementally (that is, only the updates are backed up and stored separately) from the next time onward.
An incremental backup performs a full database backup the first time it is executed, and subsequently only backs up the updates that are made to the database. Incremental backups are therefore much faster and make efficient use of disk space. You can also configure the frequency and time of incremental backups.
With incremental backups, multiple backup files are stored in the repository. However, when you restore data from an incremental backup, ACS restores data from all the backup files starting from the full backup and continuing until the latest incremental backup.
Note If you disable incremental backup for some reason, ensure that you run a full backup the next time before you can continue with incremental backups again.
You can also configure a full database backup and define its frequency and time.
ACS also allows you to run an immediate backup of the full Monitoring & Report Viewer database. However, you cannot concurrently run an incremental backup, full backup, and data purge. If any of these jobs are running, you must wait for a period of 90 minutes before you can begin the next job.
Timesaver We recommend that you take a full backup the first time and then incrementally back up your data instead of running full backups every time.
Note To ensure that your data is backed up before the purge, configure a data repository via the CLI or the ACS web interface (System Administration > Operations > Software Repositories). Refer to the CLI Reference Guide for the Cisco Secure Access Control System 5.2 for more information on configuring a repository.
If you enable incremental backup, data is purged daily at 4:00 a.m. at the local time zone where the ACS instance that runs the View process is located.
The following database limitations apply for purging:
•If the database disk usage is greater than 114 GB (95% of the total database size of 120 GB), an alarm is sent to the dashboard.
•If the database disk usage is greater than 120 GB (100% of the total database size of 120 GB), a backup is run immediately followed by a purge until the database disk usage is below 120 GB. If the backup fails, check the database disk usage again. The Monitoring & Report Viewer data is purged from the database. The oldest data is purged first.
–If the database disk usage is greater than 120 GB, but less than 150 GB (125% of the total database size of 120 GB), the Monitoring & Report Viewer decides to wait.
–If the backup fails and the database disk usage is greater than 150 GB, a purge occurs regardless of whether or not a backup has occurred until the database disk usage is below 120 GB.
For example, if you specify to preserve 5 months of data, but the database size is over 120 GB, a purge occurs. If the database size remains over 120 GB after the purge, an additional month of data is purged, which results in 4 months of data preserved. Before the purge, the database is backed up.
•If the database size is over 150 GB, a purge occurs regardless of whether or not a database backup has occurred. If the database size remains over 120 GB, additional purges occur until the database is 120 GB or less.
Note Database purge fails if we do not configure the repository and the incremental backup is set to OFF.
Note When incremental backup is disabled, data is purged at the end of every month (UTC time).
You can use the Data Purging and Incremental Backup page to:
•Configure purge window size
•Purge data from the database
•Assign a data repository backup location to manage backup (of the purge job)
•Configure incremental and full backup schedules
•Configure immediate backup.
From the Monitoring & Report Viewer, select Monitoring Configuration > System Operations > Data Management > Removal and Backup.
Table 15-1 Data Purging and Incremental Backup Page
Option
|
Description
|
Data Purging
|
Data Repository
|
Use the drop-down list box to select the data repository backup location to be used during data purging.
See the CLI Reference for ACS 5.2 to add a data repository.
|
Maximum Stored Data Period <num> months.
|
Use the drop-down list box to indicate the number of months, where <num> is the number of months of data you want to retain in the Monitoring & Report Viewer database.
|
View Full Database Backup Now
|
Data Repository
|
Use the drop-down list box to select the data repository backup location to store the full database backup.
|
Backup Now
|
Click Backup Now to start a full Monitoring & Report Viewer database backup.
|
Incremental Backup
|
On
|
Click the On radio button to enable incremental backup. If incremental backup is enabled, the delta is backed up.
|
Off
|
Click the Off radio button to disable incremental backup.
|
Configure Incremental View Database Backup
|
Data Repository
|
Use the drop-down list box to select a data repository for the backup files.
|
Schedule
|
Use the drop-down list boxes to select the time of the day when you want the incremental backup to run.
|
Frequency
|
Use the drop-down list box to choose the frequency at which you want the incremental backup to run. Valid options are:
•Daily
•Weekly—Typically occurs at the end of every week.
•Monthly—Typically occurs at the end of every month.
|
Configure Full View Database Backup
|
Data Repository
|
Use the drop-down list box to select a data repository to store the backup files.
|
Schedule
|
Use the drop-down list boxes to select the time of the day when you want the full View database backup to run.
|
Frequency
|
Use the drop-down list box to choose the frequency at which you want the full View database backup to run. Valid options are:
•Daily
•Weekly—Typically occurs at the end of every week.
•Monthly—Typically occurs at the end of every month.
|
Related Topic
Restoring Data from a Backup
Restoring Data from a Backup
Use this page to restore data from the View database that was backed up earlier. You can restore data from an incremental or full backup. If you choose to restore incremental backup data, ACS restores the full View data backup and then the rest of the incremental backups one at a time in the correct sequence.
To restore data from a backup:
Step 1 Choose Monitoring Configuration > System Operations > Data Management > Restore.
The Incremental Backup Restore page appears, displaying the Available Backups to Restore table. Table 15-2 describes the columns in the table.
Table 15-2 Incremental Backup Restore Page
Column
|
Description
|
Skip View Database backup before Restore
|
Check this check box to skip the Monitoring & Report Viewer database backup before restoring data from a backup. This option, when checked, hastens the restore process.
We recommend that you uncheck this check box because your current data might be lost if a failure occurs during the restore process.
|
Name
|
Name of the backup file. The backup filename includes the time stamp; for example, ACSViewBackup-20090618_003400.
For an incremental backup, click the Expand icon to view the associated full and incremental backups.
|
Date
|
Date on which the backup is run.
|
Repository
|
Name of the repository that contains the backup file.
|
Type
|
The type of backup, Incremental or Full.
|
Step 2 Choose a backup file that you want to restore.
Note If you choose an incremental backup file to restore, ACS restores all previously associated incremental and full backups. This restore process restores only the Monitoring & Report Viewer data.
Step 3 Click Restore to restore the backup file.
Related Topic
Configuring Data Purging and Incremental Backup
Viewing Log Collections
Use this page to view the recently collected logs from ACS servers.
From the Monitoring & Report Viewer, select Monitoring Configuration > System Operations > Log Collection.
Note You can use the refresh symbol to refresh the contents of the page.
Table 15-3 Log Collection Page
Option
|
Description
|
ACS Server
|
The name of the ACS server. Click to open the Log Collection Details page and view recently collected logs.
|
Last Syslog Message
|
Display only. Indicates the arrival time of the most recent syslog message, in the format Ddd Mmm dd hh:mm:ss timezone yyyy, where:
•Ddd = Sun, Mon, Tue, Wed, Thu, Fri, Sat.
•Mmm = Jan, Feb, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
•dd = A two-digit numeric representation of the day of the month, from 01 to 31.
•hh = A two-digit numeric representation of the hour of the day, from 00 to 23.
•mm = A two-digit numeric representation of the minute of the hour, from 00 to 59.
•ss = A two-digit numeric representation of the second of the minute, from 00 to 59.
•timezone = The time zone. In a distributed environment, the time zone displayed for all secondary servers corresponds to the time zone of the server in which the view is active.
If your primary instance has a time zone of PDT and the secondary instance is in UTC, the secondary instance displays the time zone and timestamp of syslog messages with PDT, which corresponds to the time zone of the primary instance.
•yyyy = A four-digit representation of the year.
|
Last Error
|
Display only. Indicates the name of the most recent error message.
|
Last Error Time
|
Display only. Indicates the arrival time of the most recent error message, in the format Ddd Mmm dd hh:mm:ss timezone yyyy, where:
•Ddd = Sun, Mon, Tue, Wed, Thu, Fri, Sat.
•Mmm = Jan, Feb, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
•dd = A two-digit numeric representation of the day of the month, from 01 to 31.
•hh = A two-digit numeric representation of the hour of the day, from 00 to 23.
•mm = A two-digit numeric representation of the minute of the hour, from 00 to 59.
•ss = A two-digit numeric representation of the second of the minute, from 00 to 59.
•timezone = The time zone. In a distributed environment, the timezone displayed for all secondary servers corresponds to the timezone of the server in which the view is active.
If your primary instance has a timezone of PDT and the secondary instance is in UTC, the secondary instance displays the timezone and timestamp of syslog messages with PDT, which corresponds to the timezone of the primary instance.
•yyyy = A four-digit representation of the year.
|
Get Details
|
Click to view recently collected logs for a selected ACS server.
|
Related Topic
Log Collection Details Page
Log Collection Details Page
Use this page to view the recently collected log names for an ACS server.
Step 1 From the Monitoring & Report Viewer, select Monitoring and Reports > Monitoring Configuration > Log Collection.
Step 2 Do one of the following:
•Click the name of an ACS server.
•Select the radio button of an ACS server name which you want to view recently collected logs, and click Get Details.
Note You can use the refresh symbol to refresh the contents of the page.
Table 15-4 Log Collection Details Page
Option
|
Description
|
Log Name
|
Name of the log file.
|
Last Syslog Message
|
Display only. Indicates the arrival time of the most recent syslog message, in the format Ddd Mmm dd hh:mm:ss timezone yyyy, where:
•Ddd = Sun, Mon, Tue, Wed, Thu, Fri, Sat.
•Mmm = Jan, Feb, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
•dd = A two-digit numeric representation of the day of the month, from 01 to 31.
•hh = A two-digit numeric representation of the hour of the day, from 00 to 23.
•mm = A two-digit numeric representation of the minute of the hour, from 00 to 59.
•ss = A two-digit numeric representation of the second of the minute, from 00 to 59.
•timezone = The time zone. In a distributed environment, the timezone displayed for all secondary servers corresponds to the timezone of the server in which the view is active.
If your primary instance has a timezone of PDT and the secondary instance is in UTC, the secondary instance displays the timezone and timestamp of syslog messages with PDT, which corresponds to the timezone of the primary instance.
•yyyy = A four-digit representation of the year.
|
Last Error
|
Display only. Indicates the name of the most recent error message.
|
Last Error Time
|
Display only. Indicates the arrival time of the most recent error message, in the format Ddd Mmm dd hh:mm:ss timezone yyyy, where:
•Ddd = Sun, Mon, Tue, Wed, Thu, Fri, Sat.
•Mmm = Jan, Feb, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
•dd = A two-digit numeric representation of the day of the month, from 01 to 31.
•hh = A two-digit numeric representation of the hour of the day, from 00 to 23.
•mm = A two-digit numeric representation of the minute of the hour, from 00 to 59.
•ss = A two-digit numeric representation of the second of the minute, from 00 to 59.
•timezone = The time zone. In a distributed environment, the timezone displayed for all secondary servers corresponds to the timezone of the server in which the view is active.
If your primary instance has a timezone of PDT and the secondary instance is in UTC, the secondary instance displays the timezone and timestamp of syslog messages with PDT, which corresponds to the timezone of the primary instance.
•yyyy = A four-digit representation of the year.
|
Back
|
Click to return to the Log Collection page.
|
Refresh
|
Click to refresh the data in this page.
|
Related Topic
•Viewing Log Collections
Viewing Scheduled Jobs
Use this page to view the scheduled jobs.
From the Monitoring & Report Viewer, select Monitoring Configuration > System Operations > Scheduler.
Table 15-5 Scheduler Status Page
Option
|
Description
|
Name
|
Display only. The name of the job.
|
Type
|
Display only. The type of associated job; for example, Incremental Backup Utility, Session Termination, DB Aggregation Event, Database Purge Utility, and so on. This list includes both system- and user-defined jobs.
|
Owner
|
Display only. The owner of the associated job—System.
|
Last Run Time
|
Display only. The time of the associated job, in the format Ddd Mmm dd hh:mm:ss timezone yyyy, where:
•Ddd = Sun, Mon, Tue, Wed, Thu, Fri, Sat.
•Mmm = Jan, Feb, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
•dd = A two-digit numeric representation of the day of the month, from 01 to 31.
•hh = A two-digit numeric representation of the hour of the day, from 00 to 23.
•mm = A two-digit numeric representation of the minute of the hour, from 00 to 59.
•ss = A two-digit numeric representation of the second of the minute, from 00 to 59.
•timezone = The time zone.
•yyyy = A four-digit representation of the year.
|
Last Run Result
|
Display only. The result of the last run of the associated job.
|
Status
|
Display only. The status of the associated job.
|
Note When you change any schedule through the ACS web interface, for the new schedule to take effect, you must manually restart the Job Manager process. For more information on the CLI command to restart processes, refer to http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control
_system/5.2/command/reference/cli_app_a.html#wp1618490.
Viewing Process Status
Use this page to view the status of processes running in your ACS environment.
From the Monitoring & Report Viewer, select Monitoring Configuration > System Operations > Process Status.
Note You can click the refresh symbol to refresh the contents of the page.
Table 15-6 Process Status Page
Option
|
Description
|
Process Name
|
Display only. The name of the process. Options can be:
•Database
•Management (ACS management subsystem)
•Runtime (ACS runtime subsystem)
•View-alertmanager
•View-collector
•View-database
•View-jobmanager
•View-logprocessor
|
Status
|
Display only. Indicates the status of the associated process.
|
CPU Utilization
|
Display only. Indicates the CPU utilization of the associated process.
|
Memory Utilization
|
Display only. Indicates the memory utilization of the associated process.
|
Uptime
|
Display only. Indicates the time that the process was started successfully, in the format Ddd Mmm dd hh:mm:ss timezone yyyy, where:
•Ddd = Sun, Mon, Tue, Wed, Thu, Fri, Sat.
•Mmm = Jan, Feb, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
•dd = A two-digit numeric representation of the day of the month, from 01 to 31.
•hh = A two-digit numeric representation of the hour of the day, from 00 to 23.
•mm = A two-digit numeric representation of the minute of the hour, from 00 to 59.
•ss = A two-digit numeric representation of the second of the minute, from 00 to 59.
•timezone = The time zone.
•yyyy = A four-digit representation of the year.
|
Viewing Data Upgrade Status
After you upgrade to ACS 5.2, ensure that the Monitoring & Report Viewer database upgrade is complete.
You can do this through the ACS web interface. Refer to the Installation Guide for the Cisco Secure Access Control System 5.2 for more information on the upgrade process.
To view the status of Monitoring & Report Viewer data upgrade:
Step 1 From the Monitoring & Report Viewer, select Monitoring Configuration > System Operations > Data Upgrade Status.
Step 2 The Data Upgrade Status page appears with the following information:
Status—Indicates whether or not the Monitoring & Report Viewer data upgrade is complete.
Viewing Failure Reasons
Use this page to view failure reasons.
From the Monitoring & Report Viewer, select Monitoring Configuration > System Configuration > Failure Reasons Editor.
Table 15-7 lists the field in the Failure Reasons page.
Table 15-7 Failure Reasons Page
Option
|
Description
|
Failure Reasons
|
The name of possible failure reasons. Click a failure reason name to open the Failure Reasons Editor page.
|
Related Topic
•Editing Failure Reasons
Editing Failure Reasons
Use this page to edit failure reasons and include possible resolution steps to assist administrators when they encounter failures.
Step 1 From the Monitoring & Report Viewer, select Monitoring Configuration > System Configuration > Failure Reasons Editor.
Step 2 Click:
•The name of the failure reason you want to edit.
•The radio button associated with the failure reason you want to edit, then click Edit.
The Failure Reason Editor Page appears as described in Table 15-8.
Table 15-8 Failure Reasons Editor Page
Option
|
Description
|
Failure Reason
|
Display only. The error code and associated failure reason name.
|
Description
|
Enter a free text description of the failure reason to assist administrators; use the text tools as needed.
|
Resolution Steps
|
Enter a free text description of possible resolution steps for the failure reason to assist administrators; use the text tools as needed.
|
Related Topic
Viewing Failure Reasons
Specifying E-Mail Settings
Use this page to specify the e-mail server and administrator e-mail address.
From the Monitoring & Report Viewer, select Monitoring Configuration > System Configuration > Email Settings.
Table 15-9 Email Settings Page
Option
|
Description
|
Mail Server
|
Enter a valid e-mail host server.
|
Mail From
|
Enter the e-mail address name that you want to configure for users to see when they receive e-mail from the system.
|
Configuring SNMP Preferences
You can configure SNMP preferences to authenticate access to MIB objects. The text string that you enter for SNMP preference functions as an embedded password.
To configure SNMP preferences:
Step 1 From the Monitoring & Report Viewer, choose Monitoring Configuration > System Configuration > Collection Filters.
The Collection Filters page appears.
Step 2 Enter a password in the SNMP V2 Read Community String field to authenticate MIB objects.
This Community string is used by ACS to query information via SNMP on AAA client, and cannot used by SNMP manager to query MIB information on ACS. This Community string is used by Network Device Session Status Report which is generated from Monitoring and Reports > Reports > Catalog > Network Device > Session Status Summary.
Step 3 Click Submit.
Understanding Collection Filters
You can create collection filters that allow you to filter and drop syslog events that are not used for monitoring or troubleshooting purposes. When you configure collection filters, the Monitoring & Report Viewer does not record these events in the database and saves much needed disk space.
To set your SNMP preferences:
Step 1 From the Monitoring & Report Viewer, choose Monitoring Configuration > System Configuration > Collection Filters.
The Collection Filters page appears.
Step 2 Configure SNMP preferences to authenticate access to MIB objects. For more information, see Configuring SNMP Preferences.
Step 3 Click Submit.
Your SNMP preference is now configured.
This section contains the following topics:
•Creating and Editing Collection Filters
•Deleting Collection Filters
Creating and Editing Collection Filters
Use this page to create or edit collection filters. To do this:
Step 1 From the Monitoring & Report Viewer, choose Monitoring Configuration > System Configuration > Collection Filters.
The Collection Filters page appears.
Step 2 In the Filters area, do one of the following:
•Click Create to create a collection filter.
•Check the check box of the syslog attribute that you want to edit, then click Edit.
•Check the check box of the syslog attribute that you want to delete, then click Delete.
The Add or Edit Collection Filters page described in Table 15-10 appears.
Table 15-10 Add or Edit Collection Filters Page
Option
|
Description
|
Syslog Attribute
|
•In the Add Filter page, choose any one of the following syslog attributes:
–NAS IP Address
–Access Service
–MAC Address
–User
•In the Edit Filter page, this field is Display only.
|
Value
|
Enter the value of the syslog attribute:
•NAS IP Address—Enter the IP address of the NAS that you want to filter.
•Access Service—Enter the name of the access service that you want to filter.
•MAC Address—Enter the MAC address of the machine that you want to filter.
•User—Enter the username of the user you want to filter.
|
Step 3 Click Submit.
Related Topics
•Creating and Editing Collection Filters
•Deleting Collection Filters
Deleting Collection Filters
To delete a collection filter:
Step 1 Choose Monitoring Configuration > System Configuration > Collection Filters.
The Collection Filters page appears.
Step 2 Check the check box of the collection filter or filters that you want to delete, then click Delete.
The following message appears:
Are you sure you want to delete the selected item(s)?
Step 3 Click Yes.
The Collection Filters page appears without the deleted collection filter.
Configuring System Alarm Settings
See Configuring System Alarm Settings for a description of how to configure system alarm settings.
Configuring Alarm Syslog Targets
See Understanding Alarm Syslog Targets for a description of how to configure the syslog targets.
Configuring Remote Database Settings
Use this page to configure a remote database to which you can export the Monitoring & Report Viewer data. ACS exports data to this remote database at specified intervals. You can schedule the export job to be run once every 1, 2, 4, 6, 8, 12, or 24 hours. You can create custom reporting applications that interact with this remote database. ACS supports the following databases:
•Oracle SQL Developer
•Microsoft SQL Server 2005
To configure a remote database:
Step 1 From the Monitoring & Report Viewer, choose Monitoring Configuration > System Configuration > Remote Database Settings.
The Remote Database Settings Page appears as described in Table 15-11.
Table 15-11 Remote Database Settings Page
Option
|
Description
|
Publish to Remote Database
|
Check the check box for ACS to export data to the remote database periodically. By default, ACS exports data to the remote database every 4 hours.
|
Server
|
Enter the DNS name or the IP address of the remote database.
|
Port
|
Enter the port number of the remote database.
|
Username
|
Enter the username for remote database access.
|
Password
|
Enter the password for remote database access.
|
Publish data every n hours
|
Choose a time interval from the drop-down list box for ACS to export data at the specified interval. Valid options are 1, 2, 4, 6, 8, 12, and 24 hours. The default interval is 4 hours.
|
Database Type
|
The type of remote database that you want to configure:
•Click Microsoft Database radio button to configure a Microsoft database, and enter the name of the remote database.
•Click Oracle SID radio button to configure an Oracle database, and enter the system identifier for the Oracle database.
|
Step 2 Click Submit to configure the remote database.
Note You can view the status of your export job in the Scheduler. See Viewing Scheduled Jobs for more information.
Note If there are two log collector servers that have been configured to export data to a remote database, only one log collector server can export data to the remote database at a time. If a second log collector is pointed to the same remote database, it can cause issues such as over-writing of existing entries in the tables.
Feedback
