Wireless Access

last person joined: 13 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

AP won't join Controller

This thread has been viewed 9 times
  • 1.  AP won't join Controller

    EMPLOYEE
    Posted Feb 08, 2016 04:07 AM

    Hi Guys,

     

    I'm testing a simple setup, AP and Controller in same L2 VLAN connected via a HPE switch.

    I tried DHCP/DNS methods, and then the static method, but in all cases AP just doesn't join the Controller.

     

    AP has image: ArubaOS Version 6.4.2.6-4.1.1.6   ; IP 172.16.0.103/24

    Controller : Model: Aruba7005, Version: 6.4.2.3  ; IP 172.16.0.253/24 for loopback, .254/24 on interface ; Loopback used as Controller IP.

     

     

    Any suggestions to fix the issue ? One of the line in the log says "Image Sync failed", so do i have to upgrade/downgrade image on AP manually ?

     

    Relevant Logs:

     

     

    apboot> printenv 
    bootdelay=2
    baudrate=9600
    autoload=n
    boardname=Ardmore
    servername=aruba-master
    bootcmd=boot ap
    autostart=yes
    bootfile=e500.ari
    ethaddr=40:e3:d6:c3:e1:6e
    ipaddr=172.16.0.103
    netmask=255.255.255.0
    gatewayip=172.16.0.254
    dnsip=172.16.0.254
    domainname=ARUBA-POC.LOCAL
    ethact=eth0
    master=172.16.0.253
    serverip=172.16.0.253
    stdin=serial
    stdout=serial
    stderr=serial
    
    Environment size: 359/131068 bytes
    apboot> 
    apboot> 
    apboot> boot
    Checking image @ 0xee000000
    Copying image from 0xee000000
    
    Image is signed; verifying checksum... passed
    Signer Cert OK
    Policy Cert OK
    RSA signature verified. 
    [    0.000000] Flash variant: default
    [    0.000000] 
    [    0.000000] Aruba Networks
    [    0.000000] ArubaOS Version 6.4.2.6-4.1.1.6 (build 50009 / label #50009) 
    [    0.000000] Built by p4build@tortuga on 2015-05-12 at 10:54:20 PDT (gcc version 4.5.1)
    [    0.000000] 
    [    0.000000] Memory: 506148k/524288k available (12480k kernel code, 18140k reserved, 504k data, 456k bss, 9040k init)
    [    0.002950] Processor 1 found.
    [    0.156865] Brought up 2 CPUs
    [    0.233377] PCI: Probing PCI hardware
    [    0.276103] PCI: Resetting PCI bus
    [    0.477124] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
    [    0.539368] pci 0001:02:00.0: PCI bridge to [bus 03-ff]
    [    0.601650] pci 0000:01:00.0: BAR 2: assigned [mem 0x80000000-0x801fffff 64bit]
    [    0.688633] pci 0000:01:00.0: BAR 2: set to [mem 0x80000000-0x801fffff 64bit] (PCI address [0x80000000-0x801fffff]
    [    0.812542] pci 0000:01:00.0: BAR 0: assigned [mem 0x80200000-0x80207fff 64bit]
    [    0.900039] pci 0000:01:00.0: BAR 0: set to [mem 0x80200000-0x80207fff 64bit] (PCI address [0x80200000-0x80207fff]
    [    1.023992] pci 0000:00:00.0: enabling device (0106 -> 0107)
    [    1.091694] pci 0001:03:00.0: BAR 2: assigned [mem 0xa0000000-0xa01fffff 64bit]
    [    1.179189] pci 0001:03:00.0: BAR 2: set to [mem 0xa0000000-0xa01fffff 64bit] (PCI address [0xa0000000-0xa01fffff]
    [    1.303134] pci 0001:03:00.0: BAR 0: assigned [mem 0xa0200000-0xa0207fff 64bit]
    [    1.390632] pci 0001:03:00.0: BAR 0: set to [mem 0xa0200000-0xa0207fff 64bit] (PCI address [0xa0200000-0xa0207fff]
    [    1.514584] pci 0001:02:00.0: enabling device (0106 -> 0107)
    [    7.716868] Kprobe smoke test started
    [    7.793519] Kprobe smoke test passed successfully
    [    7.964637] ee000000.nor: Found 1 x16 devices at 0x0 in 16-bit bank
    [    8.039679] Amd/Fujitsu Extended Query Table at 0x0040
    [    8.101201] number of CFI chips: 1
    [    8.145954] fsl-gianfar ethernet.2: enabled errata workarounds, flags: 0x4
    [    8.228740] /proc/gfar_eth0_stats created 
    [    8.279004] fsl-gianfar ethernet.3: enabled errata workarounds, flags: 0x4
    [    8.361774] /proc/gfar_eth1_stats created 
    [    8.426021] Enabling watchdog on CPU 1
    [    8.426029] Enabling watchdog on CPU 0
    [    8.522579] 
    [    8.522583] Starting Kernel SHA1 KAT ...Starting Kernel HMAC SHA1 FIPS KAT ...Completed Kernel HMAC SHA1 FIPS KAT 
    [    8.534624] Starting Kernel HMAC SHA256 FIPS KAT ...Completed Kernel HMAC SHA256 FIPS KAT 
    [    8.535627] Starting Kernel HMAC SHA384 FIPS KAT ...Completed Kernel HMAC SHA384 FIPS KAT 
    [    8.536062] Starting Kernel HMAC SHA512 FIPS KAT ...Completed Kernel HMAC SHA512 FIPS KAT 
    [    8.536494] Starting Kernel AES-CBC FIPS KAT ...Completed Kernel AES-CBC FIPS KAT 
    [    8.598698] Starting Kernel AES-CCM FIPS KAT ...Completed Kernel AES-CCM FIPS KAT 
    [    8.599172] Starting Kernel 3DES-CBC FIPS KAT ...Completed Kernel 3DES-CBC FIPS KAT 
    [    9.235212] Completed Kernel SHA1 KAT 
    [    9.280030] Starting Kernel HMAC-SHA1 KAT ...Completed Kernel HMAC-SHA1 KAT 
    [    9.368287] Starting Kernel DES KAT ...Completed Kernel DES KAT 
    [    9.440239] Starting Kernel AES KAT ...Completed Kernel AES KAT 
    [    9.484038] 
    Domain Name: instant.arubanetworks.com
    No panic info available
    Backup ENV.
    [   15.050781] p1020_soc: P1020 Misc Utils Driver version 1
    Ethernet port 1 mode: active-standby
    [   15.331825] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   15.397631] ADDRCONF(NETDEV_UP): bond0: link is not ready
    [   15.483281] bonding: bond0: enslaving eth0 as a backup interface with a down link.
    [   15.590170] ADDRCONF(NETDEV_UP): eth1: link is not ready
    [   15.675125] bonding: bond0: enslaving eth1 as a backup interface with a down link.
    Cfg len is 0
    Configuration file is empty, turning on default services...
    extended ssid activate due to no AP config ...
    [   18.867792] PHY: eth0 (mdio@ffe24000:00) - Link is Up - 1000/Full
    [   19.111516] bonding: bond0: link status definitely up for interface eth0.
    [   19.192800] bonding: bond0: making interface eth0 the new active one.
    [   19.269948] bonding: bond0: first active interface up!
    [   19.331542] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
    [   19.721192] Enabling eth1 due to power change [power profile 1]
    Mesh is DISABLED on this device.
    Disabling wpa_supplicant for this paltform
    [   21.899461] AP xml model 66, num_radios 2 (jiffies 10299)
    [   21.964124] init_asap_mod: installation:0
    [   22.012062] radio 0: band 1 ant 0 max_ssid 16
    [   22.064187] radio 1: band 0 ant 0 max_ssid 16
    [   22.116343] election init: rand=17 HZ=500
    [   22.164298] IAP client match init
    [   22.203972] ethernet_device_event: dev eth0 is up
    [   22.260250] ethernet_device_event: dev eth1 is up
    notify asap_mod 3g no present...
    Starting watchdog process...
    Got all network params from APboot env. Skipping DHCP
    Static IP[   22.507485] bonding: bond0: releasing backup interface eth1
     detected. Checking if LACP need[   22.608973] ethernet_device_event: dev eth1 is down
    s to be configur[   22.683436] ADDRCONF(NETDEV_UP): eth1: link is not ready
    ed
    LACP setting[   22.756536] ethernet_device_event: dev eth1 is up
     not required. AP can ping default gateway
    172.16.0.103 255.255.255.0 172.16.0.254
    Compressing all files in the /etc/httpd directory...
    Done.
    Starting Webserver
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    bind: Transport endpoint is not connected
    Launching NTP Client on pool.ntp.org
    [   27.039727] wl 0000:01:00.0: enabling device (0000 -> 0002)
    [   27.133956] wifi0: AP type AP-225, radio 0, max_bssids 16
    [   27.199521] ip_time_handler: Got ip and packets on bond0 Started master election 8-0, rand 16
    [   27.480883] wl 0001:03:00.0: enabling device (0000 -> 0002)
    [   27.779088] wifi1: AP type AP-225, radio 1, max_bssids 16
    [   28.044444] Adding bridge entry for magic vlan GW, ifindex 8453, 00:0b:86:f5:d6:4e
    [   28.135107] (00:00:26) !!! Init ---> Slave
    Clearing P1020 PCIe Error Status
    AP rebooted Thu Jan 1 00:05:58 UTC 1970; CLI cmd at uptime 0D 0H 5M 58S: reload
    shutting down watchdog process (nanny will restart it)...
    Completed SW FIPS KAT test
     
            <<<<<       Welcome to the Access Point     >>>>>
     
    User: 

     



  • 2.  RE: AP won't join Controller
    Best Answer

    Posted Feb 08, 2016 04:50 AM
    From the logs its looking like you are trying to associate an IAP to
    the controller.
    You cant associate an IAP with controller, you have a use an AP.


  • 3.  RE: AP won't join Controller

    EMPLOYEE
    Posted Feb 08, 2016 05:53 AM
    What model is the AP? 

    Sent from Nine


  • 4.  RE: AP won't join Controller

    EMPLOYEE
    Posted Feb 08, 2016 06:00 AM

    It says it is an IAP-225 in the bootup.  "Ardmore" is also the internal code name for an AP224/225 hardware.