first of all, these are all CAPs. I have seen some things about this happening with RAPs, but these are all CAPs. As far as I know, nothing happened on the controller, but 34 of our 64 135s started going into a reboot loop one evening. I have a ticket open with support, but as I said, all of their recommendations are based on RAPs.
Here is the startup log on an affected AP:
APBoot 1.2.8.1 (build 34939)
Built: 2012-08-17 at 12:54:18
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.3af 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 @ 0xf6100000
Invalid image format version: 0xffffffff
Checking image @ 0xf6800000
Invalid image format version: 0xc
eth0: up, 1 Gb/s, full duplex
DHCP broadcast 1
DHCP broadcast 2
DHCP IP address: 10.25.0.73
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 10.25.0.1
DHCP DNS server: 10.7.0.112
DHCP DNS domain: hmcorp.local
ADP multicast 1
Controller address: 10.7.0.162
Using eth0 device
TFTP from server 10.7.0.162; our IP address is 10.25.0.73; sending through gateway 10.25.0.1
Filename 'armv5te.ari'.
Load address: 0x2000000
Loading: #################################################################
##############
done
Bytes transferred = 5168276 (4edc94 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.1 (build 40563 / label #40563)
Built by p4build@port-royal on 2013-10-24 at 17:29:27 PDT (gcc version 4.3.3)
Memory: 256MB = 256MB total
Memory: 243840KB available (2816K code, 9021K data, 3936K 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
ADDRCONF(NETDEV_UP): eth1: link is not ready
eth1: link down
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 51, num_radios 2 (jiffies 2617)
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
Shutting down eth1 due to insufficient POE voltage [power profile 2]
Starting watchdog process...
Getting an IP address...
10.25.0.73 255.255.255.0 10.25.0.1
Running ADP...Done. Master is 10.7.0.162
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 cd6c0000 ah cd340000
wifi0: Base BSSID 9c:1c:12:a3:25:b0, 16 available BSSID(s)
eth0 address=9c:1c:12:c2:32:5a
br0 address=9c:1c:12:c2:32:5a
wifi0: AP type AP-135, radio 0, max_bssids 16
wifi0: Atheros 9380: mem=0xf3000000, irq=25 hw_base=0xd19c0000
ath_attach: scn cc820320 sc cc840000 ah cc880000
wifi1: Base BSSID 9c:1c:12:a3:25:a0, 16 available BSSID(s)
eth0 address=9c:1c:12:c2:32:5a
br0 address=9c:1c:12:c2:32:5a
wifi1: AP type AP-135, radio 1, max_bssids 16
wifi1: Atheros 9380: mem=0xf4000000, irq=24 hw_base=0xd1dc0000
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:22 PST 1999; SAPD: Unable to contact switch: HELLO-TIMEOUT. Last Ctrl msg: HELLO len=920 dest=10.7.0.162 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]
Here is the AP pinging the controller:
~ # ping 10.7.0.162
PING 10.7.0.162 (10.7.0.162): 56 data bytes
64 bytes from 10.7.0.162: icmp_seq=0 ttl=63 time=0.8 ms
64 bytes from 10.7.0.162: icmp_seq=1 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=2 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=3 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=4 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=5 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=6 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=7 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=8 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=9 ttl=63 time=0.9 ms
64 bytes from 10.7.0.162: icmp_seq=10 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=11 ttl=63 time=1.0 ms
64 bytes from 10.7.0.162: icmp_seq=12 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=13 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=14 ttl=63 time=12.0 ms
64 bytes from 10.7.0.162: icmp_seq=15 ttl=63 time=0.9 ms
64 bytes from 10.7.0.162: icmp_seq=16 ttl=63 time=0.7 ms
64 bytes from 10.7.0.162: icmp_seq=17 ttl=63 time=0.8 ms
64 bytes from 10.7.0.162: icmp_seq=18 ttl=63 time=0.9 ms
^C
--- 10.7.0.162 ping statistics ---
19 packets transmitted, 19 packets received, 0% packet loss
round-trip min/avg/max = 0.7/1.3/12.0 ms
~ #
and finally:
(SPIAARUBA01) # show datapath session table 10.25.0.73
Datapath Session Table Entries
------------------------------
Flags: F - fast age, S - src NAT, N - dest NAT
D - deny, R - redirect, Y - no syn
H - high prio, P - set prio, T - set ToS
C - client, M - mirror, V - VOIP
Q - Real-Time Quality analysis
I - Deep inspect, U - Locally destined
E - Media Deep Inspect, G - media signal
Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags
-------------- -------------- ---- ----- ----- ---- ---- --- --- ----------- ---- --------- --------- -----
10.25.0.73 10.7.0.162 17 8211 8222 0/0 0 0 1 1/2 f 0 0 FYCI
10.25.0.73 10.7.0.162 17 8211 8211 0/0 0 0 1 1/2 f 0 0 FCI
10.7.0.162 10.25.0.73 17 8211 8211 0/0 0 0 1 1/2 f 0 0 FYI
10.7.0.162 10.25.0.73 17 8222 8211 0/0 0 0 1 1/2 f 0 0 FYI
Any ideas what I can do?
Russell