Wireless Access

Reply
Contributor II

New APs not showing up on controller, all existing APs fine.

We have a box of both older previously used AP's (mostly 125's) and a couple new 135's. We recently switched over from a Master-Local dual 3600 configuration to a standalone 7210. Everything is working fine, we have 128 AP's in use and functioning. 

 

I've been trying to add AP's now that we have more space. We still have the 30 day 512 AP and 512 PEF licenses active, so I know it isn't a licensing issue. 

 

The AP's never stay on the controller for more than a few seconds, if at all. 

 

For example, here is the console output of a self-initiated reboot on the brand new, never before used AP135. 

 

APBoot 1.2.6.7 (build 30025)
Built: 2011-08-30 at 17:41:16

Model: AP-13x
CPU: 88F6560 A0 (DDR3)
Clock: CPU 1600MHz, L2 533MHz, SysClock 533MHz, TClock 200MHz
DRAM: 256MB
POST1: passed
Flash: 16 MB
Power: 802.3at POE
LAN: done
PHY: done
PEX 0: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
00.00 00 11ab 6560 00005 02 f1000000 00000000 00000000 00000000
00.01 00 168c 0030 00002 01 90000000 00000000 00000000 00000000
PEX 1: RC, link up, x1
bus.dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3
01.00 00 11ab 6500 00005 02 f1000000 00000000 00000000 00000000
01.01 00 168c 0030 00002 01 94000000 00000000 00000000 00000000
Net: eth0, eth1
Radio: ar9390#0, ar9390#1

Hit <Enter> to stop autoboot: 0
Checking image @ 0xf8100000
Invalid image format version: 0xffffffff
Checking image @ 0xf8800000
Invalid image format version: 0xc
eth0: up, 1 Gb/s, full duplex
DHCP broadcast 1
DHCP broadcast 2
DHCP broadcast 3
DHCP broadcast 4
DHCP broadcast 5

Retry count exceeded; starting again
eth1: down
eth0: up, 1 Gb/s, full duplex
DHCP broadcast 1
DHCP IP address: 10.10.161.128
DHCP subnet mask: 255.255.252.0
DHCP def gateway: 10.10.160.1
DHCP DNS server: 10.10.20.129
DHCP DNS domain: cushnet.org
ADP multicast 1
Controller address: 10.10.160.7
Using eth0 device
TFTP from server 10.10.160.7; our IP address is 10.10.161.128
Filename 'armv5te.ari'.
Load address: 0x2000000
Loading: #################################################################
#############
done
Bytes transferred = 5069068 (4d590c hex)

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.
Automatic boot of image at addr 0x02000000 ...
## Booting image at 02000200 ...
Uncompressing... done

