Примечания к выпуску для Cisco Cisco Content Security Management Appliance M160

If you did not patch this issue before upgrading, you will see a message during upgrade stating that it 
has been fixed. If you see this message, the following actions are required to return your appliance to 
full working order after upgrade: 

If you are upgrading from AsyncOS 8.4.0-150: 

You will see an "Upgrade failure" message after running the upgrade, but the patch has installed 
correctly. However, you must reboot the appliance manually to complete the installation process: 

After you see "Upgrade failure," the 

upgrade

 command options will reappear. Press <Enter> to exit 

the 

upgrade

 command, then enter the 

reboot

 command. 

You should also receive an alert about an application fault; ignore this. 

Retrieve the information you noted in 

. 

Remove the existing entry for your appliance from the known hosts list in your ssh utility. Then ssh 
to the appliance and accept the connection with the new key. 

If you use SCP push to transfer logs to a remote server (including Splunk): Clear the old SSH host 
key for the appliance from the remote server. 

Use the 

logconfig > hostkeyconfig > delete 

CLI command as many times as needed to clear 

the old key associated with each managed ESA and WSA virtual appliance. 

Re-establish the connection to each managed appliance and (if applicable) reassign each managed 
appliance to the appropriate configuration master: 

1. Go to Management Appliance > Centralized Services > Security Appliances and click the link for 
an appliance in the list. 

2. Click Establish Connection. 

3. (Managed WSAs only) If your appliance is configured for centralized configuration management, 
re-assign the Configuration Master to each managed WSA. 

4. Submit and commit your changes if applicable. 

5. Repeat for each managed appliance. 

The requirement in this section was introduced in AsyncOS 9.5.0-125. 

In order to view detailed file analysis results in the cloud for all files uploaded from all email and web 
security appliances in your organization, you must configure an appliance group on each appliance after 
upgrading. To configure appliance groups on your content security management appliance, see the email 
or web reporting chapter in the user guide PDF for this release. 

If you upgrade from a release earlier than AsyncOS 9.0, do the following. 

After upgrade, make the following change on the Management Appliance > System Administration > 
Disk Management page: 

For the Miscellaneous quota, allocate at least twice the amount of the current disk usage displayed 
for Miscellaneous files. 

Until you make any required disk space changes, you will not be able to load configuration files that you 
save from the appliance.