- Preface
- Introducing ACS
- Migrating from ACS 4.x to ACS 5.5
- Understanding ACS Policy Model
- Common Scenarios Using ACS
- Understanding My Workspace
- Post Installation Tasks
- Managing Network Resources
- Managing Users and Identity Stores
- Managing Policy Elements
- Managing Access Policies
- Monitoring and Reporting
- Managing Alarms
- Managing Reports
- Troubleshooting ACS with the Monitoring and Report Viewer
- Monitoring & Report Viewer System Operations
- Managing System Administrators
- Configuring System Operations
- Managing System Administration Configurations
- Understanding Logging
- AAA Protocols
- Authentication in ACS 5.5
- Open Source License Acknowledgements
- Glossary
- Index
User Guide for Cisco Secure Access Control System 5.5
- Updated:
- November 1, 2016
Chapter: Managing Alarms
- Understanding Alarms
- Viewing and Editing Alarms in Your Inbox
- Understanding Alarm Schedules
- Creating, Editing, and Duplicating Alarm Thresholds
- Configuring General Threshold Information
- Configuring Threshold Criteria
- Passed Authentications
- Failed Authentications
- Authentication Inactivity
- TACACS Command Accounting
- TACACS Command Authorization
- ACS Configuration Changes
- ACS System Diagnostics
- ACS Process Status
- ACS System Health
- ACS AAA Health
- RADIUS Sessions
- Unknown NAD
- External DB Unavailable
- RBACL Drops
- NAD-Reported AAA Downtime
- Configuring Threshold Notifications
Managing Alarms
The Monitoring feature in ACS generates alarms to notify you of critical system conditions. The monitoring component retrieves data from ACS. You can configure thresholds and rules on this data to manage alarms.
Alarm notifications are displayed in the web interface and you can get a notification of events through e-mail and Syslog messages. ACS filters duplicate alarms by default.
Understanding Alarms
There are two types of alarms in ACS:
Threshold alarms are defined on log data collected from ACS servers that notify you of certain events. For example, you can configure threshold alarms to notify you of ACS system health, ACS process status, authentication activity or inactivity, and so on.
You define threshold conditions on these data sets. When a threshold condition is met, an alarm is triggered. While defining the threshold, you also define when the threshold should be applied (the time period), the severity of the alarm, and how the notifications should be sent.
Fifteen categories of available alarm thresholds allow you to monitor many different facets of ACS system behavior. See Creating, Editing, and Duplicating Alarm Thresholds for more information on threshold alarms.
System alarms notify you of critical conditions encountered during the execution of the ACS Monitoring and Reporting viewer. System alarms also provide informational status of system activities, such as data purge events or failure of the log collector to populate the View database.
You cannot configure system alarms, which are predefined. However, you do have the option to disable system alarms or decide how you want to be notified if you have enabled them.
This section contains the following topics:
Evaluating Alarm Thresholds
ACS evaluates the threshold conditions based on a schedule. You define these schedules and, while creating a threshold, you assign a schedule to it. A schedule consists of one or more continuous or noncontinuous periods of time during the week.
For example, you can create a schedule that is active from 8:00 a.m. to 5:00 p.m., Monday through Friday. See Understanding Alarm Schedules for more information. When you assign this schedule to a threshold, ACS evaluates the threshold and generates alarms only during the active period.
ACS evaluates the thresholds periodically depending on the number of thresholds that are currently enabled.
Table 12-1 provides the length of the evaluation cycle for a given number of thresholds.
|
|
|
|---|---|
When an evaluation cycle begins, ACS evaluates each enabled threshold one after another. If the schedule associated with the threshold allows the threshold to be executed, ACS evaluates the threshold conditions. An alarm is triggered if the condition is met. See Creating, Editing, and Duplicating Alarm Thresholds for more information.
Note
System alarms do not have an associated schedule and are sent immediately after they occur. You can only enable or disable system alarms as a whole.
Notifying Users of Events
When a threshold is reached or a system alarm is generated, the alarm appears in the Alarms Inbox of the web interface. From this page, you can view the alarm details, add a comment about the alarm, and change its status to indicate that it is Acknowledged or Closed.
The alarm details in this page, wherever applicable, include one or more links to the relevant reports to help you investigate the event that triggered the alarm.
The Dashboard also displays the five most recent alarms. Alarms that you acknowledge or close are removed from this list in the Dashboard.
ACS provides you the option to receive notifications in the following formats:
- E-mail—Contains all the information that is present in the alarm details page. You can configure a list of recipients to whom this e-mail must be sent. ACS 5.5 provides you the option to receive notification of events through e-mail in HTML format.
- Syslog message—Sent to the Linux or Windows machines that you have configured as alarm syslog targets. You can configure up to two alarm syslog targets.
Viewing and Editing Alarms in Your Inbox
You can view alarms that ACS generates based on a threshold configuration or a rule on a set of data collected from ACS servers. Alarms that have met the configured thresholds are sent to your inbox. After you view an alarm, you can edit the status of the alarm, assign the alarm to an administrator, and add notes to track the event.
To view an alarm in your inbox, select Monitoring and Reports > Alarms > Inbox.
The Inbox page appears with a list of alarms that ACS triggered. Table 12-2 describes the fields on the Alarms page. Table 12-3 lists the system alarms in ACS 5.5 and its severity.
Note The Alarm for ACS database exceeding the quota is sent only when the total size of the ACS database exceeds the quota. Total size of ACS database = acs*.log + acs.db where acs*.log is the ACS database log file. Both the acs*.log and acs.db files are present under /opt/CSCOacs/db.
Note ACS cannot be used as a remote syslog server. But, you can use an external server as a syslog server. If you use an external server as a syslog server, no alarms can be generated in the ACS view as the syslog messages are sent to the external syslog server. If you want to generate the alarms in ACS view, set the logging option as localhost using CLI.
Step 1 Select Monitoring and Reports > Alarms > Inbox.
The Inbox page appears with a list of alarms that ACS triggered.
Step 2 Check the check box next to the alarm that you want to edit and click Edit.
The Inbox - Edit page appears with the following tabs:
- Alarm—This tab provides more information on the event that triggered the alarm. Table 12-4 describes the fields in the Alarm tab. You cannot edit any of the fields in the Alarm tab.
Step 3 Modify the fields in the Status tab as required. Table 12-5 describes the fields.
Step 4 Click Submit to save the changes.
The Alarms page appears with the changes you made.
Understanding Alarm Schedules
You can create alarm schedules to specify when a particular alarm threshold is run. You can create, edit, and delete alarm schedules. You can create alarm schedules to be run at different times of the day during the course of a seven-day week.
By default, ACS comes with the non-stop alarm schedule. This schedule monitors events 24 hours a day, seven days a week.
To view a list of alarm schedules, choose Monitoring and Reports > Alarms > Schedules. The Alarm Schedules page appears. Table 12-6 lists the fields in the Alarm Schedules page.
|
|
|
|---|---|
Enter a search criterion to filter the alarm schedules based on your search criterion. |
|
Click Clear Filter to clear the search results and list all the alarm schedules. |
|
This section contains the following topics:
- Creating and Editing Alarm Schedules
- Assigning Alarm Schedules to Thresholds
- Deleting Alarm Schedules
Creating and Editing Alarm Schedules
To create or edit an alarm schedule:
Step 1 Choose Monitoring and Reports > Alarms > Schedules.
The Alarm Schedules page appears.
Step 2 Do either of the following:
- Click Create.
- Check the check box next to the alarm schedule that you want to edit, then click Edit.
The Alarm Schedules - Create or Edit page appears. Table 12-7 lists the fields in the Alarms Schedules - Create or Edit page.
|
|
|
|---|---|
|
|
|
Name of the alarm schedule. The name can be up to 64 characters in length. |
|
A brief description of the alarm schedule; can be up to 255 characters in length. |
|
|
Click a square to select or deselect that hour. Use the Shift key to select or deselect a block starting from the previous selection. For more information on schedule boxes, see Schedule Boxes. |
|
Click Select All to create a schedule that monitors for events all through the week, 24 hours a day, 7 days a week. |
|
When you edit a schedule, click Undo All to revert back to the previous schedule. |
|
Step 3 Click Submit to save the alarm schedule.
The schedule that you create is added to the Schedule list box in the Threshold pages.
Assigning Alarm Schedules to Thresholds
When you create an alarm threshold, you must assign an alarm schedule for the threshold. To assign an alarm schedule:
Step 1 Choose Monitoring and Reports > Alarms > Thresholds.
Note This procedure only describes how to assign a schedule to a threshold. For detailed information on how to create, edit, or duplicate a threshold, see Creating, Editing, and Duplicating Alarm Thresholds.
Step 2 Do one of the following.
Step 3 In the General tab, choose the schedule that you want from the Schedule drop-down list box.
Step 4 Click Submit to assign the schedule to the threshold.
Deleting Alarm Schedules
Note Before you delete an alarm schedule, ensure that it is not referenced by any thresholds that are defined in ACS. You cannot delete the default schedule (nonstop) or schedules that are referenced by any thresholds.
Step 1 Choose Monitoring and Reports > Alarms > Schedules.
The Alarm Schedules page appears.
Step 2 Check the check box next to the alarm schedule that you want to delete, then click Delete.
The following message appears:
Step 3 Click Yes to delete the alarm schedule.
The alarm schedule page appears without the schedule that you deleted.
Creating, Editing, and Duplicating Alarm Thresholds
Use this page to configure thresholds for each alarm category. You can configure up to 100 thresholds.
To configure a threshold for an alarm category:
Step 1 Select Monitoring and Reports > Alarms > Thresholds.
The Alarms Thresholds page appears as described in Table 12-8 :
Step 2 Do one of the following:
- Click Create.
- Check the check box next to the alarm that you want to duplicate, then click Duplicate .
- Click the alarm name that you want to modify, or check the check box next to the alarm that you want to modify, then click Edit.
- Check the check box next to the alarm that you want to enable, then click Enable.
- Check the check box next to the alarm that you want to disable, then click Disable.
Step 3 Modify fields in the Thresholds page as required. See the following pages for information about valid field options:
Step 4 Click Submit to save your configuration.
The alarm threshold configuration is saved. The Threshold page appears with the new configuration.
- Configuring General Threshold Information
- Configuring Threshold Criteria
- Configuring Threshold Notifications
Alarm Threshold Messages
A general alarm threshold message would include the following:
<month> <date> <time> <acs instance name> <alarm category> <syslog id> <number of fragments> <first fragment> <alarm threshold name = “Value”>, <severity = “value”>, <cause = “value”>, <Detail = “Other details”>.
A sample alarm threshold message is given below:
<178> Apr 2 13:23:00 ACS Server1 0000000005 1 0 ACSVIEW_ALARM Threshold alarm name = “System_Diagnostics”, severity = Warn, cause = “Alarm caused by System_Diagnostics threshold”, detail = “(ACS Instance = ACS Server, Category = CSCOacs_Internal_Operations_Diagnostics, Severity = Warn, Message Text = CTL for syslog server certificate is empty)”
Table 12-9 displays the list of all alarm threshold messages.
Configuring General Threshold Information
To configure general threshold information, fill out the fields in the General Tab of the Thresholds page. Table 12-10 describes the fields.
Configuring Threshold Criteria
ACS 5.5 provides the following threshold categories to define different threshold criteria:
- Passed Authentications
- Failed Authentications
- Authentication Inactivity
- TACACS Command Accounting
- TACACS Command Authorization
- ACS Configuration Changes
- ACS System Diagnostics
- ACS Process Status
- ACS System Health
- ACS AAA Health
- RADIUS Sessions
- Unknown NAD
- External DB Unavailable
- RBACL Drops
- NAD-Reported AAA Downtime
Passed Authentications
When ACS evaluates this threshold, it examines the RADIUS or TACACS+ passed authentications that occurred during the time interval that you have specified up to the previous 24 hours.
These authentication records are grouped by a common attribute, such as ACS Instance, User, Identity Group, and so on. The number of records within each of these groups is computed. If the count computed for any of these groups exceeds the specified threshold, an alarm is triggered.
For example, if you configure a threshold with the following criteria: Passed authentications greater than 1000 in the past 20 minutes for an ACS instance. When ACS evaluates this threshold and three ACS instances have processed passed authentications as follows:
|
|
|
|---|---|
An alarm is triggered because at least one ACS instance has greater than 1000 passed authentications in the past 20 minutes.
Note You can specify one or more filters to limit the passed authentications that are considered for threshold evaluation. Each filter is associated with a particular attribute in the authentication records and only those records whose filter value matches the value that you specify are counted. If you specify multiple filters, only the records that match all the filter conditions are counted.
Modify the fields in the Criteria tab as described in Table 12-11 to create a threshold with the passed authentication criteria.
Failed Authentications
When ACS evaluates this threshold, it examines the RADIUS or TACACS+ failed authentications that occurred during the time interval that you have specified up to the previous 24 hours. These authentication records are grouped by a common attribute, such as ACS Instance, User, Identity Group, and so on.
The number of records within each of these groups is computed. If the count computed for any of these groups exceeds the specified threshold, an alarm is triggered.
For example, if you configure a threshold with the following criteria: Failed authentications greater than 10 in the past 2 hours for Device IP. When ACS evaluates this threshold, if failed authentications have occurred for four IP addresses in the past two hours as follows:
|
|
|
|---|---|
An alarm is triggered because at least one Device IP has greater than 10 failed authentications in the past 2 hours.
Note You can specify one or more filters to limit the failed authentications that are considered for threshold evaluation. Each filter is associated with a particular attribute in the authentication records and only those records whose filter value matches the value that you specify are counted. If you specify multiple filters, only the records that match all the filter conditions are counted.
Modify the fields in the Criteria tab as described in Table 12-12 to create a threshold with the failed authentication criteria.
Authentication Inactivity
When ACS evaluates this threshold, it examines the RADIUS or TACACS+ authentications that occurred during the time interval that you have specified up to the previous 31 days. If no authentications have occurred during the specified time interval, an alarm is triggered.
You can specify filters to generate an alarm if no authentications are seen for a particular ACS instance or device IP address during the specified time interval.
If the time interval that you have specified in the authentication inactivity threshold is lesser than that of the time taken to complete an aggregation job, which is concurrently running, then this alarm is suppressed.
The aggregation job begins at 00:05 hours every day. From 23:50 hours, up until the time the aggregation job completes, the authentication inactivity alarms are suppressed.
For example, if your aggregation job completes at 01:00 hours today, then the authentication inactivity alarms will be suppressed from 23:50 hours until 01:00 hours.
Note If you install ACS between 00:05 hours and 05:00 hours, or if you have shut down your appliance for maintenance at 00:05 hours, then the authentication inactivity alarms are suppressed until 05:00 hours.
Choose this category to define threshold criteria based on authentications that are inactive. Modify the fields in the Criteria tab as described in Table 12-13 .
TACACS Command Accounting
When ACS evaluates this threshold, it examines the TACACS+ accounting records that it received during the interval between the previous and current alarm evaluation cycle.
If one or more TACACS+ accounting records match, it calculates the time that has elapsed since the previous alarm evaluation cycle. When it reaches two, three, or five minutes depending on the number of active thresholds, ACS examines the TACACS+ accounting records received during the interval between the previous and current alarm evaluation cycle. I
If one or more TACACS+ accounting records match a specified command and privilege level, an alarm is triggered.
You can specify one or more filters to limit the accounting records that are considered for threshold evaluation. Each filter is associated with a particular attribute in the records, and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on TACACS commands. Modify the fields in the Criteria tab as described in Table 12-14 .
TACACS Command Authorization
When ACS evaluates this threshold, it examines the TACACS+ accounting records that it received during the interval between the previous and current alarm evaluation cycle.
If one or more TACACS+ accounting records match, it calculates the time that has lapsed since the previous alarm evaluation cycle. When it reaches two, three, or five minutes depending on the number of active thresholds, ACS examines the TACACS+ authorization records received during the interval between the previous and current alarm evaluation cycle.
If one or more TACACS+ authorization records match a specified command, privilege level, and passed or failed result, an alarm is triggered.
You can specify one or more filters to limit the authorization records that are considered for threshold evaluation. Each filter is associated with a particular attribute in the records, and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on TACACS command authorization profile. Modify the fields in the Criteria tab as described in Table 12-15 .
ACS Configuration Changes
When ACS evaluates this threshold, it examines the accounting records that it received during the interval between the previous and current alarm evaluation cycle.
If one or more accounting records match, it calculates the time that has lapsed since the previous alarm evaluation cycle. When it reaches two, three, or five minutes depending on the number of active thresholds, ACS examines the ACS configuration changes made during the interval between the previous and current alarm evaluation cycle. If one or more changes were made, an alarm is triggered.
You can specify one or more filters to limit which configuration changes are considered for threshold evaluation. Each filter is associated with a particular attribute in the records, and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on configuration changes made in the ACS instance. Modify the fields in the Criteria tab as described in Table 12-16 .
ACS System Diagnostics
When ACS evaluates this threshold, it examines the accounting records that it received during the interval between the previous and current alarm evaluation cycle.
If one or more accounting records match, it calculates the time that has lapsed since the previous alarm evaluation cycle. When it reaches two, three, or five minutes depending on the number of active thresholds, ACS examines system diagnostic records generated by the monitored ACS during the interval.
If one or more diagnostics were generated at or above the specified security level, an alarm is triggered. You can specify one or more filters to limit which system diagnostic records are considered for threshold evaluation.
Each filter is associated with a particular attribute in the records and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on system diagnostics in the ACS instance. Modify the fields in the Criteria tab as described in Table 12-17 .
ACS Process Status
When ACS evaluates this threshold, it examines the accounting records that it received during the interval between the previous and current alarm evaluation cycle.
If one or more accounting records match, it calculates the time that has lapsed since the previous alarm evaluation cycle. When it reaches two, three, or five minutes depending on the number of active thresholds, ACS determines whether any ACS process has failed during that time.
If ACS detects one or more failures, an alarm is triggered. You can limit the check to particular processes or a particular ACS instance or both.
Choose this category to define threshold criteria based on ACS process status. Modify the fields in the Criteria tab as described in Table 12-18 .
ACS System Health
When ACS evaluates this threshold, it examines whether any system health parameters have exceeded the specified threshold in the specified time interval up to the previous 60 minutes. These health parameters include percentage of CPU utilization, percentage of memory consumption, and so on.
If any of the parameters exceed the specified threshold, an alarm is triggered. By default, the threshold applies to all ACS instances in your deployment. If you want, you can limit the check to just a single ACS instance.
Choose this category to define threshold criteria based on the system health of ACS. Modify the fields in the Criteria tab as described in Table 12-19 .
ACS AAA Health
When ACS evaluates this threshold, it examines whether any ACS health parameters have exceeded the specified threshold in the specified time interval up to the previous 60 minutes. ACS monitors the following parameters:
If any of the parameters exceed the specified threshold, an alarm is triggered. By default, the threshold applies to all monitored ACS instances in your deployment. If you want, you can limit the check to just a single ACS instance.
Modify the fields in the Criteria tab as described in Table 12-20 .
RADIUS Sessions
When ACS evaluates this threshold, it determines whether any authenticated RADIUS sessions have occurred in the past 15 minutes where an accounting start event has not been received for the session. These events are grouped by device IP address, and if the count of occurrences for any device IP exceeds the specified threshold, an alarm is triggered. You can set a filter to limit the evaluation to a single device IP.
Choose this category to define threshold criteria based on RADIUS sessions. Modify the fields in the Criteria tab as described in Table 12-21 .
Unknown NAD
When ACS evaluates this threshold, it examines the RADIUS or TACACS+ failed authentications that have occurred during the specified time interval up to the previous 24 hours. From these failed authentications, ACS identifies those with the failure reason Unknown NAD.
The unknown network access device (NAD) authentication records are grouped by a common attribute, such as ACS instance, user, and so on, and a count of the records within each of those groups is computed. If the count of records for any group exceeds the specified threshold, an alarm is triggered. This can happen if, for example, you configure a threshold as follows:
Unknown NAD count greater than 5 in the past 1 hour for a Device IP
If in the past hour, failed authentications with an unknown NAD failure reason have occurred for two different device IP addresses as shown in the following table, an alarm is triggered, because at least one device IP address has a count greater than 5.
|
|
|
|---|---|
You can specify one or more filters to limit the failed authentications that are considered for threshold evaluation. Each filter is associated with a particular attribute in the records and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on authentications that have failed because of an unknown NAD. Modify the fields in the Criteria tab as described in Table 12-22 .
External DB Unavailable
When ACS evaluates this threshold, it examines the RADIUS or TACACS+ failed authentications that have occurred during the specified interval up to the previous 24 hours.
From these failed authentications, ACS identifies those with the failure reason, External DB unavailable. Authentication records with this failure reason are grouped by a common attribute, such as ACS instance, user, and so on, and a count of the records within each of those groups is computed.
If the count of records for any group exceeds the specified threshold, an alarm is triggered. This can happen if, for example, you configure a threshold as follows:
External DB Unavailable count greater than 5 in the past one hour for a Device IP
If in the past hour, failed authentications with an External DB Unavailable failure reason have occurred for two different device IP addresses as shown in the following table, an alarm is triggered, because at least one device IP address has a count greater than 5.
|
|
|
|---|---|
You can specify one or more filters to limit the failed authentications that are considered for threshold evaluation. Each filter is associated with a particular attribute in the records and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on an external database that ACS is unable to connect to. Modify the fields in the Criteria tab as described in Table 12-23 .
RBACL Drops
When ACS evaluates this threshold, it examines Cisco Security Group Access RBACL drops that occurred during the specified interval up to the previous 24 hours. The RBACL drop records are grouped by a particular common attribute, such as NAD, SGT, and so on.
A count of such records within each of those groups is computed. If the count for any group exceeds the specified threshold, an alarm is triggered. For example, consider the following threshold configuration:
RBACL Drops greater than 10 in the past 4 hours by a SGT.
If, in the past four hours, RBACL drops have occurred for two different source group tags as shown in the following table, an alarm is triggered, because at least one SGT has a count greater than 10.
|
|
|
|---|---|
You can specify one or more filters to limit the RBACL drop records that are considered for threshold evaluation. Each filter is associated with a particular attribute in the RBACL drop records and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Modify the fields in the Criteria tab as described in Table 12-24 .
NAD-Reported AAA Downtime
When ACS evaluates this threshold, it examines the NAD-reported AAA down events that occurred during the specified interval up to the previous 24 hours. The AAA down records are grouped by a particular common attribute, such as device IP address or device group, and a count of records within each of those groups is computed.
If the count for any group exceeds the specified threshold, an alarm is triggered. For example, consider the following threshold configuration:
AAA Down count greater than 10 in the past 4 hours by a Device IP
If, in the past four hours, NAD-reported AAA down events have occurred for three different device IP addresses as shown in the following table, an alarm is triggered, because at least one device IP address has a count greater than 10.
|
|
|
|---|---|
You can specify one or more filters to limit the AAA down records that are considered for threshold evaluation. Each filter is associated with a particular attribute in the AAA down records and only those records that match the filter condition are counted. If you specify multiple filter values, only the records that match all the filter conditions are counted.
Choose this category to define threshold criteria based on the AAA downtime that a network access device reports. Modify the fields in the Criteria tab as described in Table 12-25 .
Configuring Threshold Notifications
Use this page to configure alarm threshold notifications.
Step 1 Select Monitoring and Reports > Alarms > Thresholds, then do one of the following:
- Click Create to create a new alarm threshold.
- Click the name of an alarm threshold, or check the check box next to an existing alarm threshold and click Edit to edit a selected alarm threshold.
- Click the name of an alarm threshold, or check the check box next to an existing alarm threshold and click Duplicate to duplicate a selected alarm threshold.
Step 2 Click the Notifications tab.
The Thresholds: Notifications page appears as described in Table 12-26 :
|
|
|
|---|---|
Use the drop-down list box to select the severity level for your alarm threshold. Valid options are: |
|
Check the check box to be notified of duplicate alarms. An alarm is considered a duplicate if a previously generated alarm for the same threshold occurred within the time window specified for the current alarm. |
|
|
|
|
Enter a comma-separated list of e-mail addresses or ACS administrator names or both. Do one of the following:
When a threshold alarm occurs, an e-mail is sent to all the recipients in the Email Notification User List. |
|
Check this check box to send e-mail notifications in HTML format. Uncheck this check box to send e-mail notifications as plain text. |
|
Enter custom text messages that you want associated with your alarm threshold. |
|
|
|
|
Check this check box to send a syslog message for each system alarm that ACS generates. Note For ACS to send syslog messages successfully, you must configure Alarm Syslog Targets, which are syslog message destinations. Understanding Alarm Syslog Targets for more information. |
|
Deleting Alarm Thresholds
Step 1 Select Monitoring and Reports > Alarms > Thresholds.
The Alarms Thresholds page appears.
Step 2 Check one or more check boxes next to the thresholds you want to delete, and click Delete.
Step 3 Click OK to confirm that you want to delete the selected alarm(s).
The Alarms Thresholds page appears without the deleted threshold.
Configuring System Alarm Settings
System alarms are used to notify users of:
Use this page to enable system alarms and to specify where alarm notifications are sent. When you enable system alarms, they are sent to the Alarms Inbox. In addition, you can choose to send alarm notifications through e-mail to select recipients and as syslog messages to the destinations specified as alarm syslog targets.
From the Monitoring and Report Viewer, choose Monitoring Configuration > System Configuration > System Alarm Settings.
|
|
|
|---|---|
|
|
|
Use the drop-down list box to designate the number of hours that you want to suppress duplicate system alarms from being sent to the Email Notification User List. Valid options are 1, 2, 4, 6, 8, 12, and 24. |
|
|
|
|
Enter a comma-separated list of e-mail addresses or ACS administrator names or both. Do one of the following:
When a system alarm occurs, an e-mail is sent to all the recipients in the Email Notification User List. |
|
Check this check box to send e-mail notifications in HTML format. Uncheck this check box to send e-mail notifications as plain text. |
|
|
|
|
Check this check box to send a syslog message for each system alarm that ACS generates. For ACS to send syslog messages successfully, you must configure Alarm Syslog Targets, which are syslog message destinations. Understanding Alarm Syslog Targets for more information. |
|
Understanding Alarm Syslog Targets
Alarm syslog targets are the destinations where alarm syslog messages are sent. The Monitoring and Report Viewer sends alarm notification in the form of syslog messages. You must configure a machine that runs a syslog server to receive these syslog messages.
To view a list of configured alarm syslog targets, choose Monitoring Configuration > System Configuration > Alarm Syslog Targets.
Note You can configure a maximum of two syslog targets in the Monitoring and Report Viewer.
This section contains the following topics:
Creating and Editing Alarm Syslog Targets
To create or edit an alarm syslog target:
Step 1 Choose Monitoring Configuration > System Configuration > Alarm Syslog Targets.
The Alarm Syslog Targets page appears.
Step 2 Do one of the following:
- Click Create.
- Check the check box next to the alarm syslog target that you want to edit, then click Edit.
The Alarm Syslog Targets Create or Edit page appears.
Step 3 Modify the fields described in Table 12-28 .
Deleting Alarm Syslog Targets
Note You cannot delete the default nonstop schedule.
To delete an alarm syslog target:
Step 1 Choose Monitoring Configuration > System Configuration > Alarm Syslog Targets.
The Alarm Syslog Targets page appears.
Step 2 Check the check box next to the alarm syslog target that you want to delete, then click Delete.
The following message appears:
The Alarm Syslog Targets page appears without the deleted alarm syslog targets.
Feedback