03-26-2016 08:42 AM
Ive been struggleing with this for a few days so i am hoping one of you can help. i know the kit is long past EOL but im learning as i go,
i have had an 800 controller and 2 AP105's (one RAP) for some time. i recenly purchased (2nd hand) a pair of AP93H as i wanted wired access for a Cisco phone where the RAP is located.
so i plugged in the AP93's and purged them, but they do not show on the controller, the AP boot log shows DHCP Timeout but the DHCP is fine when in APboot
Proof DHCP works
apboot> dhcp eth0 up: 100 Mb/s full duplex DHCP broadcast 1 DHCP IP address: 10.1.2.127 DHCP subnet mask: 255.255.255.0 DHCP def gateway: 10.1.2.254 DHCP DNS server: 10.1.2.254 DHCP DNS domain: xxxxxxxxxxxxxx.net apboot> apboot> ping 10.1.2.99 eth0 up: 100 Mb/s full duplex Using eth0 device host 10.1.2.99 is alive apboot>
Boot Process (DHCP Enabled)
APBoot 188.8.131.52 (build 37301) Built: 2013-02-20 at 21:26:34 Model: AP-9x CPU: AR7242 revision: 1 Clock: 390 MHz, DDR rate: 390 MHz, Bus clock: 195 MHz DRAM: 64 MB POST1: passed Copy: done Flash: 16 MB PCI: scanning bus 0 ... dev fn venID devID class rev MBAR0 MBAR1 MBAR2 MBAR3 00 00 168c 002a 00002 01 10000004 00000000 00000000 00000000 Net: eth0 Radio: ar9280#0 Hit <Enter> to stop autoboot: 0 Checking image @ 0xbf100000 Image is signed; verifying checksum... passed Signer Cert OK Policy Cert OK RSA signature verified. ELF file is 32 bit Loading .text @ 0x80e00000 (3325720 bytes) Clearing .bss @ 0x8112bf20 (16 bytes) Loading .data @ 0x8112bf30 (32 bytes) ## Starting application at 0x80e00000 ... Uncompressing.............................. ▒▒▒ Aruba Networks ArubaOS Version 184.108.40.206 (build 35054 / label #35054) Built by p4build@corsica on 2012-08-27 at 10:31:45 PDT (gcc version 3.4.3) CPU Rev: 1101 72x CPU No manufacturing information available; assuming AP-92 Flash variant: 16M Cache parity protection disabled Using 195.000 MHz high precision timer. cycles_per_jiffy=390000 Memory: 58556k/65536k available (1640k kernel code, 6924k reserved, 720k data, 2600k init, 0k highmem) available. detected lzma initramfs initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13853184 LZMA initramfs by Ming-Ching Tiew <email@example.com> ..................................................
.................................................. .................................................. .................................................. ............ Returning IRQ 48 AR7240 GPIOC major 0 wdt: registered with refresh Enabling Watchdog Talisker RSSI LED initialization Creating 1 MTD partitions on "ar7240-nor0": 0x00000000-0x01000000 : "flash" i2c /dev entries driver i2c-talisker: using default base 0x18040000 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 Domain Name: arubanetworks.com No panic info available AG7240: Length per segment 1536 AG7240: Max segments per packet 1 AG7240: Max tx descriptor count 40 AG7240: Max rx descriptor count 252 AG7240: fifo cfg 3 01f00140 AG7240CHH: Mac address for unit 0 AG7240CHH: 00:0b:86:9c:13:46 ATHRSF1_PHY: Port 0, Neg Success ATHRSF1_PHY: unit 0 phy addr 0 <6>AP xml model 42, num_radios 1 (jiffies 3118) init_asap_mod: installation:0 radio 0: band 2 ant 1 max_ssid 16 asap_gre_init: ADDED GRE protocol c00aed60 setting bond0 as bridge child setting gre0 as split child USB not provisioned Starting watchdog process... Getting an IP address... ag7240_ring_alloc Allocated 640 at 0x8118ac00 ag7240_ring_alloc Allocated 4032 at 0x8118c000 Virian MDC CFG Value ==> 4 Setting PHY... ATHRSF1_PHY: Port 0, Neg Success ATHRSF1_PHY: unit 0 phy addr 0 Not enabling interrupts in AR7242 yet... Kernel watchdog refresh ended. DHCP timed out. Rebooting killall: nanny: no process killed killall: sapd: no process killed Sending SIGKILL to all processes. Please stand by while rebooting the system. Restarting system.
it looks like once arubaos launches there is no network communication. i am plugged from eth0 on the AP directly into the controller
the only thing i can think is that the AP's may have been on a higher arubaos version, the only difference i can see between the new ap93's and the existing 105's is that the APboot versions are different.
ive tried factory resetting them and a clearos.
setting the ip address and master using setenv gets to a prompt but the AP reboots with "failed to communicate with switch"
Boot Process (static)
ATHRSF1_PHY: unit 0 phy addr 0 Not enabling interrupts in AR7242 yet... DHCP 10.1.2.10 255.255.255.0 10.1.2.254 Running ADP...Done. Master is 10.1.2.99 Kernel watchdog refresh ended. ath_hal: module license 'Proprietary' taints kernel. ath_hal: 0.9.17.1 (AR5416, 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_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved ath_pci: 0.9.4.5 (Atheros/multi-bss) wifi0: Base BSSID 00:0b:86:41:34:60, 16 available BSSID(s) edev->dev_addr=00:0b:86:9c:13:46 edev->dev_addr=00:0b:86:9c:13:46 wifi0: AP type AP-92, radio 0, max_bssids 16 wifi0: Atheros 9280: mem=0x10000000, irq=48 hw_base=0xb0000000 AP rebooted Fri Dec 31 16:02:37 PST 1999: DHCP timed out shutting down watchdog process (nanny will restart it)... <<<<< Welcome to the Access Point >>>>> ~ # ping 10.1.2.99 PING 10.1.2.99 (10.1.2.99): 56 data bytes ^X --- 10.1.2.99 ping statistics --- 81 packets transmitted, 0 packets received, 100% packet loss ~ #
am i missing something stupid?
Solved! Go to Solution.
03-26-2016 10:49 AM
The minimum code revision for the AP-93H is (I think) 6.1.3.x. SO it won't come up, and the 800 controller you ahve won't support AOS 6.1. So you will need a new controller to run the 93H APs.
Sr. Techical Marketing Engineer
03-26-2016 11:22 AM
AP93's Mimimum code version is ArubaOS 5.0.1.x.
Full Extract to save clicking
Product and Software: This article applies to AP-92 and AP-93 and ArubaOS 5.x.
AP-92 and AP-93 are the indoor access points (APs) that support dual-band with single radio.
The minimum code that these two APs support is ArubaOS 5.0.1.x.
AP-92 and AP-93 must have ArubaOS 5.0.1.x to work as:
- campus AP
- remote AP
- mesh AP
- remote mesh
- air monitor
- AP and AM"
03-26-2016 11:32 AM - edited 03-26-2016 11:43 AM