Wireless Access

Reply
Occasional Contributor I

ap 105 not connecting to controller

When trying to install a new ap 105, I get the follow error during the boot. Others have not problems and it appears that it gets an ip address fine, why will this one not find the controller? I've factory reset with no luck. Any help is greatly appreciated.

 

Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 10.1.140.63
DHCP subnet mask: 255.255.254.0
DHCP def gateway: 10.1.140.1
DHCP DNS server: 10.1.100.30
DHCP DNS domain: whitehall.local
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3
Retry count exceeded
DNS request 1 for aruba-master.whitehall.local to 10.1.100.30
T T T T
Retry count exceeded; starting again
eth0 up: 1 Gb/s full duplex

 

Aruba Employee

Re: ap 105 not connecting to controller

How is your AP finding master controller?

Statically configured? Throguh DHCP option? By resolving aruab-master? through ADP multicast/braodcast? 

 

Occasional Contributor I

Re: ap 105 not connecting to controller

APs get dhcp address from Windows dc then resolves aruba-master

Aruba

Re: ap 105 not connecting to controller

It looks like the AP cannot contact your DNS server: 10.1.100.30 (hence the timeout message).  Are the other APs you have on the same network?  Can you plug a PC into that same port and atttempt to do an nslookup to that DNS server to make sure ?   Make sure your IP/mask information is correct.

------------------------------------------------
Systems Engineer, Northeast USA
ACCX | ACDX | ACMX

Occasional Contributor I

Re: ap 105 not connecting to controller

That port is a 140 vlan port. Other Aruba aps 105s, 135s, and even 124s, all connect fine on the same vlan. for some reason these two won't. I've tried giving static ip and aruba master information and still can't get it to boot.

Re: ap 105 not connecting to controller

with the fixed settings, what output do you get on the console?

 

i would double check that the switchport is correctly configured, try connecting another device and see if it gets IP and can do DNS correctly.

Occasional Contributor I

Re: ap 105 not connecting to controller

Well...for some reason the second time I added static ips it worked perfectly. I must have done something wrong. Now if I purgeenv and save then boot, I get a signed image but gets caught in the reboot loop below:

 

APBoot 1.2.4.4 (build 26618)
Built: 2011-01-07 at 13:42:04

Model: AP-10x
CPU:   AR7161 revision: A2
Clock: 680 MHz, DDR clock: 340 MHz, Bus clock: 170 MHz
DRAM:  128 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  0029 00002   01 10000000 00000000 00000000 00000000
       01  00  168c  0029 00002   01 10010000 00000000 00000000 00000000
Net:   eth0
Radio: ar922x#0, ar922x#1

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 (3779112 bytes)
Loading .data @ 0x8119aa30 (32 bytes)
Clearing .bss @ 0x8119aa50 (16 bytes)
## Starting application at 0x80e00000 ...
Uncompressing...................................
¦
Aruba Networks
ArubaOS Version 6.1.3.6 (build 36470 / label #36470)
Built by p4build@corsica.arubanetworks.com on 2012-12-11 at 12:16:36 PST (gcc version 4.3.3)
CPU Rev: aa
71x CPU
Flash variant: default
Cache parity protection disabled
Using 340.000 MHz high precision timer. cycles_per_jiffy=680000
Memory: 122880k/131072k available (1850k kernel code, 8108k reserved, 693k data, 2960k init, 0k highmem)
 available.
detected lzma initramfs
initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=12449792
LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ..............................................................................................................................................................................................
AR7100 GPIOC major 0
wdt: registered with refresh
Enabling Watchdog
Talisker RSSI LED initialization
Creating 1 MTD partitions on "ar7100-nor0":
0x00000000-0x01000000 : "flash"
i2c /dev entries driver
i2c-talisker: using default base 0x18040000
AD7416 driver probing for devices on AR7100 I2C
.<6>lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver

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
Testing TPM... Passed
ag7100_mod: module license 'unspecified' taints kernel.
AG7100: Length per segment 512
AG7100: Max segments per packet 4
AG7100: Max tx descriptor count    400
AG7100: Max rx descriptor count    252
AG7100: fifo cfg 3 018001ff
AG7100CHH: Mac address for unit 0
AG7100CHH: 6c:f3:7f:ca:74:d1
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 0
AP xml model 39, num_radios 2 (jiffies 4137)
init_asap_mod: installation:0
radio 0: band 1 ant 0 max_ssid 8
radio 1: band 0 ant 0 max_ssid 8
setting bond0 as bridge child
setting gre0 as split child
Starting watchdog process...
Getting an IP address...
ag7100_ring_alloc Allocated 4800 at 0x813be000
ag7100_ring_alloc Allocated 3024 at 0x813b1000
AG7100: cfg1 0xf cfg2 0x7014
ATHRF1: Port 0, Neg Success
ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 3100
AG7100: unit 0: phy not up carrier 1
Writing 4
ADDRCONF(NETDEV_UP): bond0: link is not ready
AG7100: unit 0 phy is up...RGMii 1000Mbps full duplex
AG7100: pll reg 0x18050010: 0x110000  AG7100: cfg_1: 0x1ff0000
AG7100: cfg_2: 0x3ff
AG7100: cfg_3: 0x18001ff
AG7100: cfg_4: 0xffff
AG7100: cfg_5: 0xfffef
AG7100: done cfg2 0x7215 ifctl 0x0 miictrl 0x22
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
10.1.140.64 255.255.254.0 10.1.140.1
Running ADP...cat: /tmp/master: No such file or directory
Done. Master is
killall: nanny: no process killed
killall: sapd: no process killed
Sending SIGKILL to all processes.
Please stand by while rebooting the system.
Restarting system.
.

   If I factory_reset I get the same boot as before with invalid image:

apboot> boot
Checking image @ 0xbf100000
Invalid image format version: 0xffffffff
Checking image @ 0xbf800000
Invalid image format version: 0xffffffff
eth0 up: 1 Gb/s full duplex
DHCP broadcast 1
DHCP IP address: 10.1.140.64
DHCP subnet mask: 255.255.254.0
DHCP def gateway: 10.1.140.1
DHCP DNS server: 10.1.100.30
DHCP DNS domain: whitehall.local
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3
 
Retry count exceeded
DNS request 1 for aruba-master.whitehall.local to 10.1.100.30
T T

 

Occasional Contributor I

Re: ap 105 not connecting to controller

One more update:

 

If I add an reservation in the dhcp server for the 105 ap and then reboot it it connects just fine to the controller. The weird part is that if I reserved the 140.64 address it will won't connect with controller. If I reserved a new dhcp address it works just fine. Would the controller block ip address of aps? Like a blacklist?

Re: ap 105 not connecting to controller

Duplicate IP on the network, possibly a bad ARP cache somewhere between the AP and controller? You don't have any 'down' APs in the 'show ap database' using that 64 IP correct? The controller shouldn't block anything and the fact that your DNS wouldn't respond means it's likely outside of the controller anyway.

Jerrod Howard
Sr. Techical Marketing Engineer
Occasional Contributor I

Re: ap 105 not connecting to controller

Thank you for the response. I will keep digging.

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