Controllerless Networks

 View Only
last person joined: yesterday 

Aruba Instant Wi-Fi: Meet the controllerless Wi-Fi solution that's easy to set-up, is loaded with security and smarts, and won't break your budget.
Expand all | Collapse all

Compatibility 303 and 365

This thread has been viewed 60 times
  • 1.  Compatibility 303 and 365

    Posted 15 days ago

    Hey all,

       I have 3 303 indoor APs in an IAP cluster and a 'new' 365 I need to put outside (they are all used APs that I have factory reset). I've got them all on the most current 8.11.0.1_85785 firmware, but I can't get the 365 to join the 303 cluster. Before I post more details I just want to make sure these models are compatible.

    Should they be able to be in the same cluster?

    What's strange is that when I go to the 365 IP, it redirects to the cluster master, but it doesn't show in the cluster and doesn't have the shared config if I ssh to it.

    I have confirmed they all have different IPs from DHCP reservations.

    Mike



  • 2.  RE: Compatibility 303 and 365

    MVP GURU
    Posted 15 days ago

    If they can run the same version of OS, then they can cluster. Have you tried to factory reset the outdoor AP. Make sure its in the same VLAN as the other APs when its booting back up for the first time.



    ------------------------------
    Dustin Burns

    Lead Mobility Engineer @Worldcom Exchange, Inc.

    ACCX 1271| ACMX 509| ACSP | ACDA | MVP Guru 2022-2023
    If my post was useful accept solution and/or give kudos
    ------------------------------



  • 3.  RE: Compatibility 303 and 365

    Posted 14 days ago

    I have done a factory reset, but I will try again and post results.

    Are there any settings that aren't cleared on a factory reset?

    Mike




  • 4.  RE: Compatibility 303 and 365

    Posted 14 days ago

    Below is console output from the AP. The web gui redirects to the current cluster master, but doesn't load on the AP IP and SSH is not connecting. Confirmed the switch port and vlan config is the same for each AP.

    The console output continues with !!! Init ---> Member

    passed
    SHA2 Signature available
    Signer Cert OK
    Policy Cert OK
    RSA signature verified using SHA2.
    Uncompressing Kernel Image ... OK
    [    0.000000]
    [    0.000000] Aruba Networks
    [    0.000000] ArubaOS Version 8.11.0.1-8.11.0.1 (build 85785 / label #85785)
    [    0.000000] Built by jenkins@pr-hpn-cd-build39 on 2022-12-15 at 00:23:12 PST (gcc version 4.6.3)
    [    0.000000]
    [    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
    [    0.016603] SMP: Total of 4 processors activated (384.00 BogoMIPS).
    [    0.052328] i2c-gpio driver registered
    [   17.139916] 3 ofpart partitions found on MTD device 7980000.qcom,nand
    [   17.206804] Creating 3 MTD partitions on "7980000.qcom,nand":
    [   17.275552] 0x000000000000-0x000002000000 : "aos0"
    [   17.375316] 0x000002000000-0x000004000000 : "aos1"
    [   17.462578] 0x000004000000-0x000008000000 : "ubifs"
    [   17.599380] m25p80 spi0.0: found w25q32, expected n25q128a11
    [   17.694828] Found AT97SC3203 on MSM-I2C-v2-adapter
    [   17.750458] Key type dns_resolver registered
    [   17.790786] Registering SWP/SWPB emulation handler
    [   19.134046] There is no gpio reset info
    [   19.230129]
    Starting Kernel SHA1 KAT ...
    [   19.264607] Completed Kernel SHA1 KAT
    [   19.311452] Starting Kernel HMAC-SHA1 KAT ...
    [   19.361662] Starting Kernel DES KAT ...[   19.407340] Completed Kernel DES KAT
    [   19.451145] Starting Kernel AES KAT ...
    [   19.494856] Completed Kernel AES KAT
    [   19.494856]
    [   19.558373] Starting Kernel AESGCM KAT ...
    [   19.605197] Completed Kernel AESGCM KAT
    [   19.654448] Completed Kernel HMAC-SHA1 KAT
    Thu Jan  1 00:00:00 PST 1970
    Populate AP type info
    Domain Name: SetMeUp.arubanetworks.com
    Current OEM Name : Aruba Networks
    Disabling ipv6 for devices by default
    AP-type has_ble_support: ONBOARD.
    IPv6 capability is supported for devices
    No panic info available
    Enabling ble_daemon and ble_relay via nanny
    glenmorangie: Start hotplug
    per-ap-setting not in backup and restore mode, Backup ENV.
    Installing glenmorangie ethernet driver
    [   32.907238] edma module_init
    Enter non-FIPS mode
    Cfg len is 965
    no SSID detected...
    uap controller less detected
    Mesh enabled
    single uplink platform
    Starting watchdog process...
    Aruba watchdog daemon started [4 thread(s)]
    Loading configuration file of length 965...
    wifi uplink not present...
    No valid ssid was found...
    extended ssid activate due to no valid ssid ...
    touching file /tmp/ip_mode_0
    [   38.995344] bond0: GMAC Link is up with phy_speed=1000
    error in reading source file
    Mesh is DISABLED on this device.
    extended ssid is activated on the platform ...
    copying bootuplog ...
    [   39.830652] uol: module license 'Proprietary' taints kernel.
    [   39.894652] Disabling lock debugging due to kernel taint
    [   39.959687] uol_init_driver:434 HW offload not applicable, AP will use cutting through path!
    allow PAPI
    set device anul0 mtu to 2000
    notify asap_mod 3g no present...
    Starting update SBL1 ...
    SBL1 was updated already
    Done.
    apdot1x authentication is not enabled
    LLDP not sent yet, DHCP is waiting
    LLDP not sent yet, DHCP is waiting
    LLDP not sent yet, DHCP is waiting
    Starting DHCP
    Getting an IP address...
    Jan  1 00:00:24 udhcpc[4225]: udhcpc (v0.9.9-pre) started
    Jan  1 00:00:24 udhcpc[4225]: send_discover: pkt num 0, secs 0
    Jan  1 00:00:24 udhcpc[4225]: Sending discover...
    Jan  1 00:00:24 udhcpc[4225]: send_selecting: pkt num 0, secs 0
    Jan  1 00:00:24 udhcpc[4225]: Sending select for 192.168.1.180...
    Jan  1 00:00:24 udhcpc[4225]: Lease of 192.168.1.180 obtained, lease time 60000000
    [   45.152063] ip_time_handler: Got ip and packets on bond0 Started conductor election 3-0, rand 21
    [   45.970221] (08:00:26) !!! Init ---> Member
    192.168.1.180 255.255.255.0 192.168.1.200
    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
    Put ntpdate to the nannylist.
    AP rebooted caused by cold HW reset(power loss)
    shutting down watchdog process (nanny will restart it)...

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

    Completed SW FIPS KAT test
    Power supply mode is POE:, USB Modem is not present.
    User: [   77.002024] Starting Kernel HMAC SHA1 FIPS KAT ...
    [   77.044816] Completed Kernel HMAC SHA1 FIPS KAT
    [   79.008029] Starting Kernel HMAC SHA256 FIPS KAT ...
    [   79.052918] Completed Kernel HMAC SHA256 FIPS KAT
    ble_ready NOT present @init ....
    [   81.008056] Starting Kernel HMAC SHA384 FIPS KAT ...
    [   81.052974] Completed Kernel HMAC SHA384 FIPS KAT
    [   83.008039] Starting Kernel HMAC SHA512 FIPS KAT ...
    [   83.052943] Completed Kernel HMAC SHA512 FIPS KAT
    Firmware AES-CCM Known Answer Test Passed
    [  104.703446] asap_send_elected_conductor: sent successfully
    [  104.970390] asap_send_elected_conductor: sent successfully
    [  106.970351] (15:07:08) !!! Init ---> Member
    [  107.970332] (15:07:09) !!! Init ---> Member
    [  108.970358] (15:07:10) !!! Init ---> Member
    [  109.970363] (15:07:11) !!! Init ---> Member
    [  110.970387] (15:07:12) !!! Init ---> Member
    [  111.970364] (15:07:13) !!! Init ---> Member
    [  112.970348] (15:07:14) !!! Init ---> Member
    [  113.970374] (15:07:15) !!! Init ---> Member
    [  114.970373] (15:07:16) !!! Init ---> Member
    [  115.970369] (15:07:17) !!! Init ---> Member
    [  116.970406] (15:07:18) !!! Init ---> Member
    [  117.970381] (15:07:19) !!! Init ---> Member
    [  118.970384] (15:07:20) !!! Init ---> Member
    [  119.970390] (15:07:21) !!! Init ---> Member
    [  120.970396] (15:07:22) !!! Init ---> Member
    [  121.970395] (15:07:23) !!! Init ---> Member
    [  122.970393] (15:07:24) !!! Init ---> Member
    [  123.970402] (15:07:25) !!! Init ---> Member
    [  124.970402] (15:07:26) !!! Init ---> Member
    [  125.970406] (15:07:27) !!! Init ---> Member
    [  126.970413] (15:07:28) !!! Init ---> Member
    [  127.970410] (15:07:29) !!! Init ---> Member
    [  128.970422] (15:07:30) !!! Init ---> Member
    [  129.970407] (15:07:31) !!! Init ---> Member




  • 5.  RE: Compatibility 303 and 365

    Posted 14 days ago

    I've done another factory reset and the AP is up now and I can login to the GUI and SSH, but it's still not joining the 303 cluster, so it's just a standalone AP right now.