Wireless Access

My AP stuck in a boot loop.

Please help me. Thank you!

 

 

APBoot 1.5.3.4 (build 43264)
Built: 2014-04-16 at 15:38:45

Model: AP-22x
CPU0:  P1020E, Version: 1.1, (0x80ec0011)
Core:  E500, Version: 5.1, (0x80212051)
Clock:
       CPU0: 800 MHz
       CPU1: 800 MHz
       CCB:  400 MHz
       DDR:  333.333 MHz (666.667 MT/s data rate) (Asynchronous)
       LBC:   25 MHz
L1:    D-cache 32KB enabled
       I-cache 32KB enabled
I2C:   ready
DRAM:  Configuring DDR for 666.667 MT/s data rate
DDR:   512 MB (DDR3, 32-bit, CL=5, ECC off)
POST1: memory passed
Flash: 32 MB
L2:    256 KB enabled
Power: DC
PCIe1: RC, link up, x1
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       00  00  14e4  43a2 00002   03 80000004 00000000 80200004 00000000
PCIe2: RC, link up, x1
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       00  00  14e4  43a1 00002   03 a0000004 00000000 a0200004 00000000
Net:   eth0, eth1
Radio: bcm43460#0, bcm43460#1

Hit <Enter> to stop autoboot:  0
Checking image @ 0xee000000
Invalid image format version: 0xffffffff
Checking image @ 0xeee00000
Copying image from 0xeee00000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.

Aruba Networks
ArubaOS Version 6.3.1.0 (build 39345 / label #39345)
Built by p4build@tortuga on 2013-08-08 at 16:30:24 PDT (gcc version 4.5.1)

Memory: 510348k/524288k available (8348k kernel code, 13940k reserved, 540k data                                                                                        , 352k bss, 5008k init)
Processor 1 found.
Brought up 2 CPUs
PCI: Probing PCI hardware
pci 0000:00:00.0: PCI bridge to [bus 01-ff]
pci 0001:02:00.0: PCI bridge to [bus 03-ff]
pci 0000:00:00.0: enabling device (0106 -> 0107)
pci 0001:02:00.0: enabling device (0106 -> 0107)
ee000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
/proc/gfar_eth0_stats created
/proc/gfar_eth1_stats created
Enabling watchdog on CPU 1
Enabling watchdog on CPU 0

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
Ethernet port 1 mode: active-standby
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0: enslaving eth0 as a backup interface with a down link.
ADDRCONF(NETDEV_UP): eth1: link is not ready
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 66, num_radios 2 (jiffies 3213)
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
ASAP Slowpath initialized
Starting watchdog process...
Getting an IP address...
PHY: eth1 (mdio@ffe24000:01) - Link is Up - 1000/Full
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
10.10.10.54 255.255.255.0 10.10.10.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.
 

 

After I manual config DNS, factory_reset, purge enviroment... I got other error

 

APBoot 1.5.3.4 (build 43264)
Built: 2014-04-16 at 15:38:45

Model: AP-22x
CPU0:  P1020E, Version: 1.1, (0x80ec0011)
Core:  E500, Version: 5.1, (0x80212051)
Clock:
       CPU0: 800 MHz
       CPU1: 800 MHz
       CCB:  400 MHz
       DDR:  333.333 MHz (666.667 MT/s data rate) (Asynchronous)
       LBC:   25 MHz
L1:    D-cache 32KB enabled
       I-cache 32KB enabled
I2C:   ready
DRAM:  Configuring DDR for 666.667 MT/s data rate
DDR:   512 MB (DDR3, 32-bit, CL=5, ECC off)
POST1: memory passed
Flash: 32 MB
L2:    256 KB enabled
Power: DC
PCIe1: RC, link up, x1
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       00  00  14e4  43a2 00002   03 80000004 00000000 80200004 00000000
PCIe2: RC, link up, x1
       dev fn venID devID class  rev    MBAR0    MBAR1    MBAR2    MBAR3
       00  00  14e4  43a1 00002   03 a0000004 00000000 a0200004 00000000
Net:   eth0, eth1
Radio: bcm43460#0, bcm43460#1

Hit <Enter> to stop autoboot:  0
Checking image @ 0xee000000
Invalid image format version: 0xffffffff
Checking image @ 0xeee00000
Copying image from 0xeee00000

Image is signed; verifying checksum... passed
Signer Cert OK
Policy Cert OK
RSA signature verified.

Aruba Networks
ArubaOS Version 6.3.1.0 (build 39345 / label #39345)
Built by p4build@tortuga on 2013-08-08 at 16:30:24 PDT (gcc version 4.5.1)

Memory: 510348k/524288k available (8348k kernel code, 13940k reserved, 540k data, 352k bss, 5008k init)
Processor 1 found.
Brought up 2 CPUs
PCI: Probing PCI hardware
pci 0000:00:00.0: PCI bridge to [bus 01-ff]
pci 0001:02:00.0: PCI bridge to [bus 03-ff]
pci 0000:00:00.0: enabling device (0106 -> 0107)
pci 0001:02:00.0: enabling device (0106 -> 0107)
ee000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
/proc/gfar_eth0_stats created
/proc/gfar_eth1_stats created
Enabling watchdog on CPU 1
Enabling watchdog on CPU 0

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
apfcutil: sector CACHE: Cache uninitialized
apfcutil: sector RAP: Cache uninitialized
apfcutil -c RAP: Uninitialized. Initializing.........
apfcutil: sector MESH Prov: Cache uninitialized
Ethernet port 1 mode: active-standby
ADDRCONF(NETDEV_UP): eth0: link is not ready
ADDRCONF(NETDEV_UP): bond0: link is not ready
bonding: bond0: enslaving eth0 as a backup interface with a down link.
ADDRCONF(NETDEV_UP): eth1: link is not ready
bonding: bond0: enslaving eth1 as a backup interface with a down link.
AP xml model 66, num_radios 2 (jiffies 4696)
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
ASAP Slowpath initialized
Starting watchdog process...
Getting an IP address...
PHY: eth1 (mdio@ffe24000:01) - Link is Up - 1000/Full
bonding: bond0: link status definitely up for interface eth1.
bonding: bond0: making interface eth1 the new active one.
bonding: bond0: first active interface up!
ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
192.168.1.41 255.255.255.0 192.168.1.1
Running ADP...Done. Master is 192.168.1.2
wifi0: AP type AP-225, radio 0, max_bssids 16
wifi1: AP type AP-225, radio 1, max_bssids 16
shutting down watchdog process (nanny will restart it)...

        <<<<<       Welcome to the Access Point     >>>>>
~ #
~ # ?
?: Permission denied
~ # help
help: Permission denied

The system is going down NOW !!
Sending SIGTERM to all processes.
Please stand by while rebooting the system.
Restarting system.

 I've tried tftpboot but no luck

 

Hit <Enter> to stop autoboot:  0
apboot> tftpboot
eth0: link down.
eth1: link up, speed 1 Gb/s, full duplex
DHCP broadcast 1
DHCP IP address: 192.168.1.42
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.1.1
DHCP DNS server: 192.168.1.1
DHCP DNS domain:
ADP multicast 1
ADP broadcast 1
ADP multicast 2
ADP broadcast 2
ADP multicast 3

Retry count exceeded
DNS request 1 for aruba-master. to 192.168.1.1
Using eth1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.42
Filename 'e500.ari'.
Load address: 0x8000000
Loading: T T T T T
Retry count exceeded; starting again
eth0: link down.
eth1: link up, speed 1 Gb/s, full duplex
DHCP broadcast 1
DHCP IP address: 192.168.1.42
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.1.1
DHCP DNS server: 192.168.1.1
DHCP DNS domain:
ADP broadcast 3
ADP multicast 4
ADP broadcast 4
ADP multicast 5
ADP broadcast 5

Retry count exceeded
DNS request 1 for aruba-master. to 192.168.1.1
Using eth1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.42
Filename 'e500.ari'.
Load address: 0x8000000
Loading: T T T T T
Retry count exceeded; starting again
eth0: link down.
eth1: link up, speed 1 Gb/s, full duplex
DHCP broadcast 1
DHCP IP address: 192.168.1.42
DHCP subnet mask: 255.255.255.0
DHCP def gateway: 192.168.1.1
DHCP DNS server: 192.168.1.1
DHCP DNS domain:
ADP multicast 6
ADP broadcast 6
ADP multicast 7
ADP broadcast 7
ADP multicast 8

Retry count exceeded
DNS request 1 for aruba-master. to 192.168.1.1
Using eth1 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.42
Filename 'e500.ari'.
Load address: 0x8000000
Loading: T T T T T
Retry count exceeded; starting again
eth0: link down.
eth1: link up, speed 1 Gb/s, full duplex

You list both IAP205 and AP225, is this environment running Instant or is there an AOS controller for the AP to connect to?

 

The first set of logs show the AP not discovering the controller. It appears that after you fixed the DNS settings, the AP did discover the master and attempted to connect.

I have an IAP-205 in standalone mode. I just tried to add an AP-225 to extend wifi coverage but it's stuck in a boot loop.

 

I think AP-225 found virtual controller but can not connect.

 

What should I do?

---

@matroi wrote:

I have an IAP-205 in standalone mode. I just tried to add an AP-225 to extend wifi coverage but it's stuck in a boot loop.

 

I think AP-225 found virtual controller but can not connect.

 

What should I do?

---

The AP225 can't find a virtual controller (as in an Instand based virtual controller). What is the device that's operating as 192.168.1.2? If you have an IAP operating as standalone, the AP225 will not work along with it unless the AP-225 is also running Instant firmware. You would need an IAP225 for that, as it's not possible to load Instant firmware to an AP that did not originate as an Instant model.

A AP225 will not join a Virtual Controller/IAP cluster. You would need an IAP225 for this to work. If you check the back of the 225, you can see if it is an AP or IAP.

@cclemmer: Do you mean AP-225 cannot be controlled by virtual controller?
@zalion0: My AP-225 is non-instant, it's AP not IAP. It can working with IAP-205, isn't is?

My config as below:

IAP-205: OS ArubaInstant 6.4.1, IP 192.168.1.40, Virtual controller running on it, VC's IP 192.168.1.2.
AP-225: OS 6.3.1, IP 192.168.1.41 <= just tried to add but got error.

That is correct an AP225 cannot be managed by an IAP225 or join an an IAP cluster. A IAP225 can be converted to an AP225 and managed by a physical controller but an AP225 cannot be converted to an IAP225.

Sent from my iPhone

---

@matroi wrote:

@cclemmer: Do you mean AP-225 cannot be controlled by virtual controller?

---

Yes, that is correct. For the AP to be controlled by an Instant virtual controller, you would need the IAP-225 instead.

Thank you so much!

I misunderstood that non-instant AP(s) can be controlled by a virtual controller.