Aruba Networks
ArubaOS Version 6.3.1.4 (build 42768 / label #42768)
Built by p4build@corsica.arubanetworks.com on 2014-03-18 at 13:16:29 PDT (gcc version 4.3.3)
Memory: 256MB = 256MB total
Memory: 243968KB available (2816K code, 8941K data, 3848K init, 0K highmem)
Delay calibration in progress:
Calibrating delay loop... 1597.44 BogoMIPS (lpj=1597440)
PEX0 interface detected Link X1
PEX1 interface detected Link X1
bio: create slab <bio-0> at 0
wdt: registered with refresh
Enabling Watchdog
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
i2c /dev entries driver
i2c-arran: using default base 0xf1018180

Starting Kernel SHA1 KAT ...Completed Kernel SHA1 KAT
Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT
Starting Kernel DES KAT ...Completed Kernel DES KAT
Starting Kernel AES KAT ...Completed Kernel AES KAT

Starting Kernel AESGCM KAT ...Completed Kernel AESGCM KAT
Domain Name: arubanetworks.com
No panic info available
init mv_cesa ok
Ethernet port 1 mode: active-staEthernet Channel Bonding Driver: v3.5.0 (November 4, 2008)
ndby
eth0: link up, full duplex, speed 1 Gbps
ADDRCONF(NETDEV_UP): bond0: link is not ready
eth0: link up, full duplex, speed 1 Gbps
bonding: bond0: making interface eth0 the new active one.
bonding: bond0: first active interface up!
bonding: bond0: enslaving eth0 as an active interface with an up link.
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
eth1: link down
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 51, num_radios 2 (jiffies 2569)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 16
radio 1: band 0 ant 0 max_ssid 16
ethernet_device_event: dev eth0 is up
eth0: link up, full duplex, speed 1 Gbps
eth0: link up, full duplex, speed 1 Gbps
Starting watchdog process...
Getting an IP address...
10.10.161.128 255.255.252.0 10.10.160.1
Running ADP...Done. Master is 10.10.160.7
ath_hal: 0.9.17.1 (AR5416, AR9380, REGOPS_FUNC, PRIVATE_DIAG, WRITE_EEPROM, 11D)
ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
ath_rate_atheros: Aruba Networks Rate Control Algorithm
ath_dfs: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_spectrum: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
ath_pci: 0.9.4.5 (Atheros/multi-bss)
ath_attach: scn cd3c0320 sc cd3a0000 ah cd340000
wifi0: Base BSSID d8:c7:c8:48:88:70, 16 available BSSID(s)
eth0 address=d8:c7:c8:cc:88:86
br0 address=d8:c7:c8:cc:88:86
wifi0: AP type AP-135, radio 0, max_bssids 16
wifi0: Atheros 9380: mem=0xf3000000, irq=25 hw_base=0xd1bc0000
ath_attach: scn ccfa0320 sc ccfc0000 ah cc800000
wifi1: Base BSSID d8:c7:c8:48:88:60, 16 available BSSID(s)
eth0 address=d8:c7:c8:cc:88:86
br0 address=d8:c7:c8:cc:88:86
wifi1: AP type AP-135, radio 1, max_bssids 16
wifi1: Atheros 9380: mem=0xf4000000, irq=24 hw_base=0xd1d80000
ath_ahb: 0.9.4.5 (Atheros/multi-bss)
ath_ahb: No devices found, driver not installed.

Starting FIPS KAT ... Completed FIPS KAT

AP rebooted Fri Dec 31 16:04:21 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=936 dest=10.10.160.2 tries=10 seq=0
shutting down watchdog process (nanny will restart it)...

<<<<< Welcome to the Access Point >>>>>

~ # Enabling eth1 due to LLDP power grant [power profile 1]

 

 

 

Notice in the last few lines, the HELLO len=936 dest=10.10.160.2. 

 

10.10.160.2 was our previous controller. It was not showing up on that either, but I have since taken the controller offline and powered it down to try to force the AP's over to the new controller. 

 

Our controller IP is 10.10.160.7. It appears to be getting the IP through ADP without a problem. 

 

Any ideas? I've got 9 AP's here on my desk and I can't use them right now. 

 

I tried turning on Control Plane Security with Auto Cert Provisioning and entered the subnet range our AP's sit on into the allowed addresses for Auto Cert. This didn't seem to help. 

Contributor II

Re: New APs not showing up on controller, all existing APs fine.

Other details:

 

I can ping from the unprovisionable AP's to the controller without a problem. 

 

I have tried all the different combinations of "purge, clean os, saveenv, boot" that I've found here. Same result. 

 

I've manually forced the 125's to tftpboot. They do it successfully. Still not showing up on the controller for more than a few seconds. Flag of UG and says "Down" before I can get a chance to provision. 

Guru Elite

Re: New APs not showing up on controller, all existing APs fine.

What is your LMS IP set to in the AP system profile?


Tim Cappalli | Aruba Security TME
@timcappalli | timcappalli.me | ACMX #367 / ACCX #480
Contributor II

Re: New APs not showing up on controller, all existing APs fine.

Figures one of those Brandeis guys would help! Chris Medina was just here Tuesday dropping off a S2500 and S3500 for me to play with. 

 

So that may of been it. I had the LMS IP set to 10.10.160.7, with a backup of 10.10.160.2 since I was planning to run the old 3600 as a backup controller with centralized licensing for our custom AP profile once the 7210 wrinkles are worked out. The default profile still had 10.10.160.2 for the primary. 

 

I'm going to assume that fresh/dirty AP's end up going into the default AP profile which would cause them to try to contact the IP given there. 

 

I made the change and bingo, blinky blinky happy linky. 

 

Thanks for the help!

 

 

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: