Wireless Access

Well I've gone and done it now and seem to have bricked my lab 620 controller.

Initially I tried to upgrade to 6.4.2.5 but it kept saying no space, despite clearing everything out.

I then upgraded the partition via cpboot which seemed to work fine.

After a reboot, this is where the problems started.  Initially it did reboot, but came back with an error about upgrading the boot image, and the image on the old partition was gone.

I upgrade that partition via cpboot to it's previous version and now the thing has gone completely haywire.

           <<<<<    Welcome to Aruba Networks - Aruba A620-4    >>>>>

Checking Inventory...OK
Starting watchdog processes
Check/update Boot Image
 Inside wd_intr_handler
rmi_bridge_lock is already taken from panic cpu
cpumask = f ipi_mask = f and dump_mask = 0
Value after sending ipi jiffies = 0x00001964 jiffies_64 = 0x0000000000001964
Waiting for dumps to complete  jiffies = 0x00001964 jiffies_64 = 0x0000000000001964
<0>
PANIC DUMP INITIATED!!!
SYSTEM WILL REBOOT MOMENTARILY
JIFFIES = 0x00001964 JIFFIES_64 = 0x0000000000001964

 Same thing booting into either partition.

Is it possible to recover from this?

Unfortunately no support since this is a lab controller.

Have you tried this:

http://community.arubanetworks.com/t5/Unified-Wired-Wireless-Access/Tutorial-How-to-fix-a-corrupt-OS/td-p/150468 

Unfortunately this is happening on both partitions

hi Michael

Can you post (attachment) the full log of the bootup from power on.

regards

-jeff

Jeff, boot log below.

I was looking at this article link but I don't seem to have the format command available.

CPBoot 1.0.0.0 (build 23274)
Built: 2010-01-19 at 11:11:22
DDR2 DRAM running at 466Mhz
DRAM:  Total = 512 MB
POST:  Memory test: Physical 0 - 0x10000000 - quick test
       Memory test: Physical 0x10000000 - 0x20000000 - quick test
       PASS
CPU:   XLS204, rev. A1 Clock: 600MHz
CPLD:  rev: 1.3
SMP:   All 4 cpus successfully started
Board: A620
POST2: OK
PCIE:  RC2x2 mode
Net:  xls_gmac0, xls_gmac1 [PRIME]
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca ( NAND 256MiB 3,3V 16-bit)
Boot:  Primary bootflash partition

Hit any key to stop autoboot:  0
booting system partition 1
part offset: 3200000 part size: 3200000
### JFFS2 loading 'uImage' to 0x87000000
Scanning JFFS2 FS:   load: loaded 'uImage' to 0x87000000 (62697896 bytes)
### JFFS2 load complete: 62697896 bytes loaded to 0x87000000

Booting image...

Image is signed; verifying checksum...
passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
No network device to cleanup
No network device to cleanup
Jumping to the application... 0x80678000
Linux command line:  run quiet console=ttyS0,9600
------------------------------------------------------------
Downloading SOS...done.
Uncompressing core image files...done.
Mounting the flash file systems...done.
Tuning IPv4 route cache...done.

Aruba Networks
ArubaOS Version 6.3.1.9 (build 44832 / label #44832)
Built by p4build@majorca.arubanetworks.com on 2014-07-15 at 12:57:37 PDT (gcc version 3.4.3)
Copyright (c) 2002-2014, Aruba Networks, Inc.

           <<<<<    Welcome to Aruba Networks - Aruba A620-4    >>>>>

Checking Inventory...OK
Starting watchdog processes
Check/update Boot Image
rmi_bridge_lock is already taken from panic cpu
cpumask = f ipi_mask = f and dump_mask = 0
Value after sending ipi jiffies = 0x00001c39 jiffies_64 = 0x0000000000001c39
Waiting for dumps to complete  jiffies = 0x00001c39 jiffies_64 = 0x0000000000001c39
<0>
PANIC DUMP INITIATED!!!  - SYSTEM WILL REBOOT MOMENTARILY JIFFIES = 0x00001c39 JIFFIES_64 = 0x0000000000001c39

Michael

Give the following a go

cpboot> purgeenv
cpboot> run wipe-out-flash
cpboot> reset

then interrupt the bootup, and re-do the setenvs for your TFTP server, use any one of the fastEthernet ports (labelled 0-7). I have found before you may need to saveenv after all the ip/netmask/gateway/serverip is setup, so saveenv, reset and check you can ping the server IP. If it works, then upgrade as shown:

cpboot> upgrade 0 ArubaOS_6xx_5.0.3.0_26207
partition start= 0 partition size= 52428800
Starting TFTP Download ...
Using xls_gmac1 device
TFTP from server 172.20.0.1; our IP address is 172.20.0.2
Filename 'ArubaOS_6xx_5.0.3.0_26207'.
Load address: 0x87000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #########################################################
done
Bytes transferred = 42168224 (2836fa0 hex)

see if that unsticks it.

regards

-jeff

Jeff.  You're a star....that has done the trick, with a little bit of wrangling.

I was able to boot up, but it gave the following error.

(aruba-lab) #show image version

Ancillary files are not present
*********************************************************************
* WARNING:  An additional image upgrade is required to complete the *
* installation of the AP and WebUI files. Please upgrade the boot   *
* partition again and reload the controller.                        *
*********************************************************************


Ancillary file(s) or digest file missing.
Ancillary image is missing please upgrade the image again.

----------------------------------
Partition               : 0:0 (/dev/mtdblock9) **Default boot**
Software Version        : ArubaOS 6.3.1.9 (Digitally Signed - Production Build)
Build number            : 44832
Label                   : 44832
Built on                : Tue Jul 15 12:57:37 PDT 2014
----------------------------------
Partition               : 0:1 (/dev/mtdblock10)

 Tried to upgrade partition 1 but this failed giving the following.

Upgrading partition 1
Secure file copy:....................................................
.....................................................................
File copied successfully.
Saving file to flash:
........................
Error upgrading image: Couldn't erase image partition

 So I upgraded partition 1 via cpboot method which seemed to work, but this time I made sure I didn't boot into that one.  I booted into partition 0 and still got the message about Ancillary Files missing etc.

Upgraded partition 1 via normal method in cli and this seemed to work.

Changed the boot statement to load partition 1, reloaded and crossed fingers.

All good now.  :-)

This all started when I couldn't upgrade due to insufficient space, despite clearing all files out.  I suspect that if I had done a 'write erase all' and the restored the flashbackup I wouldn't have had the problem.

Anyhow...lesson learnt.  Good thing it wasn't a customers equipment.

Michael

glad to know it's recovered eventually! yes, the 6xx gets a bit dicey once it's running dual 6.4 images, cleaning up as much as you can and then rebooting prior to any attempt to upgrade can usually help.

regards

-jeff