Wireless Access

last person joined: 20 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Problem with AP-105

This thread has been viewed 3 times
  • 1.  Problem with AP-105

    Posted Aug 16, 2012 11:13 AM

    Hello All,

     

    I have a little trouble with the AP-105. The ap-105 can't connect to the main server. I've tried reset and reconfigured with setenv ap-105 many times....

    Looks like AP not resets properly...

     

    apboot> factory_reset
    Clearing state... Checking OS image and flags
    Invalid image format version: 0xffffffff
    Continuing with OS clear
    Erasing flash sector @ 0xbf100000....done
    Erased 1 sectors
    Erasing flash sector @ 0xbff90000....done
    Erased 1 sectors

    Erasing flash sector @ 0xbffd0000....done
    Erased 1 sectors

    done
    Purging environment... Un-Protected 1 sectors
    .done
    Erased 1 sectors
    Writing
    done

    What can be wrong?



  • 2.  RE: Problem with AP-105

    Posted Aug 16, 2012 11:18 AM

    If you keep the console on the AP while it boots, what does it do?  It should log getting a DHCP address and then searching for the controller.  When it fails, copy the console logs and post it.



  • 3.  RE: Problem with AP-105

    Posted Aug 16, 2012 11:37 AM
    How does the AP discover its master controller? Can you post the output of "printenv" command from the apboot.



  • 4.  RE: Problem with AP-105

    Posted Aug 16, 2012 11:42 AM

    Thank for your quick answer!

     

    It is connecting to master server and after one minute restarting again.

    See below

     

    Hit <Enter> to stop autoboot:  0

    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 broadcast 2

    DHCP broadcast 3

    DHCP broadcast 4

    DHCP broadcast 5

     

    Retry count exceeded; starting again

    eth0 up: 1 Gb/s full duplex

    DHCP broadcast 1

    DHCP broadcast 2

    DHCP broadcast 3

    DHCP broadcast 4

    DHCP broadcast 5

    DHCP IP address: X.X.X.15

    DHCP subnet mask: 255.255.255.0

    DHCP def gateway: X.X.X.1

    DHCP DNS server: X.X.2.25

    DHCP DNS domain: XXXX.XXXXXXXXX.com

    ADP multicast 1

    Controller address: X.X.X.254

    Using eth0 device

    TFTP from server X.X.X.254; our IP address is X.X.X.15

    Filename 'mips32.ari'.

    Load address: 0x2000000

    Loading: ######################T ###################################

    done

    Bytes transferred = 3700092 (38757c hex)

     

    Image is signed; verifying checksum... passed

    Signer Cert OK

    Policy Cert OK

    RSA signature verified.

    Automatic boot of image at addr 0x02000000 ...

    ELF file is 32 bit

    Loading .text @ 0x80e00000 (3631224 bytes)

    Loading .data @ 0x81176880 (32 bytes)

    Clearing .bss @ 0x811768a0 (16 bytes)

    ## Starting application at 0x80e00000 ...

    Uncompressing.................................

    þ

    Aruba Networks

    ArubaOS Version 6.1.2.3 (build 30182 / label #30182)

    Built by p4build@corsica on 2011-09-11 at 12:10:31 PDT (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: 123008k/131072k available (1850k kernel code, 7928k reserved, 669k data, 2820k init, 0k highmem)

     available.

    detected lzma initramfs

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

    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... TPM driver running in 3203 mode with 3204S

    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: d8:c7:c8:ce:8e:9f

    ATHRF1: Port 0, Neg Success

    ATHRF1: unit 0 phy addr 0 ATHRF1: reg0 0

    AP xml model 39, num_radios 2 (jiffies 7371)

    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 0x87f42000

    ag7100_ring_alloc Allocated 3024 at 0x804d8000

    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

    x.x.x.15 255.255.255.0 x.x.x.1

    Running ADP...Done. Master is x.x.x.254

    ath_hal: 0.9.17.1 (AR5416, AR9380, 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_spectrum: 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 XXXXXXX, 8 available BSSID(s)

    bond0 address=XXXXXX

    br0 address=XXXXXXX

    wifi0: AP type AP-105, radio 0, max_bssids 8

    wifi0: Atheros 9280: mem=0x10010000, irq=49 hw_base=0xb0010000

    wifi1: Base BSSID XXXXXX, 8 available BSSID(s)

    bond0 address=XXXXXX

    br0 address=XXXXX

    wifi1: AP type AP-105, radio 1, max_bssids 8

    wifi1: Atheros 9280: mem=0x10000000, irq=48 hw_base=0xb0000000

     

    Starting FIPS KAT ... Completed FIPS KAT

     

    AP rebooted Fri Dec 31 16:04:37 PST 1999; 'reboot' command executed with no reason given (called from ).

    shutting down watchdog process (nanny will restart it)...

     

            <<<<<       Welcome to the Access Point     >>>>>

     

    ~ #

    The system is going down NOW !!

    Sending SIGTERM to all processes.

    Please stand by while rebooting the system.

    Restarting system.

     



  • 5.  RE: Problem with AP-105

    Posted Aug 16, 2012 11:59 AM

    From the logs, it says "reboot" command executed which I am assuming you restarted it to get this output, but when it automatically reboots, what is the reason for the reboot when it comes back up.

    Also, can you enable AP debug logging on the controller to get more information on what is happening for that 1 minute when it connects to the master controller.
    config terminal
    logging level debugging ap-debug <ap-name>

    show log ap-debug 



  • 6.  RE: Problem with AP-105

    Posted Aug 16, 2012 04:17 PM

    Ok, I found the reason why ap-105 restarting

     

    AP rebooted Fri Dec 31 16:19:40 PST 1999; Unable to set up IPSec tunnel after 360 tries
    shutting down watchdog process (nanny will restart it)...



    Is it possible to copied setting from ap-105 unit which is working fine?



  • 7.  RE: Problem with AP-105

    Posted Aug 16, 2012 04:39 PM
    Are you trying to provision the AP-105 as a remote AP? or do you have cpsec enabled on the controller?

    Can you post the output of "show log ap-debug all" and attach it to your post.

    Thanks,