Cisco Cisco Content Security Management Appliance M680 トラブルシューティングガイド
ESA FAQ: What is debounce timeout?
Document ID: 118113
Contributed by Nasir Shakour and Robert Sherwin, Cisco TAC
Engineers.
Engineers.
Jul 31, 2014
Contents
Introduction
What is debounce timeout?
Related Information
What is debounce timeout?
Related Information
Introduction
This document describes what a debounce timeout is and how to configure a debounce timeout on an Email
Security Appliance (ESA).
Security Appliance (ESA).
What is debounce timeout?
The ESA will send alert notifications to a user via email if there is are system errors that require user
intervention. If an error occurs frequently, the appliance can be configured to refrain from resending the
identical alert for a specified period of time. This parameter is known as the debounce timeout.
intervention. If an error occurs frequently, the appliance can be configured to refrain from resending the
identical alert for a specified period of time. This parameter is known as the debounce timeout.
Increasing the debounce timeout can be useful in certain circumstances, such as minimizing duplicate
alert notifications while a hardware component is in the process of being replaced.
alert notifications while a hardware component is in the process of being replaced.
You can specify the initial number of seconds to wait before AsyncOS will send a duplicate alert. If you set
this value to 0, duplicate alert summaries are not sent and instead, all duplicate alerts are sent without any
delay (this can lead to a large amount of email over a short amount of time). The number of seconds to wait
between sending duplicate alerts (alert interval) is increased after each alert is sent. The increase is the number
of seconds to wait plus twice the last interval. So a 5 second wait would have alerts sent at 5 seconds, 15,
seconds, 35 seconds, 75 seconds, 155 seconds, 315 seconds, etc.
this value to 0, duplicate alert summaries are not sent and instead, all duplicate alerts are sent without any
delay (this can lead to a large amount of email over a short amount of time). The number of seconds to wait
between sending duplicate alerts (alert interval) is increased after each alert is sent. The increase is the number
of seconds to wait plus twice the last interval. So a 5 second wait would have alerts sent at 5 seconds, 15,
seconds, 35 seconds, 75 seconds, 155 seconds, 315 seconds, etc.
Eventually, the interval could become quite large. You can set a cap on the number of seconds to wait
between intervals via the maximum number of seconds to wait before sending a duplicate alert field. For
example, if you set the initial value to 5 seconds, and the maximum value to 60 seconds, alerts would be sent
at 5 seconds, 15 seconds, 35 seconds, 60 seconds, 120 seconds, etc.
between intervals via the maximum number of seconds to wait before sending a duplicate alert field. For
example, if you set the initial value to 5 seconds, and the maximum value to 60 seconds, alerts would be sent
at 5 seconds, 15 seconds, 35 seconds, 60 seconds, 120 seconds, etc.
> alertconfig
Sending alerts to:
ESA_Admin@mycompany.com
Class: All − Severities: All