Table 3-18 on, Then you ca – Cisco ASA 5505 User Manual

Page 154

Advertising
background image

3-34

Cisco ASA 5500 Series Configuration Guide using the CLI

Chapter 3 Managing Feature Licenses

Configuring Licenses

Limitations and Restrictions

Your activation key remains compatible if you upgrade to the latest version from any previous version.
However, you might have issues if you want to maintain downgrade capability:

Downgrading to Version 8.1 or earlier—After you upgrade, if you activate additional feature
licenses that were introduced before 8.2, then the activation key continues to be compatible with
earlier versions if you downgrade. However if you activate feature licenses that were introduced in
8.2 or later, then the activation key is not backward compatible. If you have an incompatible license
key, then see the following guidelines:

If you previously entered an activation key in an earlier version, then the ASA uses that key
(without any of the new licenses you activated in Version 8.2 or later).

If you have a new system and do not have an earlier activation key, then you need to request a
new activation key compatible with the earlier version.

Downgrading to Version 8.2 or earlier—Version 8.3 introduced more robust time-based key usage
as well as failover license changes:

If you have more than one time-based activation key active, when you downgrade, only the most
recently activated time-based key can be active. Any other keys are made inactive.

If you have mismatched licenses on a failover pair, then downgrading will disable failover. Even
if the keys are matching, the license used will no longer be a combined license.

Table 3-18

Permanent License Reloading Requirements

Model

License Action Requiring Reload

ASA 5505, ASA 5510

Changing between the Base and Security Plus
license.

All models

Changing the Encryption license.

All models

Downgrading any permanent license (for
example, going from 10 contexts to 2 contexts).

Advertising