Руководство Пользователя для Cisco Cisco Content Security Management Appliance M1070
Chapter 11 Common Administrative Tasks
11-66
Cisco IronPort AsyncOS 7.2.0 for Security Management User Guide
OL-21768-01
Eventually, the interval could become 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, and so on.
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, and so on.
Alert Delivery
Because alert messages can be used to inform you of problems within your
IronPort appliance, they are not sent using AsyncOS’s normal mail delivery
system. Instead, alert messages pass through a separate and parallel email system
designed to operate even in the face of significant system failure in AsyncOS.
IronPort appliance, they are not sent using AsyncOS’s normal mail delivery
system. Instead, alert messages pass through a separate and parallel email system
designed to operate even in the face of significant system failure in AsyncOS.
The alert mail system does not share the same configuration as AsyncOS, which
means that alert messages may behave slightly differently from other mail
delivery:
means that alert messages may behave slightly differently from other mail
delivery:
•
Alert messages are delivered using standard DNS MX and A record lookups.
–
They do not use SMTP routes in AsyncOS versions older then 5.X.
–
They do cache the DNS entries for 30 minutes and the cache is refreshed
every 30 minutes, so in case of DNS failure the alerts still go out.
every 30 minutes, so in case of DNS failure the alerts still go out.
•
Alert messages do not pass through the work queue, so they are not scanned
for viruses or spam. They are also not subjected to message filters or content
filters.
for viruses or spam. They are also not subjected to message filters or content
filters.
•
Alert messages do not pass through the delivery queue, so they will not be
affected by bounce profiles or destination control limits.
affected by bounce profiles or destination control limits.
SMTP Routes and Alerts
Alerts sent from the appliance to addresses specified in the Alert Recipients
section follow SMTP routes defined for those destinations.
section follow SMTP routes defined for those destinations.
Cisco IronPort AutoSupport
To allow Cisco IronPort to better support and design future system changes, the
IronPort appliance can be configured to send IronPort Systems a copy of all alert
messages generated by the system. This feature, called ‘AutoSupport’, is a useful
IronPort appliance can be configured to send IronPort Systems a copy of all alert
messages generated by the system. This feature, called ‘AutoSupport’, is a useful