02-24-2016 11:02 AM - edited 02-21-2020 05:44 AM
Hi,
I'm trying to upgrade my cisco 5512-x to new version, but when I assign new version with boot command and then rebooting the firewall, it cannot load new software, it gives below error and tries several times to boot again , then going to rommon mode. So, to restore ASA, I write boot command to load current/old version of software. Current version is 9.1(2) - asa912-smp-k8.bin. I tried many interim and stable releases.
Loading flash:/asa942-11-smp-k8.bin... Booting...
Platform ASA5512
Loading...
IO memory blocks requested from bigphys 32bit: 41269
INIT: version 2.88 booting
Starting udev
Configuring network interfaces... done.
Populating dev cache
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Starting check/repair pass.
Starting verification pass.
/dev/sda1: 154 files, 97898/976999 clusters
dosfsck(/dev/sda1) returned 0
LAN Parameter Data does not match! Write may have failed.
****** REBOOT [IPDeconfiguring network interfaces... done.
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Deactivating swap...
Unmounting local filesystems...
Rebooting... Cisco BIOS Version:9B2C109A
Build Date:05/15/2013 16:34:44
There is "sh ver":
ciscoasa# sh version
Cisco Adaptive Security Appliance Software Version 9.1(2)
Device Manager Version 7.5(2)153
Compiled on Thu 09-May-13 16:20 PDT by builders
System image file is "disk0:/asa912-smp-k8.bin"
Config file at boot was "startup-config"
ciscoasa up 1 hour 27 mins
Hardware: ASA5512, 4096 MB RAM, CPU Clarkdale 2793 MHz, 1 CPU (2 cores)
ASA: 2048 MB RAM, 1 CPU (1 core)
Internal ATA Compact Flash, 4096MB
BIOS Flash MX25L6445E @ 0xffbb0000, 8192KB
Encryption hardware device : Cisco ASA-55xx on-board accelerator (revision 0x1)
Boot microcode : CNPx-MC-BOOT-2.00
SSL/IKE microcode : CNPx-MC-SSL-PLUS-T020
IPSec microcode : CNPx-MC-IPSEC-MAIN-0024
Number of accelerators: 1
Baseboard Management Controller (revision 0x1) Firmware Version: 2.4
.....
......
This platform has an ASA 5512 Security Plus license.
Serial Number: FCH1******
Configuration register is 0x1
Is it hardware problem?
And I found from search this bug:
https://tools.cisco.com/bugsearch/bug/CSCuu33125/?referring_site=bugquickviewredir
But I don't know what is the Saleen units.
Thank in advance
02-24-2016 11:04 AM
I would download the image again. I suspect it is corrupted.
02-24-2016 11:12 AM
I tried about 5-6 different images, but the same result.
03-02-2016 07:52 AM
hello ... did you find a solution? I have the same issue on a 5515 but see no update in the bug info. Thanks.
From rommon I can get it to boot from the old image. This is the output for the failed boot:
rommon #1> boot asa916-11-smp-k8.bin
Launching BootLoader...
Boot configuration file contains 2 entries.
Loading asa916-11-smp-k8.bin... Booting...
Platform ASA5515
Loading...
IO memory blocks requested from bigphys 32bit: 33163
ÿdosfsck 2.11, 12 Mar 2005, FAT32, LFN
Starting check/repair pass.
Starting verification pass.
/dev/sdb1: 38 files, 41854/1951804 clusters
dosfsck(/dev/sdb1) returned 0
LAN Parameter Data does not match! Write may have failed.
***** REBOOT [IPMI over LAN error: Failed to set IP Source] *****
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
Cisco BIOS Version:9B2C109A
Build Date:05/15/2013 16:34:44
CPU Type: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz, 3059 MHz
Total Memory:8192 MB(DDR3 1333)
System memory:619 KB, Extended Memory:3573 MB
03-02-2016 11:02 AM
Try doing an upgrade first to a release closer to the original one. Then then if that works, jump to the final one you want.
If that fails I would contact Cisco TAC. The only other thing I can think of is an actual hardware issue.
03-02-2016 12:17 PM
Thanks! Works great up to 9.1.5, one version upgrade at a time, but cannot go from 9.1.5 to 9.1.6.
Trying to get TAC involved.
03-28-2016 06:25 AM
Update: TAC decided to RMA the two ASAs.
02-24-2016 04:50 PM - edited 11-06-2017 07:15 PM
"Saleen" is the internal Cisco name for the 5512/25/45/55-X models. (The 5585-X was "Spyker".)
The newer 5506/08/16 models are known as the "Kenton" platform.
I haven't run across that particular bug before; but I'd recommend a TAC case since it looks like that may very well be the case for you/
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide