Cisco Cisco Content Security Management Appliance M1070 Mode D'Emploi

Page de 450
 
5-49
AsyncOS 9.6 for Cisco Content Security Management Appliances User Guide
 
Chapter 5      Using Centralized Web Reporting and Tracking
  Troubleshooting Web Reporting and Tracking
Data transfer between Web Security appliances and the Cisco Content Security Management 
appliance may have been interrupted, or data may have been purged. See 
If an upgrade changes the way information is reported or tracked, transactions that occurred before 
upgrade may not be represented as expected. To see if your release has this type of change, see the 
Release Notes for your release at the location specified in 
For missing results in Web Proxy Services tracking search results, see 
For unexpected results when filtering by user requested transactions, see the User Request row of 
the table in 
PDF Shows Only a Subset of Web Tracking Data 
Problem
PDF shows only some of the data that is visible on the Web Tracking page. 
Solution
For information about what data is included in and omitted from PDFs and CSV files, see the 
web tracking information in the table in 
Troubleshooting L4 Traffic Monitor Reports 
If the Web Proxy is configured as a forward proxy and L4 Traffic Monitor is set to monitor all ports, the 
IP address of the proxy’s data port is recorded and displayed as the client IP address in reports. If the 
Web Proxy is configured as a transparent proxy, enable IP spoofing to correctly record and display the 
client IP addresses. To do this, see the Cisco IronPort AsyncOS for Web User Guide
Related Topics 
 
Exported .CSV file is Different From Web Interface Data 
Problem
Domains Matched data exported to .csv file differs from the data shown in the Web interface. 
Solution
For performance reasons, only the first 300,000 entries are exported as .csv.