Cisco Cisco Email Security Appliance C170 Referências técnicas

R E P O R T I N G C O N F I G

C H A P T E R   3 :   T H E   C O M M A N D S :   R E F E R E N C E   E X A M P L E S

 249

Configure Storage Limit for Reporting Data (C-Series only)

- MAILSETUP - Configure reporting for the ESA.

- MODE - Enable centralized or local reporting for the ESA.

[]>

Code Example 3-147 

reportingconfig

 - Configure storage limit for centralized reporting data

esa01-vmw1-tpub.qa> reportingconfig

Choose the operation you want to perform:

- MAILSETUP - Configure reporting for the ESA.

- MODE - Enable centralized or local reporting for the ESA.

[]> mailsetup

SenderBase timeout used by the web interface: 5 seconds

Sender Reputation Multiplier: 3

The current level of reporting data recording is: unlimited

No custom second level domains are defined.

Legacy mailflow report: Disabled

Choose the operation you want to perform:

- SENDERBASE - Configure SenderBase timeout for the web interface.

- MULTIPLIER - Configure Sender Reputation Multiplier.

- COUNTERS - Limit counters recorded by the reporting system.

- THROTTLING - Limit unique hosts tracked for rejected connection 

reporting.

- TLD - Add customer specific domains for reporting rollup.

- STORAGE - How long centralized reporting data will be stored on 

the C-series before being overwritten.

- LEGACY - Configure legacy mailflow report.

[]> storage

While in centralized mode the C-series will store reporting data for 

the M-series to collect.  If the M-series does not collect that data 

then eventually the C-series will begin to overwrite the oldest data 

with new data.

A maximum of 24 hours of reporting data will be stored.

How many hours of reporting data should be stored before data loss?

[24]> 48

SenderBase timeout used by the web interface: 5 seconds

Sender Reputation Multiplier: 3

The current level of reporting data recording is: unlimited

Code Example 3-146 

reportingconfig

 - Enabling centralized reporting