ArubaOS and Controllers

Reply
Highlighted
Occasional Contributor II

New AP connects to wrong box.




Below:-

Booting image...
..............................

Aruba Networks
ArubaOS Version 5.0.1.0 (build 24398 / label #24398)
Built by p4build@cartman on 2010-06-13 at 23:09:36 PDT (gcc version 3.4.3)
BOARD - Mataro
CPU frequency 220.00 MHz
Using 110.000 MHz high precision timer. cycles_per_jiffy=220000
Memory: 25860k/32768k available (1996k kernel code, 6892k reserved, 656k data, 2584k init, 0k highmem)
available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13472256
LZMA initramfs by Ming-Ching Tiew ..............................................................................................................................................................................................................
wdt: registered with refresh
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
physmap flash device: 400000 at 1fc00000
Macronix Flash MX29LV320A (Top) (User Locked)
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
Parsing the partition info

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
bond0: Atheros AR2313: 00:1a:1e:c8:1f:fc, irq 3
AP xml model 2, num_radios 2 (jiffies 7056)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 8
radio 1: band 0 ant 0 max_ssid 8
asap_gre_init: ADDED GRE protocol c00a7774
setting bond0 as bridge child
setting gre0 as split child
ath_hal: module license 'Proprietary' taints kernel.
USB not provisioned
Starting waath_hal: 0.9.17.1 (tchdog process..AR5212.
Getting an IP, AR5312 address...
10.21.22.160 255.255.254.0 10.21.22., RF2413254
Running ADP, RF5413...Done. Master , RF2316is 10.1.
, RF2317)
ath_rate_atheros: Version 2.0.1
Copyright (c) 2001-2004 Atheros Communications, Inc, All Rights Reserved
ath_dfs: Version 2.0.0
Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
ath_ahb: 0.9.4.5 (Atheros/multi-bss)
devid=0x57
AR2313_REV2/7
wifi0: Base BSSID 00:1a:1e:01:ff:c8, 8 available BSSID(s)
edev->dev_addr=00:1a:1e:c8:1f:fc
edev->dev_addr=00:1a:1e:c8:1f:fc
wifi0: AP type AP-65, radio 0, max_bssids 8
wifi0: Atheros 5312 WiSoC: mem=0xb8000000, irq=2
AR2313_REV8
wifi1: Base BSSID 00:1a:1e:01:ff:c0, 8 available BSSID(s)
edev->dev_addr=00:1a:1e:c8:1f:fc
edev->dev_addr=00:1a:1e:c8:1f:fc
wifi1: AP type AP-65, radio 1, max_bssids 8
wifi1: Atheros 5312 WiSoC: mem=0xb8500000, irq=5


There it hangs.

tweet @wjhphoto
Highlighted
Occasional Contributor II

New AP connects to wrong box.

I've just discovered my problem.

Option 43. Points to the old IP address of our test Controller. That IP address now resides on the Fortinet FW.

I've been working on this for 2 fecking days only to have it found by some-one else. Grrrrrrrr!

It's not even lunch time and I'm having a seriously bad day.
tweet @wjhphoto
Guru Elite

You found it yourself.

Give yourself some credit--- You found it yourself.

*Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba Networks or Hewlett Packard Enterprise.*
ArubaOS 8.5 User Guide
InstantOS 8.5 User Guide
Airheads Knowledgebase
Airheads Video Knowledge Base
Remote Access Point Solution Guide
ArubaOS Consolidated Release Notes
ArubaOS 8 ViA VPN Solution Guide
Highlighted
Occasional Contributor II

Option 43


Hi,

I have trouble configuring an AP since it connects to the wrong controller. We have an A2400 (aruba-master, 10.9.0.200) and an A200 (aruba-test, 10.9.0.202) running OS 5.0.1.0. The AP61 has been used before.

Now I purged the configuration of the AP61 and connected it to the network. Although the default configuration has aruba-master as servername, it always connects to the A200. Even setting the serverip to 10.9.0.200 doesn't change this.

We are not using any white lists so far. This is the first time I connect an AP to our WLAN after upgrading to OS 5. So if something has changed that leads to this behavior, please let me know.

Regards
Dirk




Are you using DHCP option 43? It might be worth checking here before you spen anymore time on it....
tweet @wjhphoto
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: