Примечания к выпуску для Cisco Cisco ACE Application Control Engine Module

After the system generates the license key, you will receive a license key e-mail with an attached license 
file and installation instructions. Save the license key e-mail in a safe place in case you need it in the 
future (for example, to transfer the license to another ACE).

For information about installing and managing ACE licenses, refer to Chapter 3, Managing ACE 
Software Licenses, in the Administration Guide, Cisco ACE Application Control Engine.

To upgrade your ACE software from version A2(3.x) or A2(1.6a) or later to version A5(1.x), you must 
also migrate your ACE10 or ACE20 module to a new ACE30 module. For details about migrating to an 
ACE30 and upgrading your software to A4(1.0) or later, see the procedure in the Installation Note, Cisco 
ACE Application Control Engine ACE30 Module.

To upgrade your ACE software from A4(1.x) or A4(2.x) to version A5(1.x), the procedure in the 
following section assumes that your ACEs are configured as redundant peers to ensure that there is no 
disruption to existing connections during the upgrade process. In the following procedure, the active 
ACE is referred to as ACE-1 and the standby ACE is referred to as ACE-2.

This section includes the following topics:

Before you upgrade your ACE software, be sure that your ACE configurations meet the upgrade 
prerequisites in the following sections: 

If you are upgrading a redundant configuration from software version A4(1.x) or A4(2.x) to software 
version A5(1.x), while the two ACEs are in split mode with the earlier software version running on the 
active ACE and software version A5(1.x) running on the standby, config sync is disabled. If you make 
any configuration changes on the active ACE during this time, your changes are not synchronized to the 
standby and are lost. After you complete the upgrade, config sync is automatically reenabled. We 
recommend that you do not make any configuration changes while the two ACEs are in split mode.