Problem with cut and paste is it's "additive" to the existing configuration, and even if you erase the current configuration first, there are just a few default "things", so just pasting a configuration into an ASA (or any Cisco device) can leave things already in the running configuration lying around. Licences on ASA are tied to their serial number and are not transferable. Any help or advice is much appreciated.īrianwhelton wrote: The configuration should just be a copy and paste job, that IOS is quite old now though. Will doing this overwrite the license activation for the An圜onnect peers for the ASA that has it? I was just curious if I might have to re-apply the activation key from Cisco on each ASA after a backup and restore of the config. There seemed to be several sites showing a how-to of the procedure, with this being one of them - Opens a new window. My understanding is if I backup the config of each one and restore the config of ASA # 1 on ASA # 2 and vice versa, I should theoretically be able to physically swap the ASAs and be good to go at each location.
The site whose ASA has An圜onnect does not have users that need it, so I was going to move that ASA to a site that needs An圜onnect but is not currently licensed for it and save the company some money. The only difference is that one ASA has 25 licenses for An圜onnect and the other does not. Each is used for IPSec VPN back to our 5510 at HQ. Each is licensed for unlimited hosts and has a base license.
I have two Cisco ASA 5505s, each at different sites, each running ASA version 8.4(4)1 and ASDM 6.4(9).
0 kommentar(er)
