cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
364
Views
0
Helpful
6
Replies

Downgrade error

opnineopnine
Level 1
Level 1

Hi all,

 

We did a downgrade from 8.4 to 8.2, but after we save the configuration and we realod the asa, we go back to the 8.4 version and we get this error.

 

INFO: MIGRATION - Saving the startup configuration to file

INFO: MIGRATION - Startup configuration saved to file 'flash:8_2_5_0_startup_cfg.sav'
*** Output from config line 4, "ASA Version 8.2(5) "
..Device Manager image set, but not a valid image file disk0:/asa840-128-k8.bin
*** Output from config line 93, "asdm image disk0:/asa840..."

timeout floating-conn 0:00:00
        ^
ERROR: % Invalid input detected at '^' marker.
*** Output from config line 107, "timeout floating-conn 0:..."
.WARNING: No 'anyconnect image' commands have been issued
*** Output from config line 168, " svc enable"
.
no call-home reporting anonymous
             ^
ERROR: % Invalid input detected at '^' marker.
*** Output from config line 252, "no call-home reporting a..."

Cryptochecksum (unchanged): c53a0858 a77ecc4c 9f5baa2b a8a53bb5
Real IP migration logs:
        No ACL was changed as part of Real-ip migration

 

Thanks.

1 Accepted Solution

Accepted Solutions

Does your startup-config file specify the ASA should use the "asa825-k8.bin" image?

For ASDM, asdm-522.bin is not compatible with ASA 8.2 software. You would need at least ASDM 6.3 (and preferably ASDM 7.3(2) as it is the current and most stable ASDM release). Reference.

View solution in original post

6 Replies 6

Marvin Rhoads
Hall of Fame
Hall of Fame

Do you have a valid image file for ASA 8.2 on the ASA's disk0? You need to have that and to specify it as the first image in the boot variable of the configuration.

It looks like your ASDM image variable is set to point to ASA software image - it needs to be an ASDM image and that image needs to be on disk.

The "timeout floating-conn" variable requires at least 8.2(5) or 8.4(2) in those respective release trains. If you're booting into an image prior to one of those the variable will not be recognized.

I believe "call-home reporting anonymous" is a similar issue although the command reference is not definitive on that one.

Hello Marvin,

 

I have this asa asa825-k8.bin, the only thing is the asdm version i have is  asdm-522.bin.

 

Both of the .bin files are in the disk0.

 

Thanks. 

Does your startup-config file specify the ASA should use the "asa825-k8.bin" image?

For ASDM, asdm-522.bin is not compatible with ASA 8.2 software. You would need at least ASDM 6.3 (and preferably ASDM 7.3(2) as it is the current and most stable ASDM release). Reference.

Marvin,

In the startup I have this.

 

boot system disk0:/asa840-128-k8.bin
boot system disk0:/asa722-k8.bin

 

thanks

As long as the running-config is saved, startup-config = running-config.

So, "show run boot" will give you the current boot variable(s).

I just erased the 2 boots, lines added the one I need.

 

Thanks. 

Review Cisco Networking for a $25 gift card