Cisco ASA 5510 DRAM, 512 MB ASA5510-MEM-512= Benutzerhandbuch

Produktcode
ASA5510-MEM-512=
Seite von 32
4
Release Notes for the Cisco ASA 5500 Series, Version 8.2(x)
OL-18971-02
  Upgrading the Software
Upgrading the AIP SSC or SSM Software
When upgrading the AIP SSC or SSM, do not use the upgrade command within the IPS software; 
instead use the hw-module 1 recover configure command within the adaptive security appliance 
software.
Upgrading the Phone Proxy and MTA Instance
In Version 8.0(4), you configured a global media-termination address (MTA) on the adaptive security 
appliance. In Version 8.2, you can now configure MTAs for individual interfaces (with a minimum of 
two MTAs). As a result of this enhancement, the old CLI has been deprecated. You can continue to use 
the old configuration if desired. However, if you need to change the configuration at all, only the new 
configuration method is accepted; you cannot later restore the old configuration.
Note
If you need to maintain downgrade compatibility, you should keep the old configuration as is.
To upgrade the Phone Proxy, perform the following steps:
Step 1
Create the MTA instance to apply to the phone proxy instance for this release. See “Creating the Media 
Termination Instance” section in the Cisco ASA 5500 Series Configuration Guide using the CLI.
Step 2
To modify the existing Phone Proxy, enter the following command:
hostname(config)# phone-proxy phone_proxy_name
Where phone_proxy_name is the name of the existing Phone Proxy.
Step 3
To remove the configured MTA on the phone proxy, enter the following command:
hostname(config)# no media-termination address ip_address
Step 4
Apply the new MTA instance to the phone proxy by entering the following command:
hostname(config)# media-termination instance_name
Where instance_name is the name of the MTA that you created in 
Activation Key Compatibility When Upgrading
Your activation key remains compatible if you upgrade to Version 8.2 or later, and also if you later 
downgrade. 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 
backwards 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 adaptive security appliance 
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.