Wireless Access

last person joined: 2 hours ago 

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

Controller can't see an AP 61

Jump to Best Answer
  • 1.  Controller can't see an AP 61

    Posted Jun 14, 2012 06:54 PM

    We have one Aruba3400 controller (running  at our main site with AP 61s at 6 other sites connecting back to it.  I'm trying to set up an AP 61 at a new site connected back to the main site over a static VPN connection.  I provisioned the AP at the main site and when I take it over to the remote site the controller doesn't detect it.  The 2 lights on the left of the controller are bright but the one on the right stays dim green.  The AP pulls an IP address and I can ping it from the network the controller is on.  I have the serial breakout cable to connect to the AP if needed.  This is not a remote AP, the site is on a static VPN.  Thanks in advance for any ideas.

  • 2.  RE: Controller can't see an AP 61

    Posted Jun 14, 2012 07:21 PM

    What is the output of the command 


    show datapath session table <ap-ip-address> 



  • 3.  RE: Controller can't see an AP 61

    Posted Jun 15, 2012 02:28 AM

    If the AP tunnel connection to the controller is traversing a VPN, try reducing the MTU in the AP system profile. If that helps, you've got an MTU problem down that VPN! You might have to tune the setting.


    ap system-profile "WHATEVER YOURS IS"

    mtu 1400

  • 4.  RE: Controller can't see an AP 61

    Posted Jun 19, 2012 11:30 AM

    Thanks for the replies.

    I can only get an apboot> prompt after hitting enter to stop autoboot.  Here is the output when it boots.  Is that SIGKILL something to note?  It just cycles like this:


    Verifying checksum...
    Booting image...

    Aruba Networks
    ArubaOS Version (build 21169 / label #21169)
    Built by p4build@trinidad.arubanetworks.com on 2009-04-21 at 18:06:55 PDT (gcc version 3.4.3)
    BOARD - Merlot
    CPU frequency 180.00 MHz
    Using 90.000 MHz high precision timer. cycles_per_jiffy=180000
    Memory: 27036k/32768k available (1836k kernel code, 5716k reserved, 416k data, 1992k init, 0k highmem)
    detected lzma initramfs
    initramfs: LZMA lc=3,lp=0,pb=2,dictSize=8388608,origSize=10224640
    LZMA initramfs by Ming-Ching Tiew <mctiew@yahoo.com> .............................................................................................................................................................
    wdt: registered with refresh
    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
    bond0: Atheros AR2313: 00:0b:86:cb:26:d8, irq 4
    AP xml model 5, num_radios 1 (jiffies 7129)
    radio 0: band 2 ant 0 max_ssid 16
    ath_hal: module license 'Proprietary' taints kernel.
    ath_hal: (AR5212, AR5312, RF5111, RF5112, RF2413, RF5413)
    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: (Atheros/multi-bss)
    wifi0: Base BSSID 00:0b:86:32:6d:80, 16 available BSSID(s)
    wifi0: AP type AP-61, radio 0, max_bssids 16
    wifi0: Atheros 2313 WiSoC: mem=0xb8500000, irq=5
    net.aruba_asap.br_init = 1
    Getting an IP address...
    Running ADP...
    Done. Master is
    Sending SIGKILL to all processes.
    Please stand by while rebooting the system.
    Restarting system.

    APBoot 1.5.5 (build taylor@harpua-ENG.0000)
    Built: 2006-02-24 18:29:36 (with gcc 3.3.1)

    CPU:   AR2313 MIPS-32 at 180 MHz: 16 kB I-Cache 16 kB D-Cache
    Board: Merlot, Local Bus at 90 MHz
    DRAM:  32 MB
    POST:  passed
    FLASH: 4 MB
    Net:   en0 lo0

    Hit <Enter> to stop autoboot:  0
    Loading FLASH image @ 0xbfc40000... not present
    Loading FLASH image @ 0xbfc80000...
    Verifying checksum...
    Booting image...

  • 5.  RE: Controller can't see an AP 61

    Posted Jun 19, 2012 11:40 AM

    AP is unable to find its Master IP address and hence it reboots. 

    Done. Master is


    Which of the following methods does the AP use to find out the master controller? 


    1. DHCP 

    2. ADP

    3. DNS  (by default it looks for "aruba-master")


  • 6.  RE: Controller can't see an AP 61

    Posted Jun 19, 2012 11:44 AM

    I'm not sure which method but I saw in another post on a similar topic that they said to put in the command aruba-master <ip-address> to point it at the controller.  I just can't get to a prompt that lets me have those commands.  I guess I could bring the AP back to a main site where it does get detected by the controller and then use the breakout cable to connect to it and set the aruba-master to the controller's IP address.  I'm just not sure of the syntax.

  • 7.  RE: Controller can't see an AP 61
    Best Answer

    Posted Jun 19, 2012 11:56 AM
      |   view attached



    try this in case of dns:


    apboot> setenv servername <Wireless LAN switch host name>


    or this in case of direct ip:


    apboot> setenv serverip <Wireless LAN switch IP address>

    apboot> setenv master <Wireless LAN switch IP address>


    apboot> save
    apboot> boot


    i think its:


    apboot> printenv


    to show the current configuration.




  • 8.  RE: Controller can't see an AP 61

    Posted Jul 05, 2012 11:20 AM

    It worked when I set the aruba master IP address.  Thanks to all of you for your help.