Cisco Cisco Content Security Management Appliance M680 Notas de publicación

In reporting and tracking searches, second-level domains (regional domains listed at 

) are treated differently from subdomains, even though the two 

domain types may appear to be the same. 

For example:

Reports will not include results for a two-level domain such as 

co.uk

, but will include results for 

foo.co.uk

. Reports include subdomains under the main corporate domain, such as 

cisco.com

.

Tracking search results for the regional domain 

co.uk

 will not include domains such as 

foo.co.uk

, 

while search results for 

cisco.com

 will include subdomains such as 

subdomain.cisco.com

.

Known issues in AsyncOS for Email Security and AsyncOS for Web Security are documented in the 
release notes for those products. 

 describes the known issues for the Security Management appliance for this release. 

If you receive the error “Configuration conflict detected!” when trying to import a 6.3 
configuration to initialize a Configuration Master, try the following workaround: 

Abandon the changes, then try importing the configuration again. 

Compatibility issues with configuration files from AsyncOS 7.1.2 for Web 
Security 

Advanced file publish cannot be used to publish a configuration file from AsyncOS 
7.1.2 for Web Security to Web Security appliances running AsyncOS 7.1.0 or 7.1.1. 

Neither the 

who

 CLI command nor the Active Sessions page identify active CLI users 

whose user name is 16 characters long. 

If your Email or Web security appliance is connected to a Security Management 
appliance, reverting the version of AsyncOS on the managed appliance to a previous 
version may prevent the SMA from communicating with it.

Workaround: Re-authenticate the SMA’s connection to the managed appliance.