Access Points

Reply
Contributor II

Updated controller, RAPs not able to connect

Hi, i recently updated to 6.1.2.4 (from 6.1.2.3). I had some problems with wired RAPs in combination with Captive Portal. I was advised to update to 6.1.2.4 to fix this. So i did.

I also reset my RAPs to re-provision them, and that's where the problem seems to be. The RAPs are not able to connect anymore, please refer to the logging:

Nov  2 15:37:23  KERNEL(00:0b:86:66:b4:fb@194.53.59.35): klogd started: BusyBox v1.01 (2009.05.07-05:38+0000)
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Aruba Networks
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): ArubaOS Version 3.3.2.11-rn-3.0.1 (build 21263 / label #21263)
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Built by p4build@trinidad.arubanetworks.com on 2009-05-06 at 22:43:09 PDT (gcc version 3.4.5 Cavium Networks Version: 1.4.0, build 58)
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): CVMSEG size: 2 cache lines (256 bytes)
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Setting flash physical map for 16MB flash at 0x1ec00000
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Determined physical RAM map:
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Primary instruction cache 32kB, virtually tagged, 4 way, 64 sets, linesize 128 bytes.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Primary data cache 16kB, 64-way, 2 sets, linesize 128 bytes.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Using 400.000 MHz high precision timer. cycles_per_jiffy=800000
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Calibrating delay using timer specific routine.. 800.31 BogoMIPS (lpj=800318)
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): available.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Checking for the multiply/shift bug... no.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Checking for the daddi bug... no.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Checking for the daddiu bug... no.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): PCI Status: PCI 32-bit
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): /proc/octeon_perf: Octeon performace counter interface loaded
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): wdt: registered with refresh
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Enabling Watchdog
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Octeon ethernet driver version: 1.5.0, build 187 May 6 2009 22:45:37
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): ^IInterface 0 is GMII
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): eth0: 100Mbs Full duplex, port 0, queue 0
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): ethsw: 100Mbs Full duplex, port 1, queue 1
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): isa bounce pool size: 16 pages
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Amd/Fujitsu Extended Query Table at 0x0040
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): phys_mapped_flash: CFI does not contain boot bank location. Assuming top.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): AD7416 driver probing for devices on Palomino TPM0
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): .AD7416 driver probing for devices on octeon twsi
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): .FOUND AD7416 at address: 48
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): octeon_twsi_write8: (1byte) failed
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Found AD7416 on bus octeon twsi.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): ath_hal: module license 'Proprietary' taints kernel.
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): ^H<6>Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)
Nov 2 15:37:24 nanny: <303022> |AP 00:0b:86:66:b4:fb@194.53.59.35 nanny| Reboot Reason: AP rebooted Wed Nov 2 06:36:40 PST 2011; SAPD: Reboot after image upgrade
Nov 2 15:37:25 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): Kernel watchdog refresh ended.
Nov 2 15:37:33 sapd: <311013> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| Image upgrade failed; details follow.
Nov 2 15:37:33 sapd: <311014> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| ERROR: File size exceeded 5242880 bytes
Nov 2 15:37:33 sapd: <311014> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| Local write failed: Success.
Nov 2 15:37:33 sapd: <311014> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| ncftpget mips64.ari: no space.
Nov 2 15:37:33 sapd: <311014> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| FTP Failed: 3. Trying TFTP.
Nov 2 15:37:33 sapd: <311014> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| ERROR: File size exceeded 5242880 bytes
Nov 2 15:37:33 sapd: <311014> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| Flash Image upgrade failed: 255
Nov 2 15:37:34 sapd: <311002> |AP 00:0b:86:66:b4:fb@194.53.59.35 sapd| Rebooting: SAPD: Reboot after image upgrade
Nov 2 15:37:34 nanny: <303086> |AP 00:0b:86:66:b4:fb@194.53.59.35 nanny| Process Manager (nanny) shutting down - AP will reboot!


I found out this has something to do with the software running on the RAP.. how can I fix this?
Aruba Employee

Re: Updated controller, RAPs not able to connect

You can't provision RAPs that are running <5.0 in their "flash (provisioning/backup) partition" to a controller running 6.x, which is what you have.

Nov 2 15:37:23 KERNEL(00:0b:86:66:b4:fb@194.53.59.35): ArubaOS Version 3.3.2.11-rn-3.0.1 (build 21263 / label #21263)

You'll first need to provision those RAPs to a controller running 5.x, preferably the latest 5.x code, which is now 5.0.4.2. Then upgrade their backup partition to that code with:

apflash ap-name backup-partition

Once the AP back up and running, issue the command:

show ap image version

and confirm 5.0.4.2 (or whatever you chose to use) is in all three of the RAP's partitions. Then you can provision that RAP over to your 6.1.2.4 controller.

This is all laid out in the release notes for 6.1.2.x.
Contributor II

Re: Updated controller, RAPs not able to connect

Yes, i can confirm that this is the solution.
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: