Wireless Access

Reply
Occasional Contributor II

AP 70 reset problem

Hi.

Well, I am quite new with Aruba wireless controllers, indeed, its my first experience with wireless networks.

I have got the administering of Aruba 800 controller. I have this problem with some AP 70:

In one of our site we had energy problems during the night and some equipment restarted. When the energy came back some AP stopped working (those AP are plugged to a PoE source), at this moment I’m trying to reset them regarding the “Aruba AP 70 Access Point Installation Guide” because the controller lost the connection to those AP (I have the problem with 5 AP´s) and I want to re provision them. I made the serial breakout adapter regarding the manual pinout and I could connect to the AP via serial port but it seems that the AP is not working well, once the AP start booting I can see this message:

 

APBoot 1.5.5 (build taylor@harpua-ENG.0000)

Built: 2006-02-24 18:33:47 (with gcc 3.3.1)

 

CPU:   RC32434 MIPS-32 at 266 MHz: 8 kB I-Cache 8 kB D-Cache

Board: Muscat, Local Bus at 133 MHz

DRAM:  32 MB

POST:  passed

FLASH: 4 MB

PCI:   scanning bus0 ...

       dev fn venID devID class  rev MBAR0    MBAR1    MBAR2    MBAR3

       0a  00 100b  0020  000002 00  000fff01 07fff000 00000000 00000000

       0b  00 1106  3038  00000c 62  00000000 00000000 00000000 00000000 000ffee1

       0b  01 1106  3038  00000c 62  00000000 00000000 00000000 00000000 000ffec1

       0b  02 1106  3104  00000c 65  07ffef00 00000000 00000000 00000000

       0c  00 168c  0013  000002 01  07fe0000 00000000 00000000 00000000

       0d  00 168c  0013  000002 01  07fd0000 00000000 00000000 00000000

Net:   en0 en1 br0 lo0

Bridg: en0 en1

 

Hit <Enter> to stop autoboot:  1     I have no response when I press Enter, I tried the same with the 5 AP´s

 

APBoot 1.5.5 (build taylor@harpua-ENG.0000)

Built: 2006-02-24 18:33:47 (with gcc 3.3.1)

 

CPU:   RC32434 MIPS-32 at 266 MHz: 8 kB I-Cache 8 kB D-Cache

Board: Muscat, Local Bus at 133 MHz

DRAM:  32 MB

POST:  passed

FLASH: 4 MB

PCI:   scanning bus0 ...

       dev fn venID devID class  rev MBAR0    MBAR1    MBAR2    MBAR3

       0a  00 100b  0020  000002 00  000fff01 07fff000 00000000 00000000

       0b  00 1106  3038  00000c 62  00000000 00000000 00000000 00000000 000ffee1

       0b  01 1106  3038  00000c 62  00000000 00000000 00000000 00000000 000ffec1

       0b  02 1106  3104  00000c 65  07ffef00 00000000 00000000 00000000

       0c  00 168c  0013  000002 01  07fe0000 00000000 00000000 00000000

       0d  00 168c  0013  000002 01  07fd0000 00000000 00000000 00000000

Net:   en0 en1 br0 lo0

Bridg: en0 en1

 

Hit <Enter> to stop autoboot:  0

Loading FLASH image @ 0xbfc40000... not present

Loading FLASH image @ 0xbfc80000...

Verifying checksum...

Booting image...

..............................

 

Aruba Networks

ArubaOS Version 5.0.3.3 (build 28008 / label #28008)

Built by p4build@cyprus on 2011-04-21 at 11:18:07 PDT (gcc version 3.4.3)

BOARD - Muscat

CPU frequency 266.00 MHz

Using 133.000 MHz high precision timer. cycles_per_jiffy=266000

Memory: 25796k/32768k available (1996k kernel code, 6956k reserved, 691k data, 2612k init, 0k highmem)

available.

detected lzma initramfs

initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=13573120

LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> ................................................................................................................................................................................................................

PCI: Initializing PCI

wdt: registered with refresh

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

physmap flash device: 400000 at 1fc00000

AMD Flash AM29LV320D (Top) (Unknown locking)

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

<6>eth0: RC32434 Ethernet at 0x18060000, 00:0b:86:c7:9d:9e, Rx IRQ 40, Tx IRQ 41

natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002

Ethernet port 1 mode: tunnel

Ethernet Channel Bonding Driver: v3.0.1 (January 9, 2006)

bonding: bond0: making interface eth0 the new active one.

bonding: bond0: enslaving eth0 as an active interface with an up link.

WARNING: eth0 is down; using eth1 for uplink

bonding: bond0: enslaving eth1 as a backup interface with a down link.

AP xml model 3, num_radios 2 (jiffies 4831)

init_asap_mod: installation:0

radio 0: band 1 ant 2 max_ssid 16

radio 1: band 0 ant 2 max_ssid 16

ethernet_device_event: dev eth0 is register

ethernet_device_event: dev eth0 is up

asap_gre_init: ADDED GRE protocol c00f132c

setting bond0 as bridge child

setting gre0 as split child

USB not provisioned

Starting watchdog process...

Getting an IP address...

bonding: bond0: link status definitely down for interface eth0, disabling it

bonding: bond0: now running without any active interface !

bonding: bond0: link status definitely up for interface eth1.

bonding: bond0: making interface eth1 the new active one.

10.30.70.148 255.255.255.0 10.30.70.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.

 

The AP does not permit me to hint Enter key to stop the boot process, after that the system just restart once and again and again.

Is there any problem with the AP? Can I reset by other way?

 

Regards.

Guru Elite

Re: AP 70 reset problem

That looks like the AP cannot find the master, and is rebooting as a result.  What are you using for discovery, DNS, DHCP?

 

With regards to the "break", you need to make sure you have no flow control on your terminal program.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: AP 70 reset problem

cjoseph: fisrt of all, thanks a lot for your fast response! for discovering I use DHCP when I ping the AP in the controller CLI I reach the AP very well. I can see it active (just with ping) for a couple of seconds an then the AP reboots again. I mean, I discard a network problem. I tryed with every configuration for the terminal program and always I have the same response. Regards.
Guru Elite

Re: AP 70 reset problem

When I say discovery, do you have the "aruba-master" a-record in DNS pointing to the controller IP address?  Do you have the DHCP option 43 and 60 set?

 

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: AP 70 reset problem

cjoseph The controller is not the DHCP server, we have a DC which performs that steps. But I still do not understand, why I have no response from the AP in the console mode?
Guru Elite

Re: AP 70 reset problem

What terminal program are you using?  Again, you need to make sure that flow control is off.

 

 

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II

Re: AP 70 reset problem

I tryed to connect with both putty and MS Hyper Terminal, the only thing that I do not try is to connect the AP directly to one of the controller FE ports and telnet to the AP. I will probe with this option.
Guru Elite

Re: AP 70 reset problem

Puttiy is what you should be using 100%  just make sure flow control is off.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Aruba Employee

Re: AP 70 reset problem

putty.JPG

Thanks,

Zach Jennings
Aruba Employee

Re: AP 70 reset problem

If you made the breakout cable yourself, likely that's the issue. 

 

Maybe a pin is not terminated or possibly swapped and while you can see the boot sequence, the term is not send the break (return) key stroke.

 

If it's doing this for all 5 AP's it's probably the cable.

 

 

 

 

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